From: Baolu Lu <baolu.lu@linux.intel.com>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: Dimitri Sivanich <sivanich@hpe.com>,
Kevin Tian <kevin.tian@intel.com>, Joerg Roedel <jroedel@suse.de>,
Russ Anderson <russ.anderson@hpe.com>,
Steve Wahl <steve.wahl@hpe.com>,
Mike Travis <mike.travis@hpe.com>,
David Woodhouse <dwmw2@infradead.org>,
Kyung Min Park <kyung.min.park@intel.com>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
iommu <iommu@lists.linux-foundation.org>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH v3] iommu/vt-d: Make DMAR_UNITS_SUPPORTED a config setting
Date: Thu, 23 Jun 2022 11:38:34 +0800 [thread overview]
Message-ID: <f3139dc1-2530-bb24-93ae-a74f895822c8@linux.intel.com> (raw)
In-Reply-To: <20220623025126.ld45k72c2okodvvk@cantor>
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
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: baolu.lu@linux.intel.com, Steve Wahl <steve.wahl@hpe.com>,
Joerg Roedel <jroedel@suse.de>,
Kyung Min Park <kyung.min.park@intel.com>,
David Woodhouse <dwmw2@infradead.org>,
Will Deacon <will@kernel.org>,
iommu <iommu@lists.linux-foundation.org>,
Kevin Tian <kevin.tian@intel.com>,
Mike Travis <mike.travis@hpe.com>,
Dimitri Sivanich <sivanich@hpe.com>,
Russ Anderson <russ.anderson@hpe.com>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] iommu/vt-d: Make DMAR_UNITS_SUPPORTED a config setting
Date: Thu, 23 Jun 2022 11:38:34 +0800 [thread overview]
Message-ID: <f3139dc1-2530-bb24-93ae-a74f895822c8@linux.intel.com> (raw)
In-Reply-To: <20220623025126.ld45k72c2okodvvk@cantor>
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
next prev parent reply other threads:[~2022-06-23 3:38 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 19:46 [PATCH] iommu/vt-d: Increase DMAR_UNITS_SUPPORTED Steve Wahl
2022-05-05 19:46 ` Steve Wahl
2022-05-06 5:57 ` Baolu Lu
2022-05-06 5:57 ` Baolu Lu
2022-05-06 6:49 ` Tian, Kevin
2022-05-06 6:49 ` Tian, Kevin
2022-05-06 7:10 ` Rodel, Jorg
2022-05-06 7:10 ` Rodel, Jorg
2022-05-06 7:47 ` Tian, Kevin
2022-05-06 7:47 ` Tian, Kevin
2022-05-06 7:16 ` David Woodhouse
2022-05-06 7:16 ` David Woodhouse
2022-05-06 8:12 ` Tian, Kevin
2022-05-06 8:12 ` Tian, Kevin
2022-05-06 15:26 ` Steve Wahl
2022-05-06 15:26 ` Steve Wahl
2022-05-10 1:16 ` Tian, Kevin
2022-05-10 1:16 ` Tian, Kevin
2022-05-10 19:06 ` Steve Wahl
2022-05-10 19:06 ` Steve Wahl
2022-05-11 3:36 ` Tian, Kevin
2022-05-11 3:36 ` Tian, Kevin
2022-05-12 15:13 ` [PATCH v2] iommu/vt-d: Make DMAR_UNITS_SUPPORTED a config setting Steve Wahl
2022-05-12 15:13 ` Steve Wahl
2022-05-12 23:12 ` Steve Wahl
2022-05-12 23:12 ` Steve Wahl
2022-05-13 2:09 ` Baolu Lu
2022-05-13 2:09 ` Baolu Lu
2022-05-18 19:58 ` Steve Wahl
2022-05-18 19:58 ` Steve Wahl
2022-05-23 6:43 ` Tian, Kevin
2022-05-23 6:43 ` Tian, Kevin
2022-06-13 20:38 ` Jerry Snitselaar
2022-06-13 20:38 ` Jerry Snitselaar
2022-06-14 1:33 ` Baolu Lu
2022-06-14 1:33 ` Baolu Lu
2022-06-13 20:57 ` Jerry Snitselaar
2022-06-13 20:57 ` Jerry Snitselaar
2022-06-14 1:36 ` Baolu Lu
2022-06-14 1:36 ` Baolu Lu
2022-06-14 1:44 ` Jerry Snitselaar
2022-06-14 1:44 ` Jerry Snitselaar
2022-06-14 1:51 ` Baolu Lu
2022-06-14 1:51 ` Baolu Lu
2022-06-14 1:54 ` Jerry Snitselaar
2022-06-14 1:54 ` Jerry Snitselaar
2022-06-14 2:21 ` Baolu Lu
2022-06-14 2:21 ` Baolu Lu
2022-06-14 16:45 ` Steve Wahl
2022-06-14 16:45 ` Steve Wahl
2022-06-14 19:01 ` Jerry Snitselaar
2022-06-14 19:01 ` Jerry Snitselaar
2022-06-14 21:12 ` Steve Wahl
2022-06-14 21:12 ` Steve Wahl
2022-06-15 1:38 ` Baolu Lu
2022-06-15 1:38 ` Baolu Lu
2022-06-15 15:02 ` Steve Wahl
2022-06-15 15:02 ` Steve Wahl
2022-06-15 18:36 ` [PATCH v3] " Steve Wahl
2022-06-15 18:36 ` Steve Wahl
2022-06-15 18:39 ` Jerry Snitselaar
2022-06-15 18:39 ` Jerry Snitselaar
2022-06-22 14:52 ` Baolu Lu
2022-06-22 14:52 ` Baolu Lu
2022-06-22 15:05 ` Jerry Snitselaar
2022-06-22 15:05 ` Jerry Snitselaar
2022-06-22 15:11 ` Steve Wahl
2022-06-22 15:11 ` Steve Wahl
2022-06-23 2:29 ` Baolu Lu
2022-06-23 2:29 ` Baolu Lu
2022-06-23 2:51 ` Jerry Snitselaar
2022-06-23 2:51 ` Jerry Snitselaar
2022-06-23 3:38 ` Baolu Lu [this message]
2022-06-23 3:38 ` Baolu Lu
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=f3139dc1-2530-bb24-93ae-a74f895822c8@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jroedel@suse.de \
--cc=jsnitsel@redhat.com \
--cc=kevin.tian@intel.com \
--cc=kyung.min.park@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.travis@hpe.com \
--cc=russ.anderson@hpe.com \
--cc=sivanich@hpe.com \
--cc=steve.wahl@hpe.com \
--cc=will@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.