linux-kernel - Re: [PATCH] [50/50] x86_64: Remove fpu io port resource

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <46F44D27.4050704@garzik.org>
Date:	Fri, 21 Sep 2007 19:00:55 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Andi Kleen <ak@...e.de>
CC:	patches@...-64.org, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] [50/50] x86_64: Remove fpu io port resource

Andi Kleen wrote:
> Not needed on modern systems without external FPU
> 
> TBD on i386 it is only needed for true 386s. Could remove it there
> TBD for >= 486
> 
> Signed-off-by: Andi Kleen <ak@...e.de>
> 
> ---
>  arch/x86_64/kernel/setup.c |    2 --
>  1 file changed, 2 deletions(-)
> 
> Index: linux/arch/x86_64/kernel/setup.c
> ===================================================================
> --- linux.orig/arch/x86_64/kernel/setup.c
> +++ linux/arch/x86_64/kernel/setup.c
> @@ -121,8 +121,6 @@ struct resource standard_io_resources[] 
>  		.flags = IORESOURCE_BUSY | IORESOURCE_IO },
>  	{ .name = "dma2", .start = 0xc0, .end = 0xdf,
>  		.flags = IORESOURCE_BUSY | IORESOURCE_IO },
> -	{ .name = "fpu", .start = 0xf0, .end = 0xff,
> -		.flags = IORESOURCE_BUSY | IORESOURCE_IO }

Since we are merging x86 and x86-64, I think it would be nice at least 
to CC Thomas on patches that increase 32/64-bit differences...  because 
won't this patch have to be partial un-done when we merge i386 and x86-64?

	Jeff


-
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/