pci-passthrough and shared interrupts

pci-passthrough and shared interrupts

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 552 bytes --]

Hello,

Couple of months back when we were testing xcp 0.1.1 and pci passthrough we
ran into issues when pci-passthrough enabled device shared interrupts with
another controller(in our case interrupt was shared between ide controller
and our nic). At that time Ian Campbell suggested backporting event-channel
changes from pvops to 2.6.27 kernel. Have two questions related to this

1. I am thinking of porting the changes now but wanted to check if it has
been addressed?

2. Will shared interrupts be a problem for pci-e slots as well?

Thanks
-Ritu

[-- Attachment #1.2: Type: text/html, Size: 590 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: pci-passthrough and shared interrupts

[Konrad Rzeszutek Wilk]

On Wed, Aug 25, 2010 at 03:17:29PM -0700, Ritu kaur wrote:
> Hello,
> 
> Couple of months back when we were testing xcp 0.1.1 and pci passthrough we
> ran into issues when pci-passthrough enabled device shared interrupts with
> another controller(in our case interrupt was shared between ide controller
> and our nic). At that time Ian Campbell suggested backporting event-channel
> changes from pvops to 2.6.27 kernel. Have two questions related to this
> 
> 1. I am thinking of porting the changes now but wanted to check if it has
> been addressed?

I've added some patches in the pvops tree that make this work. You would
essentially have to backport the pciback driver to the XCP
infrastructure. And you might have to backport the event channels as
well, not sure about that.
> 
> 2. Will shared interrupts be a problem for pci-e slots as well?

No.
> 
> Thanks
> -Ritu

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

Re: pci-passthrough and shared interrupts

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 1408 bytes --]

Thanks Konrad. Additional Q below

On Wed, Aug 25, 2010 at 3:34 PM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:

> On Wed, Aug 25, 2010 at 03:17:29PM -0700, Ritu kaur wrote:
> > Hello,
> >
> > Couple of months back when we were testing xcp 0.1.1 and pci passthrough
> we
> > ran into issues when pci-passthrough enabled device shared interrupts
> with
> > another controller(in our case interrupt was shared between ide
> controller
> > and our nic). At that time Ian Campbell suggested backporting
> event-channel
> > changes from pvops to 2.6.27 kernel. Have two questions related to this
> >
> > 1. I am thinking of porting the changes now but wanted to check if it has
> > been addressed?
>
> I've added some patches in the pvops tree that make this work. You would
> essentially have to backport the pciback driver to the XCP
> infrastructure. And you might have to backport the event channels as
> well, not sure about that.
>

 I will take a look at the patches.

> >
> > 2. Will shared interrupts be a problem for pci-e slots as well?
>
> No.
>

So if I have XCP + NIC installed in pci-e slot and interrupts shared with
another device, pci passthrough should work fine, is this correct?

Thanks
-Ritu

>
>


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

[-- Attachment #1.2: Type: text/html, Size: 2454 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: pci-passthrough and shared interrupts

[Konrad Rzeszutek Wilk]

On Wed, Aug 25, 2010 at 03:48:35PM -0700, Ritu kaur wrote:
> Thanks Konrad. Additional Q below
> 
> On Wed, Aug 25, 2010 at 3:34 PM, Konrad Rzeszutek Wilk <
> konrad.wilk@oracle.com> wrote:
> 
> > On Wed, Aug 25, 2010 at 03:17:29PM -0700, Ritu kaur wrote:
> > > Hello,
> > >
> > > Couple of months back when we were testing xcp 0.1.1 and pci passthrough
> > we
> > > ran into issues when pci-passthrough enabled device shared interrupts
> > with
> > > another controller(in our case interrupt was shared between ide
> > controller
> > > and our nic). At that time Ian Campbell suggested backporting
> > event-channel
> > > changes from pvops to 2.6.27 kernel. Have two questions related to this
> > >
> > > 1. I am thinking of porting the changes now but wanted to check if it has
> > > been addressed?
> >
> > I've added some patches in the pvops tree that make this work. You would
> > essentially have to backport the pciback driver to the XCP
> > infrastructure. And you might have to backport the event channels as
> > well, not sure about that.
> >
> 
>  I will take a look at the patches.
> 
> > >
> > > 2. Will shared interrupts be a problem for pci-e slots as well?
> >
> > No.
> >
> 
> So if I have XCP + NIC installed in pci-e slot and interrupts shared with
> another device, pci passthrough should work fine, is this correct?

Ugh, I am surprised you have that. Most of the time if you do use an NIC
in PCI-e it would be MSI based. An MSI's are never shared.

So if your device is PCIe and you get legacy IRQ that is shared with
another device on your board, then you will need to backport the
'pciback' driver.

What NIC is it that does this?

Re: pci-passthrough and shared interrupts

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 3617 bytes --]

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>

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.

