 Home |
Products |
Support |
Community |
News |
xen-devel
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: | Fri, 19 May 2006 18:01:22 +0100 |
| Cc: | xen-devel@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | Fri, 19 May 2006 10:01:43 -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=aG/Q91G42twkiTVQGHkLLFIcX6ZXcaNqXPoTb6vFX9XeB7TWELVsW07kO39fjuequug1kiSn2Wtfys+0lI+vk9tuecibCdwYPlltxupab9YUVmHWd2WKb9dMjYRUPeet4uPy3UtJddd8gJV9rzpj4uXAHZdGynaYJ+HRR8rB7so= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| In-reply-to: | <1148057026.9927.22.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> |
| Reply-to: | Christian.Limpach@xxxxxxxxxxxx |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
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.
christian
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
| Previous by Date: | Re: [Xen-devel] SEDF Scheduler slice time fix, Keir Fraser |
|---|---|
| Next by Date: | Re: [Xen-devel] [PATCH] Make "xm mem-set" be lower bound on domX-min-mem, Gareth S Bestor |
| Previous by Thread: | Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid, Jeremy Katz |
| Next by Thread: | Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid, Jeremy Katz |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
