Dmitry Torokhov wrote:
However I am not really fond of idea of adding constructs like this
all over the code:
#define USE_REAL_TIME_DELAY_I_REALLY_MEAN_IT_THIS_TIME_I_SWEAR
as the time passes... Drivers should be blissfully ignorant of being
run on virtual hardware.
I agree in general, but there are two uses for this ugly construct. One
is for drivers and isolated sections of code which actually interact
with the real world. They need real time delays. The only two examples
so far are SMP coprocessor bootstrapping and blinking LEDs with a
recognizable frequency. I don't expect many more to show up.
The other use for this construct is compiling a hardware privileged
virtual domain that actually drives real hardware - you can just define
this globally to override any delay masking.
Zach
-
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]
