From: Oliver Upton <oliver.upton@linux.dev>
To: Jing Zhang <jingzhangos@google.com>
Cc: Marc Zyngier <maz@kernel.org>, KVM <kvm@vger.kernel.org>,
KVMARM <kvmarm@lists.linux.dev>,
ARMLinux <linux-arm-kernel@lists.infradead.org>,
Paolo Bonzini <pbonzini@redhat.com>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH v1] KVM: arm64: selftests: Test pointer authentication support in KVM guest
Date: Wed, 2 Aug 2023 20:17:16 +0000 [thread overview]
Message-ID: <ZMq5zDJ16xav7NPa@linux.dev> (raw)
In-Reply-To: <CAAdAUthi6oZ6oRQDFLeOFVwm2dtcTK2ERJm316x0bdn5TQObYw@mail.gmail.com>
Hi Jing,
Nothing serious, but when you're replying on a thread can you add a
leading and trailing line of whitespace between the quotation and your
reply? Otherwise threads get really dense and hard to read.
On Wed, Aug 02, 2023 at 10:19:30AM -0700, Jing Zhang wrote:
> > > + case FAIL_KVM:
> > > + TEST_FAIL("KVM doesn't support guest PAuth!\n");
> >
> > Why is that a hard failure? The vast majority of the HW out there
> > doesn't support PAuth...
> Since previous TEST_REQUIRES have passed, KVM should be able to
> support guest PAuth. The test will be skipped on those HW without
> PAuth.
So then what is the purpose of this failure mode? The only case where
this would happen is if KVM is if KVM screwed up the emulation somehow,
took a trap on a PAC instruction or register and reflected that back
into the guest as an UNDEF.
That's a perfectly valid thing to test for, but the naming and failure
messages should indicate what actually happened.
> > As I mentioned above, another thing I'd like to see is a set of
> > reference results for a given set of keys and architected algorithm
> > (QARMA3, QARMA5) so that we can compare between implementations
> > (excluding the IMPDEF implementations, of course).
> Sure. Will do.
I was initially hesitant towards testing PAC like this since it is
entirely a hardware issue besides KVM context switching, but you could
spin this off as a way to test if vCPU save/restore works correctly by
priming the vCPU from userspace.
Marc, is there something else here you're interested in exercising I
may've missed?
--
Thanks,
Oliver
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-02 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230726044652.2169513-1-jingzhangos@google.com>
[not found] ` <871qgvrwbi.wl-maz@kernel.org>
2023-08-02 17:19 ` [PATCH v1] KVM: arm64: selftests: Test pointer authentication support in KVM guest Jing Zhang
2023-08-02 20:17 ` Oliver Upton [this message]
2023-08-03 23:42 ` Jing Zhang
2023-08-02 22:13 ` Sean Christopherson
2023-08-03 3:32 ` Jing Zhang
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=ZMq5zDJ16xav7NPa@linux.dev \
--to=oliver.upton@linux.dev \
--cc=james.morse@arm.com \
--cc=jingzhangos@google.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.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;
as well as URLs for NNTP newsgroup(s).