Thanks
-Ritu

On Wed, Aug 25, 2010 at 4:43 PM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:

> On Wed, Aug 25, 2010 at 03:48:35PM -0700, Ritu kaur wrote:
> > Thanks Konrad. Additional Q below
> >
> > On Wed, Aug 25, 2010 at 3:34 PM, Konrad Rzeszutek Wilk <
> > konrad.wilk@oracle.com> wrote:
> >
> > > On Wed, Aug 25, 2010 at 03:17:29PM -0700, Ritu kaur wrote:
> > > > Hello,
> > > >
> > > > Couple of months back when we were testing xcp 0.1.1 and pci
> passthrough
> > > we
> > > > ran into issues when pci-passthrough enabled device shared interrupts
> > > with
> > > > another controller(in our case interrupt was shared between ide
> > > controller
> > > > and our nic). At that time Ian Campbell suggested backporting
> > > event-channel
> > > > changes from pvops to 2.6.27 kernel. Have two questions related to
> this
> > > >
> > > > 1. I am thinking of porting the changes now but wanted to check if it
> has
> > > > been addressed?
> > >
> > > I've added some patches in the pvops tree that make this work. You
> would
> > > essentially have to backport the pciback driver to the XCP
> > > infrastructure. And you might have to backport the event channels as
> > > well, not sure about that.
> > >
> >
> >  I will take a look at the patches.
> >
> > > >
> > > > 2. Will shared interrupts be a problem for pci-e slots as well?
> > >
> > > No.
> > >
> >
> > So if I have XCP + NIC installed in pci-e slot and interrupts shared with
> > another device, pci passthrough should work fine, is this correct?
>
> Ugh, I am surprised you have that. Most of the time if you do use an NIC
> in PCI-e it would be MSI based. An MSI's are never shared.
>
> So if your device is PCIe and you get legacy IRQ that is shared with
> another device on your board, then you will need to backport the
> 'pciback' driver.
>
> What NIC is it that does this?
>

[-- Attachment #1.2: Type: text/html, Size: 5100 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: pci-passthrough and shared interrupts

[Konrad Rzeszutek Wilk]

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.git pv/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.

Re: pci-passthrough and shared interrupts

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 2668 bytes --]

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

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

Inputs/Pointers much appreciated.

Thanks

On Fri, Aug 27, 2010 at 7:03 AM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> 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.
>

[-- Attachment #1.2: Type: text/html, Size: 4861 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: pci-passthrough and shared interrupts

[Pasi Kärkkäinen]

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
> 
>    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
> 
>    Inputs/Pointers much appreciated.
> 

http://wiki.xensource.com/xenwiki/Fedora13Xen4Tutorial

-- Pasi

>    Thanks
> 
>    On Fri, Aug 27, 2010 at 7:03 AM, Konrad Rzeszutek Wilk
>    <[1]konrad.wilk@oracle.com> 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<[2]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
>      >
>      <[3]http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=c7e3389a39a2404106a6808cca7ff698427f5f8f>xen/apic:
>      > fix shared irq device passthrough
>      >
>      commit<[4]http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=c7e3389a39a2404106a6808cca7ff698427f5f8f>|
>      >
>      commitdiff<[5]http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commitdiff;h=c7e3389a39a2404106a6808cca7ff698427f5f8f>|
>      >
>      tree<[6]http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=tree;h=66e1c9a1f8d27fe5fbcba84c303aff30f347fa99;hb=c7e3389a39a2404106a6808cca7ff698427f5f8f>
>      > *2010-03-02* Konrad Rzeszutek...
>      >
>      <[7]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
>      >
>      <[8]http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=a18fb8d2cb74868917da047ab6cc076b3773bae2>xen/apic:
>      > fix shared irq device passthrough
>      >
>      commit<[9]http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=a18fb8d2cb74868917da047ab6cc076b3773bae2>|
>      >
>      commitdiff<[10]http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commitdiff;h=a18fb8d2cb74868917da047ab6cc076b3773bae2>|
>      >
>      tree<[11]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://[12]git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
>      pv/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.
> 
> References
> 
>    Visible links
>    1. mailto:konrad.wilk@oracle.com
>    2. http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=search;h=xen/next;s=Weidong+Han;st=author
>    3. http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=c7e3389a39a2404106a6808cca7ff698427f5f8f
>    4. http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=c7e3389a39a2404106a6808cca7ff698427f5f8f
>    5. http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commitdiff;h=c7e3389a39a2404106a6808cca7ff698427f5f8f
>    6. http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=tree;h=66e1c9a1f8d27fe5fbcba84c303aff30f347fa99;hb=c7e3389a39a2404106a6808cca7ff698427f5f8f
>    7. http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=search;h=xen/next;s=Konrad+Rzeszutek+Wilk;st=author
>    8. http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=a18fb8d2cb74868917da047ab6cc076b3773bae2
>    9. http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=a18fb8d2cb74868917da047ab6cc076b3773bae2
>   10. http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commitdiff;h=a18fb8d2cb74868917da047ab6cc076b3773bae2
>   11. http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=tree;h=725a6938f301670d172fbed53995fe2a5e7c4765;hb=a18fb8d2cb74868917da047ab6cc076b3773bae2
>   12. http://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git

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

Re: pci-passthrough and shared interrupts

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 5196 bytes --]

