RE: [Xen-devel] question about patch 13252

["Lu, Guanqun" <guanqun.lu@xxxxxxxxx>]

On Friday, March 20, 2009 1:07 AM Keir Fraser wrote:

> On 19/03/2009 14:58, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:
> 
>>> If Jan can counter my claim, then you can instead switch back to the
>>> non-compat GDT for the LTR, or you can decide which descriptor to
>>> set B in based on which GDT you're running on, or force the B bit
>>> in both descriptors after the LTR, or... You have a few options. :-)
>> 
>> Correct. I wonder why you're running on the compat GDT in the first
>> place - is your Dom0 32-bit? If that's the case, then the clearing
>> of the bit that must exist somewhere simply should be extended to
>> touch the current GDT 
>> rather than the default one.
> 
> I fixed this issue as c/s 19400. I just temporarily switch over to the
> non-compat GDT to do the LTR. Guanqun: please can you test this?
> 
>  -- Keir

Hi Keir,

I tested with your patch, and in 32/32 xen/dom0 stack, S3 woks fine.
but with 64/32 xen/dom0 stack, when S3 resumes back, it complains:
        INIT: PANIC: segmentation violation at 0xb7f36405! sleeping for 30 
seconds.
and basically the shell is usable, but 'make' always got a seg fault.

The phenomenon is very similar to justing changing the number 11 to 9.

Any idea?

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