Boris Ostrovsky writes ("Re: [Xen-devel] [PATCH qemu-traditional] ioreq:
Support 32-bit default_ioport_* accesses"):
> On 05/25/2016 12:09 PM, Ian Jackson wrote:
> > I think this question can only be resolved de jure by looking at what
> > previous ACPI specification
On 05/25/2016 12:51 PM, Boris Ostrovsky wrote:
> Let me see whether which path we take.
That is "Let me see which code path we are taking in Linux"
-boris
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
On 05/25/2016 12:09 PM, Ian Jackson wrote:
> Jan Beulich writes ("Re: [Xen-devel] [PATCH qemu-traditional] ioreq: Support
> 32-bit default_ioport_* accesses"):
>> On 25.05.16 at 17:36, <boris.ostrov...@oracle.com> wrote:
>>> AccesSize parameter is opti
Jan Beulich writes ("Re: [Xen-devel] [PATCH qemu-traditional] ioreq: Support
32-bit default_ioport_* accesses"):
> On 25.05.16 at 17:36, <boris.ostrov...@oracle.com> wrote:
> > AccesSize parameter is optional when invoking the Register macro. If the
> > AccessSiz
>>> On 25.05.16 at 17:36, wrote:
> This is what the spec says:
>
> AccessSize evaluates to an 8-bit integer that specifies the size of data
> values used when accessing the
> address space as follows:
> 0 - Undefined (legacy)
> 1 - Byte access
> 2 - Word access
> 3 -
>>> On 25.05.16 at 17:08, wrote:
> On 05/25/2016 10:35 AM, Ian Jackson wrote:
>> Ian Jackson writes ("Re: [PATCH qemu-traditional] ioreq: Support 32-bit
> default_ioport_* accesses"):
>>> Boris Ostrovsky writes ("[PATCH qemu-traditional] ioreq: Support 32-bit
>
On 05/25/2016 11:22 AM, Ian Jackson wrote:
> Boris Ostrovsky writes ("Re: [PATCH qemu-traditional] ioreq: Support 32-bit
> default_ioport_* accesses"):
>> IIUIC, the Linux/ACPICA patch makes ACPICA use correct field in ACPI's
>> Generic Address Structure (section 5.2.3.2 in the 6.0 spec). Before
Boris Ostrovsky writes ("Re: [PATCH qemu-traditional] ioreq: Support 32-bit
default_ioport_* accesses"):
> IIUIC, the Linux/ACPICA patch makes ACPICA use correct field in ACPI's
> Generic Address Structure (section 5.2.3.2 in the 6.0 spec). Before the
> patch it used register's bit_width and now
On 05/25/2016 10:35 AM, Ian Jackson wrote:
> Ian Jackson writes ("Re: [PATCH qemu-traditional] ioreq: Support 32-bit
> default_ioport_* accesses"):
>> Boris Ostrovsky writes ("[PATCH qemu-traditional] ioreq: Support 32-bit
>> default_ioport_* accesses"):
>>> Recent changes in ACPICA
Ian Jackson writes ("Re: [PATCH qemu-traditional] ioreq: Support 32-bit
default_ioport_* accesses"):
> Boris Ostrovsky writes ("[PATCH qemu-traditional] ioreq: Support 32-bit
> default_ioport_* accesses"):
> > Recent changes in ACPICA (specifically, Linux commit 66b1ed5aa8dd ("ACPICA:
> > ACPI
Boris Ostrovsky writes ("[PATCH qemu-traditional] ioreq: Support 32-bit
default_ioport_* accesses"):
> Recent changes in ACPICA (specifically, Linux commit 66b1ed5aa8dd ("ACPICA:
> ACPI 2.0, Hardware: Add access_width/bit_offset support for
> acpi_hw_write()") result in guests issuing 32-bit
On Fri, May 20, 2016 at 09:52:40AM -0400, Boris Ostrovsky wrote:
> Recent changes in ACPICA (specifically, Linux commit 66b1ed5aa8dd ("ACPICA:
> ACPI 2.0, Hardware: Add access_width/bit_offset support for
> acpi_hw_write()") result in guests issuing 32-bit accesses to IO space.
>
> QEMU needs to
On Mon, May 23, 2016 at 09:02:58AM -0400, Boris Ostrovsky wrote:
> On 05/23/2016 08:02 AM, Wei Liu wrote:
> > On Fri, May 20, 2016 at 09:52:40AM -0400, Boris Ostrovsky wrote:
> >> Recent changes in ACPICA (specifically, Linux commit 66b1ed5aa8dd ("ACPICA:
> >> ACPI 2.0, Hardware: Add
On 05/23/2016 08:02 AM, Wei Liu wrote:
> On Fri, May 20, 2016 at 09:52:40AM -0400, Boris Ostrovsky wrote:
>> Recent changes in ACPICA (specifically, Linux commit 66b1ed5aa8dd ("ACPICA:
>> ACPI 2.0, Hardware: Add access_width/bit_offset support for
>> acpi_hw_write()") result in guests issuing
On Fri, May 20, 2016 at 09:52:40AM -0400, Boris Ostrovsky wrote:
> Recent changes in ACPICA (specifically, Linux commit 66b1ed5aa8dd ("ACPICA:
> ACPI 2.0, Hardware: Add access_width/bit_offset support for
> acpi_hw_write()") result in guests issuing 32-bit accesses to IO space.
>
> QEMU needs to
Recent changes in ACPICA (specifically, Linux commit 66b1ed5aa8dd ("ACPICA:
ACPI 2.0, Hardware: Add access_width/bit_offset support for
acpi_hw_write()") result in guests issuing 32-bit accesses to IO space.
QEMU needs to be able to handle them.
Signed-off-by: Boris Ostrovsky
16 matches
Mail list logo