From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ritu kaur Subject: Re: domU guest for xcp 0.1.1 Date: Tue, 13 Apr 2010 15:06:16 -0700 Message-ID: References: <20100331143913.GL1878@reaktio.net> <20100405170013.GA16921@phenom.dumpdata.com> <20100406060337.GQ1878@reaktio.net> <20100412140432.GA28403@phenom.dumpdata.com> <1271147680.7293.282.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0276603144==" Return-path: In-Reply-To: <1271147680.7293.282.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "xen-devel@lists.xensource.com" , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org --===============0276603144== Content-Type: multipart/alternative; boundary=000e0cd1b5d47e679104842578ba --000e0cd1b5d47e679104842578ba Content-Type: text/plain; charset=ISO-8859-1 Thanks Ian, I don't have the list. I looked into http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Fjeremy%2Fxen.git&a=search&h=xen%2Fstable-2.6.32.x&st=commit&s=shared I see couple of fixes that were committed for shared interrupts + passthrough. I am not sure however it is confined to those commits. If I can get a list of commits to fix shared interrupts I can take a look at patching those into xcp source. Thanks On Tue, Apr 13, 2010 at 1:34 AM, Ian Campbell wrote: > 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 > > 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. > > > > > --000e0cd1b5d47e679104842578ba Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks Ian, I don't have the list. I looked into

http://git= .kernel.org/?p=3Dlinux%2Fkernel%2Fgit%2Fjeremy%2Fxen.git&a=3Dsearch&= ;h=3Dxen%2Fstable-2.6.32.x&st=3Dcommit&s=3Dshared

I see couple of fixes that were committed for shared interrupts + passt= hrough. I am not sure however it is confined to those commits. If I can get= a list of commits to fix shared interrupts I can take a look at patching t= hose into xcp source.

Thanks

On Tue, Apr 13, 2010 at 1:34 A= M, Ian Campbell <Ian.Campbell@citrix.com> wrote:
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<= br> > 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<= br> > familiar with 2.6.27 code either but thought I could learn along with<= br> > this.
>
> Thanks
>
> On Mon, Apr 12, 2010 at 7:04 AM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> =A0 =A0 =A0 =A0 On Sun, Apr 11, 2010 at 10:11:40AM -0700, Ritu kaur wr= ote:
> =A0 =A0 =A0 =A0 > Hello
> =A0 =A0 =A0 =A0 >
>
> =A0 =A0 =A0 =A0 > Any inputs on backporting changes to xcp 2.6.27 s= ource?
>
>
> =A0 =A0 =A0 =A0 I've haven't looked at the 2.6.27 source (don&= #39;t have the
> =A0 =A0 =A0 =A0 time).
> =A0 =A0 =A0 =A0 The back-port might be as easy as just plucking in two= or
> =A0 =A0 =A0 =A0 three
> =A0 =A0 =A0 =A0 lines of code that pass in the
> =A0 =A0 =A0 =A0 BIND_PIRQ__WILL_SHARE flag to the EVTCHNOP_bind_pirq > =A0 =A0 =A0 =A0 hypercall.
>
> =A0 =A0 =A0 =A0 But .. it might be much more complex where you will ne= ed to
> =A0 =A0 =A0 =A0 backport the
> =A0 =A0 =A0 =A0 drivers/xen/events.c framework.
>
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > In addition, I had another question. I believe > =A0 =A0 =A0 =A0 pci-passthrough works for
> =A0 =A0 =A0 =A0 > pci-e slots as well. I have not tested it just wa= nted to
> =A0 =A0 =A0 =A0 check if any
> =A0 =A0 =A0 =A0 > additional config changes are needed to make it w= ork?
>
>
> =A0 =A0 =A0 =A0 Yes. It should work.
>



--000e0cd1b5d47e679104842578ba-- --===============0276603144== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0276603144==--