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 help

To: Derek Riley <derek.riley@xxxxxxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Xen help
From: George Dunlap <dunlapg@xxxxxxxxx>
Date: Wed, 12 Aug 2009 11:00:44 +0100
Cc:
Delivery-date: Wed, 12 Aug 2009 03:01:14 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=Ozm/+IEA7ybIGX6xrnZ8L/c/+I5kU9Jx8KHp8UA1OAg=; b=qNmj3lkQuXZisp2zINR/cCdubdDT1IL7DzbEwn1NR3wNJslgJeqXW6S27qC9cp8tFY SQFxShzViDfIVASaiDowivYrB/NuCbch9KjFS4HxIF+BqjPHISb1q+s+BJWsK4ERZkVV HPF05fQ8zfrQcbxgoZIfUmp/k4ESRSN4Dh65A=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=Nnou7INQ/qKxhM10EypMt5qJPeq4mDU92JhfR2/7huSak6VdyVrirSOmEgIb/YmgPe uAYhxRjjYpkjgnbE/FwhzzAQzldjn0BlMGOVQvA7iMNEQZaVowAblZU+7AiYqJanxwgE lToPI+1/iAoahr0m9PSmFVyyOWpfn/PgYmzBc=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <e314beff0908110655o62086e1evf40f2cc0e0521904@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/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: <e314beff0908100648k3bc91bbk604daa604ba869e0@xxxxxxxxxxxxxx> <add59a3f0908100658x263ddebau35fe23512b9366bc@xxxxxxxxxxxxxx> <e314beff0908100700n3995b9anbd281e188cc83ccf@xxxxxxxxxxxxxx> <de76405a0908110332m6140fef9ob12649f0c69d87ae@xxxxxxxxxxxxxx> <e314beff0908110655o62086e1evf40f2cc0e0521904@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, Aug 11, 2009 at 2:55 PM, Derek
Riley<derek.riley@xxxxxxxxxxxxxxxxxxx> wrote:
> To re-iterate what I posted, xentrace appears to be a 1-way communication
> mechanism that goes the "wrong way" for what I need.  I need to be able to
> pass information from the user space to the Xen scheduler, and Xentrace does
> just the opposite.

Sure, xentrace copies data from the hypervisor and writes it to a
file.  But the same basic technique can be turned around: you can
write a new interface so that a program in dom0 can read data from a
file and feed it into the hypervisor, to be read by (if I recall
correctly) your new scheduler feature.

So, how might you adapt the basic technique xentrace uses to put stuff
into the hypervisor instead of taking out out of the hypervisor?

 -George

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

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