linux-kernel - Re: [PATCH] x86: x86_{phys,virt}

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 8 Sep 2008 15:40:19 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jan Beulich <jbeulich@...ell.com>
Cc:	Yinghai Lu <yhlu.kernel@...il.com>, tglx@...utronix.de,
	linux-kernel@...r.kernel.org, hpa@...or.com
Subject: Re: [PATCH] x86: x86_{phys,virt}_bits field also for i386 (v2)


* Jan Beulich <jbeulich@...ell.com> wrote:

> >>> Ingo Molnar <mingo@...e.hu> 05.09.08 17:00 >>>
> >
> >* Jan Beulich <jbeulich@...ell.com> wrote:
> >
> >> Make the x86_{phys,virt}_bits common for 32- and 64-bits, and use the
> >> former in ioremap's phys_addr_valid() check also on 32bit/PAE.
> >> 
> >> Signed-off-by: Jan Beulich <jbeulich@...ell.com>
> >> 
> >> ---
> >>  arch/x86/kernel/cpu/common.c |   17 +++++++++++++++++
> >>  arch/x86/mm/ioremap.c        |   15 ++++++---------
> >>  include/asm-x86/processor.h  |    4 ++--
> >>  3 files changed, 25 insertions(+), 11 deletions(-)
> >
> >hm, the cpu/common.c bits just got reworked massively in tip/master. 
> >I've tried a blind merge (see the patch below) but at least the first 
> >hunk looks wrong. Mind looking at how to merge this?
> 
> This is my take at it:
> 
> Make the x86_{phys,virt}_bits common for 32- and 64-bits, and use the
> former in ioremap's phys_addr_valid() check also on 32bit/PAE.

applied to tip/x86/mm-debug - thanks Jan!

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/