linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Yicong Yang <yangyicong@huawei.com>
Cc: <yangyicong@hisilicon.com>, <catalin.marinas@arm.com>,
	<will@kernel.org>, <mark.rutland@arm.com>,
	<linux-arm-kernel@lists.infradead.org>, <oliver.upton@linux.dev>,
	<broonie@kernel.org>, <ryan.roberts@arm.com>,
	<linuxarm@huawei.com>, <jonathan.cameron@huawei.com>,
	<shameerali.kolothum.thodi@huawei.com>,
	<prime.zeng@hisilicon.com>, <xuwei5@huawei.com>,
	<wangkefeng.wang@huawei.com>
Subject: Re: [PATCH 1/2] arm64: Add support for FEAT_HAFT
Date: Tue, 06 Aug 2024 08:57:01 +0100	[thread overview]
Message-ID: <86le1a2ieq.wl-maz@kernel.org> (raw)
In-Reply-To: <ea436234-bf5e-14db-19e1-5fc9124d93ec@huawei.com>

On Tue, 06 Aug 2024 04:09:09 +0100,
Yicong Yang <yangyicong@huawei.com> wrote:
> 
> >> +#ifdef CONFIG_ARM64_HAFT
> >> +	{
> >> +		.desc = "Hardware managed Access Flag for Table Descriptor",
> >> +		/*
> >> +		 * Per Spec, software management of Access Flag for Table
> >> +		 * descriptor is not supported, so make this feature system
> >> +		 * wide.
> >> +		 */
> > 
> > I don't understand what you mean by this. Can you please clarify?
> > 
> 
> Since this cannot be managed by the software, we should restrict all the CPUs
> in the system to have and enable this feature which is indicated by
> ARM64_CPUCAP_BOOT_CPU_FEATURE. It's not possible for part of the CPUs don't have
> this feature and managed manually.
> 
> I make this comment here since it's handled different from what ARM64_HW_DBM does (which
> is ARM64_CPUCAP_WEAK_LOCAL_CPU_FEATURE). Maybe it's redundant and can be dropped.

Ah, I see what you mean. I think this is still important to capture,
but maybe in a clearer manner. Something like:

	Contrary to the page/block access flag, the table access flag
	cannot be emulated in software (no access fault will occur).
	Therefore mandate that all CPUs have FEAT_HAFT.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.


  reply	other threads:[~2024-08-06  7:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02  9:34 [PATCH 0/2] Support Armv8.9/v9.4 FEAT_HAFT Yicong Yang
2024-08-02  9:34 ` [PATCH 1/2] arm64: Add support for FEAT_HAFT Yicong Yang
2024-08-02 10:37   ` Marc Zyngier
2024-08-06  3:09     ` Yicong Yang
2024-08-06  7:57       ` Marc Zyngier [this message]
2024-08-06 13:11         ` Yicong Yang
2024-08-02  9:34 ` [PATCH 2/2] arm64: Enable ARCH_HAS_NONLEAF_PMD_YOUNG Yicong Yang
2024-08-02 10:40 ` [PATCH 0/2] Support Armv8.9/v9.4 FEAT_HAFT Marc Zyngier
2024-08-06  3:43   ` Yicong Yang
2024-08-06  8:06     ` Marc Zyngier
2024-08-06 13:35       ` Yicong Yang

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=86le1a2ieq.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linuxarm@huawei.com \
    --cc=mark.rutland@arm.com \
    --cc=oliver.upton@linux.dev \
    --cc=prime.zeng@hisilicon.com \
    --cc=ryan.roberts@arm.com \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=will@kernel.org \
    --cc=xuwei5@huawei.com \
    --cc=yangyicong@hisilicon.com \
    --cc=yangyicong@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).