From: Samuel Thibault <samuel.thibault@ens-lyon.org>
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>,
xen-devel@lists.xenproject.org,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH] x86/HVM: rewrite the start info structure definition in binary form
Date: Tue, 9 Feb 2016 09:26:19 +0100 [thread overview]
Message-ID: <20160209082619.GD2818@var.home> (raw)
In-Reply-To: <56B9ADE502000078000CFDFC@prv-mh.provo.novell.com>
Jan Beulich, on Tue 09 Feb 2016 01:14:13 -0700, wrote:
> >>> On 05.02.16 at 16:45, <roger.pau@citrix.com> wrote:
> > El 5/2/16 a les 14:13, Jan Beulich ha escrit:
> >> 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?
>
> This largely depends on whether you mean to mimic multiboot1 or
> multiboot2. Remember the placeholder people have to add to
> certain grub2 invocation lines? I think that's a result of their
> attempt to had through a file name.
Yes. For gnumach we've been adding the file name by hand in the command
line. Otherwise the resulting tasks would have at best their first
parameter as task name, since gnumach has no idea what these modules...
Samuel
next prev parent reply other threads:[~2016-02-09 8:26 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 [this message]
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=20160209082619.GD2818@var.home \
--to=samuel.thibault@ens-lyon.org \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=roger.pau@citrix.com \
--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).