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] [PATCH] /sys/hypervisor/uuid

To: "Jeremy Katz" <katzj@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid
From: "Christian Limpach" <christian.limpach@xxxxxxxxx>
Date: Mon, 22 May 2006 09:33:12 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 22 May 2006 01:33:36 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=a+qDSQkGuFE7aKG4qLVpzqJbx06x+v66uWLo9HAJg+zSgOgTFvFEKPou1oXpOYPYcJ0sYCPMpl8HNbowABsfgHkGNotn68JlqzroFgUl0AogZYMC66E4hIrrPkdwx/AOXskjHNO3aNYyxZpCjIQnHX7DmAnrE/xmZCdKwiB3VAg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1148059480.9927.27.camel@xxxxxxxxxxxxxx>
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: <87y7wzmeqb.fsf@xxxxxxxxxxxxxxxxx> <a74fd46bb61fffb16ab812859d83d8e8@xxxxxxxxxxxx> <20060519074112.GF2724@xxxxxxxxxxxxxxxxx> <3d8eece20605190243v626b894bp1f5e6f4ff23e56d1@xxxxxxxxxxxxxx> <1148057026.9927.22.camel@xxxxxxxxxxxxxx> <3d8eece20605191001u2f9a53afha5a56c72123b8d09@xxxxxxxxxxxxxx> <1148059480.9927.27.camel@xxxxxxxxxxxxxx>
Reply-to: Christian.Limpach@xxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 5/19/06, Jeremy Katz <katzj@xxxxxxxxxx> wrote:
> Let me copy/paste from my previous message you replied to and quoted:
> it was only added to support driver domains getting information about
> the devices to configure.

But isn't the device configuration there happening from the kernel?
I'll admit I haven't played with getting any of the device passthrough
stuff going since those patches went in.  I'm just not clear on what
benefit having userspace being able to frob at xenstore from domU really
has.  And in any case, getting it upstream is going to be an uphill
battle at best

For some of the device setup, it is more flexible if it happens in
userspace.  For example, figuring out what device a given name
corresponds too (needs lookup in /dev) or binding a loop device for a
file backed vbd.

Instead of inventing yet another interface for the kernel to
communicate with our hotplug scripts (and back), we decided to use


Xen-devel mailing list