public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Jeff Westfahl <jeff.westfahl@ni.com>
To: <edk2-devel@lists.01.org>
Cc: Jeff Westfahl <jeff.westfahl@ni.com>,
	Ruiyu Ni <ruiyu.ni@intel.com>,
	"Jaben Carsey" <jaben.carsey@intel.com>
Subject: [PATCH 0/3] ShellPkg/HandleParsingLib: Show LoadedImageProtocol info
Date: Thu, 4 May 2017 16:53:01 -0500	[thread overview]
Message-ID: <1493934784-30012-1-git-send-email-jeff.westfahl@ni.com> (raw)

In the old shell, 'dh -v' showed some useful information about the file path
associated with a LoadedImageProtocol that is no longer shown in the modern
shell.

For example, with the old shell:

    Handle D3 (3A552218)
    Image (3A54C918)   File:MicrocodeUpdate
        ParentHandle..: 3A666398
        SystemTable...: 3D2A8F18
        DeviceHandle..: 3B1C8098
        FilePath......: FvFile(F3331DE6-4A55-44E4-B767-7453F7A1A021)
        ImageBase.....: 3D650000 - 3D655540
        ImageSize.....: 5540
        CodeType......: RT_code   
        DataType......: RT_data   

compared to the new shell:

    D3: 3A552218
    LoadedImage
        Revision......: 0x00001000
        ParentHandle..: 3A666398
        SystemTable...: 3D2A8F18
        DeviceHandle..: 3B1C8098
        FilePath......: 3A552298
        OptionsSize...: 0
        LoadOptions...: 0
        ImageBase.....: 3D650000
        ImageSize.....: 5540
        CodeType......: EfiRuntimeServicesCode
        DataType......: EfiRuntimeServicesData
        Unload........: 0

Here is the output for the same handle with this series applied:

    D3: 3A552218
    LoadedImage
        Name..........: MicrocodeUpdate
        Revision......: 0x00001000
        ParentHandle..: 3A666398
        SystemTable...: 3D2A8F18
        DeviceHandle..: 3B1C8098
        FilePath......: FvFile(F3331DE6-4A55-44E4-B767-7453F7A1A021)
        OptionsSize...: 0
        LoadOptions...: 0
        ImageBase.....: 3D650000
        ImageSize.....: 5540
        CodeType......: EfiRuntimeServicesCode
        DataType......: EfiRuntimeServicesData
        Unload........: 0

Cc: Ruiyu Ni <ruiyu.ni@intel.com>
Cc: Jaben Carsey <jaben.carsey@intel.com>

Jeff Westfahl (3):
  ShellPkg/HandleParsingLib: Show LoadedImageProtocol file path as text
  ShellPkg/HandleParsingLib: Open LoadedImageProtocol first
  ShellPkg/HandleParsingLib: Show LoadedImageProtocol file name

 .../UefiHandleParsingLib/UefiHandleParsingLib.c    | 111 +++++++++++++++++++--
 .../UefiHandleParsingLib/UefiHandleParsingLib.uni  |   4 +-
 2 files changed, 104 insertions(+), 11 deletions(-)

-- 
2.7.4



             reply	other threads:[~2017-05-04 21:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04 21:53 Jeff Westfahl [this message]
2017-05-04 21:53 ` [PATCH 1/3] ShellPkg/HandleParsingLib: Show LoadedImageProtocol file path as text Jeff Westfahl
2017-05-04 21:53 ` [PATCH 2/3] ShellPkg/HandleParsingLib: Open LoadedImageProtocol first Jeff Westfahl
2017-05-04 21:53 ` [PATCH 3/3] ShellPkg/HandleParsingLib: Show LoadedImageProtocol file name Jeff Westfahl
2017-05-05  2:59 ` [PATCH 0/3] ShellPkg/HandleParsingLib: Show LoadedImageProtocol info Ni, Ruiyu
2017-05-05 12:25   ` Jeff Westfahl
2017-05-05 15:49     ` Carsey, Jaben

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1493934784-30012-1-git-send-email-jeff.westfahl@ni.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox