public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Eduard-Gabriel Munteanu <maxdamage@aladin.ro>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] UML: fix missing non-blocking I/O, now DEBUG_SHIRQ works
Date: Mon, 11 Jun 2007 13:31:54 -0400	[thread overview]
Message-ID: <20070611173154.GA6889@c2.user-mode-linux.org> (raw)
In-Reply-To: <1181512917.3157.8.camel@localhost>

On Mon, Jun 11, 2007 at 01:01:57AM +0300, Eduard-Gabriel Munteanu wrote:
> DEBUG_SHIRQ generates spurious interrupts, triggering handlers such as 
> mconsole_interrupt() or line_interrupt(). They expect data to be 
> available to be read from their sockets/pipes, but in the case of 
> spurious interrupts, the host didn't actually send anything, so UML 
> hangs in read() and friends. Setting those fd's as O_NONBLOCK makes 
> DEBUG_SHIRQ-enabled UML kernels boot and run correctly. 

Nice.

I don't really like this section though.  The casting I have now isn't
pleasant, but I don't like adding a new global to get rid of it.

> diff --git a/arch/um/drivers/mconsole_kern.c b/arch/um/drivers/mconsole_kern.c
> index 542c9ef..02d132e 100644
> --- a/arch/um/drivers/mconsole_kern.c
> +++ b/arch/um/drivers/mconsole_kern.c
> @@ -74,12 +74,11 @@ static DECLARE_WORK(mconsole_work, mc_work_proc);
>  
>  static irqreturn_t mconsole_interrupt(int irq, void *dev_id)
>  {
> -	/* long to avoid size mismatch warnings from gcc */
> -	long fd;
> +	int fd;
>  	struct mconsole_entry *new;
>  	static struct mc_request req;	/* that's OK */
>  
> -	fd = (long) dev_id;
> +	fd = *((int *) dev_id);
>  	while (mconsole_get_request(fd, &req)){
>  		if(req.cmd->context == MCONSOLE_INTR)
>  			(*req.cmd->handler)(&req);
> @@ -798,10 +797,10 @@ void mconsole_stack(struct mc_request *req)
>   */
>  static char *notify_socket = NULL;
>  
> +static int sock;
> +
>  static int mconsole_init(void)
>  {
> -	/* long to avoid size mismatch warnings from gcc */
> -	long sock;
>  	int err;
>  	char file[256];
>  
> @@ -818,7 +817,7 @@ static int mconsole_init(void)
>  
>  	err = um_request_irq(MCONSOLE_IRQ, sock, IRQ_READ, mconsole_interrupt,
>  			     IRQF_DISABLED | IRQF_SHARED | IRQF_SAMPLE_RANDOM,
> -			     "mconsole", (void *)sock);
> +			     "mconsole", &sock);
>  	if (err){
>  		printk("Failed to get IRQ for management console\n");
>  		return(1);

				Jeff

-- 
Work email - jdike at linux dot intel dot com

  reply	other threads:[~2007-06-11 17:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-10 22:01 [PATCH 1/1] UML: fix missing non-blocking I/O, now DEBUG_SHIRQ works Eduard-Gabriel Munteanu
2007-06-11 17:31 ` Jeff Dike [this message]
2007-06-11 19:39   ` Eduard-Gabriel Munteanu
2007-06-11 21:16     ` Jeff Dike
2007-06-11 22:39       ` Eduard-Gabriel Munteanu
2007-06-12  0:48         ` Jeff Dike
2007-06-12  5:44           ` Eduard-Gabriel Munteanu
2007-06-12 13:26             ` Jeff Dike
  -- strict thread matches above, loose matches on Subject: below --
2007-06-10 22:20 Eduard-Gabriel Munteanu
2007-06-11 10:26 ` Eduard-Gabriel Munteanu

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=20070611173154.GA6889@c2.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxdamage@aladin.ro \
    /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