public inbox for linux-alpha@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Cree <mcree@orcon.net.nz>
To: Matt Turner <mattst88@gmail.com>
Cc: Magnus Lindholm <linmag7@gmail.com>,
	linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] alpha: Add ARCH_HAS_PTE_SPECIAL support
Date: Sat, 4 Apr 2026 14:36:14 +1300	[thread overview]
Message-ID: <adBrDoaNR8O8_hbG@creeky> (raw)
In-Reply-To: <20260403150048.488266-1-mattst88@gmail.com>

Hi Matt,

On Fri, Apr 03, 2026 at 11:00:48AM -0400, Matt Turner wrote:
> Add _PAGE_SPECIAL using bit 19 (0x80000), which is unused in the Alpha
> PTE layout. This enables pte_special()/pte_mkspecial() for marking PTEs
> that are not backed by struct page (VDSO mappings, zero page,
> io_remap_pfn_range, etc.).
> 
> Include _PAGE_SPECIAL in _PAGE_CHG_MASK so it is preserved across
> pte_modify() calls.
> 
> Assisted-by: Claude:claude-opus-4-6
> Signed-off-by: Matt Turner <mattst88@gmail.com>
> ---
>  arch/alpha/Kconfig               | 1 +
>  arch/alpha/include/asm/pgtable.h | 5 ++++-
>  2 files changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git ./arch/alpha/Kconfig ./arch/alpha/Kconfig
> index a5feb98cc088..a29788e588ee 100644
> --- ./arch/alpha/Kconfig
> +++ ./arch/alpha/Kconfig
> @@ -8,6 +8,7 @@ config ALPHA
>  	select ARCH_HAS_FAST_MULTIPLIER
>  	select ARCH_HAS_GCOV_PROFILE_ALL
>  	select ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE
> +	select ARCH_HAS_PTE_SPECIAL
>  	select ARCH_HAS_UBSAN
>  	select ARCH_MIGHT_HAVE_PC_PARPORT
>  	select ARCH_MIGHT_HAVE_PC_SERIO

On what kernel does this patch apply?  My master branch has none of:

ARCH_HAS_FAST_MULTIPLIER
ARCH_HAS_GCOV_PROFILE_ALL
ARCH_HAS_UBSAN

and they don't seem to be added at all in the other patches you sent.

Cheers,
Michael.


      reply	other threads:[~2026-04-04  1:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-03 15:00 [PATCH] alpha: Add ARCH_HAS_PTE_SPECIAL support Matt Turner
2026-04-04  1:36 ` Michael Cree [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=adBrDoaNR8O8_hbG@creeky \
    --to=mcree@orcon.net.nz \
    --cc=linmag7@gmail.com \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattst88@gmail.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