From: Marc Zyngier <maz@kernel.org>
To: Jiaqi Yan <jiaqiyan@google.com>
Cc: oliver.upton@linux.dev, joey.gouly@arm.com,
suzuki.poulose@arm.com, yuzenghui@huawei.com,
catalin.marinas@arm.com, will@kernel.org, pbonzini@redhat.com,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
kvm@vger.kernel.org, duenwen@google.com, rananta@google.com,
James Houghton <jthoughton@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v1] KVM: arm64: Introduce KVM_CAP_ARM_SIGBUS_ON_SEA
Date: Tue, 12 Nov 2024 08:55:21 +0000 [thread overview]
Message-ID: <877c98u8zq.wl-maz@kernel.org> (raw)
In-Reply-To: <CACw3F51B-RKE0OHGZwoQo1LPxygYc77VAbCHNfU25VVrpHc4-g@mail.gmail.com>
On Fri, 08 Nov 2024 21:18:50 +0000,
Jiaqi Yan <jiaqiyan@google.com> wrote:
>
> There is also a kernel config called ARM64_RAS_EXTN but I believe it
> is for the host CPU, not about VM's RAS.
>
> But taking Oliver's opinion into account, I think we want to remove
> KVM_CAP_ARM_SIGBUS_ON_SEA. Wonder what your thoughts are.
If we stick to a signal-based signalling (which I still dislike with a
burning passion), then I agree it can be removed, as this is no
different from a signal being delivered from the rest of the kernel.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2024-11-12 8:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 21:21 [RFC PATCH v1] KVM: arm64: Introduce KVM_CAP_ARM_SIGBUS_ON_SEA Jiaqi Yan
2024-10-31 21:46 ` Oliver Upton
2024-11-08 4:54 ` Jiaqi Yan
2024-11-01 9:03 ` Marc Zyngier
2024-11-04 5:02 ` Jiaqi Yan
2024-11-08 21:18 ` Jiaqi Yan
2024-11-12 8:55 ` Marc Zyngier [this message]
2024-11-12 8:51 ` Marc Zyngier
2024-11-19 23:57 ` Jiaqi Yan
2024-11-20 7:46 ` Oliver Upton
2024-12-06 1:02 ` Jiaqi Yan
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=877c98u8zq.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=duenwen@google.com \
--cc=jiaqiyan@google.com \
--cc=joey.gouly@arm.com \
--cc=jthoughton@google.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=rananta@google.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).