public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Nicolas Ojeda Leon <ncoleon@amazon.com>
Cc: devel@edk2.groups.io, atugup@amazon.com, Alexander Graf <graf@amazon.de>
Subject: Re: [PATCH v3 3/8] Ovmf/HardwareInfoLib: Add Dxe lib to dynamically parse heterogenous data
Date: Fri, 28 Jan 2022 11:36:41 +0100	[thread overview]
Message-ID: <20220128103641.jejqmktql3nxbobu@sirius.home.kraxel.org> (raw)
In-Reply-To: <e21fb78d1f4ac10be90b377de94f4c248cf2db04.1643120206.git.ncoleon@amazon.com>

On Tue, Jan 25, 2022 at 03:30:10PM +0100, Nicolas Ojeda Leon wrote:
> Following the Hardware Info library, create the DxeHardwareInfoLib
> which implements the whole API capable of parsing heterogeneous hardware
> information. The list-like API grants callers a flexible and common
> pattern to retrieve the data. Moreover, the initial source is a BLOB
> which generalizes the host-to-guest transmission mechanism.
> 
> The Hardware Info library main objective is to provide a way to
> describe non-discoverable hardware so that the host can share the
> available resources with the guest in Ovmf platforms. This change
> features and embraces the main idea behind the library by providing
> an API that parses a BLOB into a linked list to retrieve hardware
> data from any source. Additionally, list-like APIs are provided so
> that the hardware info list can be traversed conveniently.
> Similarly, the capability is provided to filter results by specific
> hardware types. However, heterogeneous elements can be added to the
> list, increasing the flexibility. This way, a single source, for
> example a fw-cfg file, can be used to describe several instances of
> multiple types of hardware.
> 
> This part of the Hardware Info library makes use of dynamic memory
> and is intended for stages in which memory services are available.
> A motivation example is the PciHostBridgeLib. This library, part
> of the PCI driver populates the list of PCI root bridges during DXE
> stage for future steps to discover the resources under them. The
> hardware info library can be used to obtain the detailed description
> of available host bridges, for instance in the form of a fw-cfg file,
> and parse that information into a dynmaic list that allows, first to
> verify consistency of the data, and second discover the resources
> availabe for each root bridge.
> 
> Cc: Alexander Graf <graf@amazon.de>
> Cc: Gerd Hoffmann <kraxel@redhat.com>
> 
> Signed-off-by: Nicolas Ojeda Leon <ncoleon@amazon.com>

Acked-by: Gerd Hoffmann <kraxel@redhat.com>


  reply	other threads:[~2022-01-28 10:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 14:30 [PATCH v3 0/8] Handling of multiple PCI host bridges specified Ojeda Leon, Nicolas
2022-01-25 14:30 ` [PATCH v3 1/8] OvmfPkg/Library: Create base HardwareInfoLib for PCI Host Bridges Ojeda Leon, Nicolas
2022-01-28 10:36   ` Gerd Hoffmann
2022-01-25 14:30 ` [PATCH v3 2/8] Ovmf/HardwareInfoLib: Create Pei lib to parse directly from fw-cfg Ojeda Leon, Nicolas
2022-01-28 10:36   ` Gerd Hoffmann
2022-01-25 14:30 ` [PATCH v3 3/8] Ovmf/HardwareInfoLib: Add Dxe lib to dynamically parse heterogenous data Ojeda Leon, Nicolas
2022-01-28 10:36   ` Gerd Hoffmann [this message]
2022-01-25 14:30 ` [PATCH v3 4/8] Ovmf/PlatformPei: Use host-provided GPA end if available Ojeda Leon, Nicolas
2022-01-28 10:37   ` Gerd Hoffmann
2022-01-25 14:35 ` [PATCH v3 5/8] OvmfPkg/PciHostBridgeUtilityLib: Initialize RootBridges apertures with spec Ojeda Leon, Nicolas
2022-01-28 10:41   ` [edk2-devel] " Gerd Hoffmann
2022-01-25 14:36 ` [PATCH v3 6/8] MdeModulePkg, OvmfPkg: Add Pcd token for PCI pre-populated BARs Ojeda Leon, Nicolas
2022-01-25 14:37 ` [PATCH v3 7/8] MdeModulePkg/Pci MdePkg: Create service to retrieve PCI base addresses Ojeda Leon, Nicolas
2022-01-28 10:52   ` [edk2-devel] " Gerd Hoffmann
2022-01-29  1:44     ` 回复: " gaoliming
2022-01-25 14:38 ` [PATCH v3 8/8] MdeModulePkg/PciBusDxe: Handling of pre-populated PCI BARs Ojeda Leon, Nicolas

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=20220128103641.jejqmktql3nxbobu@sirius.home.kraxel.org \
    --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