All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksii Kurochko <oleksii.kurochko@gmail.com>
To: Baptiste Le Duc <baptiste.le-duc@vates.tech>,
	xen-devel@lists.xenproject.org
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Anthony PERARD" <anthony.perard@vates.tech>,
	"Michal Orzel" <michal.orzel@amd.com>,
	"Jan Beulich" <jbeulich@suse.com>,
	"Julien Grall" <julien@xen.org>,
	"Roger Pau Monné" <roger@xenproject.org>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Alistair Francis" <alistair.francis@wdc.com>,
	"Connor Davis" <connojdavis@gmail.com>,
	"Zheng Zhang" <zhangzheng@iscas.ac.cn>
Subject: Re: [PATCH v7 4/4] xen/riscv: rework the A/D bits comment in p2m_set_pte_flags()
Date: Fri, 16 Oct 2026 17:47:23 +0200	[thread overview]
Message-ID: <016b34db-7c9f-4c85-bf87-2d2d95394e98@gmail.com> (raw)
In-Reply-To: <1792164867.8631fc262581453bbf619ec5b2062170.1a14559acd50008425@vates.tech>



On 10/16/26 5:34 PM, Baptiste Le Duc wrote:
> The comment in p2m_set_pte_flags() quotes the spec at length to describe
> the two A/D bits schemes, and its TODO mixes two things: why A/D are preset
> today (OpenSBI delegates the resulting page faults to a lower privilege
> mode, so Xen would take them with no handler) and what remains to be done.
> 
> Summarize the two schemes as a short list. The reason for presetting A/D is
> not future work, so move it out of the TODO, next to the schemes. The TODO
> now keeps only the later work, handling these page faults instead of
> presetting A/D, which only concerns Svade as A/D page faults cannot happen
> otherwise.
> 
> Also note that presetting the A/D bits is harmless when the device
> tree advertises both Svade and Svadu and the platform uses hardware
> A/D updating.
> 
> No functional change.
> 
> Assisted-by: Claude:claude-opus-5-5
> Signed-off-by: Baptiste Le Duc <baptiste.le-duc@vates.tech>
LGTM:
  Reviewed-by: Oleksii Kurochko <oleksii.kurochko@gmail.com>

Thanks!

~ Oleksii


      reply	other threads:[~2026-10-16 15:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 15:31 [PATCH v7 0/4] xen/riscv: fix boot on missing extensions and MMU setup bugs Baptiste Le Duc
2026-10-16 15:34 ` [PATCH v7 1/4] xen/riscv: use pte_is_valid() in pte_is_mapping() Baptiste Le Duc
2026-10-16 15:49   ` Oleksii Kurochko
2026-10-26  9:26   ` Jan Beulich
2026-10-16 15:34 ` [PATCH v7 2/4] xen/riscv: fix A/D bits in Xen's page-table mappings Baptiste Le Duc
2026-10-23  2:37   ` Zhang Zheng
2026-10-26  9:27   ` Jan Beulich
2026-10-16 15:34 ` [PATCH v7 3/4] xen/riscv: panic if the device tree advertises neither Svade nor Svadu Baptiste Le Duc
2026-10-16 15:45   ` Oleksii Kurochko
2026-10-23  2:37   ` Zhang Zheng
2026-10-26  9:32   ` Jan Beulich
2026-10-26  9:44     ` Baptiste Le Duc
2026-10-26  9:52       ` Jan Beulich
2026-10-16 15:34 ` [PATCH v7 4/4] xen/riscv: rework the A/D bits comment in p2m_set_pte_flags() Baptiste Le Duc
2026-10-16 15:47   ` Oleksii Kurochko [this message]

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=016b34db-7c9f-4c85-bf87-2d2d95394e98@gmail.com \
    --to=oleksii.kurochko@gmail.com \
    --cc=alistair.francis@wdc.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=baptiste.le-duc@vates.tech \
    --cc=connojdavis@gmail.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=roger@xenproject.org \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    --cc=zhangzheng@iscas.ac.cn \
    /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.