From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Peter Hurley <peter@hurleysoftware.com>,
"zhenzhong.duan@oracle.com" <zhenzhong.duan@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] x86: mtrr: Constrain WB MTRR to max phys mem prior to cleanup
Date: Sat, 29 Sep 2012 18:25:48 -0300 [thread overview]
Message-ID: <20120929212548.GD8329@khazad-dum.debian.net> (raw)
In-Reply-To: <50675776.10702@zytor.com>
On Sat, 29 Sep 2012, H. Peter Anvin wrote:
> >Intel doesn't make it easy to get all processor specification updates at
> >once so that I could hunt down every processor which acknowledges the
> >existence of that errata before replying, so I will assume for the moment
> >that the comment is mostly correct.
>
> I should say: as far as I know the blacklist is there because noone
> has been willing to bother looking at if it actually matters, given
> how old the hardware is.
Hmm, well, I will probably have to look it up for a few processors that
matter to me, apparently.
Can't people that work at Intel at least petition for meta-index pages of
this kind of documentation?
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2012-09-29 21:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 17:44 [RFC] x86: mtrr: Constrain WB MTRR to max phys mem prior to cleanup Peter Hurley
2012-09-07 18:40 ` H. Peter Anvin
2012-09-10 3:54 ` zhenzhong.duan
2012-09-28 17:37 ` Peter Hurley
2012-09-29 2:41 ` Zhenzhong Duan
2012-09-29 3:16 ` H. Peter Anvin
2012-09-29 10:46 ` Henrique de Moraes Holschuh
2012-09-29 15:05 ` H. Peter Anvin
2012-09-29 20:11 ` Henrique de Moraes Holschuh
2012-09-29 20:16 ` H. Peter Anvin
2012-09-29 20:17 ` H. Peter Anvin
2012-09-29 21:25 ` Henrique de Moraes Holschuh [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-24 20:51 Peter Hurley
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=20120929212548.GD8329@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peter@hurleysoftware.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zhenzhong.duan@oracle.com \
/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.