Skip to content

Commit

Permalink
x86: Ioremap: fix wrong physical address handling in PAT code
Browse files Browse the repository at this point in the history
The following two commits fixed a problem that x86 ioremap() doesn't handle
physical address higher than 32-bit properly in X86_32 PAE mode.

 ffa71f3 (x86, ioremap: Fix incorrect
 physical address handling in PAE mode)

 35be1b7 (x86, ioremap: Fix normal
 ram range check)

But these fixes are not enough, since pat_pagerange_is_ram() in PAT code
also has a same problem. This patch fixes it.

Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Reviewed-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
LKML-Reference: <4C47DDCF.80300@jp.fujitsu.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
  • Loading branch information
Yasuaki Ishimatsu authored and Thomas Gleixner committed Jul 29, 2010
1 parent 3f8afb7 commit 3709c85
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion arch/x86/mm/pat.c
Original file line number Diff line number Diff line change
Expand Up @@ -158,7 +158,7 @@ static unsigned long pat_x_mtrr_type(u64 start, u64 end, unsigned long req_type)
return req_type;
}

static int pat_pagerange_is_ram(unsigned long start, unsigned long end)
static int pat_pagerange_is_ram(resource_size_t start, resource_size_t end)
{
int ram_page = 0, not_rampage = 0;
unsigned long page_nr;
Expand Down

0 comments on commit 3709c85

Please sign in to comment.