mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: linux-kernel@vger.kernel.org, Milton Miller <miltonm@bga.com>,
	Hendrik Brueckner <brueckner@linux.vnet.ibm.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH] HVC: do not request the irq twice.
Date: Thu, 22 Jan 2009 20:09:43 +0100	[thread overview]
Message-ID: <200901222009.43342.borntraeger@de.ibm.com> (raw)
In-Reply-To: <1232646968-32671-1-git-send-email-Ian.Campbell@citrix.com>

Am Thursday 22 January 2009 18:56:08 schrieb Ian Campbell:
> --- a/drivers/char/hvc_irq.c
> +++ b/drivers/char/hvc_irq.c
> @@ -28,6 +28,10 @@ int notifier_add_irq(struct hvc_struct *hp, int irq)
>  		hp->irq_requested = 0;
>  		return 0;
>  	}
> +
> +	if (hp->irq_requested)
> +		return 0;
> +
>  	rc = request_irq(irq, hvc_handle_interrupt, IRQF_DISABLED,
>  			   "hvc_console", hp);
>  	if (!rc)

Unfortunately I have no system with an irq based hvc console - I cannot test 
this patch. Anyway, the patch looks sane:

Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>

If this really fixes a problem, I am asking myself, if notifier_del can be 
called several times as well. If yes, it might be better to call free_irq at 
the last notifier_del - which means we need proper refcounting. Otherwise the 
console switches into polling mode....

Christian, blaming Rusty for using hvc_console in virtio_console which made me 
somehow responsible for this code...  ;-)

  reply	other threads:[~2009-01-22 19:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22 17:56 Ian Campbell
2009-01-22 19:09 ` Christian Borntraeger [this message]
2009-01-23  9:45   ` Ian Campbell

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=200901222009.43342.borntraeger@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=benh@kernel.crashing.org \
    --cc=brueckner@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miltonm@bga.com \
    --cc=rusty@rustcorp.com.au \
    /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

all inboxes | Powered by JetHome®