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: <200710011240.35802.ak@suse.de>
Date:	Mon, 1 Oct 2007 12:40:35 +0200
From:	Andi Kleen <ak@...e.de>
To:	Jeff Garzik <jeff@...zik.org>
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


> > ===================================================================
> > --- 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 }

The patch has been dropped meanwhile BTW --  Maciej pointed
out correctly that the south bridges likely decode it anyways.

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

So far I still maintain i386 and x86-64. If Thomas wants to take both
over completely he can do that; but I won't bother handling any patches i didn't 
write then anymore.

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