linux-kernel - [PATCH 00 of 55] xen64: implement 64-bit Xen support

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: <patchbomb.1215554782@localhost>
Date:	Tue, 08 Jul 2008 15:06:22 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	LKML <linux-kernel@...r.kernel.org>, x86@...nel.org,
	Stephen Tweedie <sct@...hat.com>,
	Eduardo Habkost <ehabkost@...hat.com>,
	Mark McLoughlin <markmc@...hat.com>, x86@...nel.org
Subject: [PATCH 00 of 55] xen64: implement 64-bit Xen support

Hi Ingo,

Here's the set of patches to implement 64-bit Xen support.

The first part of the series is some more (fairly minor) x86 arch
updates which here missed in the previous series.

Following that are the Xen-specific changes to implement 64-bit
support.  It works fairly well, but I know of a couple of bugs:

 - 32-bit emulation doesn't work properly yet.  Something goes wrong
   with %gs, and a userspace %gs: reference segfaults.

 - It crashes when bringing up secondary CPUs under some combinations
   of config.  I think it isn't quite setting up all the CPU sibling
   topology stuff for the various scheduler policies.  It's trying to
   set up the most simple of arrangements (every CPU is a singleton
   with no shared cache or anything else).  It was quite tricky to
   arrange this...

I hope to have followup patches to address both of these in the next
couple of days.  I expect both fixes will be small.

Thanks,
	  J

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/