From: Marc Zyngier <maz@kernel.org>
To: Jing Zhang <jingzhangos@google.com>
Cc: Cornelia Huck <cohuck@redhat.com>, KVM <kvm@vger.kernel.org>,
KVMARM <kvmarm@lists.linux.dev>,
ARMLinux <linux-arm-kernel@lists.infradead.org>,
Oliver Upton <oliver.upton@linux.dev>,
Will Deacon <will@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Fuad Tabba <tabba@google.com>, Reiji Watanabe <reijiw@google.com>,
Raghavendra Rao Ananta <rananta@google.com>,
Suraj Jitindar Singh <surajjs@amazon.com>
Subject: Re: [PATCH v8 02/11] KVM: arm64: Document KVM_ARM_GET_REG_WRITABLE_MASKS
Date: Mon, 21 Aug 2023 18:30:28 +0100 [thread overview]
Message-ID: <da71d814ea1c9485c523b0d823281ff5@kernel.org> (raw)
In-Reply-To: <CAAdAUtjG-9Ttdk3_T+OV6ea3p_r9q0yrE1XJUpdB0PwSJsN6VA@mail.gmail.com>
On 2023-08-21 18:24, Jing Zhang wrote:
> On Thu, Aug 17, 2023 at 7:00 AM Marc Zyngier <maz@kernel.org> wrote:
>>
>> On Thu, 17 Aug 2023 09:16:56 +0100,
>> Cornelia Huck <cohuck@redhat.com> wrote:
>> >
>> > On Mon, Aug 14 2023, Jing Zhang <jingzhangos@google.com> wrote:
>> >
>> > > Maybe it'd be better to leave this to whenever we do need to add other
>> > > range support?
>> >
>> > My point is: How does userspace figure out if the kernel that is running
>> > supports ranges other than id regs? If this is just an insurance against
>> > changes that might arrive or not, we can live with the awkward "just try
>> > it out" approach; if we think it's likely that we'll need to extend it,
>> > we need to add the mechanism for userspace to find out about it now, or
>> > it would need to probe for presence of the mechanism...
>>
>> Agreed. Nothing like the present to address this sort of things. it
>> really doesn't cost much, and I'd rather have it right now.
>>
>> Here's a vague attempt at an advertising mechanism. If people are OK
>> with it, I can stash that on top of Jing's series.
[...]
> Looks good to me.
Well, that's of course conditional on the other comments
I made against this series. And we're seriously running
out of time...
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2023-08-21 17:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 16:21 [PATCH v8 00/11] Enable writable for idregs DFR0,PFR0, MMFR{0,1,2,3} Jing Zhang
2023-08-07 16:21 ` [PATCH v8 01/11] KVM: arm64: Allow userspace to get the writable masks for feature ID registers Jing Zhang
2023-08-07 16:22 ` [PATCH v8 02/11] KVM: arm64: Document KVM_ARM_GET_REG_WRITABLE_MASKS Jing Zhang
2023-08-14 9:46 ` Cornelia Huck
2023-08-14 17:25 ` Jing Zhang
2023-08-17 8:16 ` Cornelia Huck
2023-08-17 14:00 ` Marc Zyngier
2023-08-21 7:17 ` Cornelia Huck
2023-08-21 17:24 ` Jing Zhang
2023-08-21 17:30 ` Marc Zyngier [this message]
2023-08-07 16:22 ` [PATCH v8 03/11] KVM: arm64: Use guest ID register values for the sake of emulation Jing Zhang
2023-08-07 16:22 ` [PATCH v8 04/11] KVM: arm64: Reject attempts to set invalid debug arch version Jing Zhang
2023-08-07 16:22 ` [PATCH v8 05/11] KVM: arm64: Enable writable for ID_AA64DFR0_EL1 and ID_DFR0_EL1 Jing Zhang
2023-08-17 15:43 ` Marc Zyngier
2023-08-21 17:37 ` Jing Zhang
2023-08-07 16:22 ` [PATCH v8 06/11] KVM: arm64: Bump up the default KVM sanitised debug version to v8p8 Jing Zhang
2023-08-07 16:22 ` [PATCH v8 07/11] KVM: arm64: Enable writable for ID_AA64PFR0_EL1 Jing Zhang
2023-08-17 15:53 ` Marc Zyngier
2023-08-21 17:40 ` Jing Zhang
2023-08-07 16:22 ` [PATCH v8 08/11] KVM: arm64: Refactor helper Macros for idreg desc Jing Zhang
2023-08-07 16:22 ` [PATCH v8 09/11] KVM: arm64: Enable writable for ID_AA64MMFR{0, 1, 2, 3}_EL1 Jing Zhang
2023-08-07 16:22 ` [PATCH v8 10/11] KVM: arm64: selftests: Import automatic system register definition generation from kernel Jing Zhang
2023-08-16 6:54 ` Shaoqin Huang
2023-08-16 17:15 ` Jing Zhang
2023-08-07 16:22 ` [PATCH v8 11/11] KVM: arm64: selftests: Test for setting ID register from usersapce Jing Zhang
2023-08-16 6:58 ` Shaoqin Huang
2023-08-16 17:23 ` 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=da71d814ea1c9485c523b0d823281ff5@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=cohuck@redhat.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=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=rananta@google.com \
--cc=reijiw@google.com \
--cc=surajjs@amazon.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox