From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ross Philipson <Ross.Philipson@citrix.com>
Cc: Konrad Rzeszutek Will <ketuzsezr@gmail.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH v4 00/04] HVM firmware passthrough
Date: Wed, 9 Jan 2013 09:55:55 -0500 [thread overview]
Message-ID: <20130109145555.GA19595@phenom.dumpdata.com> (raw)
In-Reply-To: <831D55AF5A11D64C9B4B43F59EEBF720A31FBE1BF3@FTLPMAILBOX02.citrite.net>
On Tue, Jan 08, 2013 at 07:14:11PM -0500, Ross Philipson wrote:
> > -----Original Message-----
> > From: Konrad Rzeszutek Will [mailto:ketuzsezr@gmail.com]
> > Sent: Tuesday, January 08, 2013 7:00 PM
> > To: Ross Philipson
> > Cc: xen-devel@lists.xensource.com
> > Subject: Re: [Xen-devel] [PATCH v4 00/04] HVM firmware passthrough
> >
> > On Jan 8, 2013, at 3:26 PM, Ross Philipson <Ross.Philipson@citrix.com>
> > wrote:
> >
> > >> -----Original Message-----
> > >> From: xen-devel-bounces@lists.xen.org [mailto:xen-devel-
> > >> bounces@lists.xen.org] On Behalf Of Ross Philipson
> > >> Sent: Thursday, December 20, 2012 1:55 PM
> > >> To: xen-devel@lists.xensource.com
> > >> Subject: [Xen-devel] [PATCH v4 00/04] HVM firmware passthrough
> > >>
> > >> 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.
> > > ...
> > >
> > > Is there anything else I need to do to get this patch series accepted?
> >
> > Address the comments we had. I believe it was on making this be part of
> > "xl" guest config parsing.
>
> Oh I thought I did. I said I would submit a separate set of patches for
> the work in xl once the earlier bits were in. Is that not an acceptable
> approach?
Somehow I missed that. I thought there were also comments on how the call
to the library should be done? As in - not introduce a new one but alter
the existing one? Or am I thinking of a different patchset?
next prev parent reply other threads:[~2013-01-09 14:55 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
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 [this message]
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=20130109145555.GA19595@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ross.Philipson@citrix.com \
--cc=ketuzsezr@gmail.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).