All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandru Elisei <alexandru.elisei@arm.com>
To: maz@kernel.org, linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu
Subject: [PATCH 0/2] KVM: arm64: Hide SPE from guests
Date: Fri,  9 Apr 2021 16:21:52 +0100	[thread overview]
Message-ID: <20210409152154.198566-1-alexandru.elisei@arm.com> (raw)

This was part of the KVM SPE series that I posted some time ago [1]. The
series didn't get too much attention, so I've decided to send this
fix/cleanup/improvement separately, to make it easier to review.

I've split the original patch into two because it makes more sense to me
this way, but I'm not opposed to squashing the series back into a single
patch if that is preferred.

Based on v5.12-rc6.

[1] https://www.spinics.net/lists/kvm-arm/msg42962.html

Alexandru Elisei (2):
  KVM: arm64: Don't print warning when trapping SPE registers
  KVM: arm64: Don't advertise FEAT_SPE to guests

 arch/arm64/include/asm/sysreg.h |  2 ++
 arch/arm64/kvm/sys_regs.c       | 15 +++++++++++++++
 2 files changed, 17 insertions(+)

-- 
2.31.1

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

WARNING: multiple messages have this Message-ID (diff)
From: Alexandru Elisei <alexandru.elisei@arm.com>
To: maz@kernel.org, linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu
Cc: james.morse@arm.com, julien.thierry.kdev@gmail.com,
	suzuki.poulose@arm.com
Subject: [PATCH 0/2] KVM: arm64: Hide SPE from guests
Date: Fri,  9 Apr 2021 16:21:52 +0100	[thread overview]
Message-ID: <20210409152154.198566-1-alexandru.elisei@arm.com> (raw)

This was part of the KVM SPE series that I posted some time ago [1]. The
series didn't get too much attention, so I've decided to send this
fix/cleanup/improvement separately, to make it easier to review.

I've split the original patch into two because it makes more sense to me
this way, but I'm not opposed to squashing the series back into a single
patch if that is preferred.

Based on v5.12-rc6.

[1] https://www.spinics.net/lists/kvm-arm/msg42962.html

Alexandru Elisei (2):
  KVM: arm64: Don't print warning when trapping SPE registers
  KVM: arm64: Don't advertise FEAT_SPE to guests

 arch/arm64/include/asm/sysreg.h |  2 ++
 arch/arm64/kvm/sys_regs.c       | 15 +++++++++++++++
 2 files changed, 17 insertions(+)

-- 
2.31.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2021-04-09 15:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 15:21 Alexandru Elisei [this message]
2021-04-09 15:21 ` [PATCH 0/2] KVM: arm64: Hide SPE from guests Alexandru Elisei
2021-04-09 15:21 ` [PATCH 1/2] KVM: arm64: Don't print warning when trapping SPE registers Alexandru Elisei
2021-04-09 15:21   ` Alexandru Elisei
2021-04-09 15:21 ` [PATCH 2/2] KVM: arm64: Don't advertise FEAT_SPE to guests Alexandru Elisei
2021-04-09 15:21   ` Alexandru Elisei
2021-04-11  8:47 ` [PATCH 0/2] KVM: arm64: Hide SPE from guests Marc Zyngier
2021-04-11  8:47   ` Marc Zyngier

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=20210409152154.198566-1-alexandru.elisei@arm.com \
    --to=alexandru.elisei@arm.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maz@kernel.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 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.