From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Chris Wright <chrisw@sous-sol.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Extending boot protocol & bzImage for paravirt_ops
Date: Fri, 01 Jun 2007 14:47:15 -0700 [thread overview]
Message-ID: <466093E3.4010701@goop.org> (raw)
In-Reply-To: <4660924A.2070009@zytor.com>
H. Peter Anvin wrote:
>> Do we care particularly? If 8 bytes is enough for the subarch, do we
>> care whether its a pointer or literal? After all, this is just a private
>> channel between the bootloader and some subarch-specific piece of code
>> in the kernel.
>>
>>
>
> I see two options: either we make it a pointer *and a length* so that a
> loader can reshuffle it at will (that also implies no absolute pointers
> within the data), or it's an opaque cookie anyway.
>
No, it has to be completely opaque. It might be a pointer to some
special shared memory or something, and not movable.
J
next prev parent reply other threads:[~2007-06-01 21:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 15:06 Extending boot protocol & bzImage for paravirt_ops Jeremy Fitzhardinge
2007-05-25 16:46 ` Eric W. Biederman
2007-05-25 16:46 ` Eric W. Biederman
2007-05-26 10:18 ` Rusty Russell
2007-05-26 20:42 ` H. Peter Anvin
2007-05-26 23:47 ` Jeremy Fitzhardinge
2007-05-26 23:47 ` Jeremy Fitzhardinge
2007-05-27 0:10 ` Rusty Russell
2007-05-27 0:15 ` H. Peter Anvin
2007-05-27 0:15 ` H. Peter Anvin
2007-05-26 23:47 ` Jeremy Fitzhardinge
2007-05-27 0:14 ` H. Peter Anvin
2007-05-27 0:19 ` Jeremy Fitzhardinge
2007-05-27 0:19 ` Jeremy Fitzhardinge
2007-05-30 23:16 ` Jeremy Fitzhardinge
2007-05-31 8:08 ` Vivek Goyal
2007-05-31 8:08 ` Vivek Goyal
2007-06-01 20:55 ` Jeremy Fitzhardinge
2007-06-01 21:40 ` H. Peter Anvin
2007-06-01 21:40 ` H. Peter Anvin
2007-06-01 21:47 ` Jeremy Fitzhardinge [this message]
2007-06-01 21:57 ` H. Peter Anvin
2007-06-01 21:57 ` H. Peter Anvin
2007-06-02 0:37 ` Jeremy Fitzhardinge
2007-06-02 0:37 ` Jeremy Fitzhardinge
2007-06-02 0:42 ` H. Peter Anvin
2007-06-02 0:58 ` Jeremy Fitzhardinge
2007-06-02 1:02 ` H. Peter Anvin
2007-06-02 1:08 ` Jeremy Fitzhardinge
2007-06-02 1:17 ` Eric W. Biederman
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=466093E3.4010701@goop.org \
--to=jeremy@goop.org \
--cc=chrisw@sous-sol.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.osdl.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.