From: Baolu Lu <baolu.lu@linux.intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
Christoph Hellwig <hch@infradead.org>
Cc: baolu.lu@linux.intel.com, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] iommu/vt-d: Remove INTEL_IOMMU_BROKEN_GFX_WA
Date: Mon, 29 Jan 2024 15:24:39 +0800 [thread overview]
Message-ID: <abc6771f-fafe-4ca7-898a-aecbe017b3c7@linux.intel.com> (raw)
In-Reply-To: <BN9PR11MB5276D63FAC442A415018ACB58C7E2@BN9PR11MB5276.namprd11.prod.outlook.com>
On 2024/1/29 14:08, Tian, Kevin wrote:
>> From: Christoph Hellwig <hch@infradead.org>
>> Sent: Monday, January 29, 2024 2:03 PM
>>
>> On Sat, Jan 27, 2024 at 02:45:12PM +0800, Lu Baolu wrote:
>>> Commit 62edf5dc4a524 ("intel-iommu: Restore DMAR_BROKEN_GFX_WA
>> option for
>>> broken graphics drivers") was introduced 24 years ago as a temporary
>>> workaround for graphics drivers that used physical addresses for DMA and
>>> avoided DMA APIs. This workaround was disabled by default.
>>>
>>> As 24 years have passed, it is expected that graphics driver developers
>>> have migrated their drivers to use kernel DMA APIs. Therefore, this
>>> workaround is no longer required and could been removed.
>>
>> How about you Cc the intel graphics maintainers and get a confirmation?
>>
>
> in the worst case there is still "igfx_off" option available to achieve the
> same effect.
>
> there is really no good reason to keep this config option so long while it
> was intended to be removed in 2.6.32.
>
> but yes the Intel graphics maintainers should be CCed.
>
You both are right.
I will add above in the commit message and Cc graphic guys with a new
upgraded version.
Best regards,
baolu
next prev parent reply other threads:[~2024-01-29 7:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 6:45 [PATCH 1/1] iommu/vt-d: Remove INTEL_IOMMU_BROKEN_GFX_WA Lu Baolu
2024-01-29 2:49 ` Tian, Kevin
2024-01-29 6:03 ` Christoph Hellwig
2024-01-29 6:08 ` Tian, Kevin
2024-01-29 7:24 ` Baolu Lu [this message]
2024-01-29 11:24 ` Robin Murphy
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=abc6771f-fafe-4ca7-898a-aecbe017b3c7@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=hch@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox