From: Christoffer Dall <cdall@linaro.org>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Shannon Zhao <shannon.zhao@linaro.org>,
kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH v2 0/9] arm64: KVM: Fix PMU exception generation
Date: Tue, 28 Mar 2017 15:37:18 +0200 [thread overview]
Message-ID: <20170328133718.GA20211@cbox> (raw)
In-Reply-To: <20170327160345.12402-1-marc.zyngier@arm.com>
On Mon, Mar 27, 2017 at 05:03:36PM +0100, Marc Zyngier wrote:
> Running the following code:
>
> root@zomby-woof:~# cat test-pmu.c
> int main(int argc, char *argv[])
> {
> unsigned int val;
> asm ("mrc p15, 0, %0, c9, c13, 0\n" : "=r" (val));
> return val;
> }
>
> in a 32bit guest (or a 64bit guest with a 32bit userspace) results in
> this surprising result:
>
> [ 120.347497] kvm [1150]: Unsupported guest CP15 access at: ab0945ae
> [ 120.353689] kvm [1142]: { Op0( 0), Op1( 0), CRn( 9), CRm(13), Op2( 0), func_read },
>
> which is weird, because the guest behaves correctly:
> root@zomby-woof:~# ./test-pmu
> [ 16.184422] test-pmu[740]: undefined instruction: pc=00000000ab0945ae
> [ 16.186043] Code: 00340001 b4800000 af00b085 60396078 (3f1dee19)
> Illegal instruction
>
> It gets the expected UNDEF, and all is fine. So what?
>
> It turns out that the PMU emulation code is a bit lazy, and tells the
> rest of KVM that the emulation has failed, so that an exception gets
> delivered. Subtle differences in the 32bit vs 64bit handling make it
> spit an "Unsupported..." error.
>
> This series tries to set things straight:
> - Make all PMU illegal accesses inject an UNDEF
> - Make these illegal accesses a successful emulation w.r.t the rest of KVM.
>
> In the process, we also squash an interesting bug in the 64bit CP
> access. Similar treatment is applied to the 32bit kernel, except that
> we don't ever inject an exception there (no PMU support yet).
>
I have applied this series to queue (not next since I haven't tested
thoroughly yet), with the fixups agreed in the series.
Thanks,
-Christoffer
WARNING: multiple messages have this Message-ID (diff)
From: cdall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/9] arm64: KVM: Fix PMU exception generation
Date: Tue, 28 Mar 2017 15:37:18 +0200 [thread overview]
Message-ID: <20170328133718.GA20211@cbox> (raw)
In-Reply-To: <20170327160345.12402-1-marc.zyngier@arm.com>
On Mon, Mar 27, 2017 at 05:03:36PM +0100, Marc Zyngier wrote:
> Running the following code:
>
> root at zomby-woof:~# cat test-pmu.c
> int main(int argc, char *argv[])
> {
> unsigned int val;
> asm ("mrc p15, 0, %0, c9, c13, 0\n" : "=r" (val));
> return val;
> }
>
> in a 32bit guest (or a 64bit guest with a 32bit userspace) results in
> this surprising result:
>
> [ 120.347497] kvm [1150]: Unsupported guest CP15 access at: ab0945ae
> [ 120.353689] kvm [1142]: { Op0( 0), Op1( 0), CRn( 9), CRm(13), Op2( 0), func_read },
>
> which is weird, because the guest behaves correctly:
> root at zomby-woof:~# ./test-pmu
> [ 16.184422] test-pmu[740]: undefined instruction: pc=00000000ab0945ae
> [ 16.186043] Code: 00340001 b4800000 af00b085 60396078 (3f1dee19)
> Illegal instruction
>
> It gets the expected UNDEF, and all is fine. So what?
>
> It turns out that the PMU emulation code is a bit lazy, and tells the
> rest of KVM that the emulation has failed, so that an exception gets
> delivered. Subtle differences in the 32bit vs 64bit handling make it
> spit an "Unsupported..." error.
>
> This series tries to set things straight:
> - Make all PMU illegal accesses inject an UNDEF
> - Make these illegal accesses a successful emulation w.r.t the rest of KVM.
>
> In the process, we also squash an interesting bug in the 64bit CP
> access. Similar treatment is applied to the 32bit kernel, except that
> we don't ever inject an exception there (no PMU support yet).
>
I have applied this series to queue (not next since I haven't tested
thoroughly yet), with the fixups agreed in the series.
Thanks,
-Christoffer
next prev parent reply other threads:[~2017-03-28 13:35 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 16:03 [PATCH v2 0/9] arm64: KVM: Fix PMU exception generation Marc Zyngier
2017-03-27 16:03 ` Marc Zyngier
2017-03-27 16:03 ` [PATCH v2 1/9] arm64: KVM: PMU: Refactor pmu_*_el0_disabled Marc Zyngier
2017-03-27 16:03 ` Marc Zyngier
2017-03-27 17:03 ` Suzuki K Poulose
2017-03-27 17:03 ` Suzuki K Poulose
2017-03-27 17:11 ` Marc Zyngier
2017-03-27 17:11 ` Marc Zyngier
2017-03-28 12:46 ` Christoffer Dall
2017-03-28 12:46 ` Christoffer Dall
2017-03-28 13:21 ` Marc Zyngier
2017-03-28 13:21 ` Marc Zyngier
2017-03-27 16:03 ` [PATCH v2 2/9] arm64: KVM: PMU: Inject UNDEF exception on illegal register access Marc Zyngier
2017-03-27 16:03 ` Marc Zyngier
2017-03-28 12:44 ` Christoffer Dall
2017-03-28 12:44 ` Christoffer Dall
2017-03-27 16:03 ` [PATCH v2 3/9] arm64: KVM: PMU: Inject UNDEF on non-privileged accesses Marc Zyngier
2017-03-27 16:03 ` Marc Zyngier
2017-03-28 12:45 ` Christoffer Dall
2017-03-28 12:45 ` Christoffer Dall
2017-03-27 16:03 ` [PATCH v2 4/9] arm64: KVM: Make unexpected reads from WO registers inject an undef Marc Zyngier
2017-03-27 16:03 ` Marc Zyngier
2017-03-28 12:45 ` Christoffer Dall
2017-03-28 12:45 ` Christoffer Dall
2017-03-27 16:03 ` [PATCH v2 5/9] arm64: KVM: PMU: Inject UNDEF on read access to PMSWINC_EL0 Marc Zyngier
2017-03-27 16:03 ` Marc Zyngier
2017-03-28 12:45 ` Christoffer Dall
2017-03-28 12:45 ` Christoffer Dall
2017-03-27 16:03 ` [PATCH v2 6/9] arm64: KVM: Treat sysreg accessors returning false as successful Marc Zyngier
2017-03-27 16:03 ` Marc Zyngier
2017-03-28 12:45 ` Christoffer Dall
2017-03-28 12:45 ` Christoffer Dall
2017-03-27 16:03 ` [PATCH v2 7/9] arm64: KVM: Do not corrupt registers on failed 64bit CP read Marc Zyngier
2017-03-27 16:03 ` Marc Zyngier
2017-03-28 12:46 ` Christoffer Dall
2017-03-28 12:46 ` Christoffer Dall
2017-03-28 13:24 ` Marc Zyngier
2017-03-28 13:24 ` Marc Zyngier
2017-03-27 16:03 ` [PATCH v2 8/9] arm: KVM: Make unexpected register accesses inject an undef Marc Zyngier
2017-03-27 16:03 ` Marc Zyngier
2017-03-28 12:46 ` Christoffer Dall
2017-03-28 12:46 ` Christoffer Dall
2017-03-27 16:03 ` [PATCH v2 9/9] arm: KVM: Treat CP15 accessors returning false as successful Marc Zyngier
2017-03-27 16:03 ` Marc Zyngier
2017-03-28 12:46 ` Christoffer Dall
2017-03-28 12:46 ` Christoffer Dall
2017-03-28 13:37 ` Christoffer Dall [this message]
2017-03-28 13:37 ` [PATCH v2 0/9] arm64: KVM: Fix PMU exception generation 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=20170328133718.GA20211@cbox \
--to=cdall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=shannon.zhao@linaro.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.