[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ACPI endianness
From: |
Michael S. Tsirkin |
Subject: |
Re: ACPI endianness |
Date: |
Mon, 11 Oct 2021 11:55:48 -0400 |
On Mon, Oct 11, 2021 at 03:51:01PM +0200, BALATON Zoltan wrote:
> > ... but given we did not previously do the read, maybe we should keep
> > it that way at least for the time being.
>
> How do you know there was no read before this write? Did you check it? I've
> only added a printf in the write method and saw the value was swapped but
> did not check if there was a read before that. There are no traces in these
> methods so maybe I would not see it unless adding a printf there too.
All I am saying is that qemu did not convert a write into
a read+write.
- ACPI endianness, BALATON Zoltan, 2021/10/10
- Re: ACPI endianness, Michael S. Tsirkin, 2021/10/10
- Re: ACPI endianness, Philippe Mathieu-Daudé, 2021/10/11
- Re: ACPI endianness, BALATON Zoltan, 2021/10/11
- Re: ACPI endianness, Michael S. Tsirkin, 2021/10/11
- Re: ACPI endianness, Jonathan Cameron, 2021/10/11
- Re: ACPI endianness, BALATON Zoltan, 2021/10/11
- Re: ACPI endianness, Michael S. Tsirkin, 2021/10/11
- Re: ACPI endianness, BALATON Zoltan, 2021/10/11
- Re: ACPI endianness,
Michael S. Tsirkin <=
- Re: ACPI endianness, BALATON Zoltan, 2021/10/11
- Re: ACPI endianness, BALATON Zoltan, 2021/10/25
- Re: ACPI endianness, Michael S. Tsirkin, 2021/10/25