public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [patch] s390: do not use _local_bh_enable()
Date: Fri, 23 Feb 2007 15:04:43 +0100	[thread overview]
Message-ID: <20070223140443.GA23754@elte.hu> (raw)
In-Reply-To: <1172238097.30132.34.camel@localhost>


* Martin Schwidefsky <schwidefsky@de.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


  reply	other threads:[~2007-02-23 14:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23  6:14 [patch] s390: do not use _local_bh_enable() Ingo Molnar
2007-02-23  9:36 ` Heiko Carstens
2007-02-23 13:41   ` Martin Schwidefsky
2007-02-23 14:04     ` Ingo Molnar [this message]
2007-02-23 14:20       ` Martin Schwidefsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070223140443.GA23754@elte.hu \
    --to=mingo@elte.hu \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox