[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] progress and a problem

> On Sat, 26 Jun 2004, Keir Fraser wrote:
> > Which stack are you talking about here? When Xen first deschedules
> > your while(1), the CPU should write CS,EIP,EFLAGS,SS,ESP onto Xen's
> > ring-0 stack.
> ok, what interrupt does this? 

Any interrupt. Timer, disc, ... whatever happens to cause Xen to next
execute after you disable the mask. Xen always checks the pending and
mask flags on return to ring != 0.

> > When you get a callback, Xen should see that it is 'interrupting' an
> > existing ring-1 activation, and read the appropriate SS,ESP from its
> > own (ring-0) stack. When it writes the activation frame for teh
> > callback, it will only write CS,EIP,EFLAGS. SS,ESP will not be written
> > to your ring-1 stack because the IRET at the end of your callback
> > handler will not be changing privilege levels.
> ok, I see your point. I'm really puzzled about this bad ss/sp pair. It 
> makes no sense.

I'll take a look at stack traces if you want to post me some suitably
annotated ones.

 -- Keir

This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.