linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Conor Dooley <conor@kernel.org>
Cc: <arnd@arndb.de>, Catalin Marinas <catalin.marinas@arm.com>,
	<linux-cxl@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-arch@vger.kernel.org>, <linux-mm@kvack.org>,
	Dan Williams <dan.j.williams@intel.com>,
	"H . Peter Anvin" <hpa@zytor.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Drew Fustini <fustini@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Krzysztof Kozlowski <krzk@kernel.org>, <james.morse@arm.com>,
	Will Deacon <will@kernel.org>,
	Davidlohr Bueso <dave@stgolabs.net>, <linuxarm@huawei.com>,
	Yushan Wang <wangyushan12@huawei.com>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	<x86@kernel.org>, Andy Lutomirski <luto@kernel.org>,
	Dave Jiang <dave.jiang@intel.com>
Subject: Re: [PATCH v5 0/6]  Cache coherency management subsystem
Date: Fri, 14 Nov 2025 12:49:58 +0000	[thread overview]
Message-ID: <20251114124958.00006a85@huawei.com> (raw)
In-Reply-To: <20251108-spearmint-contend-aa3dd8a0220e@spud>

On Sat, 8 Nov 2025 20:02:52 +0000
Conor Dooley <conor@kernel.org> wrote:

> Arnd,
> 
> On Fri, Oct 31, 2025 at 11:17:03AM +0000, Jonathan Cameron wrote:
> > Support system level interfaces for cache maintenance as found on some
> > ARM64 systems. It is expected that systems using other CPU architectures
> > (such as RiscV) that support CXL memory and allow for native OS flows
> > will also use this. This is needed for correct functionality during
> > various forms of memory hotplug (e.g. CXL). Typical hardware has MMIO
> > interface found via ACPI DSDT. A system will often contain multiple
> > hardware instances.
> > 
> > Includes parameter changes to cpu_cache_invalidate_memregion() but no
> > functional changes for architectures that already support this call.
> > 
> > How to merge?
> > - Current suggestion would be via Conor's drivers/cache tree which routes
> >   through the SoC tree.  
> 
> I was gonna put this in linux-next, but I'm not really sure that Arnd
> was satisfied with the discussion on the previous version about
> suitability of the directory: https://lore.kernel.org/all/20251028114348.000006ed@huawei.com/
> 
> Arnd, did that response satisfy you, or nah?

Seems Arnd is busy.  Conor, if you are happy doing so, maybe push it to a tree
linux-next picks up, but hold off on the pull request until Arnd has had a chance
to reply?

Jonathan

> 
> Cheers,
> Conor.
> 
> >   *  Andrew Morton has expressed he is fine with the MM related changes
> >      going via another appropriate tree.
> >   *  CXL maintainers expressed that they don't consider it appropriate
> >      to go through theit tree.
> >   *  The tiny touching of Arm specific code has an ack from Catalin.  
> 



  reply	other threads:[~2025-11-14 12:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31 11:17 Jonathan Cameron
2025-10-31 11:17 ` [PATCH v5 1/6] memregion: Drop unused IORES_DESC_* parameter from cpu_cache_invalidate_memregion() Jonathan Cameron
2025-10-31 11:17 ` [PATCH v5 2/6] memregion: Support fine grained invalidate by cpu_cache_invalidate_memregion() Jonathan Cameron
2025-10-31 11:17 ` [PATCH v5 3/6] lib: Support ARCH_HAS_CPU_CACHE_INVALIDATE_MEMREGION Jonathan Cameron
2025-10-31 11:17 ` [PATCH v5 4/6] arm64: Select GENERIC_CPU_CACHE_MAINTENANCE Jonathan Cameron
2025-10-31 11:17 ` [PATCH v5 5/6] MAINTAINERS: Add Jonathan Cameron to drivers/cache and add lib/cache_maint.c + header Jonathan Cameron
2025-10-31 11:17 ` [PATCH v5 6/6] cache: Support cache maintenance for HiSilicon SoC Hydra Home Agent Jonathan Cameron
2025-11-08 20:02 ` [PATCH v5 0/6] Cache coherency management subsystem Conor Dooley
2025-11-14 12:49   ` Jonathan Cameron [this message]
2025-11-14 12:52     ` Conor Dooley
2025-11-14 14:07       ` Arnd Bergmann
2025-11-14 15:57         ` Jonathan Cameron
2025-11-14 16:03           ` Arnd Bergmann

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=20251114124958.00006a85@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=conor@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=fustini@kernel.org \
    --cc=hpa@zytor.com \
    --cc=james.morse@arm.com \
    --cc=krzk@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxarm@huawei.com \
    --cc=lpieralisi@kernel.org \
    --cc=luto@kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=wangyushan12@huawei.com \
    --cc=will@kernel.org \
    --cc=x86@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