From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>, qemu-devel@nongnu.org
Cc: Igor Mammedov <imammedo@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: ACPI endianness
Date: Mon, 11 Oct 2021 07:52:15 +0200 [thread overview]
Message-ID: <612d2f0b-f312-073d-b796-c76357ba51a2@redhat.com> (raw)
In-Reply-To: <957db5ec-fc70-418-44d9-da4f81f5b98@eik.bme.hu>
On 10/10/21 15:24, BALATON Zoltan wrote:
> Hello,
>
> I'm trying to fix shutdown and reboot on pegasos2 which uses ACPI as
> part of the VIA VT8231 (similar to and modelled in hw/isa/vt82c686b.c)
> and found that the guest writes to ACPI PM1aCNT register come out with
> wrong endianness but not shure why. I have this:
>
> $ qemu-system-ppc -M pegasos2 -monitor stdio
> (qemu) info mtree
> [...]
> memory-region: pci1-io
> 0000000000000000-000000000000ffff (prio 0, i/o): pci1-io
> [...]
> 0000000000000f00-0000000000000f7f (prio 0, i/o): via-pm
> 0000000000000f00-0000000000000f03 (prio 0, i/o): acpi-evt
> 0000000000000f04-0000000000000f05 (prio 0, i/o): acpi-cnt
> 0000000000000f08-0000000000000f0b (prio 0, i/o): acpi-tmr
>
> memory-region: system
> 0000000000000000-ffffffffffffffff (prio 0, i/o): system
> 0000000000000000-000000001fffffff (prio 0, ram): pegasos2.ram
> 0000000080000000-00000000bfffffff (prio 0, i/o): alias pci1-mem0-win
> @pci1-mem 0000000080000000-00000000bfffffff
> 00000000c0000000-00000000dfffffff (prio 0, i/o): alias pci0-mem0-win
> @pci0-mem 00000000c0000000-00000000dfffffff
> 00000000f1000000-00000000f100ffff (prio 0, i/o): mv64361
> 00000000f8000000-00000000f8ffffff (prio 0, i/o): alias pci0-io-win
> @pci0-io 0000000000000000-0000000000ffffff
> 00000000f9000000-00000000f9ffffff (prio 0, i/o): alias pci0-mem1-win
> @pci0-mem 0000000000000000-0000000000ffffff
> 00000000fd000000-00000000fdffffff (prio 0, i/o): alias pci1-mem1-win
> @pci1-mem 0000000000000000-0000000000ffffff
> 00000000fe000000-00000000feffffff (prio 0, i/o): alias pci1-io-win
> @pci1-io 0000000000000000-0000000000ffffff
> 00000000ff800000-00000000ffffffff (prio 0, i/o): alias pci1-mem3-win
> @pci1-mem 00000000ff800000-00000000ffffffff
> 00000000fff00000-00000000fff7ffff (prio 0, rom): pegasos2.rom
>
> The guest (which is big endian PPC and I think wotks on real hardware)
> writes to 0xf05 in the io region which should be the high byte of the
> little endian register but in the acpi code it comes out wrong, instead
> of 0x2800 I get in acpi_pm1_cnt_write: val=0x28
Looks like a northbridge issue (MV64340).
Does Pegasos2 enables bus swapping?
See hw/pci-host/mv64361.c:585:
static void warn_swap_bit(uint64_t val)
{
if ((val & 0x3000000ULL) >> 24 != 1) {
qemu_log_mask(LOG_UNIMP, "%s: Data swap not implemented", __func__);
}
}
next prev parent reply other threads:[~2021-10-11 5:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 13:24 ACPI endianness BALATON Zoltan
2021-10-10 14:03 ` Michael S. Tsirkin
2021-10-10 14:26 ` BALATON Zoltan
2021-10-11 5:52 ` Philippe Mathieu-Daudé [this message]
2021-10-11 10:13 ` BALATON Zoltan
2021-10-11 12:19 ` Michael S. Tsirkin
2021-10-11 13:14 ` Jonathan Cameron
2021-10-11 13:27 ` BALATON Zoltan
2021-10-11 13:34 ` Michael S. Tsirkin
2021-10-11 13:51 ` BALATON Zoltan
2021-10-11 15:55 ` Michael S. Tsirkin
2021-10-11 17:47 ` BALATON Zoltan
2021-10-25 15:05 ` BALATON Zoltan
2021-10-25 17:10 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=612d2f0b-f312-073d-b796-c76357ba51a2@redhat.com \
--to=philmd@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).