From: Marc Zyngier <maz@kernel.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org,
kernel-team@android.com, kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH v2] hw/arm/virt: KVM: Enable PAuth when supported by the host
Date: Thu, 06 Jan 2022 19:25:42 +0000 [thread overview]
Message-ID: <874k6gzmx5.wl-maz@kernel.org> (raw)
In-Reply-To: <364fc879-4b13-cf37-53e0-628a843c7bfa@linaro.org>
On Thu, 06 Jan 2022 18:26:29 +0000,
Richard Henderson <richard.henderson@linaro.org> wrote:
>
> Mm. It does beg the question of why KVM exposes multiple bits. If
> they must be tied, then it only serves to make the interface more
> complicated than necessary. We would be better served to have a
> single bit to control all of PAuth.
In hindsight, there is a lot I would change in the KVM userspace ABI,
and a lot I should have pushed back on. Unfortunately, there is little
we can do now to fix it (userspace expecting this behaviour has been
in the wild for almost 3 years already).
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org, kvmarm@lists.cs.columbia.edu,
kvm@vger.kernel.org, kernel-team@android.com,
Eric Auger <eric.auger@redhat.com>,
Andrew Jones <drjones@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH v2] hw/arm/virt: KVM: Enable PAuth when supported by the host
Date: Thu, 06 Jan 2022 19:25:42 +0000 [thread overview]
Message-ID: <874k6gzmx5.wl-maz@kernel.org> (raw)
In-Reply-To: <364fc879-4b13-cf37-53e0-628a843c7bfa@linaro.org>
On Thu, 06 Jan 2022 18:26:29 +0000,
Richard Henderson <richard.henderson@linaro.org> wrote:
>
> Mm. It does beg the question of why KVM exposes multiple bits. If
> they must be tied, then it only serves to make the interface more
> complicated than necessary. We would be better served to have a
> single bit to control all of PAuth.
In hindsight, there is a lot I would change in the KVM userspace ABI,
and a lot I should have pushed back on. Unfortunately, there is little
we can do now to fix it (userspace expecting this behaviour has been
in the wild for almost 3 years already).
M.
--
Without deviation from the norm, progress is not possible.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Andrew Jones <drjones@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
Eric Auger <eric.auger@redhat.com>,
kernel-team@android.com, kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH v2] hw/arm/virt: KVM: Enable PAuth when supported by the host
Date: Thu, 06 Jan 2022 19:25:42 +0000 [thread overview]
Message-ID: <874k6gzmx5.wl-maz@kernel.org> (raw)
In-Reply-To: <364fc879-4b13-cf37-53e0-628a843c7bfa@linaro.org>
On Thu, 06 Jan 2022 18:26:29 +0000,
Richard Henderson <richard.henderson@linaro.org> wrote:
>
> Mm. It does beg the question of why KVM exposes multiple bits. If
> they must be tied, then it only serves to make the interface more
> complicated than necessary. We would be better served to have a
> single bit to control all of PAuth.
In hindsight, there is a lot I would change in the KVM userspace ABI,
and a lot I should have pushed back on. Unfortunately, there is little
we can do now to fix it (userspace expecting this behaviour has been
in the wild for almost 3 years already).
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2022-01-06 19:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 18:05 [PATCH v2] hw/arm/virt: KVM: Enable PAuth when supported by the host Marc Zyngier
2022-01-03 18:05 ` Marc Zyngier
2022-01-03 18:05 ` Marc Zyngier
2022-01-05 14:58 ` Andrew Jones
2022-01-05 14:58 ` Andrew Jones
2022-01-05 14:58 ` Andrew Jones
2022-01-05 21:36 ` Richard Henderson
2022-01-05 21:36 ` Richard Henderson
2022-01-05 21:36 ` Richard Henderson
2022-01-06 9:16 ` Marc Zyngier
2022-01-06 9:16 ` Marc Zyngier
2022-01-06 9:16 ` Marc Zyngier
2022-01-06 17:20 ` Richard Henderson
2022-01-06 17:20 ` Richard Henderson
2022-01-06 17:20 ` Richard Henderson
2022-01-06 17:29 ` Marc Zyngier
2022-01-06 17:29 ` Marc Zyngier
2022-01-06 17:29 ` Marc Zyngier
2022-01-06 18:26 ` Richard Henderson
2022-01-06 18:26 ` Richard Henderson
2022-01-06 18:26 ` Richard Henderson
2022-01-06 19:25 ` Marc Zyngier [this message]
2022-01-06 19:25 ` Marc Zyngier
2022-01-06 19:25 ` Marc Zyngier
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=874k6gzmx5.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=kernel-team@android.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@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.