public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] enhance x86 MTRR handling
Date: Thu, 12 May 2005 12:18:26 -0400	[thread overview]
Message-ID: <20050512161825.GC17618@redhat.com> (raw)
In-Reply-To: <s2832b02.028@emea1-mh.id2.novell.com>

On Thu, May 12, 2005 at 11:08:21AM +0200, Jan Beulich wrote:

 > - the code to correct inconsistent settings during secondary processor
 >   startup tried (if necessary) to correct, among other things, the value
 >   in IA32_MTRR_DEF_TYPE, however the newly compute value would never get
 >   used to be stored in the respective MSR
 > - the generic range validation code checked that the end of the
 >   to-be-added range would be above 1MB; the value checked should have been
 >   the start of the range
 > - when contained regions are detected, previously this was allowed only
 >   when the old region was uncacheable; this can be symmetric (i.e. the new
 >   region can also be uncacheable) and even further as per Intel's
 >   documentation write-trough and write-back for either region is also
 >   compatible with the respective opposite in the other

Whilst your changes may have merit, I'd much rather see effort spent
on getting PAT into shape than further massaging MTRR.  Its well past its
smell-by-date, and theres been no activity whatsoever afaik on getting
Terrence Ripperda's cachemap stuff beaten into shape.

I'll dust off the last version he sent and diff against latest-mm later
so it can get some more commentary. It seems everyone is in violent
agreement that we want PAT support, but nothing seems to happen.

		Dave


  reply	other threads:[~2005-05-12 16:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-12  9:08 [PATCH] enhance x86 MTRR handling Jan Beulich
2005-05-12 16:18 ` Dave Jones [this message]
2005-05-12 17:02   ` David Addison
2005-05-12 21:41   ` [RFC] Cachemap for 2.6.12rc4-mm1. Was " Dave Jones
2005-05-13 13:29     ` Andi Kleen
2005-05-13 14:24       ` Dave Hansen
2005-05-13 14:35         ` Andi Kleen
2005-05-13 15:52       ` Dave Jones
2005-05-18 22:01         ` Terence Ripperda
2005-05-18 22:03           ` Andi Kleen
2005-05-18 22:15             ` Terence Ripperda
2005-05-18 22:42               ` Andi Kleen
2005-05-19  3:57             ` Randy Dunlap
2005-05-13 22:40     ` H. Peter Anvin
2005-05-13 23:23       ` Dave Jones
2005-05-13 23:36         ` H. Peter Anvin
2005-05-13 23:42           ` Dave Jones
2005-05-13 23:49             ` 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=20050512161825.GC17618@redhat.com \
    --to=davej@redhat.com \
    --cc=JBeulich@novell.com \
    --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