| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] RE: Biweekly VMX status report. Xen: #20255 & Xen0:#b6ba
|
To: |
"Kay, Allen M" <allen.m.kay@xxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx> |
|
Subject: |
Re: [Xen-devel] RE: Biweekly VMX status report. Xen: #20255 & Xen0:#b6ba0... |
|
From: |
Keir Fraser <keir.fraser@xxxxxxxxxxxxx> |
|
Date: |
Thu, 01 Oct 2009 08:19:16 +0100 |
|
Cc: |
"Xin, Xiaohui" <xiaohui.xin@xxxxxxxxx>, "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Xu, Jiajun" <jiajun.xu@xxxxxxxxx>, "Han, Weidong" <weidong.han@xxxxxxxxx>, George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, "Li, Xin" <xin.li@xxxxxxxxx>, "Nakajima, Jun" <jun.nakajima@xxxxxxxxx> |
|
Delivery-date: |
Thu, 01 Oct 2009 00:19:42 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<57C9024A16AD2D4C97DC78E552063EA3E2F041C2@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> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
Thread-index: |
AcpBrYrco58/Uyp9QQeyDtqDvK+xaQAg70IgAA2M+3I= |
|
Thread-topic: |
[Xen-devel] RE: Biweekly VMX status report. Xen: #20255 & Xen0:#b6ba0... |
|
User-agent: |
Microsoft-Entourage/12.20.0.090605 |
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
|
| <Prev in Thread] |
Current Thread |
[Next in Thread> |
- Re: [Xen-devel] RE: Biweekly VMX status report. Xen: #20255 & Xen0:#b6ba0...,
Keir Fraser <=
|
|
|
| |
|
Home