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] current not very current (vs curr_vcpu)

To: Mukesh Rathor <mukesh.rathor@xxxxxxxxxx>
Subject: Re: [Xen-devel] current not very current (vs curr_vcpu)
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 19 Feb 2010 21:34:39 +0000
Cc: "Xen-devel@xxxxxxxxxxxxxxxxxxx" <Xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 19 Feb 2010 13:35:33 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100219112349.2cd1854a@xxxxxxxxxxxxxxxxxxxx>
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: AcqxmRL0T5+VlHu9Q8GytA0DFZey0gAEkQCG
Thread-topic: [Xen-devel] current not very current (vs curr_vcpu)
User-agent: Microsoft-Entourage/12.23.0.091001
On 19/02/2010 19:23, "Mukesh Rathor" <mukesh.rathor@xxxxxxxxxx> wrote:

> Yes, but my point is it doesn't appear to be running idle vcpu as
> indicated by regs->rsp and regs->rip. They both point to dom0 context.
> This from printk in ns16550_interrupt().
> 
> To rephrase the question, if regs->rip and regs->rsp show guest context
> in do_IRQ(), then current must always point to guest vcpu, correct?

Oh, so the serial interrupt interrupted a guest's execution? Then yes,
current should point at that guest.

 -- Keir



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