public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Packard <keithp@keithp.com>
To: David Woodhouse <dwmw2@infradead.org>,
	Eugeni Dodonov <eugeni.dodonov@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] iommu: export no_iommu and dmar_disabled symbols
Date: Wed, 23 Nov 2011 12:48:19 -0800	[thread overview]
Message-ID: <86aa7mefak.fsf@sumi.keithp.com> (raw)
In-Reply-To: <1322080560.15493.206.camel@shinybook.infradead.org>

[-- Attachment #1: Type: text/plain, Size: 787 bytes --]

On Wed, 23 Nov 2011 20:36:00 +0000, David Woodhouse <dwmw2@infradead.org> wrote:

> This is horrid. In the general case, drivers have no business knowing
> this. We need to properly identify what is wrong with this hardware, and
> put in a quirk for it — perhaps refusing to enable the IOMMU at all on
> the broken chipsets.

That'd be fine with me, right now we're disabling RC6 and semaphores --
semaphores aren't all that important, although they do improve
performance a bit. RC6 is important, saving a huge amount of power.

I'd also be OK with requiring special options to enable DMAR and having
that also disable RC6/semaphores, if you'd rather expose that. In either
case, we need something that works and avoids hanging machines.

-- 
keith.packard@intel.com

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2011-11-23 20:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1322526298-2746-1-git-send-email-eugeni.dodonov@intel.com>
2011-11-19  6:41 ` [PATCH] drm/i915: By default, enable RC6 on IVB and SNB when reasonable Keith Packard
2011-11-19  7:37   ` [Intel-gfx] " Kenneth Graunke
2011-11-19  9:25   ` Eugeni Dodonov
2011-11-19 18:32     ` Keith Packard
2011-11-20 21:19       ` Eugeni Dodonov
2011-11-22 20:15   ` Matthew Garrett
     [not found]     ` <CAC7Lmnts+QwZ2XTvbTQa=aa3XO5_Sna0vk3KHWJJ6oi6+D5BXw@mail.gmail.com>
2011-11-22 20:51       ` Matthew Garrett
2011-11-23  3:31     ` Keith Packard
2011-11-23 10:26       ` Daniel Vetter
2011-11-23 14:01         ` David Woodhouse
2011-11-23 14:39           ` Daniel Vetter
2011-11-23 15:03             ` David Woodhouse
2011-11-23 15:31               ` Daniel Vetter
2011-11-23 15:36                 ` David Woodhouse
2011-11-23 15:46                 ` Daniel Vetter
2011-11-23 15:41               ` Daniel Vetter
2011-11-23 15:43                 ` David Woodhouse
2011-11-23 20:35                   ` Daniel Vetter
2011-11-23 18:42   ` [PATCH] iommu: export no_iommu and dmar_disabled symbols Eugeni Dodonov
2011-11-23 20:36     ` [Intel-gfx] " David Woodhouse
2011-11-23 20:48       ` Keith Packard [this message]
2011-12-09 23:53   ` drm/i915: Enabling RC6 where possible Keith Packard
2011-12-09 23:53     ` [PATCH 1/2] iommu: Export intel_iommu_enabled to signal when iommu is in use Keith Packard
2011-12-09 23:53     ` [PATCH 2/2] drm/i915: By default, enable RC6 on IVB and SNB when reasonable Keith Packard
2011-12-13  3:45       ` Matthew Garrett

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=86aa7mefak.fsf@sumi.keithp.com \
    --to=keithp@keithp.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=dwmw2@infradead.org \
    --cc=eugeni.dodonov@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.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