From: David Woodhouse <dwmw2@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, andi@firstfloor.org,
arjan@infradead.org, torvalds@linux-foundation.org,
sfr@canb.auug.org.au, Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH] Blacklist DMAR on Intel G31/G33 chipsets
Date: Sun, 07 Sep 2008 09:20:18 +0100 [thread overview]
Message-ID: <1220775618.2985.408.camel@pmac.infradead.org> (raw)
In-Reply-To: <20080906154935.GD1774@elte.hu>
On Sat, 2008-09-06 at 17:49 +0200, Ingo Molnar wrote:
> Jesse's call obviously, but the DMI thing local to intel-iommu.c still
> looks better to me in all regards. I'm no fan of DMI in general - it
> just doesnt scale - but here a crappy BIOS gets punished with a DMI
> quirk and that's OK.
The DMI was my first choice too -- I was only trying to do it with PCI
to keep Andi happy.
There is a non-zero possibility that the same BIOS bug gets copied to
other boards, I suppose -- but it's not exactly hard to add another
board to the table if we find that to be the case.
Shall I resubmit the original version to Linus again for 2.6.27, then?
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2008-09-07 8:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 20:14 Misc fixes for 2.6.27 David Woodhouse
2008-09-01 22:32 ` Andi Kleen
2008-09-01 22:35 ` Arjan van de Ven
2008-09-01 23:01 ` Andi Kleen
2008-09-01 23:16 ` Arjan van de Ven
2008-09-02 6:19 ` Andi Kleen
2008-09-02 8:23 ` David Woodhouse
2008-09-03 10:53 ` Blacklist DMAR on Intel G31/G33 chipsets David Woodhouse
2008-09-03 12:09 ` Andi Kleen
2008-09-03 12:22 ` David Woodhouse
2008-09-04 8:54 ` [PATCH] " David Woodhouse
2008-09-05 18:34 ` Ingo Molnar
2008-09-05 18:47 ` David Woodhouse
2008-09-06 15:49 ` Ingo Molnar
2008-09-07 8:20 ` David Woodhouse [this message]
2008-09-07 15:35 ` [2.6.27 PATCH] " David Woodhouse
2008-09-09 18:39 ` Jesse Barnes
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=1220775618.2985.408.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®