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

RE: [PATCH] fix dirty_bit in xenivt.S (was Re: [Xen-ia64-devel] Fail tocreate VTI domain in lates Cset 10143)


  • To: "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Thu, 25 May 2006 10:20:56 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 24 May 2006 19:22:08 -0700
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcZ/nLp4j4TaeNjMQD6fWVIRT+mPIwABMMrg
  • Thread-topic: [PATCH] fix dirty_bit in xenivt.S (was Re: [Xen-ia64-devel] Fail tocreate VTI domain in lates Cset 10143)

>From: Isaku Yamahata [mailto:yamahata@xxxxxxxxxxxxx]
>Sent: 2006年5月25日 9:42
>>
>> Hi, Isaku,
>>      I'm interesting why your patch can fix potential issue here. Ideally
>> XEN_HYPER_ITC_D is only the fast path which should have the same
>> effect as GP fault caused by itc.d. If your patch really helps, that means
>> the two paths (slow/fast) are incompatible which need to be solved,
>right?
>
>Hi Kevin.
>In fact the patch only hides the root cause.
>Evantually I was able to reproduce it and get its stack trace
>by inserting dump_stack() right after the debug message.
>The following stack trace explains, I hope.
>I'll make a patch to __get_domain_bundle().
>
>Anyway I don't see any reason why only itc.d of dirty_bit handler isn't
>para-virtualized so that the patch should be applied.

Sure that patch is required. :-)

Thanks,
Kevin

_______________________________________________
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®.