From: "Alex Bennée" <alex.bennee@linaro.org>
To: Kashyap Chamarthy <kchamart@redhat.com>
Cc: qemu-devel@nongnu.org, maz@kernel.org,
"Joel Stanley" <joel@jms.id.au>,
"Ninad Palsule" <ninad@linux.ibm.com>,
qemu-arm@nongnu.org,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Alexandre Iooss" <erdnaxe@crans.org>,
"Jamin Lin" <jamin_lin@aspeedtech.com>,
"Cédric Le Goater" <clg@kaod.org>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
"Eric Auger" <eric.auger@redhat.com>,
"Yi Liu" <yi.l.liu@intel.com>, "Hao Wu" <wuhaotsh@google.com>,
"Tyrone Ting" <kfting@nuvoton.com>,
sebott@redhat.com, "Steven Lee" <steven_lee@aspeedtech.com>,
"Zhenzhong Duan" <zhenzhong.duan@intel.com>,
"Troy Lee" <leetroy@gmail.com>,
"Alistair Francis" <alistair@alistair23.me>
Subject: Re: [PATCH v2 2/3] docs/cpu-features: Update "PAuth" (Pointer Authentication) details
Date: Thu, 13 Feb 2025 21:17:43 +0000 [thread overview]
Message-ID: <87pljlpmrs.fsf@draig.linaro.org> (raw)
In-Reply-To: <20250213135032.2987289-3-kchamart@redhat.com> (Kashyap Chamarthy's message of "Thu, 13 Feb 2025 14:50:30 +0100")
Kashyap Chamarthy <kchamart@redhat.com> writes:
> PAuth (Pointer Authentication), a security feature in software, is
> relevant for both KVM and QEMU. Relect this fact into the docs:
>
> - For KVM, `pauth` is a binary, "on" vs "off" option. The host CPU
> will choose the cryptographic algorithm.
>
> - For TCG, however, along with `pauth`, a couple of properties can be
> controlled -- they're are related to cryptographic algorithm choice.
>
> Thanks to Peter Maydell and Marc Zyngier for explaining more about PAuth
> on IRC (#qemu, OFTC).
>
> Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2025-02-13 21:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 13:50 [PATCH v2 0/3] docs: Small changes to system/arm/cpu-features and more Kashyap Chamarthy
2025-02-13 13:50 ` [PATCH v2 1/3] docs/cpu-features: Consistently use vCPU instead of VCPU Kashyap Chamarthy
2025-02-13 21:09 ` Alex Bennée
2025-02-14 15:06 ` Kashyap Chamarthy
2025-02-13 13:50 ` [PATCH v2 2/3] docs/cpu-features: Update "PAuth" (Pointer Authentication) details Kashyap Chamarthy
2025-02-13 21:17 ` Alex Bennée [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-17 16:37 [PATCH v2 0/3] docs: Small changes to system/arm/cpu-features and more Kashyap Chamarthy
2025-02-17 16:37 ` [PATCH v2 2/3] docs/cpu-features: Update "PAuth" (Pointer Authentication) details Kashyap Chamarthy
2025-02-17 17:43 ` Eric Auger
2025-02-18 11:28 ` Kashyap Chamarthy
2025-02-18 11:34 ` Peter Maydell
2025-02-18 11:42 ` Eric Auger
2025-02-18 12:02 ` Kashyap Chamarthy
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=87pljlpmrs.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=alistair@alistair23.me \
--cc=andrew@codeconstruct.com.au \
--cc=clg@kaod.org \
--cc=edgar.iglesias@gmail.com \
--cc=erdnaxe@crans.org \
--cc=eric.auger@redhat.com \
--cc=jamin_lin@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=kchamart@redhat.com \
--cc=kfting@nuvoton.com \
--cc=leetroy@gmail.com \
--cc=maz@kernel.org \
--cc=ninad@linux.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sebott@redhat.com \
--cc=steven_lee@aspeedtech.com \
--cc=wuhaotsh@google.com \
--cc=yi.l.liu@intel.com \
--cc=zhenzhong.duan@intel.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 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.