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-devel

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

To: "Jimi Xenidis" <jimix@xxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [patch] make hypercall_preempt_check() a little moresensitive
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Fri, 31 Mar 2006 10:32:48 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Hollis Blanchard <hollisb@xxxxxxxxxx>, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 31 Mar 2006 02:34:40 +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/QAAJStw
Thread-topic: [Xen-devel] [patch] make hypercall_preempt_check() a little moresensitive
>From: Jimi Xenidis [mailto:jimix@xxxxxxxxxxxxxx]
>Sent: 2006年3月31日 10:20
>Yes, some bits can be controlled by xenlinux

OK, it's always good thing to learn a different model.

>
>> to
>> disable real external interrupts on that physical processor,
>
>Yes, even this bit, tho' it this is on the 970 class of processor,
>newer processors can be configured to not disable externals, but they
>can still set the bit.

So, is there any brief info about the model that ppc is currently using, like 
whether dom0/domU is para-virtualized or unmodifield, if para-virtualized, 
to which extent? Maybe I asked too many questions in one mail, but such 
info may help other people to understand your specific requirement more 
easily. I think I'm still lacking of a whole picture about current xen/ppc 
model. :-)

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

Thanks,
Kevin

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

<Prev in Thread] Current Thread [Next in Thread>