From: Stratos Psomadakis <psomas@ece.ntua.gr>
To: linux-kernel@vger.kernel.org
Cc: rusty@rustcorp.com.au
Subject: Two questions about paravirt boot sequence(head_32.S)
Date: Thu, 14 Apr 2011 13:33:51 +0300 [thread overview]
Message-ID: <4DA6CD8F.6080206@ece.ntua.gr> (raw)
[-- Attachment #1: Type: text/plain, Size: 371 bytes --]
1)I cannot understand why the WEAK entries are required after the
bad_subarch label :/ Any hints?
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?
Thanks! :)
--
Stratos Psomadakis
<psomas@ece.ntua.gr>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next reply other threads:[~2011-04-14 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 10:33 Stratos Psomadakis [this message]
2011-04-14 10:47 ` Two questions about paravirt boot sequence(head_32.S) Stratos Psomadakis
2011-04-14 12:10 ` Rusty Russell
2011-04-15 14:08 ` Konrad Rzeszutek Wilk
2011-04-15 14:14 ` Stratos Psomadakis
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=4DA6CD8F.6080206@ece.ntua.gr \
--to=psomas@ece.ntua.gr \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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).