Mailing List Archive

Jan Beulich wrote:
> With this option set, the kernel simply doesn't build. Jan

Why is this patch required?

Jun
---
Intel Open Source Technology Center

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

As I said - with the option turned on, the kernel doesn't build. If you
didn't see this yourself, yet, I don't understand why you're concerned.
drivers/pci/msi.c depends on the symbols set_intr_gate and interrupt,
both of which aren't available in either 32- or 64-bit paravirtualized
kernels. If this is functionality that can legitimately be used here,
someone will first have to take the time to actually implement it; until
then it should be disabled to prevent build failures (there are several
other build options that I likely will submit disabling patches for,
even though the functionality isn't necessarily restricted to native
kernels). Jan

>>> "Nakajima, Jun" <jun.nakajima@intel.com> 19.12.05 18:08:19 >>>
Jan Beulich wrote:
> With this option set, the kernel simply doesn't build. Jan

Why is this patch required?

Jun
---
Intel Open Source Technology Center

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

On Mon, Dec 19, 2005 at 09:08:19AM -0800, Nakajima, Jun wrote:
> Why is this patch required?

MSI is not yet supported by Xen.

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=49

--
Vincent Hanquez

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

On Mon, Dec 19, 2005 at 02:40:18PM +0100, Jan Beulich wrote:
> Index: 2005-12-16/drivers/pci/Kconfig
> ===================================================================
> --- 2005-12-16.orig/drivers/pci/Kconfig 2005-11-21 16:41:39.000000000 +0100
> +++ 2005-12-16/drivers/pci/Kconfig 2005-12-19 14:31:37.939450896 +0100
> @@ -4,7 +4,7 @@
> config PCI_MSI
> bool "Message Signaled Interrupts (MSI and MSI-X)"
> depends on PCI
> - depends on (X86_LOCAL_APIC && X86_IO_APIC) || IA64
> + depends on (X86_LOCAL_APIC && X86_IO_APIC && !XEN) || IA64
> help
> This allows device drivers to enable MSI (Message Signaled
> Interrupts). Message Signaled Interrupts enable a device to

I've sent almost same fix days ago.. I guess it was lost somewhere ..

more generally I did sent a bunch of patches to be able to build a
make allyesconfig kernel in x86 and x86_64.

--
Vincent Hanquez

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

Vincent Hanquez wrote:
> On Mon, Dec 19, 2005 at 09:08:19AM -0800, Nakajima, Jun wrote:
>> Why is this patch required?
>
> MSI is not yet supported by Xen.
>
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=49

Okay, Xen needs to support MSI first. I don't expect significant impacts
to XenLinux though. A good thing with MSI is that we can eliminate IO
APIC things from dom0. I wrote part of the MSI code (e.g. switch irqs
and vectors) for Linux, so I'll talk to Keir. BTW, CONFIG_PCI_MMCONFIG
(required for PCI Express) is working fine in dom0.

Jun
---
Intel Open Source Technology Center

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