> >> later in the boot after your own drivers have properly bound.
> useful. Cc'ing Steven Smith in case he has any comments to make.
-- Getting log messages out of the drivers and into dom0.
is available by reading a two-byte magic number from IO port 0x10.
this is 0, skip to 6.
closed-source ones, which use product number 1.
4) The drivers write a four-byte build number to IO port 0x10.
useful for debugging and support.
This isn't exactly a pretty protocol, but it does solve the problem.
which has a product_name of xensource-windows.
on Windows) it's complicated and messy, and generally best avoided.
+   modelled as a token bucket, with one token for every byte of log.