[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a2d1c44d-6450-4641-843e-8981bdb4d533@linux.intel.com>
Date: Wed, 24 Apr 2024 11:43:30 +0800
From: Baolu Lu <baolu.lu@...ux.intel.com>
To: Dimitri Sivanich <sivanich@....com>, Thomas Gleixner
<tglx@...utronix.de>, Joerg Roedel <joro@...tes.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@....com>,
Will Deacon <will@...nel.org>, Robin Murphy <robin.murphy@....com>,
David Woodhouse <dwmw2@...radead.org>, Mark Rutland <mark.rutland@....com>,
Peter Zijlstra <peterz@...radead.org>, Arnd Bergmann <arnd@...db.de>,
YueHaibing <yuehaibing@...wei.com>, iommu@...ts.linux.dev
Cc: baolu.lu@...ux.intel.com, linux-kernel@...r.kernel.org,
Steve Wahl <steve.wahl@....com>, Russ Anderson <russ.anderson@....com>
Subject: Re: [PATCH v2] iommu/vt-d: Allocate DMAR fault interrupts locally
On 3/22/24 4:50 AM, Dimitri Sivanich wrote:
> The Intel IOMMU code currently tries to allocate all DMAR fault interrupt
> vectors on the boot cpu. On large systems with high DMAR counts this
> results in vector exhaustion, and most of the vectors are not initially
> allocated socket local.
>
> Instead, have a cpu on each node do the vector allocation for the DMARs on
> that node. The boot cpu still does the allocation for its node during its
> boot sequence.
>
> Signed-off-by: Dimitri Sivanich<sivanich@....com>
> ---
>
> v2: per Thomas Gleixner, implement this from a DYN CPU hotplug state, though
> this implementation runs in CPUHP_AP_ONLINE_DYN space rather than
> CPUHP_BP_PREPARE_DYN space.
Patch has been queued for iommu/vt-d.
Best regards,
baolu
Powered by blists - more mailing lists