[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN9PR11MB52765241E3261B58BE93E8A88C002@BN9PR11MB5276.namprd11.prod.outlook.com>
Date: Mon, 8 Apr 2024 06:54:41 +0000
From: "Tian, Kevin" <kevin.tian@...el.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>, Lu Baolu
<baolu.lu@...ux.intel.com>, Mark Rutland <mark.rutland@....com>, "Peter
Zijlstra" <peterz@...radead.org>, Arnd Bergmann <arnd@...db.de>, YueHaibing
<yuehaibing@...wei.com>, "iommu@...ts.linux.dev" <iommu@...ts.linux.dev>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Steve Wahl
<steve.wahl@....com>, "Anderson, Russ" <russ.anderson@....com>
Subject: RE: [PATCH v2] iommu/vt-d: Allocate DMAR fault interrupts locally
> From: Dimitri Sivanich <sivanich@....com>
> Sent: Friday, March 22, 2024 4:51 AM
>
> 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>
Reviewed-by: Kevin Tian <kevin.tian@...el.com>
Powered by blists - more mailing lists