Re: [PATCH v3] PCI: ACPI: IA64: fix IO port generic range check

2016-03-23 Thread Hanjun Guo
On 2016/3/21 19:12, Lorenzo Pieralisi wrote: The [0 - 64k] ACPI PCI IO port resource boundary check in: acpi_dev_ioresource_flags() is currently applied blindly in the ACPI resource parsing to all architectures, but only x86 suffers from that IO space limitation. On arches (ie IA64 and ARM64)

Re: [PATCH v3] PCI: ACPI: IA64: fix IO port generic range check

2016-03-23 Thread Hanjun Guo
On 2016/3/21 19:12, Lorenzo Pieralisi wrote: The [0 - 64k] ACPI PCI IO port resource boundary check in: acpi_dev_ioresource_flags() is currently applied blindly in the ACPI resource parsing to all architectures, but only x86 suffers from that IO space limitation. On arches (ie IA64 and ARM64)

Re: [PATCH v3] PCI: ACPI: IA64: fix IO port generic range check

2016-03-22 Thread Rafael J. Wysocki
On Tuesday, March 22, 2016 08:02:19 AM Bjorn Helgaas wrote: > On Mon, Mar 21, 2016 at 01:42:01PM +0100, Rafael J. Wysocki wrote: > > On Mon, Mar 21, 2016 at 12:12 PM, Lorenzo Pieralisi [cut] > > > > > > Fixes: 3772aea7d6f3 ("ia64/PCI/ACPI: Use common ACPI resource parsing > > > interface for

Re: [PATCH v3] PCI: ACPI: IA64: fix IO port generic range check

2016-03-22 Thread Rafael J. Wysocki
On Tuesday, March 22, 2016 08:02:19 AM Bjorn Helgaas wrote: > On Mon, Mar 21, 2016 at 01:42:01PM +0100, Rafael J. Wysocki wrote: > > On Mon, Mar 21, 2016 at 12:12 PM, Lorenzo Pieralisi [cut] > > > > > > Fixes: 3772aea7d6f3 ("ia64/PCI/ACPI: Use common ACPI resource parsing > > > interface for

Re: [PATCH v3] PCI: ACPI: IA64: fix IO port generic range check

2016-03-22 Thread Bjorn Helgaas
On Mon, Mar 21, 2016 at 01:42:01PM +0100, Rafael J. Wysocki wrote: > On Mon, Mar 21, 2016 at 12:12 PM, Lorenzo Pieralisi > wrote: > > The [0 - 64k] ACPI PCI IO port resource boundary check in: > > > > acpi_dev_ioresource_flags() > > > > is currently applied blindly in

Re: [PATCH v3] PCI: ACPI: IA64: fix IO port generic range check

2016-03-22 Thread Bjorn Helgaas
On Mon, Mar 21, 2016 at 01:42:01PM +0100, Rafael J. Wysocki wrote: > On Mon, Mar 21, 2016 at 12:12 PM, Lorenzo Pieralisi > wrote: > > The [0 - 64k] ACPI PCI IO port resource boundary check in: > > > > acpi_dev_ioresource_flags() > > > > is currently applied blindly in the ACPI resource parsing to

Re: [PATCH v3] PCI: ACPI: IA64: fix IO port generic range check

2016-03-21 Thread Rafael J. Wysocki
On Mon, Mar 21, 2016 at 12:12 PM, Lorenzo Pieralisi wrote: > The [0 - 64k] ACPI PCI IO port resource boundary check in: > > acpi_dev_ioresource_flags() > > is currently applied blindly in the ACPI resource parsing to all > architectures, but only x86 suffers from that

Re: [PATCH v3] PCI: ACPI: IA64: fix IO port generic range check

2016-03-21 Thread Rafael J. Wysocki
On Mon, Mar 21, 2016 at 12:12 PM, Lorenzo Pieralisi wrote: > The [0 - 64k] ACPI PCI IO port resource boundary check in: > > acpi_dev_ioresource_flags() > > is currently applied blindly in the ACPI resource parsing to all > architectures, but only x86 suffers from that IO space limitation. > > On

[PATCH v3] PCI: ACPI: IA64: fix IO port generic range check

2016-03-21 Thread Lorenzo Pieralisi
The [0 - 64k] ACPI PCI IO port resource boundary check in: acpi_dev_ioresource_flags() is currently applied blindly in the ACPI resource parsing to all architectures, but only x86 suffers from that IO space limitation. On arches (ie IA64 and ARM64) where IO space is memory mapped, the PCI root

[PATCH v3] PCI: ACPI: IA64: fix IO port generic range check

2016-03-21 Thread Lorenzo Pieralisi
The [0 - 64k] ACPI PCI IO port resource boundary check in: acpi_dev_ioresource_flags() is currently applied blindly in the ACPI resource parsing to all architectures, but only x86 suffers from that IO space limitation. On arches (ie IA64 and ARM64) where IO space is memory mapped, the PCI root