public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: "Andi Kleen" <ak@suse.de>
Cc: "Andreas Herrmann" <andreas.herrmann3@amd.com>,
	"Suresh B Siddha" <suresh.b.siddha@intel.com>,
	"Richard Gooch" <rgooch@safe-mbox.com>,
	<linux-kernel@vger.kernel.org>, <discuss@x86-64.org>
Subject: Re: [discuss] [patch] mtrr: fix issues with large addresses
Date: Tue, 06 Feb 2007 09:31:45 +0000	[thread overview]
Message-ID: <45C85911.76E4.0078.0@novell.com> (raw)
In-Reply-To: <200702060853.30812.ak@suse.de>

>>> Andi Kleen <ak@suse.de> 06.02.07 08:53 >>>
>On Monday 05 February 2007 23:50, Siddha, Suresh B wrote:
>> On Mon, Feb 05, 2007 at 06:19:59PM +0100, Andreas Herrmann wrote:
>> > o added check to restrict base address to 36 bit on i386
>> 
>> Why is this? It can go upto implemented physical bits, right?
>
>In theory it can, but Linux doesn't support it.

I don't think I remember a restriction here, at least not below 44 bits
(that's where pfn-s would need to become 64-bit wide).

Jan

  reply	other threads:[~2007-02-06  9:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-05 17:19 [patch] mtrr: fix issues with large addresses Andreas Herrmann
2007-02-05 22:50 ` Siddha, Suresh B
2007-02-06  7:53   ` Andi Kleen
2007-02-06  9:31     ` Jan Beulich [this message]
2007-02-06  9:45       ` [discuss] " Andi Kleen
2007-02-06  9:53         ` Jan Beulich
2007-02-06 10:54           ` Andi Kleen
2007-02-06 16:25             ` Andreas Herrmann
2007-02-06 16:16       ` Andreas Herrmann
2007-02-06  0:26 ` Eric W. Biederman
2007-02-06 16:08   ` Andreas Herrmann
2007-02-06 17:54     ` Eric W. Biederman
2007-02-06 18:42       ` [discuss] " Andreas Herrmann
2007-02-06 19:08         ` Eric W. Biederman
2007-02-06 19:25           ` Joerg Roedel
2007-02-06 19:44             ` Eric W. Biederman

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=45C85911.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=ak@suse.de \
    --cc=andreas.herrmann3@amd.com \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@safe-mbox.com \
    --cc=suresh.b.siddha@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox