linux-kernel - Two questions about paravirt boot sequence(head

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4DA6CD8F.6080206@ece.ntua.gr>
Date:	Thu, 14 Apr 2011 13:33:51 +0300
From:	Stratos Psomadakis <psomas@....ntua.gr>
To:	linux-kernel@...r.kernel.org
CC:	rusty@...tcorp.com.au
Subject: Two questions about paravirt boot sequence(head_32.S)

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@....ntua.gr>

Download attachment "signature.asc" of type "application/pgp-signature" (263 bytes)