From: Don Dutile <ddutile@redhat.com>
To: Pat Erley <pat-lkml@erley.org>
Cc: linux-pci@vger.kernel.org
Subject: Re: Ricoh Multifunction Device DMAR Bug
Date: Mon, 22 Oct 2012 18:28:08 -0400 [thread overview]
Message-ID: <5085C878.3000307@redhat.com> (raw)
In-Reply-To: <5081F0D2.50509@erley.org>
On 10/19/2012 08:31 PM, Pat Erley wrote:
> I've been hitting the bug talked about in this thread:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=605888
>
> and using the patch in Comment 7 as a work around. In reading on, I saw that redhat released a kernel (kernel-2.6.35.6-45.fc14) that contains a patch like this:
>
The proposed fedora patch was to demo how identifying the ricoh device,
and pointing it's IOMMU resources to be the same as the fcn-0 device
was a proof of concept.
Being in the main-line, high-frequency map-single function would
destroy the performance for all devices on all systems, even those w/o ricoh device.
So, although 'it works', it has poor performance.
Now, if you only care about isolation/protection, and not performance, it works for you! :)
But for all other systems, the patch is a non-starter.
I believe the final solution was to disable iommu on these systems.
Devices behaving badly (using wrong src-id of DMA xactions).
> http://lists.fedoraproject.org/pipermail/scm-commits/2010-October/510785.html
>
> Is there any reason to omit this from mainline? The patch that redhat is using seems like a 'better' fix than the fixup I'm using from Comment 7, but does that completely disable DMAR when this device is present? That seems like an overkill approach, when there is the hack from the thread from redhat's bugzilla. Is there some other impact from the patch I'm using? Everything works fine on my system with it.
>
> Anyways, the point to all of this was, I really don't like having to carry patches and apply them with each update. I'd love to see some fixup get into mainline, especially if it can be minimal impact on functionality, like the first thread linked here. Is there anything else I can provide to help facilitate this?
>
> Pat Erley
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-10-22 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 0:31 Ricoh Multifunction Device DMAR Bug Pat Erley
2012-10-22 22:28 ` Don Dutile [this message]
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=5085C878.3000307@redhat.com \
--to=ddutile@redhat.com \
--cc=linux-pci@vger.kernel.org \
--cc=pat-lkml@erley.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;
as well as URLs for NNTP newsgroup(s).