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/
Home Products Support Community News


Re: [Xen-devel] domU guest for xcp 0.1.1

To: Ritu kaur <ritu.kaur.us@xxxxxxxxx>
Subject: Re: [Xen-devel] domU guest for xcp 0.1.1
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Mon, 12 Apr 2010 10:04:32 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 12 Apr 2010 07:06:53 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <s2m29b32d341004111011sf84c9b6el54ede417b8458cfe@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: <20100331143913.GL1878@xxxxxxxxxxx> <h2i29b32d341003311410j6ce550c5k325b9707c6e66cc0@xxxxxxxxxxxxxx> <v2x29b32d341004010548y80eb3c5bxe83b328001da9a85@xxxxxxxxxxxxxx> <j2z29b32d341004050710w997a9f8aka0b44c309e080620@xxxxxxxxxxxxxx> <20100405170013.GA16921@xxxxxxxxxxxxxxxxxxx> <g2p29b32d341004052100ja56a4fi7967fa4dcc65462e@xxxxxxxxxxxxxx> <20100406060337.GQ1878@xxxxxxxxxxx> <l2h29b32d341004060631v5e8447d6h98acea18b461f32@xxxxxxxxxxxxxx> <h2x29b32d341004090853q7f2be5c9l2b42880dc40ffe21@xxxxxxxxxxxxxx> <s2m29b32d341004111011sf84c9b6el54ede417b8458cfe@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
On Sun, Apr 11, 2010 at 10:11:40AM -0700, Ritu kaur wrote:
> Hello
> Any inputs on backporting changes to xcp 2.6.27 source?

I've haven't looked at the 2.6.27 source (don't have the time).
The back-port might be as easy as just plucking in two or three
lines of code that pass in the
BIND_PIRQ__WILL_SHARE flag to the EVTCHNOP_bind_pirq hypercall.

But .. it might be much more complex where you will need to backport the
drivers/xen/events.c framework.

> In addition, I had another question. I believe pci-passthrough works for
> pci-e slots as well. I have not tested it just wanted to check if any
> additional config changes are needed to make it work?

Yes. It should work.

Xen-devel mailing list