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

[Xen-devel] Re: [Qemu-devel] [RfC / Patch] xenner: event channel impleme

To: Avi Kivity <avi@xxxxxxxxxx>
Subject: [Xen-devel] Re: [Qemu-devel] [RfC / Patch] xenner: event channel implementation.
From: Gerd Hoffmann <kraxel@xxxxxxxxxx>
Date: Tue, 28 Apr 2009 17:00:55 +0200
Cc: Xen Development Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>, "qemu-devel@xxxxxxxxxx" <qemu-devel@xxxxxxxxxx>
Delivery-date: Tue, 28 Apr 2009 08:01:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49EF4485.4080700@xxxxxxxxxx>
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: <49EF1EE6.5080900@xxxxxxxxxx> <49EF4485.4080700@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090324 Fedora/3.0-2.1.beta2.fc11 Thunderbird/3.0b2
On 04/22/09 18:23, Avi Kivity wrote:
Gerd Hoffmann wrote:
The function calls in the source code (xen backend drivers) are not
changed directly, but using a include file with a bunch of #defines.
That way I don't have to change s/xc_evtchn_/xc_evtchn./ all over the
place. Also xenner can easily be disabled at compile time and the
indirect function pointer calls simply go away then.

I don't think the last bit is worthwhile. Function pointers these days
are pretty fast, their cost will be dwarfed by the syscall and hypercall
overhead.

New revision of the patch.

- --disable-xen) xen="no"
+ --disable-xen) xen="no"; xenner="no"

It would be nice to be able to build without the original Xen libraries.

Planned for. Will not work (yet) though as I'll have to emulate all xen bits, and the event channels are only a part of the whole story.

Curious, can there be any domain other than the guest and the fake dom0
you're emulating?

Simplified that.

cheers,
  Gerd

Attachment: 0001-xenner-event-channel-implementation.patch
Description: Text document

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