Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1420166 > unrolled thread
| Started by | Rui Wang <rui.y.wang@intel.com> |
|---|---|
| First post | 2016-06-12 08:30 +0200 |
| Last post | 2016-06-23 07:30 +0200 |
| Articles | 7 — 3 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH V3 1/3] x86/ioapic: Support hot-removal of IOAPICs present during boot Rui Wang <rui.y.wang@intel.com> - 2016-06-12 08:30 +0200
Re: [PATCH V3 1/3] x86/ioapic: Support hot-removal of IOAPICs present during boot Bjorn Helgaas <helgaas@kernel.org> - 2016-06-16 19:20 +0200
RE: [PATCH V3 1/3] x86/ioapic: Support hot-removal of IOAPICs present during boot Rui Wang <rui.y.wang@intel.com> - 2016-06-22 09:30 +0200
Re: [PATCH V3 1/3] x86/ioapic: Support hot-removal of IOAPICs present during boot Bjorn Helgaas <helgaas@kernel.org> - 2016-06-22 17:20 +0200
[PATCH V4 1/3] x86/ioapic: Support hot-removal of IOAPICs present during boot Rui Wang <rui.y.wang@intel.com> - 2016-06-22 10:00 +0200
Re: [PATCH V4 1/3] x86/ioapic: Support hot-removal of IOAPICs present during boot Bjorn Helgaas <helgaas@kernel.org> - 2016-06-22 17:20 +0200
Re: [PATCH V4 1/3] x86/ioapic: Support hot-removal of IOAPICs present during boot <> - 2016-06-23 07:30 +0200
| From | Rui Wang <rui.y.wang@intel.com> |
|---|---|
| Date | 2016-06-12 08:30 +0200 |
| Subject | Re: [PATCH V3 1/3] x86/ioapic: Support hot-removal of IOAPICs present during boot |
| Message-ID | <rJ74e-5a2-11@gated-at.bofh.it> |
On Saturday, June 11, 2016 12:43 AM, Bjorn Helgaas wrote:
> On Wed, Jun 08, 2016 at 05:32:44PM +0800, Rui Wang wrote:
> > @@ -1779,8 +1780,12 @@ void __init
> > pci_assign_unassigned_resources(void)
> > {
> > struct pci_bus *root_bus;
> >
> > - list_for_each_entry(root_bus, &pci_root_buses, node)
> > + list_for_each_entry(root_bus, &pci_root_buses, node) {
> > pci_assign_unassigned_root_bus_resources(root_bus);
> > +#ifdef CONFIG_X86
> > + acpi_ioapic_add(ACPI_HANDLE(root_bus->bridge));
> > +#endif
>
> This seems like a strange place to call acpi_ioapic_add(). Your object is to call
> acpi_ioapic_add() during root bus enumeration.
>
> I assume we *can't* call acpi_ioapic_add() from acpi_pci_root_add() at boot
> time, for some reason you'll explain. But is there a reason we have to call it
> from pci_assign_unassigned_resources() (where it requires an ifdef) instead
> of from pcibios_assign_resources(), which is already x86-specific?
>
> In acpi_pci_root_add(), we have this:
>
> acpi_pci_root_add(...)
> {
> ...
> if (hotadd)
> acpi_ioapic_add(root);
>
> So the obvious question is why don't we just remove the "if (hotadd)"
> and call acpi_ioapic_add() always.
>
> I'm sure the reason is some ordering problem, but we need a comment in
> acpi_pci_root_add() about why the obvious solution doesn't work.
>
Hi Bjorn,
Yes it's an ording issue. acpi_ioapic_add() and also ioapic_insert_resources()
have to be later than pci initialization in order to deal with IOAPICs mapped
on a PCI BAR. There's a comment about this inside pcibios_resource_survey()
above ioapic_insert_resources(). We can also add a comment inside
acpi_pci_root_add(), though.
And yes calling acpi_ioapic_add() in pcibios_assign_resources() doesn't require
ifdef CONFIG_X86. But it'll require a loop to iterate through the root buses,
and call acpi_ioapic_add() within the loop. pci_assign_unassigned_resources()
already has that loop. Do you still prefer adding it to
pcibios_assign_resources() ?
Regards,
Rui
[toc] | [next] | [standalone]
| From | Bjorn Helgaas <helgaas@kernel.org> |
|---|---|
| Date | 2016-06-16 19:20 +0200 |
| Subject | Re: [PATCH V3 1/3] x86/ioapic: Support hot-removal of IOAPICs present during boot |
| Message-ID | <rKJ7r-2Jr-11@gated-at.bofh.it> |
| In reply to | #1420166 |
On Sun, Jun 12, 2016 at 02:06:09PM +0800, Rui Wang wrote:
> On Saturday, June 11, 2016 12:43 AM, Bjorn Helgaas wrote:
> > On Wed, Jun 08, 2016 at 05:32:44PM +0800, Rui Wang wrote:
> > > @@ -1779,8 +1780,12 @@ void __init
> > > pci_assign_unassigned_resources(void)
> > > {
> > > struct pci_bus *root_bus;
> > >
> > > - list_for_each_entry(root_bus, &pci_root_buses, node)
> > > + list_for_each_entry(root_bus, &pci_root_buses, node) {
> > > pci_assign_unassigned_root_bus_resources(root_bus);
> > > +#ifdef CONFIG_X86
> > > + acpi_ioapic_add(ACPI_HANDLE(root_bus->bridge));
> > > +#endif
> >
> > This seems like a strange place to call acpi_ioapic_add(). Your object is to call
> > acpi_ioapic_add() during root bus enumeration.
> >
> > I assume we *can't* call acpi_ioapic_add() from acpi_pci_root_add() at boot
> > time, for some reason you'll explain. But is there a reason we have to call it
> > from pci_assign_unassigned_resources() (where it requires an ifdef) instead
> > of from pcibios_assign_resources(), which is already x86-specific?
> >
> > In acpi_pci_root_add(), we have this:
> >
> > acpi_pci_root_add(...)
> > {
> > ...
> > if (hotadd)
> > acpi_ioapic_add(root);
> >
> > So the obvious question is why don't we just remove the "if (hotadd)"
> > and call acpi_ioapic_add() always.
> >
> > I'm sure the reason is some ordering problem, but we need a comment in
> > acpi_pci_root_add() about why the obvious solution doesn't work.
>
> Yes it's an ording issue. acpi_ioapic_add() and also ioapic_insert_resources()
> have to be later than pci initialization in order to deal with IOAPICs mapped
> on a PCI BAR. There's a comment about this inside pcibios_resource_survey()
> above ioapic_insert_resources(). We can also add a comment inside
> acpi_pci_root_add(), though.
>
> And yes calling acpi_ioapic_add() in pcibios_assign_resources() doesn't require
> ifdef CONFIG_X86. But it'll require a loop to iterate through the root buses,
> and call acpi_ioapic_add() within the loop. pci_assign_unassigned_resources()
> already has that loop. Do you still prefer adding it to
> pcibios_assign_resources() ?
ioapic_insert_resources() is x86-specific, but I'm not sure why; it
seems like it does things that should be applicable to ia64 as well.
acpi_ioapic_add() is not x86-specific, and it is called from
acpi_pci_root_add() for the hot-add case. You're adding an
x86-xpecific call in pci_assign_unassigned_resources(). Why should
the hot-add case be for all arches, but the boot-time case only for
x86?
[toc] | [prev] | [next] | [standalone]
| From | Rui Wang <rui.y.wang@intel.com> |
|---|---|
| Date | 2016-06-22 09:30 +0200 |
| Message-ID | <rMKLL-oX-7@gated-at.bofh.it> |
| In reply to | #1424288 |
On Friday, June 17, 2016 1:10 AM, Bjorn Helgaas wrote: > ioapic_insert_resources() is x86-specific, but I'm not sure why; it seems > like it does things that should be applicable to ia64 as well. > > acpi_ioapic_add() is not x86-specific, and it is called from > acpi_pci_root_add() for the hot-add case. You're adding an x86-xpecific call > in pci_assign_unassigned_resources(). Why should the hot-add case be for > all arches, but the boot-time case only for x86? Hi Bjorn, It turns out that IOAPIC hotplug has not been pursued on ia64. There were demos showing CPU sockets online/offline on ia64 but the CPUs had no IIO, thus no IOAPIC hotplug. So to answer the first question: ioapic_insert_resources() is x86-specific because it's inserting what has been setup in io_apic_init_mappings() which, through mpc_ioapic_addr(), is capable of handling both the static case (acpi_parse_ioapic(), etc.) and the hotplug case (acpi_ioapic_add()). But on ia64, there's only the static case through acpi_parse_iosapic(), no need for the hotplug case yet. To answer the second question: acpi_ioapic_add() is in effect x86-specific, because it's an empty function when CONFIG_ACPI_HOTPLUG_IOAPIC isn't defined. And CONFIG_ACPI_HOTPLUG_IOAPIC depends on CONFIG_X86_IO_APIC (see drivers/acpi/Kconfig). This was introduced in c183619b6 (x86/irq, ACPI: Implement ACPI driver to support IOAPIC hotplug). That commit shows the dependency. I'll send a newer version with comments explaining these. Thanks Rui
[toc] | [prev] | [next] | [standalone]
| From | Bjorn Helgaas <helgaas@kernel.org> |
|---|---|
| Date | 2016-06-22 17:20 +0200 |
| Subject | Re: [PATCH V3 1/3] x86/ioapic: Support hot-removal of IOAPICs present during boot |
| Message-ID | <rMS6C-57o-19@gated-at.bofh.it> |
| In reply to | #1428496 |
On Wed, Jun 22, 2016 at 03:13:32PM +0800, Rui Wang wrote: > On Friday, June 17, 2016 1:10 AM, Bjorn Helgaas wrote: > > ioapic_insert_resources() is x86-specific, but I'm not sure why; it seems > > like it does things that should be applicable to ia64 as well. > > > > acpi_ioapic_add() is not x86-specific, and it is called from > > acpi_pci_root_add() for the hot-add case. You're adding an x86-xpecific call > > in pci_assign_unassigned_resources(). Why should the hot-add case be for > > all arches, but the boot-time case only for x86? > > Hi Bjorn, > > It turns out that IOAPIC hotplug has not been pursued on ia64. There were > demos showing CPU sockets online/offline on ia64 but the CPUs had no IIO, > thus no IOAPIC hotplug. That doesn't mean we need to write code that's gratuitously x86-specific. > So to answer the first question: > ioapic_insert_resources() is x86-specific because it's inserting what has > been setup in io_apic_init_mappings() which, through mpc_ioapic_addr(), is > capable of handling both the static case (acpi_parse_ioapic(), etc.) and the > hotplug case (acpi_ioapic_add()). But on ia64, there's only the static > case through acpi_parse_iosapic(), no need for the hotplug case yet. ioapic_insert_resources() inserts IOAPIC resources on x86. Where are IOSAPIC resources inserted on ia64? > To answer the second question: > acpi_ioapic_add() is in effect x86-specific, because it's an empty function > when CONFIG_ACPI_HOTPLUG_IOAPIC isn't defined. And CONFIG_ACPI_HOTPLUG_IOAPIC > depends on CONFIG_X86_IO_APIC (see drivers/acpi/Kconfig). This was introduced > in c183619b6 (x86/irq, ACPI: Implement ACPI driver to support IOAPIC hotplug). > That commit shows the dependency. > > I'll send a newer version with comments explaining these. I'd rather have code that is not x86-specific than comments explaining why the code is x86-specific.
[toc] | [prev] | [next] | [standalone]
| From | Rui Wang <rui.y.wang@intel.com> |
|---|---|
| Date | 2016-06-22 10:00 +0200 |
| Subject | [PATCH V4 1/3] x86/ioapic: Support hot-removal of IOAPICs present during boot |
| Message-ID | <rMLeO-AU-15@gated-at.bofh.it> |
| In reply to | #1424288 |
v4: Add comments explaining when to call acpi_ioapic_add().
v3: Previous versions break mips. This version fixes it.
IOAPICs present during system boot aren't added to ioapic_list,
thus are unable to be hot-removed. Fix it by calling
acpi_ioapic_add() during root bus enumeration.
Signed-off-by: Rui Wang <rui.y.wang@intel.com>
---
drivers/acpi/internal.h | 2 --
drivers/acpi/ioapic.c | 7 ++++---
drivers/acpi/pci_root.c | 13 ++++++++++++-
drivers/pci/setup-bus.c | 7 ++++++-
include/linux/acpi.h | 3 +++
5 files changed, 25 insertions(+), 7 deletions(-)
diff --git a/drivers/acpi/internal.h b/drivers/acpi/internal.h
index 27cc7fe..6d8e67e 100644
--- a/drivers/acpi/internal.h
+++ b/drivers/acpi/internal.h
@@ -40,10 +40,8 @@ int acpi_sysfs_init(void);
void acpi_container_init(void);
void acpi_memory_hotplug_init(void);
#ifdef CONFIG_ACPI_HOTPLUG_IOAPIC
-int acpi_ioapic_add(struct acpi_pci_root *root);
int acpi_ioapic_remove(struct acpi_pci_root *root);
#else
-static inline int acpi_ioapic_add(struct acpi_pci_root *root) { return 0; }
static inline int acpi_ioapic_remove(struct acpi_pci_root *root) { return 0; }
#endif
#ifdef CONFIG_ACPI_DOCK
diff --git a/drivers/acpi/ioapic.c b/drivers/acpi/ioapic.c
index ccdc8db..0f272e2 100644
--- a/drivers/acpi/ioapic.c
+++ b/drivers/acpi/ioapic.c
@@ -189,16 +189,17 @@ exit:
return AE_OK;
}
-int acpi_ioapic_add(struct acpi_pci_root *root)
+int acpi_ioapic_add(acpi_handle root_handle)
{
acpi_status status, retval = AE_OK;
- status = acpi_walk_namespace(ACPI_TYPE_DEVICE, root->device->handle,
+ status = acpi_walk_namespace(ACPI_TYPE_DEVICE, root_handle,
UINT_MAX, handle_ioapic_add, NULL,
- root->device->handle, (void **)&retval);
+ root_handle, (void **)&retval);
return ACPI_SUCCESS(status) && ACPI_SUCCESS(retval) ? 0 : -ENODEV;
}
+EXPORT_SYMBOL_GPL(acpi_ioapic_add);
int acpi_ioapic_remove(struct acpi_pci_root *root)
{
diff --git a/drivers/acpi/pci_root.c b/drivers/acpi/pci_root.c
index ae3fe4e..31e4440 100644
--- a/drivers/acpi/pci_root.c
+++ b/drivers/acpi/pci_root.c
@@ -614,7 +614,18 @@ static int acpi_pci_root_add(struct acpi_device *device,
if (hotadd) {
pcibios_resource_survey_bus(root->bus);
pci_assign_unassigned_root_bus_resources(root->bus);
- acpi_ioapic_add(root);
+
+ /*
+ * This is only called for the hotadd case. For the boot-time
+ * case, we need to wait until after PCI initialization in
+ * order to deal with IOAPICs mapped in on a PCI BAR.
+ *
+ * This is currently x86-specific, because acpi_ioapic_add()
+ * is an empty function without CONFIG_ACPI_HOTPLUG_IOAPIC.
+ * And CONFIG_ACPI_HOTPLUG_IOAPIC depends on CONFIG_X86_IO_APIC
+ * (see drivers/acpi/Kconfig).
+ */
+ acpi_ioapic_add(root->device->handle);
}
pci_lock_rescan_remove();
diff --git a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
index 55641a3..0658921 100644
--- a/drivers/pci/setup-bus.c
+++ b/drivers/pci/setup-bus.c
@@ -25,6 +25,7 @@
#include <linux/ioport.h>
#include <linux/cache.h>
#include <linux/slab.h>
+#include <linux/acpi.h>
#include "pci.h"
unsigned int pci_flags;
@@ -1779,8 +1780,12 @@ void __init pci_assign_unassigned_resources(void)
{
struct pci_bus *root_bus;
- list_for_each_entry(root_bus, &pci_root_buses, node)
+ list_for_each_entry(root_bus, &pci_root_buses, node) {
pci_assign_unassigned_root_bus_resources(root_bus);
+#ifdef CONFIG_X86
+ acpi_ioapic_add(ACPI_HANDLE(root_bus->bridge));
+#endif
+ }
}
void pci_assign_unassigned_bridge_resources(struct pci_dev *bridge)
diff --git a/include/linux/acpi.h b/include/linux/acpi.h
index 288fac5..3ed22df 100644
--- a/include/linux/acpi.h
+++ b/include/linux/acpi.h
@@ -262,6 +262,9 @@ int acpi_unmap_cpu(int cpu);
#ifdef CONFIG_ACPI_HOTPLUG_IOAPIC
int acpi_get_ioapic_id(acpi_handle handle, u32 gsi_base, u64 *phys_addr);
+int acpi_ioapic_add(acpi_handle root);
+#else
+static inline int acpi_ioapic_add(acpi_handle root) { return 0; }
#endif
int acpi_register_ioapic(acpi_handle handle, u64 phys_addr, u32 gsi_base);
--
1.8.3.1
[toc] | [prev] | [next] | [standalone]
| From | Bjorn Helgaas <helgaas@kernel.org> |
|---|---|
| Date | 2016-06-22 17:20 +0200 |
| Subject | Re: [PATCH V4 1/3] x86/ioapic: Support hot-removal of IOAPICs present during boot |
| Message-ID | <rMS6B-57o-1@gated-at.bofh.it> |
| In reply to | #1428528 |
On Wed, Jun 22, 2016 at 03:40:19PM +0800, Rui Wang wrote:
> v4: Add comments explaining when to call acpi_ioapic_add().
> v3: Previous versions break mips. This version fixes it.
>
> IOAPICs present during system boot aren't added to ioapic_list,
> thus are unable to be hot-removed. Fix it by calling
> acpi_ioapic_add() during root bus enumeration.
>
> Signed-off-by: Rui Wang <rui.y.wang@intel.com>
> ---
> drivers/acpi/internal.h | 2 --
> drivers/acpi/ioapic.c | 7 ++++---
> drivers/acpi/pci_root.c | 13 ++++++++++++-
> drivers/pci/setup-bus.c | 7 ++++++-
> include/linux/acpi.h | 3 +++
> 5 files changed, 25 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/acpi/internal.h b/drivers/acpi/internal.h
> index 27cc7fe..6d8e67e 100644
> --- a/drivers/acpi/internal.h
> +++ b/drivers/acpi/internal.h
> @@ -40,10 +40,8 @@ int acpi_sysfs_init(void);
> void acpi_container_init(void);
> void acpi_memory_hotplug_init(void);
> #ifdef CONFIG_ACPI_HOTPLUG_IOAPIC
> -int acpi_ioapic_add(struct acpi_pci_root *root);
> int acpi_ioapic_remove(struct acpi_pci_root *root);
> #else
> -static inline int acpi_ioapic_add(struct acpi_pci_root *root) { return 0; }
> static inline int acpi_ioapic_remove(struct acpi_pci_root *root) { return 0; }
> #endif
> #ifdef CONFIG_ACPI_DOCK
> diff --git a/drivers/acpi/ioapic.c b/drivers/acpi/ioapic.c
> index ccdc8db..0f272e2 100644
> --- a/drivers/acpi/ioapic.c
> +++ b/drivers/acpi/ioapic.c
> @@ -189,16 +189,17 @@ exit:
> return AE_OK;
> }
>
> -int acpi_ioapic_add(struct acpi_pci_root *root)
> +int acpi_ioapic_add(acpi_handle root_handle)
> {
> acpi_status status, retval = AE_OK;
>
> - status = acpi_walk_namespace(ACPI_TYPE_DEVICE, root->device->handle,
> + status = acpi_walk_namespace(ACPI_TYPE_DEVICE, root_handle,
> UINT_MAX, handle_ioapic_add, NULL,
> - root->device->handle, (void **)&retval);
> + root_handle, (void **)&retval);
>
> return ACPI_SUCCESS(status) && ACPI_SUCCESS(retval) ? 0 : -ENODEV;
> }
> +EXPORT_SYMBOL_GPL(acpi_ioapic_add);
>
> int acpi_ioapic_remove(struct acpi_pci_root *root)
> {
> diff --git a/drivers/acpi/pci_root.c b/drivers/acpi/pci_root.c
> index ae3fe4e..31e4440 100644
> --- a/drivers/acpi/pci_root.c
> +++ b/drivers/acpi/pci_root.c
> @@ -614,7 +614,18 @@ static int acpi_pci_root_add(struct acpi_device *device,
> if (hotadd) {
> pcibios_resource_survey_bus(root->bus);
> pci_assign_unassigned_root_bus_resources(root->bus);
> - acpi_ioapic_add(root);
> +
> + /*
> + * This is only called for the hotadd case. For the boot-time
> + * case, we need to wait until after PCI initialization in
> + * order to deal with IOAPICs mapped in on a PCI BAR.
> + *
> + * This is currently x86-specific, because acpi_ioapic_add()
> + * is an empty function without CONFIG_ACPI_HOTPLUG_IOAPIC.
> + * And CONFIG_ACPI_HOTPLUG_IOAPIC depends on CONFIG_X86_IO_APIC
> + * (see drivers/acpi/Kconfig).
> + */
> + acpi_ioapic_add(root->device->handle);
> }
>
> pci_lock_rescan_remove();
> diff --git a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
> index 55641a3..0658921 100644
> --- a/drivers/pci/setup-bus.c
> +++ b/drivers/pci/setup-bus.c
> @@ -25,6 +25,7 @@
> #include <linux/ioport.h>
> #include <linux/cache.h>
> #include <linux/slab.h>
> +#include <linux/acpi.h>
> #include "pci.h"
>
> unsigned int pci_flags;
> @@ -1779,8 +1780,12 @@ void __init pci_assign_unassigned_resources(void)
> {
> struct pci_bus *root_bus;
>
> - list_for_each_entry(root_bus, &pci_root_buses, node)
> + list_for_each_entry(root_bus, &pci_root_buses, node) {
> pci_assign_unassigned_root_bus_resources(root_bus);
> +#ifdef CONFIG_X86
> + acpi_ioapic_add(ACPI_HANDLE(root_bus->bridge));
> +#endif
Doesn't this do the right thing even if you omit the #ifdefs, since you
define a stub function below?
> + }
> }
>
> void pci_assign_unassigned_bridge_resources(struct pci_dev *bridge)
> diff --git a/include/linux/acpi.h b/include/linux/acpi.h
> index 288fac5..3ed22df 100644
> --- a/include/linux/acpi.h
> +++ b/include/linux/acpi.h
> @@ -262,6 +262,9 @@ int acpi_unmap_cpu(int cpu);
>
> #ifdef CONFIG_ACPI_HOTPLUG_IOAPIC
> int acpi_get_ioapic_id(acpi_handle handle, u32 gsi_base, u64 *phys_addr);
> +int acpi_ioapic_add(acpi_handle root);
> +#else
> +static inline int acpi_ioapic_add(acpi_handle root) { return 0; }
> #endif
>
> int acpi_register_ioapic(acpi_handle handle, u64 phys_addr, u32 gsi_base);
> --
> 1.8.3.1
>
[toc] | [prev] | [next] | [standalone]
| From | <> |
|---|---|
| Date | 2016-06-23 07:30 +0200 |
| Subject | Re: [PATCH V4 1/3] x86/ioapic: Support hot-removal of IOAPICs present during boot |
| Message-ID | <rN5nb-5t9-15@gated-at.bofh.it> |
| In reply to | #1428884 |
From: Rui Wang <rui.y.wang@intel.com>
On Wed, June 22, 2016 11:15 PM Bjorn Helgaas wrote:
> [...]
> > @@ -1779,8 +1780,12 @@ void __init
> > pci_assign_unassigned_resources(void)
> > {
> > struct pci_bus *root_bus;
> >
> > - list_for_each_entry(root_bus, &pci_root_buses, node)
> > + list_for_each_entry(root_bus, &pci_root_buses, node) {
> > pci_assign_unassigned_root_bus_resources(root_bus);
> > +#ifdef CONFIG_X86
> > + acpi_ioapic_add(ACPI_HANDLE(root_bus->bridge));
> > +#endif
>
> Doesn't this do the right thing even if you omit the #ifdefs, since you
> define a stub function below?
>
No. Without the '#ifdef CONFIG_X86' it breaks MIPS arch. The stub function is
within 'ifdef CONFIG_ACPI'. On archs without ACPI it doesn't compile due to
'undefined reference to acpi_ioapic_add'.
Thanks
Rui
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web