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. > > > > >