public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcin Dalecki <dalecki@evision.ag>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
	Bill Davidsen <davidsen@tmr.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Safety of IRQ during i/o
Date: Thu, 25 Jul 2002 09:54:25 +0200	[thread overview]
Message-ID: <3D3FAEB1.6070704@evision.ag> (raw)
In-Reply-To: Pine.SOL.4.30.0207250041400.15959-100000@mion.elka.pw.edu.pl

Bartlomiej Zolnierkiewicz wrote:
> On Wed, 24 Jul 2002, Pete Zaitcev wrote:
> 
> 
>>>[...]
>>>I would think that this would be safe when using DMA, and likely to be
>>>safe for PIO and more recent chipsets, but I wouldn't want to actually
>>>tell anyone that.
>>
>>A little story from OLS. I have a 486/75 laptop, which can only
>>do PIO. It always was losing characters evern on 9600 baud on its
>>serial port, and I thought it was simply broken for five years.
> 
> 
> :-)
> 
> 
>>A guy who did a security talk showed me that doing hdparm -u
>>fixes the problem. Apparently, the lappy has a non-buffering UART.
>>
>>So, it seems that hdparm -u is a very useful thing for obsotele
>>boxes. If you do DMA, you probably do not care.
> 
> 
> Yup, for PIO unmask (if possible) is a must.

It's even for DMA a good thing, since the IRQ handler in question can
reenter the RQ handler. The invention of the not unmasking
behaviour in Linux is the result of some not entierly ATA-2 compliant
devices long long time ago gone. Basically XT disks on PC. They did have 
the habbit of splewing IRQs too early for command ACK.


  reply	other threads:[~2002-07-25  7:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1027541521.16533.linux-kernel2news@redhat.com>
2002-07-24 22:37 ` Safety of IRQ during i/o Pete Zaitcev
2002-07-24 22:42   ` Bartlomiej Zolnierkiewicz
2002-07-25  7:54     ` Marcin Dalecki [this message]
2002-07-25 10:26       ` Alan Cox
2002-07-25  9:34         ` Marcin Dalecki
2002-07-25 11:15           ` Roger Larsson
2002-07-25 11:17         ` Bill Davidsen
2002-07-26  0:34           ` Marcin Dalecki
2002-07-24 19:58 Bill Davidsen

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=3D3FAEB1.6070704@evision.ag \
    --to=dalecki@evision.ag \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@dalecki.de \
    --cc=zaitcev@redhat.com \
    /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