All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, Nicholas Piggin <npiggin@gmail.com>
Cc: Timothy Pearson <tpearson@raptorengineering.com>
Subject: Re: [PATCH] KVM: PPC: Book3S HV: Fix KVM_RUN clobbering FP/VEC user registers
Date: Sun, 03 Dec 2023 10:00:37 +1100	[thread overview]
Message-ID: <170155803785.146803.4946329954526131755.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20231122025811.2973-1-npiggin@gmail.com>

On Wed, 22 Nov 2023 12:58:11 +1000, Nicholas Piggin wrote:
> Before running a guest, the host process (e.g., QEMU) FP/VEC registers
> are saved if they were being used, similarly to when the kernel uses FP
> registers. The guest values are then be loaded into regs, and the host
> process registers will be restored lazily when it uses FP/VEC.
> 
> KVM HV has a bug here: the host process registers do get saved, but the
> user MSR bits remain enabled, which indicates the registers are valid
> for the process. After they are clobbered by running the guest, this
> valid indication causes the host process to take on the FP/VEC regiter
> values of the guest.
> 
> [...]

Applied to powerpc/fixes.

[1/1] KVM: PPC: Book3S HV: Fix KVM_RUN clobbering FP/VEC user registers
      https://git.kernel.org/powerpc/c/dc158d23b33df9033bcc8e7117e8591dd2f9d125

cheers

      reply	other threads:[~2023-12-02 23:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22  2:58 [PATCH] KVM: PPC: Book3S HV: Fix KVM_RUN clobbering FP/VEC user registers Nicholas Piggin
2023-12-02 23:00 ` Michael Ellerman [this message]

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=170155803785.146803.4946329954526131755.b4-ty@ellerman.id.au \
    --to=patch-notifications@ellerman.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=npiggin@gmail.com \
    --cc=tpearson@raptorengineering.com \
    /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.