[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9a649ff4-55fe-478a-bfd7-f3287534499a@intel.com>
Date: Mon, 25 Aug 2025 15:36:39 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Baolu Lu <baolu.lu@...ux.intel.com>, "Tian, Kevin"
<kevin.tian@...el.com>, Jason Gunthorpe <jgg@...dia.com>
Cc: Joerg Roedel <joro@...tes.org>, Will Deacon <will@...nel.org>,
Robin Murphy <robin.murphy@....com>, Jann Horn <jannh@...gle.com>,
Vasant Hegde <vasant.hegde@....com>, Alistair Popple <apopple@...dia.com>,
Peter Zijlstra <peterz@...radead.org>, Uladzislau Rezki <urezki@...il.com>,
Jean-Philippe Brucker <jean-philippe@...aro.org>,
Andy Lutomirski <luto@...nel.org>, "Lai, Yi1" <yi1.lai@...el.com>,
"iommu@...ts.linux.dev" <iommu@...ts.linux.dev>,
"security@...nel.org" <security@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH v3 1/1] iommu/sva: Invalidate KVA range on kernel TLB
flush
On 8/22/25 20:26, Baolu Lu wrote:
> +static struct {
> + /* list for pagetable_dtor_free() */
> + struct list_head dtor;
> + /* list for __free_page() */
> + struct list_head page;
> + /* list for free_pages() */
> + struct list_head pages;
> + /* protect all the ptdesc lists */
> + spinlock_t lock;
> + struct work_struct work;
Could you explain a bit why this now needs three separate lists? Seems
like pure overkill.
Powered by blists - more mailing lists