The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Kyle McMartin <kyle@infradead.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: enable DMAR by default
Date: Fri, 27 Feb 2009 03:54:00 +0900	[thread overview]
Message-ID: <1235674440.8730.119.camel@macbook.infradead.org> (raw)
In-Reply-To: <20090226180304.GA10940@elte.hu>

On Thu, 2009-02-26 at 19:03 +0100, Ingo Molnar wrote:
> * Kyle McMartin <kyle@infradead.org> wrote:
> 
> > From: Kyle McMartin <kyle@redhat.com>
> > 
> > Now that the obvious bugs have been worked out, specifically 
> > the iwlagn issue, and the write buffer errata, DMAR should be 
> > safe to turn back on by default. (We've had it on since those 
> > patches were first written a few weeks ago, without any 
> > noticeable bug reports (most have been due to the dma-api 
> > debug patchset.))
> > 
> > Signed-off-by: Kyle McMartin <kyle@redhat.com>
> > 
> > ---
> > Probably 2.6.29 material, but should definitely go in for 2.6.30.
> 
> Definitely agreed on .30. Can do it in .29 as well if David and 
> the rest of the Cc: agrees.

Definitely. I wasn't any happier than you were with the patch which
disabled it in the first place.... but it was necessary at the time.

Enthusiastically-Acked-by: David Woodhouse <David.Woodhouse@intel.com>

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@intel.com                              Intel Corporation


      reply	other threads:[~2009-02-26 18:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-26 17:57 [PATCH] x86: enable DMAR by default Kyle McMartin
2009-02-26 18:03 ` Ingo Molnar
2009-02-26 18:54   ` 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=1235674440.8730.119.camel@macbook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=hpa@zytor.com \
    --cc=kyle@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=x86@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