From: Kevin Winchester <kjwinchester@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Latest -git ioremap error
Date: Sun, 03 Feb 2008 21:10:26 -0400 [thread overview]
Message-ID: <47A66602.1040907@gmail.com> (raw)
In-Reply-To: <20080203213353.GB27737@elte.hu>
Ingo Molnar wrote:
> * Kevin Winchester <kjwinchester@gmail.com> wrote:
>
>>> x86: fix ioremap RAM check
>>>
>>> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>>> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
>> Lucky first try - reverting this commit fixes the problem for me. Any
>> ideas?
>
> Could you check the patch below - does that too fix the problem for you?
>
Yes, the patch below fixes the problem. I guess that makes it a:
Tested-by: Kevin Winchester <kjwinchester@gmail.com>
> Ingo
>
> ----------------->
> Subject: x86: relax RAM check in ioremap()
> From: Ingo Molnar <mingo@elte.hu>
>
> Kevin Winchester reported the loss of direct rendering, due to:
>
> [ 0.588184] agpgart: Detected AGP bridge 0
> [ 0.588184] agpgart: unable to get memory for graphics translation table.
> [ 0.588184] agpgart: agp_backend_initialize() failed.
> [ 0.588207] agpgart-amd64: probe of 0000:00:00.0 failed with error -12
>
> and bisected it down to:
>
>> commit 266b9f8727976769e2ed2dad77ac9295f37e321e
>> Author: Thomas Gleixner <tglx@linutronix.de>
>> Date: Wed Jan 30 13:34:06 2008 +0100
>>
>> x86: fix ioremap RAM check
>
> this check was too strict and caused an ioremap() failure.
>
> the problem is due to the somewhat unclean way of how the GART code
> reserves a memory range for its aperture, and how it utilizes it
> later on.
>
> Allow RAM pages to be ioremap()-ed too, as long as they are reserved.
>
> Bisected-by: Kevin Winchester <kjwinchester@gmail.com>
> Acked-by: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> ---
> arch/x86/mm/ioremap.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> Index: linux-x86.q/arch/x86/mm/ioremap.c
> ===================================================================
> --- linux-x86.q.orig/arch/x86/mm/ioremap.c
> +++ linux-x86.q/arch/x86/mm/ioremap.c
> @@ -116,7 +116,7 @@ static void __iomem *__ioremap(unsigned
> {
> void __iomem *addr;
> struct vm_struct *area;
> - unsigned long offset, last_addr;
> + unsigned long pfn, offset, last_addr;
> pgprot_t prot;
>
> /* Don't allow wraparound or zero size */
> @@ -133,9 +133,9 @@ static void __iomem *__ioremap(unsigned
> /*
> * Don't allow anybody to remap normal RAM that we're using..
> */
> - for (offset = phys_addr >> PAGE_SHIFT; offset < max_pfn_mapped &&
> - (offset << PAGE_SHIFT) < last_addr; offset++) {
> - if (page_is_ram(offset))
> + for (pfn = phys_addr >> PAGE_SHIFT; pfn < max_pfn_mapped &&
> + (pfn << PAGE_SHIFT) < last_addr; pfn++) {
> + if (pfn_valid(pfn) && !PageReserved(pfn_to_page(pfn)))
> return NULL;
> }
>
next prev parent reply other threads:[~2008-02-04 1:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 18:23 Latest -git ioremap error Kevin Winchester
2008-02-03 18:33 ` Kevin Winchester
2008-02-03 21:33 ` Ingo Molnar
2008-02-04 1:10 ` Kevin Winchester [this message]
2008-02-04 6:01 ` Mike Galbraith
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=47A66602.1040907@gmail.com \
--to=kjwinchester@gmail.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 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.