All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "\"J.A. Magallón\"" <jamagallon@ono.com>,
	Linux-Kernel <linux-kernel@vger.kernel.org>,
	"Yinghai Lu" <yinghai@kernel.org>,
	"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [PATCH 2/2] x86: mtrr_cleanup try gran_size to less than 1M
Date: Fri, 3 Oct 2008 09:42:46 +0200	[thread overview]
Message-ID: <20081003074246.GE4950@elte.hu> (raw)
In-Reply-To: <48E5CBFC.3090702@zytor.com>


* H. Peter Anvin <hpa@zytor.com> wrote:

> Ingo Molnar wrote:
>> * J.A. Magallón <jamagallon@ono.com> wrote:
>>
>>> Also, on a 64 bit box with 4Gb, it gives this:
>>>
>>> cicely:~# cat /proc/mtrr
>>> reg00: base=0x00000000 (   0MB), size=4096MB: write-back, count=1
>>> reg01: base=0x100000000 (4096MB), size=1024MB: write-back, count=1
>>> reg02: base=0x140000000 (5120MB), size= 512MB: write-back, count=1
>>> reg03: base=0x160000000 (5632MB), size= 256MB: write-back, count=1
>>> reg04: base=0x80000000 (2048MB), size=2048MB: uncachable, count=1
>>>
>>> Patch below cleans up formatting, with space for big bases and sizes (64 Gb).
>>
>> applied to tip/x86/mtrr, thanks!
>>
>>> +++ arch/x86/kernel/cpu/mtrr/if.c     2008-10-03 00:22:34.000000000 +0200
>>> @@ -16,7 +16,7 @@
>>>  static const char *const mtrr_strings[MTRR_NUM_TYPES] =
>>>  {
>>>      "uncachable",               /* 0 */
>>> -    "write-combining",          /* 1 */
>>> +    "write-combine",            /* 1 */
>>
>> hm, maybe this bit could confuse versions of Xorg that modifies  
>> /proc/mtrr - i.e. this could be part of the ABI towards user-space.  
>> We'll see.
>>
>
> This *IS* part of the ABI toward userspace, although I think Xorg uses 
> the ioctl() interface.

yeah, but aspects of the ABI that applications do not rely on can 
generally be changed. OTOH, i've undone this aspect of the patch - 
/proc/mtrr is a legacy interface and changes to it are unnecessary. I 
kept the boot printout cleanups.

	Ingo

  reply	other threads:[~2008-10-03  7:43 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30  1:54 [PATCH 1/2] x86: mtrr_cleanup prepare to make gran_size to less 1M Yinghai Lu
2008-09-30  1:54 ` [PATCH 2/2] x86: mtrr_cleanup try gran_size to less than 1M Yinghai Lu
2008-10-02 22:03   ` J.A. Magallón
2008-10-02 22:33     ` Yinghai Lu
2008-10-02 22:52       ` Yinghai Lu
2008-10-02 23:00         ` J.A. Magallón
2008-10-02 23:20           ` Yinghai Lu
2008-10-02 22:58       ` J.A. Magallón
2008-10-02 23:55       ` D. Hugh Redelmeier
2008-10-03  1:27         ` Yinghai Lu
2008-10-02 22:32   ` J.A. Magallón
2008-10-02 22:39     ` Yinghai Lu
2008-10-02 22:46       ` Yinghai Lu
2008-10-03  7:38         ` Ingo Molnar
2008-10-02 23:20       ` J.A. Magallón
2008-10-02 23:45         ` Yinghai Lu
2008-10-03  7:37     ` Ingo Molnar
2008-10-03  7:38       ` H. Peter Anvin
2008-10-03  7:42         ` Ingo Molnar [this message]
2008-10-03  7:44           ` H. Peter Anvin
2008-10-03 14:57         ` D. Hugh Redelmeier
2008-10-03  7:40       ` H. Peter Anvin
2008-10-03  7:44         ` Ingo Molnar
2008-10-03  7:41       ` J.A. Magallón
2008-09-30  4:07 ` [PATCH 1/2] x86: mtrr_cleanup prepare to make gran_size to less 1M H. Peter Anvin
2008-09-30  7:45   ` Ingo Molnar
2008-09-30  8:11     ` Ingo Molnar
2008-09-30 16:06       ` Yinghai Lu
2008-09-30 18:50       ` 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=20081003074246.GE4950@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=jamagallon@ono.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=yinghai@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.