Re: [Xen-devel] syscall32 being vectored through syscall handler

On Tue, Feb 24, 2009 at 02:24:16AM -0500, John Levon wrote:

> I've verified that we're setting up two different callback addresses,
> but a 32u/64k/64h syscall is ending up in the 64u handler. From what I
> can see, this code:

I'd missed the SMP case, completely forgot that the handlers get
initialized via vcpu_guest_context_t when bringing up a CPU...

regards
john

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] syscall32 being vectored through syscall handler, John Levon Re: [Xen-devel] syscall32 being vectored through syscall handler, John Levon <=

Previous by Date:

Re: [Xen-devel] Use paravirtualized kernel with HVM-image?, Boris Derzhavets

Next by Date:

Re: [Xen-devel] Unplugging a dom0 vcpu and domain destruction, George Dunlap

Previous by Thread:

[Xen-devel] syscall32 being vectored through syscall handler, John Levon

Next by Thread:

[Xen-devel] [PATCH] Make offlined CPU enter deepest C state, Yu, Ke

Indexes:

[Date] [Thread] [Top] [All Lists]