From: Marc Zyngier <maz@kernel.org>
To: puranjay@kernel.org
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Arnd Bergmann" <arnd@kernel.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
"Sumit Garg" <sumit.garg@linaro.org>,
puranjay12@gmail.com, "Ard Biesheuvel" <ardb@kernel.org>,
"Oliver Upton" <oliver.upton@linux.dev>,
"Suzuki K Poulose" <suzuki.poulose@arm.com>,
"Joey Gouly" <joey.gouly@arm.com>,
"Zenghui Yu" <zenghui.yu@linux.dev>
Subject: Re: Supporting KVM_GUESTDBG_BLOCKIRQ or something similar on ARM64
Date: Mon, 28 Oct 2024 11:23:30 +0000 [thread overview]
Message-ID: <86ed4031zh.wl-maz@kernel.org> (raw)
In-Reply-To: <mb61p4j4wwlap.fsf@kernel.org>
[+ArdB, which I assume you really wanted to Cc on this, as well as the
KVM/arm64 stakeholders]
On Mon, 28 Oct 2024 10:53:34 +0000,
puranjay@kernel.org wrote:
>
> Hi Everyone,
>
> I work on the BPF JIT for arm64 and regularly use Qemu with gdb for
> debugging by single stepping parts of the code. I realized that whenever
> I enable KVM, single stepping doesn't work as expected and it lands in an
> interrupt handler.
I disagree. Single-stepping works *exactly* as you should expect, by
not interfering with the rest of the system.
> It always worked for me on x86 so I looked in the source code and found
> that x86 supports KVM_GUESTDBG_BLOCKIRQ that blocks IRQs when single
> stepping.
Right, and that is not an architectural behaviour, but something that
helps the person running the debugger. I'm not saying it is not
useful, but that this is an *additional* behaviour that the
architecture is not supposed to cover.
Also, given that KVM_GUESTDBG_BLOCKIRQ has *zero* documentation,
nobody felt compelled to implement it. I didn't even know of its
existence until you mentioned it.
> I assume that arm64 doesn't support KVM_GUESTDBG_BLOCKIRQ because it is
> not trivial to implement this on arm64 due to some architectural
> limitations? There was a patch [1] posted in 2022 to solve this issue
> but it was not merged.
That patch does the wrong thing when it comes to KVM. We are not
building a Linux-only hypervisor, and we need a solution that works
irrespective of the guest.
> Let's start a discussion about what needs to be done to support this on
> arm64.
A good start would be to define the semantics of such a flag:
- what should it affect? the vcpu you are single-stepping? all vcpu?
- should userspace to know that interrupts are pending?
- should this result in any effect on the guest's view of time?
- what of interactions on the rest of the system (such as devices)?
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2024-10-28 11:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 10:53 Supporting KVM_GUESTDBG_BLOCKIRQ or something similar on ARM64 puranjay
2024-10-28 11:23 ` Marc Zyngier [this message]
2024-10-29 8:52 ` Ard Biesheuvel
2024-10-29 9:53 ` Marc Zyngier
2024-10-29 10:00 ` Ard Biesheuvel
2024-10-29 13:57 ` Mark Rutland
2024-10-29 15:36 ` 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=86ed4031zh.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=alex.bennee@linaro.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oliver.upton@linux.dev \
--cc=puranjay12@gmail.com \
--cc=puranjay@kernel.org \
--cc=sumit.garg@linaro.org \
--cc=suzuki.poulose@arm.com \
--cc=zenghui.yu@linux.dev \
/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.