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 02/14] Nested Virtualization: localevent

To: Christoph Egger <Christoph.Egger@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 02/14] Nested Virtualization: localevent
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 5 Aug 2010 17:19:14 +0100
Cc:
Delivery-date: Thu, 05 Aug 2010 09:20:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C8809B4C.1CE41%keir.fraser@xxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acs0scHLXOS0KTe3TDql4Wm484XqWQAA43aEAAEoiCc=
Thread-topic: [Xen-devel] [PATCH 02/14] Nested Virtualization: localevent
User-agent: Microsoft-Entourage/12.24.0.100205
I seem to remember we discussed the reason for this a bit some time ago. It
looked to me like you were calling a function that makes sense only on a
running guest (and a locally currently running guest at that) after the
guest was dead, during cleanup/teardown. If I'm remebering correctly then
the fix would be to not do that then. ;-)

 -- Keir

On 05/08/2010 16:46, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx> wrote:

> The functions are called local_event_delivery* because they implicitly act
> on current. They don't need to take a vcpu parameter. If you find you need a
> vcpu parameter then you are using them, or one of their callers,
> incorrectly.
> 
>  -- Keir
> 
> On 05/08/2010 16:00, "Christoph Egger" <Christoph.Egger@xxxxxxx> wrote:
> 
>> 
>> Signed-off-by: Christoph Egger <Christoph.Egger@xxxxxxx>
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



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