Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Andrew Jones <drjones@redhat.com>
To: kvmarm@lists.cs.columbia.edu
Cc: maz@kernel.org, xu910121@sina.com, Dave.Martin@arm.com
Subject: [PATCH v2 0/3] KVM: arm64: Fix get-reg-list regression
Date: Mon,  2 Nov 2020 19:50:34 +0100	[thread overview]
Message-ID: <20201102185037.49248-1-drjones@redhat.com> (raw)

张东旭 <xu910121@sina.com> reported a regression seen with CentOS
when migrating from an old kernel to a new one. The problem was
that QEMU rejected the migration since KVM_GET_REG_LIST reported
a register was missing on the destination. Extra registers are OK
on the destination, but not missing ones. The regression reproduces
with upstream kernels when migrating from a 4.15 or later kernel,
up to one with commit 73433762fcae ("KVM: arm64/sve: System register
context switch and access support"), to a kernel that includes that
commit, e.g. the latest mainline (5.10-rc2).

The first patch of this series is the fix. The next two patches,
which don't have any intended functional changes, allow ID_SANITISED
to be used for registers that flip between exposing features and
being RAZ, which allows some code to be removed.

v2:
 - CC stable [Marc]
 - Only one RAZ flag is enough [Marc]
 - Move id_visibility() up by read_id_reg() since they'll likely
   be maintained together [drew]

Andrew Jones (3):
  KVM: arm64: Don't hide ID registers from userspace
  KVM: arm64: Check RAZ visibility in ID register accessors
  KVM: arm64: Remove AA64ZFR0_EL1 accessors

 arch/arm64/kvm/sys_regs.c | 96 +++++++++++----------------------------
 arch/arm64/kvm/sys_regs.h | 10 ++++
 2 files changed, 37 insertions(+), 69 deletions(-)

-- 
2.26.2

_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

             reply	other threads:[~2020-11-02 18:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 18:50 Andrew Jones [this message]
2020-11-02 18:50 ` [PATCH v2 1/3] KVM: arm64: Don't hide ID registers from userspace Andrew Jones
2020-11-03 11:18   ` Dave Martin
2020-11-03 13:32     ` Andrew Jones
2020-11-04 16:11       ` Dave Martin
2020-11-02 18:50 ` [PATCH v2 2/3] KVM: arm64: Check RAZ visibility in ID register accessors Andrew Jones
2020-11-03 11:23   ` Dave Martin
2020-11-03 13:38     ` Andrew Jones
2020-11-04 16:31       ` Dave Martin
2020-11-02 18:50 ` [PATCH v2 3/3] KVM: arm64: Remove AA64ZFR0_EL1 accessors Andrew Jones
2020-11-03 11:32   ` Dave Martin
2020-11-03 13:46     ` Andrew Jones
2020-11-04 16:36       ` Dave Martin
2020-11-03 11:37 ` [PATCH v2 0/3] KVM: arm64: Fix get-reg-list regression Dave Martin
2020-11-03 13:52   ` Andrew Jones
2020-11-04 16:41     ` Dave Martin

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=20201102185037.49248-1-drjones@redhat.com \
    --to=drjones@redhat.com \
    --cc=Dave.Martin@arm.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=maz@kernel.org \
    --cc=xu910121@sina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox