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] pci-passthrough and shared interrupts

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] pci-passthrough and shared interrupts
From: Ritu kaur <ritu.kaur.us@xxxxxxxxx>
Date: Fri, 1 Oct 2010 08:36:03 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 01 Oct 2010 08:36:58 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=mrdiV84XFdTVDwzuITKJ9M7a35N69KAOADEIn57USKk=; b=Kqm0e7T378CuRjexEIEq7SSUhVu77tFxNxIul9HoSGG5B4jSxl7Nc7x+EivRYwnXX0 9AKJ5v91lSkf3w94Iopzlv7XP6bj5FaPUaBUijuXfO/L2TDaNCyAFQO8dOhWAnqUE3yP 4n0ekWeHou3yshp/um381H4fk03i+F9C/BMHw=
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=EiRz86ojSW7QwbXcZZVZeyMRHnPWNtlSg5+XOk8cMMZNhu2Hwdegmp8J/C7LNdLQgT V6UCs9eJnWwAVzR0CLdhtnKt4XIg49SbxENh8JdVR4+uYHSDGBPeEFYvDcZt14f4Xwzq U63xZK1up9wkypUA5LkRjIASNIkGyAFA/yPSQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20101001134529.GA28639@xxxxxxxxxxxx>
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: <AANLkTin8j7gFkt3x_+QFrJJ+iaP7dk2q6RH5Sm8aoa1Q@xxxxxxxxxxxxxx> <20100825223415.GA6326@xxxxxxxxxxxxxxxxxxx> <AANLkTim_Fn8ZMHvtVBLz453cC+C7g0pqMKKj7MS_kLAm@xxxxxxxxxxxxxx> <20100825234330.GA6588@xxxxxxxxxxxxxxxxxxx> <AANLkTi=vYDh0XoMo9p9e+2P+sVbqH5q+RJzpYB0E+vuV@xxxxxxxxxxxxxx> <20100827140347.GA4454@xxxxxxxxxxxxxxxxxxx> <AANLkTi=_m-=WDFSd3imunXAVUsYn2B1_rvCGyOrjDOKb@xxxxxxxxxxxxxx> <20101001134529.GA28639@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Konrad,

Frankly, I am confused. XCP(which is similar to Citrix Xenserver but open-source and newer-kernel) requires DDK to build a kernel image. If I understand your suggestion correctly I should be able to

1. Take PVOPS kernel code, compile it in XCP DDK and load it into dom0
2. Take PVOPS kernel code, compile it in domU OS and load it into domU

then, I should be able to get pci-passthrough + shared interrupts between devices working correctly?  Please clarify/confirm

Thanks

On Fri, Oct 1, 2010 at 6:45 AM, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:
On Wed, Sep 29, 2010 at 07:14:11PM -0700, Ritu kaur wrote:
> Konrad/All,
>
> I have been asked to look into the option of using pvops kernel(which do not
> have pci-passthrough + shared interrupts issue) and needed some inputs

I think you are confused. The PVOPS kernel does have all these patches..
>
> 1. Does pvops run on Fedora Core or any specific distributions I need to
> use?
> 2. Does it have some form of gui interface to control/manage domU's

PVOPS is the *kernel*. Nothing else. You should be able to take, say XCP,
and replace the kernel with the PVOPS kernel if you want too.


>
> Inputs/Pointers much appreciated.
>
> Thanks
>
> On Fri, Aug 27, 2010 at 7:03 AM, Konrad Rzeszutek Wilk <
> konrad.wilk@xxxxxxxxxx> wrote:
>
> > On Thu, Aug 26, 2010 at 03:58:15PM -0700, Ritu kaur wrote:
> > > Thanks Konrad,
> > >
> > > I went to git repository for xen/next and found following two fixes for
> > > shared irq
> > > *2010-03-08* Weidong
> > > Han<
> > http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=search;h=xen/next;s=Weidong+Han;st=author
> > >xen/apic:
> > > fix shared irq device passthrough
> > > <
> > http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=c7e3389a39a2404106a6808cca7ff698427f5f8f
> > >xen/apic:
> > > fix shared irq device passthrough
> > > commit<
> > http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=c7e3389a39a2404106a6808cca7ff698427f5f8f
> > >|
> > > commitdiff<
> > http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commitdiff;h=c7e3389a39a2404106a6808cca7ff698427f5f8f
> > >|
> > > tree<
> > http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=tree;h=66e1c9a1f8d27fe5fbcba84c303aff30f347fa99;hb=c7e3389a39a2404106a6808cca7ff698427f5f8f
> > >
> > > *2010-03-02* Konrad Rzeszutek...
> > > <
> > http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=search;h=xen/next;s=Konrad+Rzeszutek+Wilk;st=author
> > >xen/apic:
> > > fix shared irq device passthrough
> > > <
> > http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=a18fb8d2cb74868917da047ab6cc076b3773bae2
> > >xen/apic:
> > > fix shared irq device passthrough
> > > commit<
> > http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=a18fb8d2cb74868917da047ab6cc076b3773bae2
> > >|
> > > commitdiff<
> > http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commitdiff;h=a18fb8d2cb74868917da047ab6cc076b3773bae2
> > >|
> > > tree<
> > http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=tree;h=725a6938f301670d172fbed53995fe2a5e7c4765;hb=a18fb8d2cb74868917da047ab6cc076b3773bae2
> > >
> >
> > You also need the patches in the drivers/xen/pciback directory.
> >
> > Jeremy has been pulling those out of my git tree:
> > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.gitpv/pciback-2.6.32
> > >
> > > I believe these are the only changes I need to backport to xcp?
> > >
> > > Regarding the nic, it was just a clarification I needed. Its a regular
> > 10G
> > > nic which is being co-developed along with qlogic.
> >
> > Don't worry about it. It will do MSIs.
> >

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel