Hm. Well, the reason I'd like to leave the queueing code there is
because perhaps at some point in the future something may need to call
mtrr_add() before smp_begin(). So I see it as future proofing.
Also, the cost is essentially 0, as the queue is freed by
free_initmem(). So to me it doesn't seem like kernel bloat.
However, if you insist, I'll rip out the queueing code and replace it
with printk()s telling you that you can't call mtrr_add() yet. I think
it's worth having the warning (generating a lockup or an OOPS is
probably not a good idea: you should at least warn people about what's
wrong if possible).
Note that the cost of the warnings (post free_initmem()) is the
dominant factor to kernel bloat here :-)
Regards,
Richard....
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html