From: Alex Williamson <alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org
Subject: Re: [GIT PULL] Intel IOMMU for 4.1
Date: Sun, 26 Apr 2015 12:16:47 -0600 [thread overview]
Message-ID: <1430072207.8301.103.camel@redhat.com> (raw)
In-Reply-To: <1430070924.13479.5.camel-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
On Sun, 2015-04-26 at 18:55 +0100, David Woodhouse wrote:
> On Sun, 2015-04-26 at 11:33 -0600, Alex Williamson wrote:
> > Curious why these weren't posted to the mailing list.
>
> Apologies for that. I was thinking of this tree as *only* collecting
> the stuff for SVM, and had mostly forgotten the bug-fixes. I was going
> to post the series once I had it all in better shape... and when it
> became apparent that SVM wasn't going to make it for 4.1 I wasn't
> actually going to push these early parts that *are* ready at all. But
> then I started getting badgered about the X2APIC_OPT_OUT nonsense.
>
> > This one in particular not only ignores RMRR on IGD, but any PCI
> > class display device. We may understand why IGD has RMRRs, but we
> > certainly don't understand enough to ignore RMRRs for other GPUs,
> > should they exist.
>
> If they exist, they'll exist for precisely the same reason — to let
> the graphics device continue to render its framebuffer after the IOMMU
> is turned on.
>
> For a discrete card with a discrete video BIOS, as opposed to chipset
> -integrated stuff, I suspect it's actually much *less* likely that
> there's any other weirdness going on.
Hmm, we've seen RMRRs used for health monitoring and thermal control on
other devices. These are exactly the kinds of RMRR use cases that
causes us trouble via the IOMMU API. GPUs are potentially the smartest
and most power hungry peripherals in a system. I don't see how thermal
monitoring wouldn't be an attractive target for GPUs. Are you counting
on system vendors not having sufficient pull with the GPU vendors to
hack into their firmware? I had sort of envisioned that we'd need to
match the RMRRs to the use cases we know about for IGD to make sure
nothing sneaks by. We should at least be documenting what the expected
use cases are, the ranges involved, and why we can ignore them. Thanks,
Alex
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2015-04-26 18:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-26 8:51 [GIT PULL] Intel IOMMU for 4.1 David Woodhouse
[not found] ` <1430038266.4833.14.camel-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-04-26 17:33 ` Alex Williamson
[not found] ` <1430069591.8301.91.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-04-26 17:55 ` David Woodhouse
[not found] ` <1430070924.13479.5.camel-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-04-26 18:16 ` Alex Williamson [this message]
[not found] ` <1430072207.8301.103.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-04-27 14:00 ` Linda Knippers
[not found] ` <553E4109.5060903-VXdhtT5mjnY@public.gmane.org>
2015-04-27 15:39 ` Alex Williamson
[not found] ` <1430149195.4472.43.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-04-27 15:48 ` Linus Torvalds
[not found] ` <CA+55aFx+QhMZpCtnG2sHib+kk5BR+PeEa99-CCushSA5oAqVxw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-27 16:09 ` Linda Knippers
2015-04-27 16:16 ` Alex Williamson
2015-04-27 17:28 ` David Woodhouse
2015-04-27 17:12 ` David Woodhouse
[not found] ` <1430154752.6377.19.camel-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-04-27 17:30 ` Alex Williamson
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=1430072207.8301.103.camel@redhat.com \
--to=alex.williamson-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox