Re: [RFC Patch V2 03/16] ACPI, x86/PCI: Move resource_to_addr() to acpi generic

2014-06-17 Thread Bjorn Helgaas
On Mon, Jun 16, 2014 at 11:29 PM, Jiang Liu wrote: > From: Yinghai Lu > > Rui Wang reported ioapic hot-add does not work on his machine > that _CRS have MEMORY_FIXED. > He also proposed to expose resource_to_addr() and use it for ioapic. > > We should move it to acpi generic, as ioapi.c current

Re: [RFC Patch V2 03/16] ACPI, x86/PCI: Move resource_to_addr() to acpi generic

2014-06-17 Thread Bjorn Helgaas
On Mon, Jun 16, 2014 at 11:29 PM, Jiang Liu jiang@linux.intel.com wrote: From: Yinghai Lu ying...@kernel.org Rui Wang reported ioapic hot-add does not work on his machine that _CRS have MEMORY_FIXED. He also proposed to expose resource_to_addr() and use it for ioapic. We should move it

[RFC Patch V2 03/16] ACPI, x86/PCI: Move resource_to_addr() to acpi generic

2014-06-16 Thread Jiang Liu
From: Yinghai Lu Rui Wang reported ioapic hot-add does not work on his machine that _CRS have MEMORY_FIXED. He also proposed to expose resource_to_addr() and use it for ioapic. We should move it to acpi generic, as ioapi.c current is in drivers/pci/. Or should move it to acpica?

[RFC Patch V2 03/16] ACPI, x86/PCI: Move resource_to_addr() to acpi generic

2014-06-16 Thread Jiang Liu
From: Yinghai Lu ying...@kernel.org Rui Wang reported ioapic hot-add does not work on his machine that _CRS have MEMORY_FIXED. He also proposed to expose resource_to_addr() and use it for ioapic. We should move it to acpi generic, as ioapi.c current is in drivers/pci/. Or should move it to