[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJtEV7ZKZkVbNCL95-eVvvHt0C6bS-hJTi_OJwBtadineeOR3Q@mail.gmail.com>
Date: Sat, 9 Mar 2013 13:07:15 +0800
From: Andrew Cooks <acooks@...il.com>
To: Gaudenz Steinlin <gaudenz@...iologie.ch>
Cc: Alex Williamson <alex.williamson@...hat.com>,
Justin Piszcz <jpiszcz@...idpixels.com>,
David Woodhouse <dwmw2@...radead.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
"open list:INTEL IOMMU (VT-d)" <iommu@...ts.linux-foundation.org>,
open list <linux-kernel@...r.kernel.org>,
"open list:PCI SUBSYSTEM" <linux-pci@...r.kernel.org>
Subject: Re: [PATCH v4] Quirk for buggy dma source tags with Intel IOMMU.
On Fri, Mar 8, 2013 at 7:43 PM, Gaudenz Steinlin <gaudenz@...iologie.ch> wrote:
>
> Hi Andrew
>
> Andrew Cooks <acooks@...il.com> writes:
>
>> This patch creates a quirk to allow the Intel IOMMU to be enabled for devices
>> that use incorrect tags during DMA. It is similar to the quirk for Ricoh
>> devices, but allows mapping multiple functions and mapping of 'ghost'
>> functions that do not correspond to real devices. Devices that need this
>> include a variety of Marvell 88SE91xx based SATA controllers. [1][2]
>
> I can confirm that this version of the patch also works for my mini-PCIe
> device (88NV9143). See the my mail about it for more information. I had
> to manually fix the patch because the patch utility did not understand
> it. There is a formatting error in the last hunk for quirks.c (missing
> space before context line) and the line count in the hunk header is
> wrong (66 lines changed should be 56 lines). I hope nothing was missing
> from the patch.
>
> Tested on 3.8.2.
Thanks for testing.
The formatting error is embarrassing. I was impatient and removed some
unused content from the patch, instead of cleaning the source. The
thing about posting to open lists with thousands or subscribers and
searchable archives is that it's impossible to hide incompetence.
a.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists