Displaying 7 results from an estimated 7 matches for "acpi_fadt_no_msi".
2014 Jul 05
0
How to check for proper MSI support?
...as been stripped
> out by now, you can see the full lspci -vvvxxx at
> http://marc.info/?l=linux-pci&m=140443441730503&w=2
Huh, this stinks. We don't really have a good way of figuring out
whether the system chipset supports MSI. The ACPI FADT "MSI Not
Supported" bit (ACPI_FADT_NO_MSI) was added to the ACPI v3.0b spec in
October 2006, so that won't help the systems that predate that or
don't have ACPI.
We have quirks for some Serverworks, ATI, and VIA chipsets that
basically do the same as booting with "pci=nomsi". But as you say,
it's unreasonable to add...
2014 Jul 05
0
How to check for proper MSI support?
...ut by now, you can see the full lspci -vvvxxx at
>> http://marc.info/?l=linux-pci&m=140443441730503&w=2
>
> Huh, this stinks. We don't really have a good way of figuring out
> whether the system chipset supports MSI. The ACPI FADT "MSI Not
> Supported" bit (ACPI_FADT_NO_MSI) was added to the ACPI v3.0b spec in
> October 2006, so that won't help the systems that predate that or
> don't have ACPI.
>
> We have quirks for some Serverworks, ATI, and VIA chipsets that
> basically do the same as booting with "pci=nomsi". But as you say,
>...
2014 Jul 04
4
How to check for proper MSI support?
On Thu, Jul 3, 2014 at 11:56 PM, Yijing Wang <wangyijing at huawei.com> wrote:
> On 2014/7/4 11:30, Ilia Mirkin wrote:
>> On Thu, Jul 3, 2014 at 11:09 PM, Yijing Wang <wangyijing at huawei.com> wrote:
>>> On 2014/7/4 10:43, Ilia Mirkin wrote:
>>>> On Thu, Jul 3, 2014 at 10:35 PM, Yijing Wang <wangyijing at huawei.com> wrote:
>>>>> Hi
2013 Jul 22
69
[xen-unstable] Commit 2ca9fbd739b8a72b16dd790d0fff7b75f5488fb8 AMD IOMMU: allocate IRTE entries instead of using a static mapping, makes dom0 boot process stall several times.
Hi Jan,
After commit 2ca9fbd739b8a72b16dd790d0fff7b75f5488fb8 AMD IOMMU: allocate IRTE entries instead of using a static mapping, booting dom0 stalls several times.
Sometimes this results in RCU stall warnings from the dom0 kernel, hitting the "any" key, on normal or serial console, makes the boot continue for a while but it stalls several times.
(It also stalls on shutdown BTW)
I have
2011 Jun 02
0
[PATCH] pci: Use pr_<level> and pr_fmt
...* Copyright (C) 2004 Intel Corp.
*/
+#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
+
#include <linux/delay.h>
#include <linux/init.h>
#include <linux/pci.h>
@@ -387,12 +389,12 @@ static int __init acpi_pci_init(void)
int ret;
if (acpi_gbl_FADT.boot_flags & ACPI_FADT_NO_MSI) {
- printk(KERN_INFO"ACPI FADT declares the system doesn't support MSI, so disable it\n");
+ pr_info("ACPI FADT declares the system doesn't support MSI, so disable it\n");
pci_no_msi();
}
if (acpi_gbl_FADT.boot_flags & ACPI_FADT_NO_ASPM) {
- printk(KERN_...
2011 Jun 02
0
[PATCH] pci: Use pr_<level> and pr_fmt
...* Copyright (C) 2004 Intel Corp.
*/
+#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
+
#include <linux/delay.h>
#include <linux/init.h>
#include <linux/pci.h>
@@ -387,12 +389,12 @@ static int __init acpi_pci_init(void)
int ret;
if (acpi_gbl_FADT.boot_flags & ACPI_FADT_NO_MSI) {
- printk(KERN_INFO"ACPI FADT declares the system doesn't support MSI, so disable it\n");
+ pr_info("ACPI FADT declares the system doesn't support MSI, so disable it\n");
pci_no_msi();
}
if (acpi_gbl_FADT.boot_flags & ACPI_FADT_NO_ASPM) {
- printk(KERN_...
2011 Jun 02
0
[PATCH] pci: Use pr_<level> and pr_fmt
...* Copyright (C) 2004 Intel Corp.
*/
+#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
+
#include <linux/delay.h>
#include <linux/init.h>
#include <linux/pci.h>
@@ -387,12 +389,12 @@ static int __init acpi_pci_init(void)
int ret;
if (acpi_gbl_FADT.boot_flags & ACPI_FADT_NO_MSI) {
- printk(KERN_INFO"ACPI FADT declares the system doesn't support MSI, so disable it\n");
+ pr_info("ACPI FADT declares the system doesn't support MSI, so disable it\n");
pci_no_msi();
}
if (acpi_gbl_FADT.boot_flags & ACPI_FADT_NO_ASPM) {
- printk(KERN_...