All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduard-Gabriel Munteanu <maxdamage@aladin.ro>
To: Jeff Dike <jdike@addtoit.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] UML - Console should handle spurious IRQS
Date: Sun, 29 Jul 2007 03:50:59 +0300	[thread overview]
Message-ID: <46ABE473.2030507@aladin.ro> (raw)
In-Reply-To: <20070727152344.GA6776@c2.user-mode-linux.org>

*This message was transferred with a trial version of CommuniGate(r) Pro*
Jeff Dike wrote:
> The previous DEBUG_SHIRQ patch missed one case.  The console doesn't
> set its host descriptors non-blocking.

Sorry, things looked okay when I tested on my UML environment (Puppy 
Linux). Some xterms popped around (because I was using "con=xterm") and 
the system was usable, so it gave me no indication something was wrong.

I thought of adding an extra debugging option to warn us when a blocking 
  I/O operation is issued for a socket/fd, but UML-specific code is not 
consistent regarding glibc functions. That is, most of the time it calls 
os_*(), but sometimes it calls functions like recvfrom() directly. I'll 
grep the source code for such calls and send a patch to clean it up a bit.

There might still be such cases, I haven't tested all channel types yet.

  reply	other threads:[~2007-07-29  1:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27 15:23 [uml-devel] [PATCH] UML - Console should handle spurious IRQS Jeff Dike
2007-07-27 15:23 ` Jeff Dike
2007-07-29  0:50 ` Eduard-Gabriel Munteanu [this message]
2007-07-30 19:54   ` Jeff Dike

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=46ABE473.2030507@aladin.ro \
    --to=maxdamage@aladin.ro \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.