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

RE: [Xen-ia64-devel] [PATCH] VTI: fix Oops: time tick before it's due


  • To: "Xu, Anthony" <anthony.xu@xxxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Wed, 8 Mar 2006 09:28:50 +0800
  • Delivery-date: Wed, 08 Mar 2006 01:29:31 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcY/Nfo10yUmvXboQ/ilYUxNUUIIWQDGYlNg
  • Thread-topic: [Xen-ia64-devel] [PATCH] VTI: fix Oops: time tick before it's due

Alex,
What's your opinion about this patch?

Thanks,
-Anthony 

>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Xu, Anthony
>Sent: 2006年3月4日 10:47
>To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: [Xen-ia64-devel] [PATCH] VTI: fix Oops: time tick before it's due
>
>1. Guest may set itm several times in one execution of timer handler of
>guest.
>  VMM need to handle this situation.
>2. VMM don't need to stop guest timer when switching out and rest guest
>timer
>when switching in, this may make room for some corner case, I don't
>figure out
>this kind of corner cases now :-), I just removed this logic.
>3. When VMM emulate writing itv, VMM can't simply stop timer, when guest
>is masked.
>4. All operations such as read/write itv, itc, itm don't need to disable
>
>interrupt, due to there is no conflict access.
>
>After all these modifications, VTIdomain don't complain "Oops: time tick
>before
>it's due", I don't do the full test:-).
>
>Signed-off-by: Anthony Xu <anthony.xu@xxxxxxxxx>
>
>Thanks,
>-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®.