qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: "Gerd Hoffmann" <kraxel@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH-for-9.2? v2 1/2] hw/display/vga: Do not reset 'big_endian_fb' in vga_common_reset()
Date: Tue, 03 Dec 2024 12:30:49 +1100	[thread overview]
Message-ID: <2f6a993cd0e12c2bf903440f9f921d7af58bee36.camel@kernel.crashing.org> (raw)
In-Reply-To: <21c5e930-d7ee-4dd8-a238-862f4db87849@linaro.org>

It's been a long time, I only have vague memories of this :-) But I
think it should be ok.

It does definitely make sense in the virtio case and similar where
the property is set once for the instance.

For bochs and ati, there's a register to configure it as well, so there
*may* be an expectation that it gets reset there, I'm less certain.

So tentatively...

Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>


On Mon, 2024-12-02 at 20:48 +0100, Philippe Mathieu-Daudé wrote:
> ping?
> 
> On 29/11/24 11:17, Philippe Mathieu-Daudé wrote:
> > The 'pci-vga' device allow setting a 'big-endian-framebuffer'
> > property since commit 3c2784fc864 ("vga: Expose framebuffer
> > byteorder as a QOM property"). Similarly, the 'virtio-vga'
> > device since commit 8be61ce2ce3 ("virtio-vga: implement
> > big-endian-framebuffer property").
> > 
> > Both call vga_common_reset() in their reset handler, respectively
> > pci_secondary_vga_reset() and virtio_vga_base_reset_hold(), which
> > reset 'big_endian_fb', overwritting the property. This is not
> > correct: the hardware is expected to keep its configured
> > endianness during resets.
> > 
> > Move 'big_endian_fb' assignment from vga_common_reset() to
> > vga_common_init() which is called once when the common VGA state
> > is initialized.
> > 
> > Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> > ---
> >   hw/display/vga.c | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/hw/display/vga.c b/hw/display/vga.c
> > index 892fedc8dce..b074b58c90d 100644
> > --- a/hw/display/vga.c
> > +++ b/hw/display/vga.c
> > @@ -1873,7 +1873,6 @@ void vga_common_reset(VGACommonState *s)
> >       s->cursor_start = 0;
> >       s->cursor_end = 0;
> >       s->cursor_offset = 0;
> > -    s->big_endian_fb = s->default_endian_fb;
> >       memset(s->invalidated_y_table, '\0', sizeof(s-
> > >invalidated_y_table));
> >       memset(s->last_palette, '\0', sizeof(s->last_palette));
> >       memset(s->last_ch_attr, '\0', sizeof(s->last_ch_attr));
> > @@ -2266,6 +2265,7 @@ bool vga_common_init(VGACommonState *s,
> > Object *obj, Error **errp)
> >        * all target endian dependencies from this file.
> >        */
> >       s->default_endian_fb = target_words_bigendian();
> > +    s->big_endian_fb = s->default_endian_fb;
> >   
> >       vga_dirty_log_start(s);
> >   



  reply	other threads:[~2024-12-03  1:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-29 10:17 [PATCH v2 0/2] hw/display/vga: Do not reset 'big_endian_fb' in vga_common_reset() Philippe Mathieu-Daudé
2024-11-29 10:17 ` [PATCH-for-9.2? v2 1/2] " Philippe Mathieu-Daudé
2024-12-02 19:48   ` Philippe Mathieu-Daudé
2024-12-03  1:30     ` Benjamin Herrenschmidt [this message]
2024-12-03 10:51       ` Gerd Hoffmann
2024-12-03 12:21         ` BALATON Zoltan
2024-12-05 23:00         ` Benjamin Herrenschmidt
2024-12-06  9:28           ` Gerd Hoffmann
2024-12-09  1:12             ` Benjamin Herrenschmidt
2024-11-29 10:17 ` [PATCH v2 2/2] hw/display/vga: Remove pointless VGACommonState::default_endian_fb Philippe Mathieu-Daudé

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=2f6a993cd0e12c2bf903440f9f921d7af58bee36.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=kraxel@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --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).