All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@suse.de>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: PAE patches / hypercall interface changes
Date: 09 Jun 2005 11:40:29 +0200	[thread overview]
Message-ID: <87br6f27hu.fsf@bytesex.org> (raw)
In-Reply-To: <20050608181627.GB20591@bytesex>

Gerd Knorr <kraxel@suse.de> writes:

> > (XEN) System RAM: 6143MB (6290476kB)
> > Not enough memory for frame table
> 
> I'll have a look tomorrow.

Here we go.

Boot allocator uses "unsigned long" for physical addresses and thus
doesn't work in PAE mode.  Fix below.  That patch could make it work
(or at least fail later in boot ;)

cheers,

  Gerd

==============================[ cut here ]==============================
--- xen.orig/common/page_alloc.c	2005-06-08 16:25:02.000000000 +0200
+++ xen/common/page_alloc.c	2005-06-09 11:37:29.000000000 +0200
@@ -148,7 +148,7 @@ unsigned long init_boot_allocator(unsign
     return bitmap_start + bitmap_size;
 }
 
-void init_boot_pages(unsigned long ps, unsigned long pe)
+void init_boot_pages(physaddr_t ps, physaddr_t pe)
 {
     unsigned long bad_pfn;
     char *p;
--- xen.orig/include/xen/mm.h	2005-06-08 16:25:02.000000000 +0200
+++ xen/include/xen/mm.h	2005-06-09 11:38:41.000000000 +0200
@@ -11,7 +11,7 @@ struct pfn_info;
 
 /* Boot-time allocator. Turns into generic allocator after bootstrap. */
 unsigned long init_boot_allocator(unsigned long bitmap_start);
-void init_boot_pages(unsigned long ps, unsigned long pe);
+void init_boot_pages(physaddr_t ps, physaddr_t pe);
 unsigned long alloc_boot_pages(unsigned long size, unsigned long align);
 void end_boot_allocator(void);

  reply	other threads:[~2005-06-09  9:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 15:21 PAE patches / hypercall interface changes Gerd Knorr
2005-06-08 17:56 ` Christopher S. Aker
2005-06-08 18:16   ` Gerd Knorr
2005-06-09  9:40     ` Gerd Knorr [this message]
2005-06-11  3:51       ` Christopher S. Aker

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=87br6f27hu.fsf@bytesex.org \
    --to=kraxel@suse.de \
    --cc=caker@theshore.net \
    --cc=xen-devel@lists.xensource.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 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.