From: Andrew Jones <drjones@redhat.com>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
"'Marc Zyngier'" <marc.zyngier@arm.com>
Subject: Re: [PATCH v4 0/4] KVM: arm64: BUG FIX: Correctly handle zero register transfers
Date: Mon, 7 Dec 2015 17:45:55 -0600 [thread overview]
Message-ID: <20151207234555.GA2980@hawk.localdomain> (raw)
In-Reply-To: <20151207223631.GJ4402@hawk.localdomain>
On Mon, Dec 07, 2015 at 04:36:31PM -0600, Andrew Jones wrote:
> On Mon, Dec 07, 2015 at 11:36:28AM +0300, Pavel Fedin wrote:
> > Hello!
> >
> > > FYI, I tried writing test cases for this issue with kvm-unit-tests. The
> > > issue didn't reproduce for me. It's quite possible my test cases are
> > > flawed, so I'm not making any claims about the validity of the series
> >
> > This is indeed very interesting, so i'll take a look at it.
> > For now i've just only took a quick glance at the code, and i have at least one suggestion. Could you happen to have sp == 0 in
> > check_xzr_sysreg()? In this case it will magically work.
> > Also, you could try to write a test which tries to overwrite xzr. Something like:
> >
> > volatile int *addr1;
> > volatile int *addr2;
> >
> > asm volatile("str %3, [%1]\n\t"
> > "ldr wzr, [%1]\n\t"
> > "str wzr, [%2]\n\t",
> > "ldr %0, [%2]\n\t"
> > :"=r"(res):"r"(addr1), "r"(addr2), "r"(some_nonzero_val):"memory");
> >
> > Then check for res == some_nonzero_val. If they are equal, you've got the bug :)
> >
>
> Besides the fixes mentioned in other mails, I did add this load to xzr
> tests too. For mmio we get the expected failure. mrs seems to work
> though, but maybe that's expected.
>
> qemu-system-aarch64 -machine virt,accel=kvm -cpu host \
> -device virtio-serial-device -device virtconsole,chardev=ctd \
> -chardev testdev,id=ctd -display none -serial stdio \
> -kernel arm/xzr-test.flat -smp 2
>
> PASS: mmio: sanity check: read 0x55555555
> FAIL: mmio: 'str wzr' check: read 0x0badc0de
> FAIL: mmio: 'ldr wzr' check: read 0x0badc0de
> PASS: sysreg: sp = 0x00000000401affe0
> FAIL: sysreg: from xzr check: read 0xffffc0de0badc0de
> PASS: sysreg: to xzr check: read 0x0000000000000000
>
I messed up the "load into xzr" test royally in the last attached patch.
It was quite wrong. I have now tested
asm volatile(
"str %3, [%1]\n\t"
"ldr wzr, [%1]\n\t"
"str wzr, [%2]\n\t"
"ldr %0, [%2]\n\t"
:"=r"(val):"r"(addr), "r"(addr2), "r"(0x55555555):"memory");
report("mmio: 'ldr wzr' check: read 0x%08lx", val != 0x55555555, val);
which passes and
val = readl(addr);
printf("addr = 0x%08lx\n", val);
val = readl(addr2);
printf("addr2 = 0x%08lx\n", val);
gives
addr = 0x55555555
addr2 = 0x00000000
So it looks like we don't "change" xzr somehow with loads. Anyway, I
probably won't clean this test up and post it. I don't think we really
need to add it as a regression test, unless others disagree and would
like to see it added.
Thanks,
drew
next prev parent reply other threads:[~2015-12-07 23:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 12:03 [PATCH v4 0/4] KVM: arm64: BUG FIX: Correctly handle zero register transfers Pavel Fedin
2015-12-04 12:03 ` [PATCH v4 1/4] KVM: arm64: Correctly handle zero register during MMIO Pavel Fedin
2015-12-04 15:33 ` Marc Zyngier
2015-12-04 12:03 ` [PATCH v4 2/4] KVM: arm64: Remove const from struct sys_reg_params Pavel Fedin
2015-12-04 13:00 ` Marc Zyngier
2015-12-04 12:03 ` [PATCH v4 3/4] KVM: arm64: Correctly handle zero register in system register accesses Pavel Fedin
2015-12-04 12:03 ` [PATCH v4 4/4] KVM: arm64: Get rid of old vcpu_reg() Pavel Fedin
2015-12-05 0:33 ` [PATCH v4 0/4] KVM: arm64: BUG FIX: Correctly handle zero register transfers Andrew Jones
2015-12-07 8:36 ` Pavel Fedin
2015-12-07 22:36 ` Andrew Jones
2015-12-07 23:45 ` Andrew Jones [this message]
2015-12-08 6:57 ` Pavel Fedin
2015-12-08 14:48 ` Andrew Jones
2015-12-07 8:47 ` Pavel Fedin
2015-12-07 21:50 ` Andrew Jones
2015-12-07 9:48 ` Pavel Fedin
2015-12-07 21:58 ` Andrew Jones
2015-12-07 22:25 ` Andrew Jones
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=20151207234555.GA2980@hawk.localdomain \
--to=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=p.fedin@samsung.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