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: Ritu kaur <ritu.kaur.us@xxxxxxxxx>
Subject: Re: [Xen-devel] domU guest for xcp 0.1.1
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Tue, 13 Apr 2010 09:34:40 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Tue, 13 Apr 2010 01:35:35 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <y2h29b32d341004121514lb8463894i6603892cf173978f@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>
Organization: Citrix Systems, Inc.
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> <y2h29b32d341004121514lb8463894i6603892cf173978f@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Backporting is usually pretty easy but it does somewhat depend on the
scope of the changesets you are backporting, do you have a list?

Please try and pickup complete upstream commits and include them in the
relevant place within the 2.6.27 patch queue (either the "Patches from
Linux Torvalds linux-2.6.git tree" or "Patches from xen.git" section I
guess) and sort plus name the patches as described in the section
headers.

Ian.

On Mon, 2010-04-12 at 23:14 +0100, Ritu kaur wrote:
> 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