Thanks Pasi, This is what we need. I will test it out and get back to you
guys with any questions.

Thanks


On Wed, Sep 29, 2010 at 11:01 PM, Pasi Kärkkäinen <pasik@iki.fi> 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
> >
> >    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
> >
> >    Inputs/Pointers much appreciated.
> >
>
> http://wiki.xensource.com/xenwiki/Fedora13Xen4Tutorial
>
> -- Pasi
>
> >    Thanks
> >
> >    On Fri, Aug 27, 2010 at 7:03 AM, Konrad Rzeszutek Wilk
> >    <[1]konrad.wilk@oracle.com> 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<[2]
> 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
> >      >
> >      <[3]
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=c7e3389a39a2404106a6808cca7ff698427f5f8f
> >xen/apic:
> >      > fix shared irq device passthrough
> >      >
> >      commit<[4]
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=c7e3389a39a2404106a6808cca7ff698427f5f8f
> >|
> >      >
> >      commitdiff<[5]
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commitdiff;h=c7e3389a39a2404106a6808cca7ff698427f5f8f
> >|
> >      >
> >      tree<[6]
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=tree;h=66e1c9a1f8d27fe5fbcba84c303aff30f347fa99;hb=c7e3389a39a2404106a6808cca7ff698427f5f8f
> >
> >      > *2010-03-02* Konrad Rzeszutek...
> >      >
> >      <[7]
> 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
> >      >
> >      <[8]
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=a18fb8d2cb74868917da047ab6cc076b3773bae2
> >xen/apic:
> >      > fix shared irq device passthrough
> >      >
> >      commit<[9]
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=a18fb8d2cb74868917da047ab6cc076b3773bae2
> >|
> >      >
> >      commitdiff<[10]
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commitdiff;h=a18fb8d2cb74868917da047ab6cc076b3773bae2
> >|
> >      >
> >      tree<[11]
> 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://[12]git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
> >      pv/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.
> >
> > References
> >
> >    Visible links
> >    1. mailto:konrad.wilk@oracle.com
> >    2.
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=search;h=xen/next;s=Weidong+Han;st=author
> >    3.
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=c7e3389a39a2404106a6808cca7ff698427f5f8f
> >    4.
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=c7e3389a39a2404106a6808cca7ff698427f5f8f
> >    5.
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commitdiff;h=c7e3389a39a2404106a6808cca7ff698427f5f8f
> >    6.
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=tree;h=66e1c9a1f8d27fe5fbcba84c303aff30f347fa99;hb=c7e3389a39a2404106a6808cca7ff698427f5f8f
> >    7.
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=search;h=xen/next;s=Konrad+Rzeszutek+Wilk;st=author
> >    8.
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=a18fb8d2cb74868917da047ab6cc076b3773bae2
> >    9.
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=a18fb8d2cb74868917da047ab6cc076b3773bae2
> >   10.
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commitdiff;h=a18fb8d2cb74868917da047ab6cc076b3773bae2
> >   11.
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=tree;h=725a6938f301670d172fbed53995fe2a5e7c4765;hb=a18fb8d2cb74868917da047ab6cc076b3773bae2
> >   12. http://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
>
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
>

[-- Attachment #1.2: Type: text/html, Size: 9632 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: pci-passthrough and shared interrupts

[Konrad Rzeszutek Wilk]

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@oracle.com> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: pci-passthrough and shared interrupts

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 3996 bytes --]

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@oracle.com> 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@oracle.com> 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@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
>

[-- Attachment #1.2: Type: text/html, Size: 7001 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: pci-passthrough and shared interrupts

[Konrad Rzeszutek Wilk]

On Fri, Oct 01, 2010 at 08:36:03AM -0700, Ritu kaur wrote:
> 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

Yes.

Re: pci-passthrough and shared interrupts

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 1642 bytes --]

Thanks Konrad, I checked my old emails(back in March 2010) to see if I had
tried this combination when I was testing xcp. I did try this combination
and the problem I had faced was configuration errors due to IDE_DISK. I
couldn't get past this problem. Snippets below

/*********************************************************
Thanks Konrad.
>
>    I downloaded new code and still doesn't work(albeit different problem).
I
>    will enumerate them below
>
>    (Please note 1, 2 and 3 are seen with old xen/next as well). What
seemed
>    simple testing of pci passthrough via config changes doesn't seem to be
>    the case.
>
>    1. mkinitrd doesn't work in xcp ddk. I get below errors
>
>    mkinitrd -f ./initrd-2.6.32.ing 2.6.32
>    modinfo: could not find module ide-disk
>    No module ide-disk found for kernel 2.6.32, aborting.
>
******************************************************************************************************************/



On Fri, Oct 1, 2010 at 8:58 AM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:

> On Fri, Oct 01, 2010 at 08:36:03AM -0700, Ritu kaur wrote:
> > 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
>
> Yes.
>

[-- Attachment #1.2: Type: text/html, Size: 2158 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: pci-passthrough and shared interrupts

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 2376 bytes --]

Pasi,

Installation/compilation of xen source on fedora core went through fine. I
am facing an issue when dom0_mem is set to 1024M. During boot I get the
message

/*********************
Panic on CPU 0
Not enough RAM for domain 0 allocation
**********************/

Same thing happens when dom0_mem is set to 512M

when dom0_mem is set to 256M,  I get following message

/***************************
Panic on CPU 0
Domain 0 allocation is too small for kernel image
****************************/

Is 8GB ram mandatory? In my machine it is 2GB ram, inputs appreciated.

Thanks


On Sun, Oct 3, 2010 at 9:07 AM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:

> Thanks Konrad, I checked my old emails(back in March 2010) to see if I had
> tried this combination when I was testing xcp. I did try this combination
> and the problem I had faced was configuration errors due to IDE_DISK. I
> couldn't get past this problem. Snippets below
>
> /*********************************************************
> Thanks Konrad.
> >
> >    I downloaded new code and still doesn't work(albeit different
> problem). I
> >    will enumerate them below
> >
> >    (Please note 1, 2 and 3 are seen with old xen/next as well). What
> seemed
> >    simple testing of pci passthrough via config changes doesn't seem to
> be
> >    the case.
> >
> >    1. mkinitrd doesn't work in xcp ddk. I get below errors
> >
> >    mkinitrd -f ./initrd-2.6.32.ing 2.6.32
> >    modinfo: could not find module ide-disk
> >    No module ide-disk found for kernel 2.6.32, aborting.
> >
>
> ******************************************************************************************************************/
>
>
>
>
> On Fri, Oct 1, 2010 at 8:58 AM, Konrad Rzeszutek Wilk <
> konrad.wilk@oracle.com> wrote:
>
>> On Fri, Oct 01, 2010 at 08:36:03AM -0700, Ritu kaur wrote:
>> > 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
>>
>> Yes.
>>
>
>

[-- Attachment #1.2: Type: text/html, Size: 3238 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: pci-passthrough and shared interrupts

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 681 bytes --]

On Fri, Oct 1, 2010 at 8:58 AM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:

> On Fri, Oct 01, 2010 at 08:36:03AM -0700, Ritu kaur wrote:
> > 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
>
> Yes.
>

