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] Switching to user mode from domU kernel

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Switching to user mode from domU kernel
From: Trammell Hudson <hudson@xxxxxxxxxxxxxx>
Date: Mon, 22 Oct 2007 18:00:22 -0400
Delivery-date: Mon, 22 Oct 2007 15:01:07 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C342C2A5.F475%Keir.Fraser@xxxxxxxxxxxx>
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>
References: <20071022195215.GE18929@xxxxxxxxxxxxxx> <C342C2A5.F475%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.10i
On Mon, Oct 22, 2007 at 09:12:05PM +0100, Keir Fraser wrote:
> On 22/10/07 20:52, "Trammell Hudson" <hudson@xxxxxxxxxxxxxx> wrote:
> > I've masked all events and the pending field in the shared_info
> > structure is zero.  There are no waiting characters in the incoming
> > xen_console->in_prod array.
> 
> Perhaps the page you think is shared_info isn't really? If Xen is calling
> you back repeatedly then it thinks events are pending.

That was it!  I had misunderstood the comment in the start_info
structure in xen.h:

    unsigned long shared_info;  /* MACHINE address of shared info struct. */
    xen_pfn_t store_mfn;        /* MACHINE page number of shared page.    */

I thought that the store_mfn was the machine page number for the
shared info structure and had used that as my xen_shared_info
pointer.  Mapping the address pointed to by shared_info instead
makes it work perfectly.

Now my kernel transfers into the user code and faults as expected.

Thank you!

-- Trammell

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

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