On Tue, 2002-10-01 at 22:44, Matthew Dobson wrote:
> > STANDALONE seems to be a very namespace-polluting choice of define.
> > MULTIQUAD_STANDALONE, MQ_STANDALONE... anything would be better imo.
>
> The #define is most definitely *not* NUMA/Multiquad specific. In this
> particular instance, it is guarding Multiquad specific code... The
> STANDALONE option (please clarify if I'm wrong, Alan) is for code that
> is compiled along with the kernel, with the kernel headers, etc, but is
> not acually part of the kernel proper.
Indeed
Its set by the boot loader code that wants to also use inb/outb etc but
not get the kernel magic wonders of numa-q and other evil abuses of PC
iomapping
-
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/
This archive was generated by hypermail 2b29 : Mon Oct 07 2002 - 22:00:30 EST