From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>,
"Samuel Thibault" <samuel.thibault@ens-lyon.org>,
"Jan Beulich" <JBeulich@suse.com>,
"Ian Campbell" <ian.campbell@citrix.com>,
"Wei Liu" <wei.liu2@citrix.com>,
"Ian Jackson" <ian.jackson@eu.citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] x86/HVM: rewrite the start info structure definition in binary form
Date: Tue, 9 Feb 2016 10:58:11 +0000 [thread overview]
Message-ID: <56B9C643.8080102@citrix.com> (raw)
In-Reply-To: <56B9C5EF.9010009@citrix.com>
On 09/02/16 10:56, Roger Pau Monné wrote:
> El 9/2/16 a les 11:49, Samuel Thibault ha escrit:
>> Roger Pau Monné, on Tue 09 Feb 2016 11:45:01 +0100, wrote:
>>> El 9/2/16 a les 11:41, Samuel Thibault ha escrit:
>>>> Roger Pau Monné, on Tue 09 Feb 2016 11:38:43 +0100, wrote:
>>>>> Other OSes that use the pv loader don't pass any module at all AFAIK.
>>>> GNU Mach does need several modules.
>>> How do you usually pass multiple modules from an xl configuration file
>>> at the moment?
>> We pack the modules and command lines in one big blob, which we really
>> don't like.
> Right, this should allow you to pass multiple modules, but someone needs
> to implement the xl/libxl/libxc side in order to do it. As said, I don't
> think this should block it from being accepted.
+1 on both counts.
~Andrew
prev parent reply other threads:[~2016-02-09 10:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 12:28 [PATCH] x86/HVM: rewrite the start info structure definition in binary form Roger Pau Monne
2016-02-05 13:13 ` Jan Beulich
2016-02-05 15:45 ` Roger Pau Monné
2016-02-09 8:14 ` Jan Beulich
2016-02-09 8:26 ` Samuel Thibault
2016-02-09 10:38 ` Roger Pau Monné
2016-02-09 10:41 ` Samuel Thibault
2016-02-09 10:45 ` Roger Pau Monné
2016-02-09 10:49 ` Samuel Thibault
2016-02-09 10:56 ` Roger Pau Monné
2016-02-09 10:58 ` Andrew Cooper [this message]
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=56B9C643.8080102@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=roger.pau@citrix.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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).