xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ross Philipson <Ross.Philipson@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH v4 00/04] HVM firmware passthrough
Date: Fri, 21 Dec 2012 21:12:25 -0500	[thread overview]
Message-ID: <20121222021225.GA3468@phenom.dumpdata.com> (raw)
In-Reply-To: <831D55AF5A11D64C9B4B43F59EEBF720A31F6B65DA@FTLPMAILBOX02.citrite.net>

On Fri, Dec 21, 2012 at 06:31:58PM -0500, Ross Philipson wrote:
> > -----Original Message-----
> > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> > Sent: Friday, December 21, 2012 2:46 PM
> > To: Ross Philipson
> > Cc: xen-devel@lists.xensource.com
> > Subject: Re: [Xen-devel] [PATCH v4 00/04] HVM firmware passthrough
> > 
> > On Thu, Dec 20, 2012 at 01:55:10PM -0500, Ross Philipson wrote:
> > > This patch series introduces support of loading external blocks of
> > > firmware into a guest. These blocks can currently contain SMBIOS
> > > and/or ACPI firmware information that is used by HVMLOADER to modify a
> > > guests virtual firmware at startup. These modules are only used by
> > HVMLOADER and are effectively discarded after HVMLOADER has completed.
> > >
> > > The domain building code in libxenguest is passed these firmware
> > > blocks in the xc_hvm_build_args structure and loads them into the new
> > > guest, returning the load address. The loading is done in what will
> > > become the guests low RAM area just behind to load location for
> > > HVMLOADER. After their use by HVMLOADER they are effectively
> > > discarded. It is the caller's job to load the base address and length
> > > values in xenstore using the paths defined in the new hvm_defs.h
> > header so HVMLOADER can located the blocks.
> > >
> > 
> > Are there patches to plug this in the 'xl'?
> > 
> 
> So far there are only patches to expose it at the xc layer. Nothing else
> seems to use the xc_hvm_build() call (only xc_hvm_build_target_mem()).
> Since the use of this feature seems dependent on a user's particular
> needs, I am not sure how it could generically be built into xl. Any
> suggestions are welcome though and I could post subsequent patches.

I was thinking something like this:

firmware="nvidia.bin"
acpi_dsdt="acpi.dsdt"

?
> 
> Thanks
> Ross

  reply	other threads:[~2012-12-22  2:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-20 18:55 [PATCH v4 00/04] HVM firmware passthrough Ross Philipson
2012-12-21 19:45 ` Konrad Rzeszutek Wilk
2012-12-21 23:31   ` Ross Philipson
2012-12-22  2:12     ` Konrad Rzeszutek Wilk [this message]
2012-12-22 23:46       ` Ross Philipson
2013-01-02 13:25         ` Ian Campbell
2013-01-02 17:26           ` Ross Philipson
2013-01-03 15:35         ` David Vrabel
2013-01-08 23:26 ` Ross Philipson
2013-01-09  0:00   ` Konrad Rzeszutek Will
2013-01-09  0:14     ` Ross Philipson
2013-01-09 14:55       ` Konrad Rzeszutek Wilk
2013-01-09 18:04         ` Ross Philipson
2013-02-12 15:47           ` Ian Jackson
2013-02-12 21:30             ` Ross Philipson

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=20121222021225.GA3468@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ross.Philipson@citrix.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).