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 IPC

To: Derek Riley <derek.riley@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen IPC
From: George Dunlap <dunlapg@xxxxxxxxx>
Date: Thu, 6 Aug 2009 15:20:48 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 06 Aug 2009 07:21:16 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=8dJwr9PIw1gPbjBEbWGF6aNglxx8k6G8ocCtdq+uyIA=; b=wSvD8Ee3WkGrJgI56JNk0Dq99Ealk7b5RFDmDpSJF2KEnxxZr5iP4GhOtMzj/LU2pL +KjBKfXXKURFGKo7+XHXRPzWQhaSJybVR8ijYFRX7CTlLKUzSz2pcvcK4NnEnNzImRlG vaSy3jnQFk5NfrJBBner08Zbi+hD9GU8inJM8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Gz93ubhAo8INw8PvSV8tLt0mrTolngiKjnYixKnwt6kwQSUQbo7BtBfo/tUhsTj/sv vKACU/U/Ynlj/eEWmzUdL5YnO1rABhSe17GjaXtKH74qNH5euG9FkegEE7gq1K/KXHEr bzONlAZeBv8HJ7mt3OHkc+t7E1s/hb2Oo0f8c=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <e314beff0908060704s58b17f2av2df67ae2d6cbcce@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: <e314beff0907310939n588b8dc9w683f9d6a06dff9aa@xxxxxxxxxxxxxx> <de76405a0908031017q4003c92ao3582e21a239daed6@xxxxxxxxxxxxxx> <e314beff0908060701of43c2f2t9ebd3aa2cc31b79f@xxxxxxxxxxxxxx> <e314beff0908060704s58b17f2av2df67ae2d6cbcce@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I'm afraid the only documentation is the source code itself.  Look in
tools/xentrace.c, and xen/common/trace.c.  The basic idea is that the
page is a ring buffer with producer and consumer pointers.  Xen always
writes a record, then updates the producer; xentrace always reads a
record, then updates the consumer.  If incrementing the producer would
clobber a consumer, then Xen just drops the trace record.

Good luck,
 -George

On Thu, Aug 6, 2009 at 3:04 PM, Derek
Riley<derek.riley@xxxxxxxxxxxxxxxxxxx> wrote:
>
>
> On Thu, Aug 6, 2009 at 9:01 AM, Derek Riley
> <derek.riley@xxxxxxxxxxxxxxxxxxx> wrote:
>>
>> Thanks for your response.  I am working with the Xen Hypervisor, but I am
>> not familiar with xentrace.  I found some information about it through
>> google searches, but I was unable to discover how it uses the shared page
>> you mentioned.  Do you have any links to point me in the right direction?
>> Thanks
>> --Derek
>>
>> On Mon, Aug 3, 2009 at 12:17 PM, George Dunlap
>> <George.Dunlap@xxxxxxxxxxxxx> wrote:
>>>
>>> Derek,
>>>
>>> I assume you mean "Xen Hypervisor" (as the kernel would be probably
>>> Linux dom0 kernel)?
>>>
>>> You might look at the xentrace mechanism for using a shared page to
>>> pass information out of Xen.  You could probably adapt the same idea
>>> to pass information into Xen if you needed to.
>>>
>>>  -George
>>>
>>> On Fri, Jul 31, 2009 at 5:39 PM, Derek
>>> Riley<derek.riley@xxxxxxxxxxxxxxxxxxx> wrote:
>>> > Hello-
>>> > I am working on a project to modify Xen to precisely control the
>>> > execution
>>> > times of the individual guest domains, and I need some help.  I
>>> > considered
>>> > modifying the XM python program, but it is not precise or fast enough
>>> > for my
>>> > application.
>>> >
>>> > I want to be able to pass short, simple message quickly between an
>>> > application-level process and the Xen kernel asynchonously.  I found an
>>> > IPC
>>> > mechanism designed for the method called netlink
>>> > (http://www.linuxjournal.com/article/7356), but I am not sure how to
>>> > incorporate it into the Xen kernel.  When I attempt to recompile the
>>> > kernel
>>> > with netlink, I get errors that seem to stem from type issues I am not
>>> > familiar with.
>>> >
>>> > 2 questions:
>>> > Is it possible to use a mechanism such as netlink with Xen?  If so,
>>> > how?
>>> > Is there other functionality within Xen that could be used with minimal
>>> > modification to do IPC within domain0?
>>> >
>>> > Any help/advice would be greatly appreciated.  Thanks!
>>> > --Derek
>>> > _______________________________________________
>>> > 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
>
>

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

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