[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f3139dc1-2530-bb24-93ae-a74f895822c8@linux.intel.com>
Date: Thu, 23 Jun 2022 11:38:34 +0800
From: Baolu Lu <baolu.lu@...ux.intel.com>
To: Jerry Snitselaar <jsnitsel@...hat.com>
Cc: baolu.lu@...ux.intel.com, Steve Wahl <steve.wahl@....com>,
Joerg Roedel <jroedel@...e.de>,
Kyung Min Park <kyung.min.park@...el.com>,
David Woodhouse <dwmw2@...radead.org>,
Will Deacon <will@...nel.org>,
iommu <iommu@...ts.linux-foundation.org>,
Kevin Tian <kevin.tian@...el.com>,
Mike Travis <mike.travis@....com>,
Dimitri Sivanich <sivanich@....com>,
Russ Anderson <russ.anderson@....com>,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] iommu/vt-d: Make DMAR_UNITS_SUPPORTED a config setting
On 2022/6/23 10:51, Jerry Snitselaar wrote:
>> The real problem here is that the iommu sequence ID overflows if
>> DMAR_UNITS_SUPPORTED is not big enough. This is purely a software
>> implementation issue, I am not sure whether user opt-in when building a
>> kernel package could help a lot here.
>>
> Is this something that could be figured out when parsing the dmar
> table? It looks like currently iommu_refcnt[], iommu_did[], and
> dmar_seq_ids[] depend on it.
That's definitely a better solution.
Best regards,
baolu
Powered by blists - more mailing lists