From: alex.bennee@linaro.org (Alex Bennée)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] plug KVM ARMv7 debug leakage
Date: Thu, 11 May 2017 13:46:10 +0100 [thread overview]
Message-ID: <20170511124612.11212-1-alex.bennee@linaro.org> (raw)
Hi,
This is pretty much v1 + comments from Marc and a minor re-factor of
the trap path to make it cleaner w.r.t. cp14/cp15 trapping.
Zhichao Huang (2):
KVM: arm: plug potential guest hardware debug leakage
KVM: arm: rename pm_fake handler to trap_raz_wi
arch/arm/include/asm/kvm_coproc.h | 3 +-
arch/arm/kvm/coproc.c | 105 ++++++++++++++++++++++++++------------
arch/arm/kvm/handle_exit.c | 4 +-
arch/arm/kvm/hyp/switch.c | 4 +-
4 files changed, 80 insertions(+), 36 deletions(-)
--
2.11.0
next reply other threads:[~2017-05-11 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 12:46 Alex Bennée [this message]
2017-05-11 12:46 ` [PATCH v2 1/2] KVM: arm: plug potential guest hardware debug leakage Alex Bennée
2017-05-11 12:46 ` [PATCH v2 2/2] KVM: arm: rename pm_fake handler to trap_raz_wi Alex Bennée
2017-05-15 12:30 ` [PATCH v2 0/2] plug KVM ARMv7 debug leakage Christoffer Dall
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=20170511124612.11212-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).