linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Nhat Pham <nphamcs@gmail.com>
Cc: akpm@linux-foundation.org, linux-api@vger.kernel.org,
	kernel-team@meta.com, linux-arch@vger.kernel.org,
	hannes@cmpxchg.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, arnd@arndb.de, will@kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: wire up cachestat for arm64
Date: Fri, 12 May 2023 11:42:26 +0100	[thread overview]
Message-ID: <ZF4YEjiTOeu3jx+5@arm.com> (raw)
In-Reply-To: <20230511092843.3896327-1-nphamcs@gmail.com>

On Thu, May 11, 2023 at 02:28:43AM -0700, Nhat Pham wrote:
> cachestat is a new syscall that was previously wired in for most
> architectures:
> 
> https://lore.kernel.org/lkml/20230503013608.2431726-1-nphamcs@gmail.com/
> https://lore.kernel.org/linux-mm/20230510195806.2902878-1-nphamcs@gmail.com/
> 
> However, those patches miss arm64, which has its own syscall table in arch/arm64.
> This patch wires cachestat in for arm64.

You may want to clarify that this is for compat support on arm64,
otherwise native support uses the generic syscall numbers already.

> 
> Signed-off-by: Nhat Pham <nphamcs@gmail.com>
> Suggested-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Suggested-by: Arnd Bergmann <arnd@arndb.de>

Acked-by: Catalin Marinas <catalin.marinas@arm.com>

  parent reply	other threads:[~2023-05-12 10:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 19:58 [PATCH] cachestat: wire up cachestat for other architectures Nhat Pham
2023-05-11  3:23 ` Michael Ellerman
2023-05-11 19:34   ` Nhat Pham
2023-05-11  7:01 ` Geert Uytterhoeven
2023-05-11  9:01   ` Nhat Pham
2023-05-11  7:04 ` Arnd Bergmann
2023-05-11  9:30   ` Nhat Pham
2023-05-11  7:57 ` Heiko Carstens
2023-05-11  9:28 ` [PATCH] arm64: wire up cachestat for arm64 Nhat Pham
2023-05-11 10:29   ` Arnd Bergmann
2023-05-12 10:42   ` Catalin Marinas [this message]
2023-05-12 21:15     ` Andrew Morton
2023-05-12 21:47       ` Nhat Pham

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=ZF4YEjiTOeu3jx+5@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=hannes@cmpxchg.org \
    --cc=kernel-team@meta.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nphamcs@gmail.com \
    --cc=will@kernel.org \
    /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).