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/
Home Products Support Community News


Re: [Xen-devel] Re: [Xen-changelog] [xen-unstable] Clean up handling of

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-changelog] [xen-unstable] Clean up handling of IS_PRIV_FOR() and rcu_[un]lock_domain().
From: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>
Date: Sat, 5 Apr 2008 16:28:14 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 05 Apr 2008 07:29:29 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C413DCED.1587C%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/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>
Mail-followup-to: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
References: <20080329112316.GC4482@implementation> <C413DCED.1587C%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.12-2006-07-14

Keir Fraser, le Sat 29 Mar 2008 11:47:57 +0000, a écrit :
> > IIRC the event channel ops are not needed right now, but will probably
> > be in the future.
> They were all fine, except there was one inexplicable check of IS_PRIV_FOR()
> in bind_interdomain() which I nuked. It was so bizarre that I assumed you
> must have put it there for a reason, and this would be one that you'd
> complain about.

I'm now complaining :)

The bind_interdomain() trick is needed for the ioreq events channel:
when it gets installed, it is supposed to be between the HVM domain and
dom0 (the stub domain doesn't exist anyway).  The meaning of the test is
hence to allow the stub domain to hijack that event channel (because it
has privileges on the remote domain).

With that fix, stub domains are working again (but Cirrus bios doesn't
work yet)


Xen-devel mailing list