From: Stratos Psomadakis <psomas@ece.ntua.gr>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Two questions about paravirt boot sequence(head_32.S)
Date: Fri, 15 Apr 2011 17:14:59 +0300 [thread overview]
Message-ID: <4DA852E3.9080702@ece.ntua.gr> (raw)
In-Reply-To: <20110415140846.GA32334@dumpdata.com>
On 04/15/2011 05:08 PM, Konrad Rzeszutek Wilk wrote:
> On Thu, Apr 14, 2011 at 09:40:05PM +0930, Rusty Russell wrote:
>> On Thu, 14 Apr 2011 13:33:51 +0300, Stratos Psomadakis <psomas@ece.ntua.gr> wrote:
>>> 2)I think that xen doesn't use any more the hardware subarch boot
>>> parameter, and uses a 'different' path/boot sequence, hence the
>>> xen_entry in head_32.S is not needed any more. Am I missing something?
>> Yep, Xen never actually used it.
> Does lguest use it? It looked like a neat idea - what happened?
yeap, afaik, lguest uses the subarch field to jump to its own 'entry
point'...
--
Stratos Psomadakis
<psomas@ece.ntua.gr>
prev parent reply other threads:[~2011-04-15 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 10:33 Two questions about paravirt boot sequence(head_32.S) Stratos Psomadakis
2011-04-14 10:47 ` Stratos Psomadakis
2011-04-14 12:10 ` Rusty Russell
2011-04-15 14:08 ` Konrad Rzeszutek Wilk
2011-04-15 14:14 ` Stratos Psomadakis [this message]
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=4DA852E3.9080702@ece.ntua.gr \
--to=psomas@ece.ntua.gr \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.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.