[-- Attachment #1.2: Type: text/html, Size: 1049 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: pci-passthrough and shared interrupts

[Pasi Kärkkäinen]

On Sun, Oct 03, 2010 at 09:41:55AM -0700, Ritu kaur wrote:
>    Pasi,
> 
>    Installation/compilation of xen source on fedora core went through fine. I
>    am facing an issue when dom0_mem is set to 1024M. During boot I get the
>    message
> 
>    /*********************
>    Panic on CPU 0
>    Not enough RAM for domain 0 allocation
>    **********************/
> 
>    Same thing happens when dom0_mem is set to 512M
> 
>    when dom0_mem is set to 256M,  I get following message
> 
>    /***************************
>    Panic on CPU 0
>    Domain 0 allocation is too small for kernel image
>    ****************************/
> 
>    Is 8GB ram mandatory? In my machine it is 2GB ram, inputs appreciated.
> 

It sounds like you wrote the value wrong, ie. you didn't specify 'M' to make it megabytes,
so you got kilobytes.. and thus it's too small to fit the dom0 kernel image there.

-- Pasi

>    Thanks
> 
>    On Sun, Oct 3, 2010 at 9:07 AM, Ritu kaur <[1]ritu.kaur.us@[2]gmail.com>
>    wrote:
> 
>      Thanks Konrad, I checked my old emails(back in March 2010) to see if I
>      had tried this combination when I was testing xcp. I did try this
>      combination and the problem I had faced was configuration errors due to
>      IDE_DISK. I couldn't get past this problem. Snippets below
> 
>      /*********************************************************
>      Thanks Konrad.
>      >
>      >    I downloaded new code and still doesn't work(albeit different
>      problem). I
>      >    will enumerate them below
>      >
>      >    (Please note 1, 2 and 3 are seen with old xen/next as well). What
>      seemed
>      >    simple testing of pci passthrough via config changes doesn't seem
>      to be
>      >    the case.
>      >
>      >    1. mkinitrd doesn't work in xcp ddk. I get below errors
>      >
>      >    mkinitrd -f ./initrd-2.6.32.ing 2.6.32
>      >    modinfo: could not find module ide-disk
>      >    No module ide-disk found for kernel 2.6.32, aborting.
>      >
>      ******************************************************************************************************************/
> 
>      On Fri, Oct 1, 2010 at 8:58 AM, Konrad Rzeszutek Wilk
>      <[3]konrad.wilk@oracle.com> wrote:
> 
>        On Fri, Oct 01, 2010 at 08:36:03AM -0700, Ritu kaur wrote:
>        > 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
> 
>        Yes.
> 
> References
> 
>    Visible links
>    1. http://ritu.kaur.us/
>    2. http://gmail.com/
>    3. mailto:konrad.wilk@oracle.com

Re: pci-passthrough and shared interrupts

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 5158 bytes --]

Hi Pasi,

I do have it as dom0_mem=256M, following is my grub.conf....

/**********************************************************
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/mapper/vg_f13-lv_root
#          initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
#hiddenmenu
title Fedora (2.6.34.7-56.fc13.x86_64)
        root (hd0,0)
        kernel /vmlinuz-2.6.34.7-56.fc13.x86_64 ro
root=/dev/mapper/vg_f13-lv_root rd_LVM_LV=vg_f13/lv_root
rd_LVM_LV=vg_f13/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
        initrd /initramfs-2.6.34.7-56.fc13.x86_64.img
title Fedora (2.6.33.3-85.fc13.x86_64)
        root (hd0,0)
        kernel /vmlinuz-2.6.33.3-85.fc13.x86_64 ro
root=/dev/mapper/vg_f13-lv_root rd_LVM_LV=vg_f13/lv_root
rd_LVM_LV=vg_f13/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
        initrd /initramfs-2.6.33.3-85.fc13.x86_64.img
title Fedora Xen 4.0 with Linux 2.6.32.23 pvops dom0
        root (hd0,0)
        kernel /xen.gz dom0_mem=256M loglvl=all guest_loglvl=all
        module /vmlinuz-2.6.32.23 ro root=/dev/mapper/vg_f13-lv_root
nomodeset
        module /initramfs-2.6.32.23.img
************************************************************************************************************/

Thanks

On Sun, Oct 3, 2010 at 9:54 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:

> On Sun, Oct 03, 2010 at 09:41:55AM -0700, Ritu kaur wrote:
> >    Pasi,
> >
> >    Installation/compilation of xen source on fedora core went through
> fine. I
> >    am facing an issue when dom0_mem is set to 1024M. During boot I get
> the
> >    message
> >
> >    /*********************
> >    Panic on CPU 0
> >    Not enough RAM for domain 0 allocation
> >    **********************/
> >
> >    Same thing happens when dom0_mem is set to 512M
> >
> >    when dom0_mem is set to 256M,  I get following message
> >
> >    /***************************
> >    Panic on CPU 0
> >    Domain 0 allocation is too small for kernel image
> >    ****************************/
> >
> >    Is 8GB ram mandatory? In my machine it is 2GB ram, inputs appreciated.
> >
>
> It sounds like you wrote the value wrong, ie. you didn't specify 'M' to
> make it megabytes,
> so you got kilobytes.. and thus it's too small to fit the dom0 kernel image
> there.
>
> -- Pasi
>
> >    Thanks
> >
> >    On Sun, Oct 3, 2010 at 9:07 AM, Ritu kaur <[1]ritu.kaur.us@[2]
> gmail.com>
> >    wrote:
> >
> >      Thanks Konrad, I checked my old emails(back in March 2010) to see if
> I
> >      had tried this combination when I was testing xcp. I did try this
> >      combination and the problem I had faced was configuration errors due
> to
> >      IDE_DISK. I couldn't get past this problem. Snippets below
> >
> >      /*********************************************************
> >      Thanks Konrad.
> >      >
> >      >    I downloaded new code and still doesn't work(albeit different
> >      problem). I
> >      >    will enumerate them below
> >      >
> >      >    (Please note 1, 2 and 3 are seen with old xen/next as well).
> What
> >      seemed
> >      >    simple testing of pci passthrough via config changes doesn't
> seem
> >      to be
> >      >    the case.
> >      >
> >      >    1. mkinitrd doesn't work in xcp ddk. I get below errors
> >      >
> >      >    mkinitrd -f ./initrd-2.6.32.ing 2.6.32
> >      >    modinfo: could not find module ide-disk
> >      >    No module ide-disk found for kernel 2.6.32, aborting.
> >      >
> >
>  ******************************************************************************************************************/
> >
> >      On Fri, Oct 1, 2010 at 8:58 AM, Konrad Rzeszutek Wilk
> >      <[3]konrad.wilk@oracle.com> wrote:
> >
> >        On Fri, Oct 01, 2010 at 08:36:03AM -0700, Ritu kaur wrote:
> >        > 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
> >
> >        Yes.
> >
> > References
> >
> >    Visible links
> >    1. http://ritu.kaur.us/
> >    2. http://gmail.com/
> >    3. mailto:konrad.wilk@oracle.com
>

