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

Re: [Xen-devel] VMX status report 12542:91951de7592c


  • To: Keir Fraser <keir@xxxxxxxxxxxxx>, "Yu, Ping Y" <ping.y.yu@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Tue, 28 Nov 2006 15:23:07 +0000
  • Delivery-date: Tue, 28 Nov 2006 07:23:16 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AccRzW1PE3gfF9VARKiKLg//5KS2wgAJ7ldgAAFnUOIANWLE8AABFSXgAAsd03U=
  • Thread-topic: [Xen-devel] VMX status report 12542:91951de7592c

On 28/11/06 10:04, "Keir Fraser" <keir@xxxxxxxxxxxxx> wrote:

> On 28/11/06 9:34 am, "Yu, Ping Y" <ping.y.yu@xxxxxxxxx> wrote:
> 
>> Keir,
>> 
>> During our testing in c/s 12548, the PV build issue is fixed while the other
>> is still there.
>> 
>> Ping
> 
> I'll add some more tracing to help track it down.

I added some more tracing in c/s 12591. However, you can expect for the
"Access faulted on page boundary" message to appear occasionally. Crucially
we expect to see the printed 'ea' value be a little bit smaller than the
printed 'cr2' value (by up to 7 bytes).

If the extra tracing doesn't turn up anything interesting I'll quieten it
down again later this week.

 -- Keir


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


 


Rackspace

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