WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

RE: [Xen-devel] [patch] make hypercall_preempt_check() a littlemoresensi

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Jimi Xenidis" <jimix@xxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [patch] make hypercall_preempt_check() a littlemoresensitive
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Fri, 31 Mar 2006 10:50:19 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Hollis Blanchard <hollisb@xxxxxxxxxx>, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 31 Mar 2006 02:52:00 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZUaZsjeqmq8qlMQ/eBJsNU94sQ/QAAJStwAAC0nZA=
Thread-topic: [Xen-devel] [patch] make hypercall_preempt_check() a littlemoresensitive
>From: Tian,Kevin
>Sent: 2006年3月31日 10:33
>>
>>This is an interesting example,  but why deliver an upcall thru the
>>HV in the first place, why not just call the evtchn handler directly?
>
>Then you may fall into dead loop, since evtchn_device_upcall tries to get
>spinlock while unmask_evtchn path may already holds the lock.
>

A more natural way to think about this model is described in the comment, 
where says to emulate hw_resend_irq behavior. On native system, such 
irq is resent to the system bus for interrupt logic to arbitrate upon priority 
and mask status. Here event is resent to let virtual interrupt logic (event 
dispatcher) to arbitrate. Such logic is (shouldn't be) unknown at the point 
of evtchn_unmask. :-)

Thanks,
Kevin

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

<Prev in Thread] Current Thread [Next in Thread>
  • RE: [Xen-devel] [patch] make hypercall_preempt_check() a littlemoresensitive, Tian, Kevin <=