Re: [Xen-devel] RE: Biweekly VMX status report. Xen: #20255 & Xen0:#b6ba0...

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

On 01/10/2009 01:53, "Kay, Allen M" <allen.m.kay@xxxxxxxxx> wrote:

> I'm still seeing the same assertion failure with this patch on my NHM EP
> system.
> 
> (XEN) Xen call trace:
> (XEN)    [<ffff82c4801b01a5>] ept_sync_domain+0x62/0x9c
> (XEN)    [<ffff82c4801e559d>] ept_set_entry+0x6c1/0x7f6
> (XEN)    [<ffff82c4801e5905>] ept_change_entry_emt_with_range+0x233/0x25e
> (XEN)    [<ffff82c4801b0209>] vmx_set_uc_mode+0x2a/0x5d

Yes, that's the other optimistically lock-free call path I eyeballed. It
needs fixing too. Hence why I'm waiting for a combined all-in-one fixup
patch, else we'll be trickling the fixes callpath-by-callpath.

 -- Keir



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