Messages in this thread | | | From | "H. Peter Anvin" <> | Subject | Re: 2.4.19pre3aa2 | Date | 14 Mar 2002 13:16:53 -0800 |
| |
Followup to: <20020314133223.B19636@suse.de> By author: Dave Jones <davej@suse.de> In newsgroup: linux.dev.kernel > > On Thu, Mar 14, 2002 at 03:28:01AM +0100, Andrea Arcangeli wrote: > > Only in 2.4.19pre3aa2: 21_pte-highmem-f00f-1 > > > > vmalloc called before smp_init was an hack, right way > > is to use fixmap. CONFIG_M686 doesn't mean much these > > days, but it's ok and probably most vendors will use it > > for the smp kernels, so it will save 4096 of the vmalloc space. > > I just didn't wanted to clobber the code with || CONFIG_K7 || > > CONFIG_... | ... given all the other f00f stuff is also > > conditional only to M686 and probably nobody bothered to compile > > it out for my same reason > > Brian Gerst had a patch a few months back to introduce a CONFIG_F00F > if a relevant CONFIG_Mxxx was chosen[1]. It never got applied anywhere, but makes > more sense than the CONFIG_M686 we currently use. > > [1] 386/486/586. With addition of my Vendor choice menu, we could even further > narrow it down to Intel only. >
One thing: I would again like to see "compatibility" and "optimization" be separated out. The current CPU type menu is a bit of both.
It's actually quite useful these days to compile for 386 or 486, but optimize for 686.
-hpa -- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |