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] Root filesystem access from Xen Hypervisor

To: Tej <bewith.tej@xxxxxxxxx>
Subject: Re: [Xen-devel] Root filesystem access from Xen Hypervisor
From: "George Dunlap" <George.Dunlap@xxxxxxxxxxxxx>
Date: Fri, 14 Nov 2008 14:58:11 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 14 Nov 2008 06:58:41 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=Houqn7a/qbb/qQl2FkZ+4e5thA1eID6u+6TbnZvjcIg=; b=w81pv/i7EtHuh2zfn+EBw1+lxaXMfgGjsLMLZjTkeT4UviMKcTLpVFDbxY8Ox7difE S16hIotkGgIKMmYOxeOMvrcew90RKKUvWBLe8c3+nSuVDgsCfhogEbqRT1JM7d5kbQiS irornp2naKhCDP0RmY43ik7Cq5MFb74FQJyGk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=k22Ctj1fOecowRKuXAJ8diJ/YyAzScix8mQY6c6n9mRec651TImcnk2I6ZzTDA5rM+ q76zFa00ezhP28lULGvgriyu0zGqPHTFYKBXr2dfDNZ/4+FCdQC1Jiav+YhQxfl3Z1r6 47cdFGEstakN2l36lAC5+tdQ/xdK8AecWt1A4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <f1c9d250811140415t2cf173d1gca79f47f3acd55e2@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: <f1c9d250811140345s376fc76v639cd1a587ba29f7@xxxxxxxxxxxxxx> <de76405a0811140406q32fc54d9w5a0f4dd7adbb2642@xxxxxxxxxxxxxx> <f1c9d250811140415t2cf173d1gca79f47f3acd55e2@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
If you want to export data out of the hypervisor, the easiest thing to
do is set up a shared memory mechanism.  Look at xen/common/trace.c
and tools/xentrace/xentrace.c for one simple xen-to-userspace example.

Hmm... if you want to reuse as much of the interface as possible,
you'll probably need to make a Linux kernel module that implements
/proc/gcov-xen.  The hypervisor can write usage data to the shared
page(s), and the kernel module can read it, interpret it, and make the
/proc files based on it.

For a sample of how to use xen-to-kernel shared memory, you can look
at xenoprofile; but be warned that it's suffering some bitrot.

Let me know how you fare -- it seems like an interesting project.

 -George

On Fri, Nov 14, 2008 at 12:15 PM, Tej <bewith.tej@xxxxxxxxx> wrote:
> On 11/14/08, George Dunlap <dunlapg@xxxxxxxxx> wrote:
>> /proc is owned by the Linux Kernel; Xen has no filesystem code in it.
>>
>> What is it you're trying to do?
>
> i am trying to port the gcov for XEN HYpervisor. I could able to
> create profiling info but i could not able to populate filesystem for
> profiling purpose.
>
>
>>
>>  -George
>>
>> On Fri, Nov 14, 2008 at 11:45 AM, Tej <bewith.tej@xxxxxxxxx> wrote:
>>> Can we Access the root filesystem from Xen Hypervisor Code.
>>> e.g creating dir at /proc
>>>
>>>
>>> Any pointers will be useful.
>>>
>>>
>>> thanks
>>> -tej
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-devel
>>>
>>
>

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

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