* Martin Schwidefsky <[email protected]> wrote:
> [...] cio_tpi and sclp_sync_wait are used to wait for the interrupt of
> the console device to make room in the buffer for a printk out of
> disabled context.
ouch. So you want/need to wait for a specific type of interrupt, in a
section of code that has all interrupts disabled? Is this the only form
of communication to the hypervisor, for this particular purpose? It
seems to me that polling a bit in a buffer shared between the hypervisor
and the guest OS [combined with cpu_relax()] would fit this scenario
alot better (and wouldnt cause any such gymnastics to avoid regular
Linux irq processing) than waiting for an interrupt to be injected by
the hypervisor. Or is this interrupt-based interface an ABI property and
the only way to do it?
Ingo
-
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]
