From: "Michael S. Tsirkin" <mst@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] hw/acpi: Set memory regions to native endian as a work around
Date: Mon, 6 Mar 2023 13:34:42 -0500 [thread overview]
Message-ID: <20230306133246-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <485be109-57a5-178a-1ac6-291fd05d9baa@eik.bme.hu>
On Thu, Mar 02, 2023 at 02:42:17PM +0100, BALATON Zoltan wrote:
> On Tue, 21 Feb 2023, Paolo Bonzini wrote:
> > On 2/21/23 13:48, BALATON Zoltan wrote:
> > > My patch works and don't see what else could it break.
> >
> > I strongly suspect that your patch, while fixing access to one byte of
> > the (2-byte) registers, breaks access to the other byte.
> >
> > Thanks for the reproduction instructions, I'll take a look.
>
> Any chance this can still be fixed? As a bugfix we may have one more week
> maybe.
>
> Regards,
> BALATON Zoltan
I'm not holding my breath for a fix ATM but I am also not really willing
to change this for everyone and risk breaking weird configs such as BE
hosts.
How about propagating a flag from pegasos saying "enable memory core bug
workaround"?
--
MST
next prev parent reply other threads:[~2023-03-06 18:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 13:05 [PATCH] hw/acpi: Set memory regions to native endian as a work around BALATON Zoltan
2021-11-08 13:32 ` Michael S. Tsirkin
2021-11-08 15:22 ` BALATON Zoltan
2021-12-16 10:27 ` Michael S. Tsirkin
2021-11-08 14:30 ` Paolo Bonzini
2021-11-08 15:04 ` Paolo Bonzini
2021-11-08 15:16 ` BALATON Zoltan
2021-11-13 18:47 ` BALATON Zoltan
2022-01-19 9:19 ` Michael S. Tsirkin
2022-02-22 14:40 ` Michael S. Tsirkin
2023-02-20 18:24 ` BALATON Zoltan
2023-02-20 22:33 ` Michael S. Tsirkin
2023-02-20 23:25 ` BALATON Zoltan
2023-02-21 8:30 ` Paolo Bonzini
2023-02-21 12:48 ` BALATON Zoltan
2023-02-21 12:55 ` BALATON Zoltan
2023-03-06 22:56 ` Paolo Bonzini
2023-03-06 23:11 ` BALATON Zoltan
2023-03-06 23:36 ` Paolo Bonzini
2023-03-07 0:06 ` BALATON Zoltan
2023-03-07 5:58 ` Paolo Bonzini
2023-03-07 10:01 ` BALATON Zoltan
2023-03-07 11:26 ` Paolo Bonzini
2023-03-07 12:54 ` BALATON Zoltan
2023-03-07 15:14 ` Paolo Bonzini
2023-03-07 15:21 ` BALATON Zoltan
2023-03-07 16:48 ` Paolo Bonzini
2023-04-30 23:10 ` BALATON Zoltan
2023-04-30 23:26 ` BALATON Zoltan
2023-02-21 14:02 ` Paolo Bonzini
2023-03-02 13:42 ` BALATON Zoltan
2023-03-06 18:34 ` Michael S. Tsirkin [this message]
2023-03-03 8:22 ` Michael S. Tsirkin
2023-03-11 20:59 ` 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=20230306133246-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=imammedo@redhat.com \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.