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

RE: [Xen-ia64-devel] [PATCH] Xen panics when domvti is destroyed


  • To: "Kouya SHIMURA" <kouya@xxxxxxxxxxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Fri, 13 Oct 2006 08:30:01 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 12 Oct 2006 17:30:51 -0700
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: Acbt7209boW4eroiSz636o/5lfegFAAbl7ew
  • Thread-topic: [Xen-ia64-devel] [PATCH] Xen panics when domvti is destroyed

>From: Kouya SHIMURA [mailto:kouya@xxxxxxxxxxxxxx]
>Sent: 2006年10月12日 19:13
>To: Xu, Anthony
>Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [Xen-ia64-devel] [PATCH] Xen panics when domvti is destroyed
>
>Abnormal OS might wake up the same vcpu from other vcpus simultaneously.
>We don't care such a case? :P


Good thinking,
I think there are two situations,
If two other vcpus wake up one vcpu at the exact same time, then this vcpu 
receives only one vcpu wakeup interrupt.
If two other vcpus wake up one vcpu sequentially, the first interrupt is 
thought of as vcpu wakeup interrupt, the second interrupt is injected into 
Guest OS by this vcpu, it is the Guest OS responsible to handle this abnormal 
interrupt.

Anthony




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


 


Rackspace

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