All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Jan Beulich" <JBeulich@suse.com>,
	"Roger Pau Monné" <roger.pau@citrix.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: Thu, 27 Aug 2015 10:43:06 +0100	[thread overview]
Message-ID: <55DEDBAA.9030601@citrix.com> (raw)
In-Reply-To: <55DEE093020000780009D4E0@prv-mh.provo.novell.com>

On 27/08/15 09:04, Jan Beulich wrote:
>>>> On 26.08.15 at 16:44, <roger.pau@citrix.com> wrote:
>> 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.
> But the statement leaves open whether there is any free memory at
> all after those structures, or whether instead all free memory lives
> at lower addresses. Nor do I consider it appropriate to take a present
> (one might say overly simplistic) implementation as a basis for setting
> arbitrary restrictions.

I agree.  This sounds like a FreeBSD bug, and absolutely shouldn't be a
written restriction in the boot ABI.

~Andrew

  reply	other threads:[~2015-08-27  9:43 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é
2015-08-27  8:04       ` Jan Beulich
2015-08-27  9:43         ` Andrew Cooper [this message]
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=55DEDBAA.9030601@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=elena.ufimtseva@oracle.com \
    --cc=roger.pau@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.