This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] RE: x86_64 SMP support (status update)

To: "Chris Wright" <chrisw@xxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] RE: x86_64 SMP support (status update)
From: "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
Date: Mon, 27 Jun 2005 14:44:22 -0700
Delivery-date: Mon, 27 Jun 2005 21:43:21 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcV7XWR/RTGTqkx1Sw+ieQD2KSioOgAAZrjA
Thread-topic: x86_64 SMP support (status update)
Chris Wright wrote:
> * Chris Wright (chrisw@xxxxxxxx) wrote:
>> * Nakajima, Jun (jun.nakajima@xxxxxxxxx) wrote:
>>> Good progress and good start, i.e. we have at least one virutal
>>> processor there :-). 
>>> We'll look at the problem too.
>> Great, thanks.  I'm pretty suspect of the gdt, but only on a hunch.
>> Any clues why the copy is faulting might be useful.
> Here's an updated patch that fixes that faulting.  It uses gdt per
> page like i386 is doing, still crashing upon schedule.  Why does each
> gdt entry need it's own page?
> thanks,
> -chris

Each gdt entry? I think gdt should be per vcpu, but I don't understand
"each gdt entry". Can you please point to the code you are talking

Intel Open Source Technology Center

Xen-devel mailing list