From: Marc Zyngier <maz@kernel.org>
To: Jing Zhang <jingzhangos@google.com>,Mostafa Saleh <smostafa@google.com>
Cc: KVM <kvm@vger.kernel.org>, KVMARM <kvmarm@lists.linux.dev>,
Oliver Upton <oliver.upton@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Mingwei Zhang <mizhang@google.com>,
David Matlack <dmatlack@google.com>
Subject: Re: [RFC] KVM: Proposed uAPI for querying GSI and irqbypass status
Date: Wed, 05 Aug 2026 09:47:11 +0100 [thread overview]
Message-ID: <86cxvxar8w.wl-maz@kernel.org> (raw)
In-Reply-To: <anLz0HJ9CKuRbTPh@google.com>
On Wed, 05 Aug 2026 09:26:56 +0100,
Mostafa Saleh <smostafa@google.com> wrote:
>
> Hi Jing,
>
> On Fri, Jul 31, 2026 at 10:26:26AM -0700, Jing Zhang wrote:
[drop the LLM generated stuff]
> > While interfaces in debugfs are fantastic for manual, retroactive
> > debugging on a developer workstation, they are not Dependable for
> > fleet-wide observability. This RFC aims to provide a proactive
> > monitoring solution that aligns KVM with production operational
> > requirements across architectures (both ARM and x86).
> >
> > Would love to hear your thoughts on this perspective.
>
> I agree that debugfs is not suitable for that purpose.
>
> My main concerns are:
> 1- Why is /proc/interrupts not enough, it should show whether the
> interrupts are going through the host (not bypassed) and it should
> show when the host get a doorbell if the vCPU was not resident.
This.
Also, there is a very long standing ask to represent the output of
/proc/interrupts as a structured set, retrieved through a generic
kernel interface. I.e. *not* something KVM specific. Everybody asks,
nobody does. As usual.
And if you are interested in things being "Dependable for fleet-wide
observability" (I *love* the LLM-generated jargon), there is no way
you can make sense of what the guest sees without looking at the full
picture, i.e. the full machine.
> 2- Technical feasibility on arm64. Since the host does not have
> visibility into interrupts directly injected into the guest, it
> cannot accurately maintain the proposed counters vgic_its_vlpis_hw.
And GICv5 is going to make things even less observable, as only
doorbells fire on the host. My take is that for these, a PMU-type
interface is better suited.
But in general, a KVM-specific for something that is a system-wide
problem is IMO the wrong approach. You may want to put tglx in that
loop and see what he has to say.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-08-05 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 16:26 [RFC] KVM: Proposed uAPI for querying GSI and irqbypass status Jing Zhang
2026-07-28 9:45 ` Mostafa Saleh
2026-07-31 17:26 ` Jing Zhang
2026-08-05 8:26 ` Mostafa Saleh
2026-08-05 8:47 ` Marc Zyngier [this message]
2026-08-06 0:32 ` Sean Christopherson
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=86cxvxar8w.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=dmatlack@google.com \
--cc=jingzhangos@google.com \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=mizhang@google.com \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=smostafa@google.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