All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Brice Goglin <brice.goglin@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org
Subject: Re: MTRR use in drivers
Date: Sun, 23 Jun 2013 15:10:36 -0700	[thread overview]
Message-ID: <51C7725C.5090801@zytor.com> (raw)
In-Reply-To: <20130623215649.GA1288@khazad-dum.debian.net>

On 06/23/2013 02:56 PM, Henrique de Moraes Holschuh wrote:
> 
> And as far as I could find from Intel's not-that-complete public
> "specification updates", we are applying the errata workaround to a few more
> processors than strictly required, but since I have no idea how to write a
> test case, I can't whitelist the 3rd-gen Pentium M on my T43, nor can I get
> ThinkPad owners to test it for us on 1st and 2nd-gen Pentium M and report
> back.
> 

Which specific erratum are you referring to, here?  The "WC becomes UC"
erratum?  I don't think there is a sane testcase for it since it needs a
very complicated setup to trigger.

	-hpa

WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Brice Goglin <brice.goglin@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org
Subject: Re: MTRR use in drivers
Date: Sun, 23 Jun 2013 15:10:36 -0700	[thread overview]
Message-ID: <51C7725C.5090801@zytor.com> (raw)
In-Reply-To: <20130623215649.GA1288@khazad-dum.debian.net>

On 06/23/2013 02:56 PM, Henrique de Moraes Holschuh wrote:
> 
> And as far as I could find from Intel's not-that-complete public
> "specification updates", we are applying the errata workaround to a few more
> processors than strictly required, but since I have no idea how to write a
> test case, I can't whitelist the 3rd-gen Pentium M on my T43, nor can I get
> ThinkPad owners to test it for us on 1st and 2nd-gen Pentium M and report
> back.
> 

Which specific erratum are you referring to, here?  The "WC becomes UC"
erratum?  I don't think there is a sane testcase for it since it needs a
very complicated setup to trigger.

	-hpa


  reply	other threads:[~2013-06-23 22:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21  5:00 MTRR use in drivers H. Peter Anvin
2013-06-23  6:35 ` Brice Goglin
2013-06-23 14:07   ` H. Peter Anvin
2013-06-23 14:07     ` H. Peter Anvin
2013-06-23 19:29     ` Henrique de Moraes Holschuh
2013-06-23 20:02       ` H. Peter Anvin
2013-06-23 20:30         ` Dave Airlie
2013-06-23 20:38           ` H. Peter Anvin
2013-06-23 20:54             ` Dave Airlie
2013-06-23 20:58               ` H. Peter Anvin
2013-06-23 21:27                 ` Dave Airlie
2013-06-23 21:27                   ` Dave Airlie
2013-06-23 23:09             ` Andy Lutomirski
2013-06-23 21:56         ` Henrique de Moraes Holschuh
2013-06-23 22:10           ` H. Peter Anvin [this message]
2013-06-23 22:10             ` H. Peter Anvin
2013-06-24  0:02             ` Henrique de Moraes Holschuh
2013-06-24  0:31               ` H. Peter Anvin

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=51C7725C.5090801@zytor.com \
    --to=hpa@zytor.com \
    --cc=brice.goglin@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hmh@hmh.eng.br \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.