From: Tian Zheng <zhengtian10@huawei.com>
To: Leonardo Bras <leo.bras@arm.com>
Cc: Oliver Upton <oupton@kernel.org>, <maz@kernel.org>,
<catalin.marinas@arm.com>, <will@kernel.org>, <corbet@lwn.net>,
<pbonzini@redhat.com>, <yuzenghui@huawei.com>,
<wangzhou1@hisilicon.com>, <yangjinqian1@huawei.com>,
<caijian11@h-partners.com>, <liuyonglong@huawei.com>,
<tangchengchang@huawei.com>, <yezhenyu2@huawei.com>,
<yubihong@huawei.com>, <linuxarm@huawei.com>,
<joey.gouly@arm.com>, <kvmarm@lists.linux.dev>,
<kvm@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <seiden@linux.ibm.com>,
<suzuki.poulose@arm.com>, <fuad.tabba@linux.dev>,
<mark.rutland@arm.com>, <seanjc@google.com>,
<rdunlap@infradead.org>, <linux-doc@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>, <skhan@linuxfoundation.org>
Subject: Re: [PATCH v5 01/15] KVM: arm64: pgtables: Change write bit from S2AP_W to DBM
Date: Thu, 29 Oct 2026 15:08:27 +0800 [thread overview]
Message-ID: <6d2411a3-b37b-4cdb-80ca-10654cc88a17@huawei.com> (raw)
In-Reply-To: <at9raEVrsbb7rj6n@LeoBrasDK>
On 10/26/2026 11:02 PM, Leonardo Bras wrote:
> On Wed, Sep 30, 2026 at 10:44:26AM +0800, Tian Zheng wrote:
>> On 9/30/2026 8:25 AM, Oliver Upton wrote:
>>> Hmm... I'd actually like to see this structured where the "write" bit
>>> could either be S2AP_W or DBM depending on if the system supports
>>> FEAT_HAFDBS. Look at how HVHE is handled for selecting the right AP
>>> encoding for the hyp stage-1 page tables.
>>>
>>
>> Hi Oliver,
>>
>> Thanks for the suggestion. I missed the case where FEAT_HAFDBS is not
>> supported. Systems without the feature should keep the original
>> encoding, with S2AP[1] as the write permission bit. I'll follow the HVHE
>> pattern to select between the two encodings in the next version.
>>
>> Thanks!
>> Tian
>>
>
> Hi Oliver, Tian,
>
> After some digging, I think it would be better if we kept using S2AP[1] as
> a writable bit, while DBM can be treated as "Can promote a non-writable
> page to writable if HAFDBS=on".
>
> I know it's not that intuitive, as the Arm ARM even introduced the concept
> of Writable-clean an Writable-dirty, but I think it will be the best way of
> referring to what was intended of the bit.
>
> I wrote down what I mean by that:
> https://lore.kernel.org/all/20261026144413.441566-1-leo.bras@arm.com/
>
> tl;dr:
> - DBM + S2AP[1] is set on writable entries (KVM_PGTABLE_PROT_W)
> - Writable detection is made only on S2AP[1], so no changes
> - Wrprotect sets S2AP[1]=0 from the PTE, and also DBM=0 if it's a block
>
> On dirty-tracking:
> - If HAFDBS=0 : no functional change, DBM bit there but unused
> - If HDBSS=1
> - Pages: writable-clean promoted to writable-dirty on write, HDBSS does
> the tracking
> - Blocks: faults on write, splits in pages, pages get DBM=1.
> (argh, I think we need a PROT_DBM for that)
>
> Does that make sense?
>
> Thanks!
> Leo
Hi Leo,
Got it. I'll wait for the conclusion of your discussion with Oliver
before proceeding.
Thanks,
Tian
next prev parent reply other threads:[~2026-10-29 7:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 10:36 [PATCH v5 00/15] KVM: arm64: FEAT_HDBSS support for stage-2 dirty tracking Tian Zheng
2026-09-29 10:36 ` [PATCH v5 01/15] KVM: arm64: pgtables: Change write bit from S2AP_W to DBM Tian Zheng
2026-09-30 0:25 ` Oliver Upton
2026-09-30 2:44 ` Tian Zheng
2026-10-26 15:02 ` Leonardo Bras
2026-10-29 7:08 ` Tian Zheng [this message]
2026-09-29 10:36 ` [PATCH v5 02/15] KVM: arm64: Add KVM_PGTABLE_PROT_DIRTY Tian Zheng
2026-09-30 0:35 ` Oliver Upton
2026-09-30 2:57 ` Tian Zheng
2026-09-29 10:36 ` [PATCH v5 03/15] KVM: arm64: Introduce a dedicated walker for stage2 write-protect Tian Zheng
2026-09-29 10:36 ` [PATCH v5 04/15] KVM: arm64: Add KVM_REQ_RELOAD_STAGE2 Tian Zheng
2026-09-29 10:36 ` [PATCH v5 05/15] KVM: arm64: Harvest stage-2 dirty state into the host folio account Tian Zheng
2026-10-26 18:05 ` Leonardo Bras
2026-09-29 10:36 ` [PATCH v5 06/15] KVM: arm64: Add support for FEAT_HDBSS Tian Zheng
2026-10-26 18:12 ` Leonardo Bras
2026-09-29 10:36 ` [PATCH v5 07/15] KVM: arm64: Add HDBSS per-vCPU buffer management Tian Zheng
2026-10-26 18:27 ` Leonardo Bras
2026-09-29 10:36 ` [PATCH v5 08/15] KVM: arm64: Flush the HDBSS buffer on VM exit Tian Zheng
2026-10-27 18:13 ` Leonardo Bras
2026-09-29 10:36 ` [PATCH v5 09/15] KVM: arm64: Handle HDBSS faults Tian Zheng
2026-09-29 10:36 ` [PATCH v5 10/15] KVM: Add kvm_arch_dirty_ring_size_updated() hook Tian Zheng
2026-09-29 10:36 ` [PATCH v5 11/15] KVM: arm64: Reserve dirty ring space for the HDBSS buffer Tian Zheng
2026-09-29 10:36 ` [PATCH v5 12/15] KVM: arm64: Derive the VM hardware dirty mode from dirty logging Tian Zheng
2026-09-29 10:36 ` [PATCH v5 13/15] KVM: arm64: Add HDBSS buffer size ioctl for dirty-bitmap mode Tian Zheng
2026-09-29 10:36 ` [PATCH v5 14/15] KVM: arm64: Document HDBSS buffer size ioctl Tian Zheng
2026-09-29 10:36 ` [PATCH v5 15/15] KVM: arm64: selftests: Add HDBSS buffer size ioctl interface test Tian Zheng
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=6d2411a3-b37b-4cdb-80ca-10654cc88a17@huawei.com \
--to=zhengtian10@huawei.com \
--cc=caijian11@h-partners.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=leo.bras@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=pbonzini@redhat.com \
--cc=rdunlap@infradead.org \
--cc=seanjc@google.com \
--cc=seiden@linux.ibm.com \
--cc=skhan@linuxfoundation.org \
--cc=suzuki.poulose@arm.com \
--cc=tangchengchang@huawei.com \
--cc=wangzhou1@hisilicon.com \
--cc=will@kernel.org \
--cc=yangjinqian1@huawei.com \
--cc=yezhenyu2@huawei.com \
--cc=yubihong@huawei.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
all inboxes | Powered by JetHome®