From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Cc: Elena Ufimtseva <elena.ufimtseva@oracle.com>,
xen-devel <xen-devel@lists.xenproject.org>,
BorisOstrovsky <boris.ostrovsky@oracle.com>,
Tim Deegan <tim@xen.org>
Subject: Re: [Draft B] Boot ABI for HVM guests without a device-model
Date: Wed, 26 Aug 2015 16:44:41 +0200 [thread overview]
Message-ID: <55DDD0D9.4080800@citrix.com> (raw)
In-Reply-To: <55DDAD38.9020200@citrix.com>
El 26/08/15 a les 14.12, Andrew Cooper ha escrit:
> On 26/08/15 13:00, Jan Beulich wrote:
>>> This structure is guaranteed to always be placed in memory after the
>> DYM "These structures are ..."?
>>
>>> loaded kernel and modules.
>
> There is no requirement for the command line/module information to be
> after the loaded kernel. All it needs to do is not overlap.
IMHO, this is helpful in order to get last used physical address, after
which free memory starts. Current FreeBSD implementation relies on this,
if we didn't do it that way I would have to calculate where the symtab +
strtab ends, which is more complex.
>>> There's no upper bound on the size of the
>>> structure, users should be aware that it might cross a page boundary.
>> How is there no size limit? It's (currently) 16 bytes, and I don't see
>> why it would change. And even if - as implied by the previous
>> comment - this also relates to struct hvm_start_info: Its size is
>> fixed (and unlikely to change much) too.
>
> I agree it is unlikely to change (but there is a flags field just in
> case), but we shouldn't impose unnecessary arbitrary restrictions.
After reading it again, I realize this is not properly worded. What I
wanted to say is that the cmdline or the list of loaded modules might
cross a page boundary.
Roger.
next prev parent reply other threads:[~2015-08-26 14:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 11:48 [Draft B] Boot ABI for HVM guests without a device-model Roger Pau Monné
2015-08-26 12:00 ` Jan Beulich
2015-08-26 12:12 ` Andrew Cooper
2015-08-26 14:44 ` Roger Pau Monné [this message]
2015-08-27 8:04 ` Jan Beulich
2015-08-27 9:43 ` Andrew Cooper
2015-08-27 9:57 ` Roger Pau Monné
2015-08-27 11:08 ` Jan Beulich
2015-08-26 12:18 ` Andrew Cooper
2015-08-26 15:38 ` Roger Pau Monné
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=55DDD0D9.4080800@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=elena.ufimtseva@oracle.com \
--cc=tim@xen.org \
--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).