From: "Michael S. Tsirkin" <mst@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: imammedo@redhat.com, Simon John <github@the-jedi.co.uk>,
qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH] Allow acpi-tmr size=2
Date: Mon, 13 Jul 2020 07:14:01 -0400 [thread overview]
Message-ID: <20200713070946-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <4a5cfe21-d370-8ebf-b905-c37d39b68353@msgid.tls.msk.ru>
On Mon, Jul 13, 2020 at 10:20:12AM +0300, Michael Tokarev wrote:
> 12.07.2020 15:00, Simon John wrote:
> > macos guests no longer boot after commit 5d971f9e672507210e77d020d89e0e89165c8fc9
> >
> > acpi-tmr needs 2 byte memory accesses, so breaks as that commit only allows 4 bytes.
> >
> > Fixes: 5d971f9e672507210e7 (memory: Revert "memory: accept mismatching sizes in memory_region_access_valid")
> > Buglink: https://bugs.launchpad.net/qemu/+bug/1886318
>
> Actually this fixes 77d58b1e47c8d1c661f98f12b47ab519d3561488
> Author: Gerd Hoffmann <kraxel@redhat.com>
> Date: Thu Nov 22 12:12:30 2012 +0100
> Subject: apci: switch timer to memory api
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
>
> because this is the commit which put min_access_size = 4 in there
> (5d971f9e672507210e7 is just a messenger, actual error were here
> earlier but it went unnoticed).
>
> While min_access_size=4 was most likely an error, I wonder why
> we use 1 now, while the subject says it needs 2? What real min
> size is here for ACPI PM timer?
>
> /mjt
Well the ACPI spec 1.0b says
4.7.3.3 Power Management Timer (PM_TMR)
...
This register is accessed as 32 bits.
and this text is still there in 6.2.
So it's probably worth it to cite this in the commit log
and explain it's a spec violation.
I think it's better to be restrictive and only allow the
minimal variation from spec - in this case I guess this means 2 byte
reads.
In any case pls do include an explanation for why you picked
one over the other.
>
> > Signed-off-by: Simon John <git@the-jedi.co.uk>
> > ---
> > Â hw/acpi/core.c | 2 +-
> > Â 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/hw/acpi/core.c b/hw/acpi/core.c
> > index f6d9ec4f13..05ff29b9d7 100644
> > --- a/hw/acpi/core.c
> > +++ b/hw/acpi/core.c
> > @@ -527,7 +527,7 @@ static void acpi_pm_tmr_write(void *opaque, hwaddr addr, uint64_t val,
> > Â static const MemoryRegionOps acpi_pm_tmr_ops = {
> > Â Â Â Â .read = acpi_pm_tmr_read,
> > Â Â Â Â .write = acpi_pm_tmr_write,
> > -Â Â Â .valid.min_access_size = 4,
> > +Â Â Â .valid.min_access_size = 1,
> > Â Â Â Â .valid.max_access_size = 4,
> > Â Â Â Â .endianness = DEVICE_LITTLE_ENDIAN,
> > Â };
next prev parent reply other threads:[~2020-07-13 11:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 12:00 [PATCH] Allow acpi-tmr size=2 Simon John
2020-07-13 7:20 ` Michael Tokarev
2020-07-13 7:43 ` Michael Tokarev
2020-07-13 11:01 ` Michael S. Tsirkin
2020-07-13 11:14 ` Michael S. Tsirkin [this message]
2020-07-13 11:46 ` Simon John
2020-07-13 12:17 ` Michael S. Tsirkin
2020-07-13 14:16 ` Michael Tokarev
2020-07-14 7:55 ` Michael S. Tsirkin
2020-07-14 10:55 ` Philippe Mathieu-Daudé
2020-07-14 11:12 ` Michael S. Tsirkin
2020-07-14 9:29 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2020-07-13 13:50 Simon John
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=20200713070946-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=github@the-jedi.co.uk \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=mjt@tls.msk.ru \
--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).