Martin Bligh <[email protected]> writes:
>>>>I don't recall anyone expressing any desire for the ability to set these
>>>>things at runtime. Unless there is such a requirement I'd suggest that the
>>>>best way to address Eric's point is to simply rename the relevant functions
>>>>from foo() to subarch_foo().
>>>>
>>>
>>> Avoiding the runtime assignment isn't possible if you want a generic subarch
>>> that truly can run on multiple different platforms.
>> Well as I said - I haven't seen any requirement for this expressed. That
>> doesn't mean that such a requirements doesn't exist, of course.
>
> I think there is a real requirement to do this at boot-time, yes. We don't want
> a proliferation of different kernel builds in distros,
> but one kernel that installs and boots everywhere (think installer
> kernels on boot CDs, etc ... plus testing requirements). Autoswitching,
> without magic user-flags. That's what the generic subarch was always
> for, and frankly the others all ought to die (apart from possibly really
> specialised non-mainstream stuff like voyager and NUMA-Q).
Plus it is pretty simple if you compile for a single architecture to
kill the function pointers. That is how the alpha is currently structured.
So for the people who don't want it switchable the code can just compile
out.
Getting this infrastructure now before i386 becomes primarily and embedded
architecture will be nice.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
