From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] x86/HVM: rewrite the start info structure definition in binary form
Date: Fri, 5 Feb 2016 16:45:34 +0100 [thread overview]
Message-ID: <56B4C39E.50206@citrix.com> (raw)
In-Reply-To: <56B4AE1C02000078000CF06E@prv-mh.provo.novell.com>
El 5/2/16 a les 14:13, Jan Beulich ha escrit:
>>>> On 05.02.16 at 13:28, <roger.pau@citrix.com> wrote:
>> This will prevent alignments from getting in the way. It's not safe to
>> define this memory structures using C anyway, since the ABI depends on the
>> bitness, while our protocol does not.
>>
>> Also add a command line parameter to each module, and a reserved field in
>> order to have the layout aligned. Note that the current implementation in
>> libxc doesn't make use of the module command line at all.
>
> Which would seem wrong then - what use is the field if it doesn't
> get filled? Or is that because it has nowhere to come from?
Right now it has nowhere to come from as you say.
Once we enable this ABI for Dom0 boot we are just going to copy what's
in the "string" field defined in the multiboot spec for each module
structure that's passed to Dom0. That's the primary use I can see for
this ATM.
It was requested by Samuel, and I think it's fine to add it to the spec,
even if we are not going to use it right now. Samuel requires something
like this in order to properly pass parameters to boot modules in gnumach.
> But
> even then - wouldn't what I've read on the other thread mean
> at least the filename should be put there (as kind of the first
> command line element)?
Really? I didn't get that impression at all, what's the filename useful
for anyway?
IMHO this would need plumbing through libxl/xl in order to be able to
specify command line arguments for modules, which is something that we
don't support at the moment.
Roger.
next prev parent reply other threads:[~2016-02-05 15:45 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é [this message]
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
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=56B4C39E.50206@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.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).