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] Xen with dom0 pvops on ultra-recent "git tip" kernel on

To: Christophe Saout <christophe@xxxxxxxx>
Subject: Re: [Xen-devel] Xen with dom0 pvops on ultra-recent "git tip" kernel on x86_64
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Fri, 16 Jan 2009 09:23:51 -0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 16 Jan 2009 09:24:18 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1231865847.5257.8.camel@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>
References: <49690103.5020706@xxxxxx> <1231619339.5616.15.camel@xxxxxxxxxxxxxxxxxxxx> <20090110203706.GW15052@xxxxxxxxxxxxxxx> <1231622029.4778.1.camel@xxxxxxxxxxxxxxxxxxxx> <1231683478.4809.43.camel@xxxxxxxxxxxxxxxxxxxx> <1231685561.4809.50.camel@xxxxxxxxxxxxxxxxxxxx> <1231691732.5342.3.camel@xxxxxxxxxxxxxxxxxxxx> <1231769868.4838.4.camel@xxxxxxxxxxxxxxxxxxxx> <1231778480.4742.3.camel@xxxxxxxxxxxxxxxxxxxx> <1231838888.4823.5.camel@xxxxxxxxxxxxxxxxxxxx> <20090113153302.GZ15052@xxxxxxxxxxxxxxx> <1231864918.5257.6.camel@xxxxxxxxxxxxxxxxxxxx> <1231865847.5257.8.camel@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.19 (X11/20090105)
Christophe Saout wrote:
Hello,

The X server crashes in some I/O port "inb()" command.  Seems like the
io permissions aren't correctly passed through or something. (iopl or
ioperm or so)  I'll try to debug a bit more later.

The native Xen kernel has an arch/x86/kernel/ioport-xen.c which calls:

        HYPERVISOR_physdev_op(PHYSDEVOP_set_iobitmap, &set_iobitmap);

Is this a feature mabye still missing from the paravirtualized Xen?

If yes, what would it take?  A new paravirt call?

Hi Christophe,

Firstly, thanks a lot for trying out the pvops dom0 and doing so much debugging on it. I'm still catching up on my rather daunting email backlog - including your torrent of messages - so feel free to remind me about/resent anything important which still needs looking at.

I haven't been brave enough to even attempt starting X; there's a lot of work to be done if you want to do anything beyond dumb framebuffer.

Anyway, in this case, I definitely haven't added this call, so it will need to be done somewhere. Does it need to be called once at startup, or on every context switch? There may well be a suitable place to hook this into already, but we can add a new pvop if its really needed.

   J

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

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