linux-kernel - Re: [patch] s390: do not use _local_bh

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070223140443.GA23754@elte.hu>
Date:	Fri, 23 Feb 2007 15:04:43 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Martin Schwidefsky <schwidefsky@...ibm.com>
Cc:	Heiko Carstens <heiko.carstens@...ibm.com>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [patch] s390: do not use _local_bh_enable()

* Martin Schwidefsky <schwidefsky@...ibm.com> 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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/