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

xen-devel

[Top] [All Lists]

Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid

To: Christian.Limpach@xxxxxxxxxxxx
Subject: Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid
From: Jeremy Katz <katzj@xxxxxxxxxx>
Date: 2006年5月19日 13:24:40 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: 2006年5月19日 10:24:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <3d8eece20605191001u2f9a53afha5a56c72123b8d09@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, 2006年05月19日 at 18:01 +0100, Christian Limpach wrote:
> On 5/19/06, Jeremy Katz <katzj@xxxxxxxxxx> wrote:
> > On Fri, 2006年05月19日 at 10:43 +0100, Christian Limpach wrote:
> > > Also, the guest domain xenstore interface was never really intended to
> > > be used in anger, it was only added to support driver domains getting
> > > information about the devices to configure. The immediate issue would
> > > be that access to xenstore is through a file in /proc/xen and I'd
> > > expect that to change at some point. Might be good to already add the
> > > new path to all tools as a fallback option now. Any suggestions for
> > > where this would end up in /sys I presume?
> >
> > Actually, I'd suggest just taking it out and shooting it altogether.
>
> Well, no.
>
> > What was the _intended_ use of having this exposed to the guest,
> > especially given that anything exposed shouldn't be considered a stable
> > ABI/API?
>
> 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.
... one of these days I'll learn to read :-)
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
Jeremy
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid , Markus Armbruster
Next by Date: [Xen-devel] [PATCH] minor tweak to keep network-bridge working in busybox environment , David Lively
Previous by Thread: Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid , Christian Limpach
Next by Thread: Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid , Christian Limpach
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /