From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [git pull] x86 PAT changes
Date: Fri, 25 Apr 2008 16:43:59 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0804251351511.2779@woody.linux-foundation.org> (raw)
In-Reply-To: <20080424225625.GB8717@elte.hu>
On Fri, 25 Apr 2008, Ingo Molnar wrote:
> Linus, please pull the x86-pat git tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86-pat.git for-linus
>
> this adds the second (and final) phase of the x86 PAT changes. Due to
> generic impact (the drivers/char/mem.c and include/asm-generic/iomap.h
> changes) this is offered as a separate tree.
So why is PAT dependent on NONPROMISC_DEVMEM here?
It seems pointless and wrong. Somebody might want to have both the full
/dev/mem and PAT.
Also, it causes this message for me on one of my machines:
EXT3-fs: mounted filesystem with ordered data mode.
Overlap at 0xe0300000-0xe0400000
Overlap at 0xe0300000-0xe0400000
Overlap at 0xe0300000-0xe0400000
Overlap at 0xe0300000-0xe0400000
Overlap at 0xe0300000-0xe0400000
Overlap at 0xe0300000-0xe0400000
mtrr: no more MTRRs available
Overlap at 0xd0000000-0xe0000000
Overlap at 0xe0300000-0xe0400000
Overlap at 0xe0300000-0xe0380000
EXT3 FS on dm-0, internal journal
...
eth0: no IPv6 routers present
Overlap at 0xd0000000-0xe0000000
Overlap at 0xe0300000-0xe0400000
Overlap at 0xe0300000-0xe0380000
Overlap at 0xd0000000-0xe0000000
Overlap at 0xe0300000-0xe0400000
Overlap at 0xe0300000-0xe0380000
Overlap at 0xd0000000-0xe0000000
Overlap at 0xe0300000-0xe0400000
Overlap at 0xe0300000-0xe0380000
Overlap at 0xd0000000-0xe0000000
Overlap at 0xe0300000-0xe0400000
Overlap at 0xe0300000-0xe0380000
Overlap at 0xd0000000-0xe0000000
Overlap at 0xe0300000-0xe0400000
Overlap at 0xe0300000-0xe0380000
Overlap at 0xe0300000-0xe0400000
Overlap at 0xe0300000-0xe0400000
Overlap at 0xe0300000-0xe0400000
Overlap at 0xe0300000-0xe0400000
Overlap at 0xe0300000-0xe0400000
Overlap at 0xe0300000-0xe0400000
Overlap at 0xd0000000-0xd0020000
mtrr: no more MTRRs available
Overlap at 0xd0000000-0xe0000000
Overlap at 0xe0300000-0xe0400000
Overlap at 0xe0300000-0xe0380000
which is a bit annoying. Forgotten debug printk, perhaps?
Linus
next prev parent reply other threads:[~2008-04-25 23:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 22:56 Ingo Molnar
2008-04-25 23:43 ` Linus Torvalds [this message]
2008-04-26 0:06 ` H. Peter Anvin
2008-04-26 1:12 ` Linus Torvalds
2008-04-26 8:56 ` Ingo Molnar
2008-04-26 16:54 ` Pallipadi, Venkatesh
2008-04-26 17:15 ` Linus Torvalds
2008-04-26 18:32 ` Venki Pallipadi
2008-04-26 19:07 ` [patch] x86, PAT: disable /dev/mem mmap RAM with PAT Ingo Molnar
2008-04-26 9:57 ` [git pull] x86 PAT changes Ingo Molnar
2008-04-26 13:40 ` Gabriel C
2008-04-26 14:42 ` Ingo Molnar
2008-04-26 15:37 ` Gabriel C
2008-04-26 15:41 ` Ingo Molnar
2008-04-26 16:43 ` Linus Torvalds
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=alpine.LFD.1.10.0804251351511.2779@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®