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] domU guest for xcp 0.1.1

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] domU guest for xcp 0.1.1
From: Ritu kaur <ritu.kaur.us@xxxxxxxxx>
Date: Mon, 12 Apr 2010 15:14:24 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 12 Apr 2010 15:15:12 -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:received:message-id:subject:from:to:cc:content-type; bh=iI10yKndEcwKxF1hBRTl+m2+t+nlUWNIdLQ1pdDBbq8=; b=SGYzXimFjDjNN1QmO3uex8WA6gtiJHOxDMq6h0QPze0JbJk5pChhZxPKKyh0ie/A9f hrZ6mi3ZV3AJ/CFA7Bvlw1GbTFy1FMyBnz2XCJ9XiCrlKaS1uD1nh+NIJsSXI3egopIA w5Yt+R2JbBn0iXjQFyv8FxXM3HYB9D/+VWros=
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; b=qh9f35ZcEwDSe8HtltzIMv+97iVKMXnaRQ9DpvQVnDCALAC1dbJs2f2Wv06nGRyNzY EfbSUTDDNUktbDag0zz0BlsGHWh2HEUTKhJOF8y0HKTZ3lUgsNVvf0LUJzEmbycaysIy I8pSCeIOn6dB9ewgH+DreCEN14nfqS6VP5WJg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100412140432.GA28403@xxxxxxxxxxxxxxxxxxx>
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> <v2x29b32d341004010548y80eb3c5bxe83b328001da9a85@xxxxxxxxxxxxxx> <j2z29b32d341004050710w997a9f8aka0b44c309e080620@xxxxxxxxxxxxxx> <20100405170013.GA16921@xxxxxxxxxxxxxxxxxxx> <g2p29b32d341004052100ja56a4fi7967fa4dcc65462e@xxxxxxxxxxxxxx> <20100406060337.GQ1878@xxxxxxxxxxx> <l2h29b32d341004060631v5e8447d6h98acea18b461f32@xxxxxxxxxxxxxx> <h2x29b32d341004090853q7f2be5c9l2b42880dc40ffe21@xxxxxxxxxxxxxx> <s2m29b32d341004111011sf84c9b6el54ede417b8458cfe@xxxxxxxxxxxxxx> <20100412140432.GA28403@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thanks Konrad. The reason I am asking is if it is feasible and doable in a reasonable amount of time(2 ~ 3 weeks of development/testing) I can check with my boss if I could volunteer to do this work. I am not familiar with 2.6.27 code either but thought I could learn along with this.

Thanks

On Mon, Apr 12, 2010 at 7:04 AM, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:
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
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel