From: Sean Christopherson <seanjc@google.com>
To: Jing Zhang <jingzhangos@google.com>
Cc: KVM <kvm@vger.kernel.org>, KVMARM <kvmarm@lists.linux.dev>,
ARMLinux <linux-arm-kernel@lists.infradead.org>,
Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
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 15:13:25 -0700 [thread overview]
Message-ID: <ZMrVBWg+c3PSUilR@google.com> (raw)
In-Reply-To: <20230726044652.2169513-1-jingzhangos@google.com>
On Tue, Jul 25, 2023, Jing Zhang wrote:
> Add a selftest to verify the support for pointer authentication in KVM
> guest.
>
> Signed-off-by: Jing Zhang <jingzhangos@google.com>
...
> + /* Shouldn't be here unless the pac_corruptor didn't do its work */
> + GUEST_SYNC(FAIL);
FYI, I'm fast tracking guest printf support along with a pile of GUEST_ASSERT()
changes through kvm-x86/selftests[*]. At a glance, this test can probably use
e.g. GUEST_FAIL() to make things easier to debug.
[*] https://lore.kernel.org/all/20230729003643.1053367-1-seanjc@google.com
_______________________________________________
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 22:13 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
2023-08-03 23:42 ` Jing Zhang
2023-08-02 22:13 ` Sean Christopherson [this message]
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=ZMrVBWg+c3PSUilR@google.com \
--to=seanjc@google.com \
--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=oliver.upton@linux.dev \
--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).