From: Keir Fraser <keir.xen@gmail.com>
To: Ross Philipson <Ross.Philipson@citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Tim Deegan <tim@xen.org>, Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH 00/07] HVM firmware passthrough
Date: Mon, 19 Mar 2012 23:44:58 +0000 [thread overview]
Message-ID: <CB8D757A.2EB53%keir.xen@gmail.com> (raw)
In-Reply-To: <831D55AF5A11D64C9B4B43F59EEBF720724FB1BAA8@FTLPMAILBOX02.citrite.net>
On 19/03/2012 22:04, "Ross Philipson" <Ross.Philipson@citrix.com> wrote:
> This patch series introduces support of loading HVMLOADER extension modules
> into a guest. These modules can contain firmware information that is used
> by HVMLOADER to modify a guests virtual firmware at startup. These modules
> are only used by HVMLOADER.
There has been agreement, and work mainly by Tim, to get rid of our existing
hvm_info_table structure. This is similar in some ways, communicating
between builder and hvmloader via guest memory, but on major steroids.
Actually it looks like this also whacks some parameters through xenstore as
well (which is the newer way that Tim had been adding). So is this some
kludgy combination of old and new?
Would like feedback at least from Tim.
-- Keir
> The HVM module framework is generic allowing it to load any number of
> modules irrespective of the contents. The domain building code in libxenguest
> reads the modules and loads them into the new guest. The loading is done in
> what will become the guests low RAM area just behind to load location for
> HVMLOADER. A header structure is constructed which locates the module set
> and this header's base GPA is passed to the HVMLOADER in the ECX:EDX
> registers. The early entry code in HVMLOADER fetches these values and
> initializes module support.
>
> Currently two types of firmware information are recognized and processed
> in the HVMLOADER though this could be extended.
> 1. SMBIOS: The SMBIOS table building code will attempt to retrieve a
> predefined set of tables it allows to be overridden by passed through
> tables. If a match is found the passed in table will be used. In addition
> the SMBIOS code will also enumerate and process as many vendor defined
> tables (in the range of types 128 - 255) as are passed in.
> 2. ACPI: Static and code (SSDTs) tables can be added to the set of ACPI
> table built by HVMLOADER. The ACPI builder code will enumerate passed in
> tables and add them at the end of the secondary table list.
>
> There are 7 patches in the series:
> 01 - Add public HVM definitions header for firmware module passthrough
> support.
> 02 - Add module processing support in HVMLOADER.
> 03 - Fetch module set base address and initialize module support.
> 04 - Pass through support for SMBIOS.
> 05 - Pass through support for ACPI.
> 06 - Module file reading utility.
> 07 - Xen control tools support for loading the firmware modules.
>
> Signed-off-by: Ross Philipson <ross.philipson@citrix.com>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-03-19 23:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 22:04 [PATCH 00/07] HVM firmware passthrough Ross Philipson
2012-03-19 23:44 ` Keir Fraser [this message]
2012-03-19 23:58 ` Ross Philipson
2012-03-20 9:24 ` Tim Deegan
2012-03-22 11:26 ` Tim Deegan
2012-03-22 14:03 ` Ross Philipson
2012-04-04 9:30 ` Ian Campbell
2012-04-04 19:25 ` Ross Philipson
2012-04-05 10:08 ` Ian Campbell
2012-04-05 20:06 ` Ross Philipson
2012-04-10 14:21 ` Ian Campbell
2012-04-10 15:28 ` Ross Philipson
2012-04-10 15:39 ` Ian Campbell
2012-04-10 19:04 ` Ross Philipson
2012-04-11 8:44 ` Ian Campbell
2012-04-11 16:29 ` Ross Philipson
2012-04-13 9:38 ` Ian Campbell
2012-04-25 18:47 ` Ross Philipson
2012-04-25 20:47 ` Tim Deegan
2012-04-25 21:05 ` Ross Philipson
2012-04-26 7:46 ` Ian Campbell
2012-05-01 19:47 ` Julian Pidancet
2012-05-01 22:17 ` Tim Deegan
2012-05-01 22:59 ` Julian Pidancet
2012-05-01 23:21 ` Tim Deegan
2012-05-02 9:51 ` Ian Campbell
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-all 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=CB8D757A.2EB53%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ross.Philipson@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.