From: P@draigBrady.com
To: "Remy Böhmer" <remy.bohmer@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bigphysarea for 2.6.10 en 2.6.11
Date: Mon, 13 Jun 2005 10:28:40 +0100 [thread overview]
Message-ID: <42AD51C8.4000703@draigBrady.com> (raw)
In-Reply-To: <a7fe805f05061113426c86ba92@mail.gmail.com>
Remy Böhmer wrote:
> I have pulled the bigphysarea patch (as posted by Nick Martin for
> kernel 2.6.9) towards the kernels 2.6.10 and 2.6.11.
> Maybe there is somebody out there who can use it.
>
> (it only suits the i386 kernel, I have not done this job for other platforms.)
> First the 2.6.10 version is listed below, after this the 2.6.11 version
>
> Have fun with it!
>
> Remy
>
> linux-2.6.10.bigphys/mm/bigphysarea.c
> --- linux-2.6.10.orig/mm/bigphysarea.c Wed Dec 31 19:00:00 1969
> +++ linux-2.6.10.bigphys/mm/bigphysarea.c Mon Nov 15 15:49:01 2004
> +static
> +int __init bigphysarea_setup(char *str)
> +{
> + int par;
> + if (get_option(&str,&par)) {
> + bigphysarea_pages = par;
> + // Alloc the memory
> + bigphysarea =
> alloc_bootmem_low_pages(bigphysarea_pages<<PAGE_SHIFT);
> + if (!bigphysarea) {
> + printk(KERN_CRIT "bigphysarea: not enough
> memory for %d pages\n",bigphysarea_pages);
> + return -ENOMEM;
> + }
> +
> + // register the resource for it
> + mem_resource.start = bigphysarea;
That should be: mem_resource.start = virt_to_phys(bigphysarea);
Otherwise you could get a collision?
--
Pádraig Brady - http://www.pixelbeat.org
--
next prev parent reply other threads:[~2005-06-13 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 20:42 [PATCH] bigphysarea for 2.6.10 en 2.6.11 Remy Böhmer
2005-06-13 9:28 ` P [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-01 14:15 Floyd Miller
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=42AD51C8.4000703@draigBrady.com \
--to=p@draigbrady.com \
--cc=linux-kernel@vger.kernel.org \
--cc=remy.bohmer@gmail.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