linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Dave Hansen <dave.hansen@intel.com>,
	Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Kevin Tian <kevin.tian@intel.com>,
	Jason Gunthorpe <jgg@nvidia.com>, Jann Horn <jannh@google.com>,
	Vasant Hegde <vasant.hegde@amd.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Alistair Popple <apopple@nvidia.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Uladzislau Rezki <urezki@gmail.com>,
	Jean-Philippe Brucker <jean-philippe@linaro.org>,
	Andy Lutomirski <luto@kernel.org>, Yi Lai <yi1.lai@intel.com>,
	David Hildenbrand <david@redhat.com>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
	Michal Hocko <mhocko@kernel.org>,
	Matthew Wilcox <willy@infradead.org>
Cc: baolu.lu@linux.intel.com, iommu@lists.linux.dev,
	security@kernel.org, x86@kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/8] Fix stale IOTLB entries for kernel address space
Date: Tue, 14 Oct 2025 21:21:01 +0800	[thread overview]
Message-ID: <a1883b7d-b5f9-419b-ba51-735a977522d9@linux.intel.com> (raw)
In-Reply-To: <d3cf3716-98ec-419b-90b7-b91b83599498@intel.com>

On 10/9/2025 3:42 AM, Dave Hansen wrote:
> I wondered why no mm folks were commenting on this. linux-mm@ was cc'd,
> but the_people_ on cc seem to have been almost all IOMMU and x86 folks.
> so I added a few mm folks...
> 
> On 9/25/25 13:24, Dave Hansen wrote:
>> On 9/18/25 22:39, Lu Baolu wrote:
>>> This solution introduces a deferred freeing mechanism for kernel page
>>> table pages, which provides a safe window to notify the IOMMU to
>>> invalidate its caches before the page is reused.
>> I think all the activity has died down and I everyone seems happy enough
>> with how this looks. Right?
>>
>> So is this something we should prod Andrew to take through the mm tree,
>> or is it x86-specific enough it should go through tip?
> Hi Folks! We've got a bug fix here that has impact on x86, mm, and IOMMU
> code. I know I've talked with a few of you about this along the way, but
> it's really thin on mm reviews, probably because mm folks haven't been
> cc'd. Any eyeballs on it would be appreciated!
> 
> It seems like it should_probably_ go through the mm tree, although I'm
> happy to send it through tip if folks disagree.

Thank you all for the review comments. I have updated this series with a
new version and posted it here, with the mm folks cc'ed:

https://lore.kernel.org/linux-iommu/20251014130437.1090448-1-baolu.lu@linux.intel.com/

Thanks,
baolu


      parent reply	other threads:[~2025-10-14 13:21 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-19  5:39 [PATCH v5 0/8] Fix stale IOTLB entries for kernel address space Lu Baolu
2025-09-19  5:39 ` [PATCH v5 1/8] mm: Add a ptdesc flag to mark kernel page tables Lu Baolu
2025-10-08 19:56   ` Matthew Wilcox
2025-10-11  6:24     ` Baolu Lu
2025-09-19  5:40 ` [PATCH v5 2/8] mm: Actually mark kernel page table pages Lu Baolu
2025-10-09 19:19   ` David Hildenbrand
2025-10-13  7:17   ` Mike Rapoport
2025-09-19  5:40 ` [PATCH v5 3/8] x86/mm: Use 'ptdesc' when freeing PMD pages Lu Baolu
2025-10-09 19:25   ` David Hildenbrand
2025-10-09 19:31     ` Dave Hansen
2025-10-11  6:26       ` Baolu Lu
2025-09-19  5:40 ` [PATCH v5 4/8] mm: Introduce pure page table freeing function Lu Baolu
2025-10-09 19:26   ` David Hildenbrand
2025-10-13  7:24   ` Mike Rapoport
2025-09-19  5:40 ` [PATCH v5 5/8] x86/mm: Use pagetable_free() Lu Baolu
2025-09-24 12:40   ` Jason Gunthorpe
2025-10-09 19:26   ` David Hildenbrand
2025-10-13  7:28   ` Mike Rapoport
2025-09-19  5:40 ` [PATCH v5 6/8] mm: Introduce deferred freeing for kernel page tables Lu Baolu
2025-10-09 19:28   ` David Hildenbrand
2025-10-09 19:32     ` Dave Hansen
2025-10-10 15:47   ` David Hildenbrand
2025-10-11  6:30     ` Baolu Lu
2025-09-19  5:40 ` [PATCH v5 7/8] mm: Hook up Kconfig options for async page table freeing Lu Baolu
2025-09-19  5:40 ` [PATCH v5 8/8] iommu/sva: Invalidate stale IOTLB entries for kernel address space Lu Baolu
2025-09-25 20:24 ` [PATCH v5 0/8] Fix " Dave Hansen
2025-10-08 19:42   ` Dave Hansen
2025-10-09 19:16     ` David Hildenbrand
2025-10-14 13:21     ` Baolu Lu [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=a1883b7d-b5f9-419b-ba51-735a977522d9@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=apopple@nvidia.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=david@redhat.com \
    --cc=iommu@lists.linux.dev \
    --cc=jannh@google.com \
    --cc=jean-philippe@linaro.org \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=luto@kernel.org \
    --cc=mhocko@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=robin.murphy@arm.com \
    --cc=rppt@kernel.org \
    --cc=security@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=urezki@gmail.com \
    --cc=vasant.hegde@amd.com \
    --cc=vbabka@suse.cz \
    --cc=will@kernel.org \
    --cc=willy@infradead.org \
    --cc=x86@kernel.org \
    --cc=yi1.lai@intel.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).