From: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Shaohua Li <shli-b10kYP2dOMg@public.gmane.org>
Cc: "iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
"jroedel-l3A5Bk7waGM@public.gmane.org"
<jroedel-l3A5Bk7waGM@public.gmane.org>,
"Kernel-team-b10kYP2dOMg@public.gmane.org"
<Kernel-team-b10kYP2dOMg@public.gmane.org>
Subject: Re: [PATCH] intel-iommu: respect iommu=pt
Date: Tue, 24 Nov 2015 22:29:30 +0000 [thread overview]
Message-ID: <1448404170.44976.123.camel@infradead.org> (raw)
In-Reply-To: <20151124221515.GB2106568-tb7CFzD8y5b7E6g3fPdp/g2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 690 bytes --]
On Tue, 2015-11-24 at 14:15 -0800, Shaohua Li wrote:
> > I'm reluctant to change that. If it hurts you, kick your system
> > vendor until they stop doing stupid things with RMRRs.
>
> Hmm, yes, it's a device with RMRR. Don't think we can ask vendor to
> stop it though.
Get a new vendor?
> I'd really like an option to avoid the penality for RMRR devices.
RMRR devices should just die. It's insanely stupid in almost all cases.
> Would a new option like 'iommu=strictpt' work?
Which does what? Forces passthrough in *all* cases, even when it then
has to use SWIOTLB?
I would much prefer to just accept that RMRR-afflicted devices are
crippled.
--
dwmw2
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5691 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2015-11-24 22:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 21:53 [PATCH] intel-iommu: respect iommu=pt Shaohua Li
[not found] ` <58e2344c50053de58ceed658272ecc0f349c2f2f.1448401068.git.shli-b10kYP2dOMg@public.gmane.org>
2015-11-24 21:59 ` Woodhouse, David
[not found] ` <1448402349.44976.112.camel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-11-24 22:15 ` Shaohua Li
[not found] ` <20151124221515.GB2106568-tb7CFzD8y5b7E6g3fPdp/g2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2015-11-24 22:29 ` David Woodhouse [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=1448404170.44976.123.camel@infradead.org \
--to=dwmw2-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=Kernel-team-b10kYP2dOMg@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=jroedel-l3A5Bk7waGM@public.gmane.org \
--cc=shli-b10kYP2dOMg@public.gmane.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.