WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749

To: "Li, Haicheng" <haicheng.li@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>, Gianluca Guida <gianluca.guida@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749
From: "Li, Haicheng" <haicheng.li@xxxxxxxxx>
Date: Tue, 16 Dec 2008 15:24:59 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Li, Xin" <xin.li@xxxxxxxxx>
Delivery-date: Mon, 15 Dec 2008 23:25:46 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <76780B19A496DC4B80439008DAD7076C01C6B5114B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <0B53E02A2965CE4F9ADB38B34501A3A16825BA99@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C56C05E1.CD5%keir.fraser@xxxxxxxxxxxxx> <76780B19A496DC4B80439008DAD7076C01C6B5114B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcldK/fZZNTFfVr6k0WK9hRQshPOTwAAZfOQAALnZR0ADcmHgABRQwZvACMnlFAAAwoSIA==
Thread-topic: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749
Li, Haicheng wrote:
> Keir Fraser wrote:
>> On 13/12/2008 22:43, "Nakajima, Jun" <jun.nakajima@xxxxxxxxx> wrote:
>> 
>>>> I think you agree that we don't need to keep guest 'actual' EFER.NX
>>>> in sync with its 'shadow' EFER.NX?
>>>> 
>>> 
>>> That should be okay. The fact we see the NX bit in the shadow page
>>> tables means at least the BSP enabled NX. And I don't expect other
>>> processors would do otherwise. In other words, such out-of-sync
>>> situations be transient anyway.
>> 
>> Attached is my proposed patch. Does it look okay to everyone?
>> Haicheng: could you test if it gets rid of the HVM Solaris crash?
>> 
>>  Thanks,
>>  Keir
> 
> Yes, we will test your patch and keep you posted with result.
> 
> -haicheng

Hi Keir,

We tested your patch, it does fix the bug of HVM Solaris crash, viz. SMP 64bit 
Solaris10u5 HVM can boot up successfully with your patch applied. Thanks.



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