Linux IOMMU Development
 help / color / mirror / Atom feed
From: Linda Knippers <linda.knippers-VXdhtT5mjnY@public.gmane.org>
To: Linus Torvalds
	<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
	Alex Williamson
	<alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Subject: Re: [GIT PULL] Intel IOMMU for 4.1
Date: Mon, 27 Apr 2015 12:09:47 -0400	[thread overview]
Message-ID: <553E5F4B.6020208@hp.com> (raw)
In-Reply-To: <CA+55aFx+QhMZpCtnG2sHib+kk5BR+PeEa99-CCushSA5oAqVxw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 4/27/2015 11:48 AM, Linus Torvalds wrote:
> On Mon, Apr 27, 2015 at 8:39 AM, Alex Williamson
> <alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
>>
>> Since this got pulled anyway, do you plan to follow-up with patches to
>> limit the graphics RMRR exception to the known and acceptable uses and
>> document them, or should I send a revert patch?  I don't think what we
>> have here is acceptable going forward or being backported to stable.
>> Thanks,
> 
> Does anybody actually *care* about RMRR?

I care, just not so much for GPUs.

> The thing is shit. We know it's shit. We already had Linda pipe up to
> tell us that there are bogus RMRR's for ever slot in older machines.

I'd call them unnecessary.

> And we already ignore RMRR for USB controllers because it was just
> useless garbage.
> 
> Is there any reason to *not* just ignore RMRR for all video devices
> like we do now? Seriously?

I was only speaking about one particular use case of RMRR for video
devices.  I'm not sure what anyone else is doing with them.

> I'm *so* not impressed with firmware tables. These things are always
> uniformly wrong. We should strive to generate the information from our
> actual hardware knowledge, with BIOS tables being the absolutely least
> trusted source of information.

In some cases though, you really do need the firmware to provide the tables.
Too few RMRRs are worse than too many.

-- ljk
> 
>                      Linus
> 

  parent reply	other threads:[~2015-04-27 16:09 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
     [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 [this message]
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=553E5F4B.6020208@hp.com \
    --to=linda.knippers-vxdhtt5mjny@public.gmane.org \
    --cc=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