public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: James Morse <james.morse@arm.com>
To: kvmarm@lists.cs.columbia.edu
Cc: kvm@vger.kernel.org, Marc Zyngier <marc.zyngier@arm.com>,
	linuxarm@huawei.com, gengdongjiu@huawei.com,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 0/4] support exception state migration and set VSESR_EL2 by user space
Date: Tue, 10 Jul 2018 17:49:48 +0100	[thread overview]
Message-ID: <20180710164952.23736-1-james.morse@arm.com> (raw)

Hi guys,

This is GengDongjiu's get/set events series[0], with additional plumbing for
32bit.

This series adds the get/set events API to KVM for arm/arm64 so that
user-space can migrate pending SError, (which KVM may have made pending
as part of its device emulation), and for RAS make a new SError with a
specific ESR value pending. (Only systems with the v8.2 RAS Extensions
can specify an ESR, KVM advertises this capability with a new cap:
KVM_CAP_ARM_INJECT_SERROR_ESR)

User-space can use this for emulation of the v8.2 CPU RAS features
(using error nodes backed by mmio) or as part of NOTIFY_SEI which
extends a v8.2 RAS SError to also have firmware-first CPER records.


Thanks,

James

[0] https://lists.cs.columbia.edu/pipermail/kvmarm/2018-July/032010.html

Dongjiu Geng (2):
  arm/arm64: KVM: Add KVM_GET/SET_VCPU_EVENTS
  arm64: KVM: export the capability to set guest SError syndrome

James Morse (2):
  KVM: arm64: Share the parts of get/set events useful to 32bit
  KVM: arm: Add 32bit get/set events support

 Documentation/virtual/kvm/api.txt    | 44 +++++++++++++++++++++++---
 arch/arm/include/asm/kvm_host.h      |  5 +++
 arch/arm/include/uapi/asm/kvm.h      | 13 ++++++++
 arch/arm/kvm/guest.c                 | 23 ++++++++++++++
 arch/arm64/include/asm/kvm_emulate.h |  5 +++
 arch/arm64/include/asm/kvm_host.h    |  7 +++++
 arch/arm64/include/uapi/asm/kvm.h    | 13 ++++++++
 arch/arm64/kvm/guest.c               | 33 +++++++++++++++++++
 arch/arm64/kvm/inject_fault.c        |  6 ++--
 arch/arm64/kvm/reset.c               |  4 +++
 include/uapi/linux/kvm.h             |  1 +
 virt/kvm/arm/arm.c                   | 47 ++++++++++++++++++++++++++++
 12 files changed, 194 insertions(+), 7 deletions(-)

-- 
2.18.0

             reply	other threads:[~2018-07-10 16:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10 16:49 James Morse [this message]
2018-07-10 16:49 ` [PATCH v7 1/4] arm/arm64: KVM: Add KVM_GET/SET_VCPU_EVENTS James Morse
2018-07-11  6:48   ` gengdongjiu
2018-07-11  7:45     ` Marc Zyngier
2018-07-10 16:49 ` [PATCH v7 2/4] arm64: KVM: export the capability to set guest SError syndrome James Morse
2018-07-10 16:49 ` [PATCH v7 3/4] KVM: arm64: Share the parts of get/set events useful to 32bit James Morse
2018-07-11  7:16   ` gengdongjiu
2018-07-13 15:27     ` James Morse
2018-07-10 16:49 ` [PATCH v7 4/4] KVM: arm: Add 32bit get/set events support James Morse
2018-07-11  3:14 ` [PATCH v7 0/4] support exception state migration and set VSESR_EL2 by user space gengdongjiu

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=20180710164952.23736-1-james.morse@arm.com \
    --to=james.morse@arm.com \
    --cc=gengdongjiu@huawei.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linuxarm@huawei.com \
    --cc=marc.zyngier@arm.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