qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: ~myrslint <myrskylintu@proton.me>,
	qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH qemu v8 1/1] Honor guest PAT on x86, absent Bochs display
Date: Tue, 14 Oct 2025 23:01:11 +0300	[thread overview]
Message-ID: <2f9abed7-2cb8-4c96-b9cd-5e8d2084b1e7@collabora.com> (raw)
In-Reply-To: <176045956423.5579.13349691093596703310-1@git.sr.ht>

On 10/14/25 19:23, ~myrslint wrote:
> From: myrslint <qemu.haziness801@passinbox.com>
> 
> On x86_64, where most CPUs support self-snoop, it is preferrable to
> always honor guest PAT. Not doing so is a quirk. There is a default
> enabled KVM quirk flag which enforces not doing so due to a former bug
> in Bochs display driver.
> 
> The bug has been fixed but not enough has yet passed since so we only
> disable said quirk flag if a Bochs display is not configured for the
> virtual machine.
> 
> This commit also moves around a bit of code that would be called when
> the initialization of a VM is done.
> 
> Signed-off-by: myrslint <qemu.haziness801@passinbox.com>
> ---
>  accel/kvm/kvm-all.c        |  1 +
>  accel/stubs/kvm-stub.c     |  1 +
>  hw/display/bochs-display.c | 17 +++++++++++++++
>  include/system/kvm.h       |  9 ++++++++
>  target/i386/kvm/kvm.c      | 42 +++++++++++++++++++++++++++++++-------
>  5 files changed, 63 insertions(+), 7 deletions(-)

Looks perfect. Now up to Paolo to review further and apply the patch.

Reviewed-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>

-- 
Best regards,
Dmitry


  reply	other threads:[~2025-10-14 20:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14 16:32 [PATCH qemu v8 0/1] Honor guest PAT on x86, absent Bochs display ~myrslint
2025-10-14 16:23 ` [PATCH qemu v8 1/1] " ~myrslint
2025-10-14 20:01   ` Dmitry Osipenko [this message]
2025-10-14 20:07     ` Dmitry Osipenko

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=2f9abed7-2cb8-4c96-b9cd-5e8d2084b1e7@collabora.com \
    --to=dmitry.osipenko@collabora.com \
    --cc=kraxel@redhat.com \
    --cc=myrskylintu@proton.me \
    --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 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).