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

[Xen-devel] potential bug where mem_event_request_t gfn value == -1?

  • To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Bob Jung <Bob.Jung@xxxxxxxxxxxx>
  • Date: Fri, 6 Jan 2012 20:49:53 +0000
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Delivery-date: Fri, 06 Jan 2012 20:51:17 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AczMtL50Jdzl6W3yQtCso6ZNlTNuLw==
  • Thread-topic: potential bug where mem_event_request_t gfn value == -1?

Hi there,

I am running an adapted version of tools/tests/xen_access/xen_access.c  to get 
and respond to memory events to do some analysis.  Anyways, after registering 
for and receiving single stepping events in my ring buffer where the 
me_event_request_t's  reason field == MEM_EVENT_REASON_SINGLESTEP, I sometimes 
see that the gfn in the request is -1.

the guest is HVM windows 32 bit.  For 99.99% of the single step traps the 
req.gfn value is the correct guest frame number value, but every now and again 
I get a -1

Does anyone know why this could happen?  

Xen-devel mailing list



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