From: Marc Zyngier <maz@kernel.org>
To: Tian Zheng <zhengtian10@huawei.com>
Cc: <oliver.upton@linux.dev>, <catalin.marinas@arm.com>,
<corbet@lwn.net>, <pbonzini@redhat.com>, <will@kernel.org>,
<linux-kernel@vger.kernel.org>, <yuzenghui@huawei.com>,
<wangzhou1@hisilicon.com>, <yezhenyu2@huawei.com>,
<xiexiangyou@huawei.com>, <zhengchuan@huawei.com>,
<linuxarm@huawei.com>, <joey.gouly@arm.com>,
<kvmarm@lists.linux.dev>, <kvm@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-doc@vger.kernel.org>, <suzuki.poulose@arm.com>
Subject: Re: [PATCH v2 2/5] KVM: arm64: Support set the DBM attr during memory abort
Date: Sat, 22 Nov 2025 12:54:15 +0000 [thread overview]
Message-ID: <86v7j2qlc8.wl-maz@kernel.org> (raw)
In-Reply-To: <20251121092342.3393318-3-zhengtian10@huawei.com>
On Fri, 21 Nov 2025 09:23:39 +0000,
Tian Zheng <zhengtian10@huawei.com> wrote:
>
> From: eillon <yezhenyu2@huawei.com>
>
> Add DBM support to automatically promote write-clean pages to
> write-dirty, preventing users from being trapped in EL2 due to
> missing write permissions.
>
> Since the DBM attribute was introduced in ARMv8.1 and remains
> optional in later architecture revisions, including ARMv9.5.
What is the relevance of this statement?
>
> Support set the DBM attr during user_mem_abort().
I don't think this commit message accurately describes what the code
does. This merely adds support to the page table code to set the DBM
bit in the S2 PTE, and nothing else.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-11-22 12:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 9:23 [PATCH v2 0/5] Support the FEAT_HDBSS introduced in Armv9.5 Tian Zheng
2025-11-21 9:23 ` [PATCH v2 1/5] arm64/sysreg: Add HDBSS related register information Tian Zheng
2025-11-22 12:40 ` Marc Zyngier
2025-11-27 11:48 ` Tian Zheng
2025-12-02 6:51 ` Tian Zheng
2025-11-21 9:23 ` [PATCH v2 2/5] KVM: arm64: Support set the DBM attr during memory abort Tian Zheng
2025-11-22 12:54 ` Marc Zyngier [this message]
2025-11-27 12:19 ` Tian Zheng
2025-11-21 9:23 ` [PATCH v2 3/5] KVM: arm64: Add support for FEAT_HDBSS Tian Zheng
2025-11-22 13:25 ` Marc Zyngier
2025-11-27 13:24 ` Tian Zheng
2025-11-21 9:23 ` [PATCH v2 4/5] KVM: arm64: Enable HDBSS support and handle HDBSSF events Tian Zheng
2025-11-22 16:17 ` Marc Zyngier
2025-11-28 9:21 ` Tian Zheng
2025-12-17 13:39 ` Robert Hoo
2025-12-24 6:15 ` Tian Zheng
2025-12-28 13:21 ` Robert Hoo
2025-11-21 9:23 ` [PATCH v2 5/5] KVM: arm64: Document HDBSS ioctl Tian Zheng
2025-11-21 9:54 ` [PATCH v2 0/5] Support the FEAT_HDBSS introduced in Armv9.5 Marc Zyngier
2025-11-21 10:21 ` z00939249
2025-11-22 16:23 ` 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=86v7j2qlc8.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=suzuki.poulose@arm.com \
--cc=wangzhou1@hisilicon.com \
--cc=will@kernel.org \
--cc=xiexiangyou@huawei.com \
--cc=yezhenyu2@huawei.com \
--cc=yuzenghui@huawei.com \
--cc=zhengchuan@huawei.com \
--cc=zhengtian10@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).