From: Karl Mehltretter <kmehltretter@gmail.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Oliver Upton <oupton@kernel.org>,
Sascha Bischoff <sascha.bischoff@arm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Jonathan Cameron <jic23@kernel.org>,
Timothy Hayes <timothy.hayes@arm.com>,
kvmarm@lists.linux.dev, kvm@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: KVM: Fix the GICv5 KVM_IRQ_LINE PPI range
Date: Sat, 15 Aug 2026 15:07:38 +0200 [thread overview]
Message-ID: <aoBhU6XIarXxeQYB@gmail.com> (raw)
In-Reply-To: <86wltrzm5n.wl-maz@kernel.org>
On Sat, Aug 15, 2026 at 11:57:24AM +0100, Marc Zyngier wrote:
> > + in-kernel GICv5: PPI, irq_id between 0 and 63 (incl.), and
>
> No. Please understand the difference between *implementation* and
> *architecture*.
Got it. That distinction could perhaps be clearer in api.rst, but 0-127
is intentional, not a missed doc update.
> > + Userspace must query this attribute after initializing the VGIC with
> > + KVM_DEV_ARM_VGIC_CTRL_INIT.
> > +
>
> Must? Why? Userspace can perfectly live with ever querying this.
Hah, yes. I meant "if you query this, you must do so after init
to get anything other than zero"
Please consider this patch withdrawn.
Thanks,
Karl
prev parent reply other threads:[~2026-08-15 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 9:25 [PATCH] Documentation: KVM: Fix the GICv5 KVM_IRQ_LINE PPI range Karl Mehltretter
2026-08-15 10:57 ` Marc Zyngier
2026-08-15 13:07 ` Karl Mehltretter [this message]
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=aoBhU6XIarXxeQYB@gmail.com \
--to=kmehltretter@gmail.com \
--cc=corbet@lwn.net \
--cc=jic23@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=pbonzini@redhat.com \
--cc=sascha.bischoff@arm.com \
--cc=skhan@linuxfoundation.org \
--cc=timothy.hayes@arm.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