mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Chris Wright <chrisw@sous-sol.org>,
	jeremy@xensource.com, linux-kernel@vger.kernel.org,
	Christian.Limpach@cl.cam.ac.uk, clameter@sgi.com,
	ebiederm@xmission.com, kraxel@suse.de, hollisb@us.ibm.com,
	ian.pratt@xensource.com, rusty@rustcorp.com.au, zach@vmware.com
Subject: Re: [PATCH 7 of 13] Make __FIXADDR_TOP variable to allow it to make space for a hypervisor
Date: Tue, 1 Aug 2006 14:37:51 -0700	[thread overview]
Message-ID: <20060801213751.GA11244@sequoia.sous-sol.org> (raw)
In-Reply-To: <20060801073428.f543ba9f.akpm@osdl.org>

* Andrew Morton (akpm@osdl.org) wrote:
> On Tue, 1 Aug 2006 02:03:30 -0700
> Chris Wright <chrisw@sous-sol.org> wrote:
> 
> > * Jeremy Fitzhardinge (jeremy@xensource.com) wrote:
> > > -#define MAXMEM			(-__PAGE_OFFSET-__VMALLOC_RESERVE)
> > > +#define MAXMEM			(__FIXADDR_TOP-__PAGE_OFFSET-__VMALLOC_RESERVE)
> > 
> > In the native case we lose one page of lowmem now.
> 
> erm, isn't this the hunk which gave one of my machines a 4kb highmem zone?
> I have memories of reverting it.

Yes, that does sound quite familiar.  I couldn't find the thread, do you
recall any of the details?  I expect it's the same issue as the off by one
page I mentioned above.

thanks,
-chris

  reply	other threads:[~2006-08-01 21:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <patchbomb.1154421371@ezr.goop.org>
     [not found] ` <b6c100bb5ca5e2839ac8.1154421378@ezr.goop.org>
2006-08-01  9:03   ` Chris Wright
2006-08-01 14:34     ` Andrew Morton
2006-08-01 21:37       ` Chris Wright [this message]
2006-08-02  1:47         ` Rusty Russell
2006-08-02  7:01           ` Chris Wright
2006-08-02  7:20             ` Rusty Russell
2006-08-02  8:26               ` Chris Wright

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=20060801213751.GA11244@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=ebiederm@xmission.com \
    --cc=hollisb@us.ibm.com \
    --cc=ian.pratt@xensource.com \
    --cc=jeremy@xensource.com \
    --cc=kraxel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=zach@vmware.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
Powered by JetHome