[-- Attachment #1.2: Type: text/html, Size: 6365 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: pci-passthrough and shared interrupts

[Pasi Kärkkäinen]

On Sun, Oct 03, 2010 at 10:12:58AM -0700, Ritu kaur wrote:
>    Hi Pasi,
> 
>    I do have it as dom0_mem=256M, following is my grub.conf....
> 

That's weird..

Can you please paste the full Xen boot logs (from serial console or SOL).

-- Pasi

>    /**********************************************************
>    # grub.conf generated by anaconda
>    #
>    # Note that you do not have to rerun grub after making changes to this
>    file
>    # NOTICE:  You have a /boot partition.  This means that
>    #          all kernel and initrd paths are relative to /boot/, eg.
>    #          root (hd0,0)
>    #          kernel /vmlinuz-version ro root=/dev/mapper/vg_f13-lv_root
>    #          initrd /initrd-[generic-]version.img
>    #boot=/dev/sda
>    default=0
>    timeout=10
>    splashimage=(hd0,0)/grub/splash.xpm.gz
>    #hiddenmenu
>    title Fedora (2.6.34.7-56.fc13.x86_64)
>            root (hd0,0)
>            kernel /vmlinuz-2.6.34.7-56.fc13.x86_64 ro
>    root=/dev/mapper/vg_f13-lv_root rd_LVM_LV=vg_f13/lv_root
>    rd_LVM_LV=vg_f13/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8
>    SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
>            initrd /initramfs-2.6.34.7-56.fc13.x86_64.img
>    title Fedora (2.6.33.3-85.fc13.x86_64)
>            root (hd0,0)
>            kernel /vmlinuz-2.6.33.3-85.fc13.x86_64 ro
>    root=/dev/mapper/vg_f13-lv_root rd_LVM_LV=vg_f13/lv_root
>    rd_LVM_LV=vg_f13/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8
>    SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
>            initrd /initramfs-2.6.33.3-85.fc13.x86_64.img
>    title Fedora Xen 4.0 with Linux 2.6.32.23 pvops dom0
>            root (hd0,0)
>            kernel /xen.gz dom0_mem=256M loglvl=all guest_loglvl=all
>            module /vmlinuz-2.6.32.23 ro root=/dev/mapper/vg_f13-lv_root
>    nomodeset
>            module /initramfs-2.6.32.23.img
>    ************************************************************************************************************/
> 
>    Thanks
> 
>    On Sun, Oct 3, 2010 at 9:54 AM, Pasi Kärkkäinen <[1]pasik@iki.fi> wrote:
> 
>      On Sun, Oct 03, 2010 at 09:41:55AM -0700, Ritu kaur wrote:
>      >    Pasi,
>      >
>      >    Installation/compilation of xen source on fedora core went through
>      fine. I
>      >    am facing an issue when dom0_mem is set to 1024M. During boot I get
>      the
>      >    message
>      >
>      >    /*********************
>      >    Panic on CPU 0
>      >    Not enough RAM for domain 0 allocation
>      >    **********************/
>      >
>      >    Same thing happens when dom0_mem is set to 512M
>      >
>      >    when dom0_mem is set to 256M,  I get following message
>      >
>      >    /***************************
>      >    Panic on CPU 0
>      >    Domain 0 allocation is too small for kernel image
>      >    ****************************/
>      >
>      >    Is 8GB ram mandatory? In my machine it is 2GB ram, inputs
>      appreciated.
>      >
> 
>      It sounds like you wrote the value wrong, ie. you didn't specify 'M' to
>      make it megabytes,
>      so you got kilobytes.. and thus it's too small to fit the dom0 kernel
>      image there.
> 
>      -- Pasi
> 
>      >    Thanks
>      >
>      >    On Sun, Oct 3, 2010 at 9:07 AM, Ritu kaur
>      <[1][2]ritu.kaur.us@[2][3]gmail.com>
>      >    wrote:
>      >
>      >      Thanks Konrad, I checked my old emails(back in March 2010) to see
>      if I
>      >      had tried this combination when I was testing xcp. I did try this
>      >      combination and the problem I had faced was configuration errors
>      due to
>      >      IDE_DISK. I couldn't get past this problem. Snippets below
>      >
>      >      /*********************************************************
>      >      Thanks Konrad.
>      >      >
>      >      >    I downloaded new code and still doesn't work(albeit
>      different
>      >      problem). I
>      >      >    will enumerate them below
>      >      >
>      >      >    (Please note 1, 2 and 3 are seen with old xen/next as well).
>      What
>      >      seemed
>      >      >    simple testing of pci passthrough via config changes doesn't
>      seem
>      >      to be
>      >      >    the case.
>      >      >
>      >      >    1. mkinitrd doesn't work in xcp ddk. I get below errors
>      >      >
>      >      >    mkinitrd -f ./initrd-2.6.32.ing 2.6.32
>      >      >    modinfo: could not find module ide-disk
>      >      >    No module ide-disk found for kernel 2.6.32, aborting.
>      >      >
>      >
>       ******************************************************************************************************************/
>      >
>      >      On Fri, Oct 1, 2010 at 8:58 AM, Konrad Rzeszutek Wilk
>      >      <[3][4]konrad.wilk@oracle.com> wrote:
>      >
>      >        On Fri, Oct 01, 2010 at 08:36:03AM -0700, Ritu kaur wrote:
>      >        > 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
>      >
>      >        Yes.
>      >
>      > References
>      >
>      >    Visible links
>      >    1. [5]http://ritu.kaur.us/
>      >    2. [6]http://gmail.com/
>      >    3. mailto:[7]konrad.wilk@oracle.com
> 
> References
> 
>    Visible links
>    1. mailto:pasik@iki.fi
>    2. http://ritu.kaur.us/
>    3. http://gmail.com/
>    4. mailto:konrad.wilk@oracle.com
>    5. http://ritu.kaur.us/
>    6. http://gmail.com/
>    7. mailto:konrad.wilk@oracle.com