From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Finn Thain <fthain@telegraphics.com.au>,
"Song Bao Hua (Barry Song)" <song.bao.hua@hisilicon.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"funaho@jurai.org" <funaho@jurai.org>,
"philb@gnu.org" <philb@gnu.org>,
"corbet@lwn.net" <corbet@lwn.net>,
"mingo@redhat.com" <mingo@redhat.com>,
"linux-m68k@lists.linux-m68k.org"
<linux-m68k@lists.linux-m68k.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] IRQ handlers run with some high-priority interrupts(not NMI) enabled on some platform
Date: Thu, 18 Feb 2021 16:38:40 +0100 [thread overview]
Message-ID: <CAMuHMdVD+BhxXcmZYvVK5QgtNsmbgyzS_Yx+dbFYmN8xdw0kDA@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a08y3pH6OGtPnPs_HMHRh0Q8xnKr40Lt=vMCW6T1yjz6w@mail.gmail.com>
Hi Arnd,
On Thu, Feb 18, 2021 at 2:59 PM Arnd Bergmann <arnd@kernel.org> wrote:
> On Thu, Feb 18, 2021 at 1:30 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > The reason drivers/ide is doing that may be related to IDE hard drive
> > quirks. The old WD Caviar drives didn't obey disabling the IDE interrupt
> > at the drive level. On PC, that worked fine, as IRQs 14 and 15 weren't
> > shared with other devices. On systems with shared interrupts, that
> > broke badly, and led to an interrupt storm.
>
> So presumably anyone that has one of those old drives will not be
> able to move to drivers/ata then? I see that drivers/ata doesn't do
> the transfers in interrupt mode, so it would seem to rely on masking
> at the device level.
I don't know. This was an issue I debugged on a friend's Amiga in 1995
or so ;-) All bad WD Caviars may have died in the meantime...
BTW, it wouldn't be the first time a drive quirk handling wasn't ported
from drivers/ide/ to drivers/ata/.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2021-02-18 18:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 1:18 [RFC] IRQ handlers run with some high-priority interrupts(not NMI) enabled on some platform Song Bao Hua (Barry Song)
2021-02-12 22:34 ` Arnd Bergmann
2021-02-12 23:00 ` Song Bao Hua (Barry Song)
2021-02-12 23:05 ` Arnd Bergmann
2021-02-12 23:46 ` Song Bao Hua (Barry Song)
2021-02-13 16:32 ` Arnd Bergmann
2021-02-13 22:18 ` Song Bao Hua (Barry Song)
2021-02-13 23:18 ` Song Bao Hua (Barry Song)
2021-02-14 5:10 ` Finn Thain
2021-02-15 13:06 ` Andy Shevchenko
2021-02-15 22:22 ` Finn Thain
2021-02-17 22:41 ` Song Bao Hua (Barry Song)
2021-02-18 5:30 ` Finn Thain
2021-02-18 11:19 ` Arnd Bergmann
2021-02-18 12:30 ` Geert Uytterhoeven
2021-02-18 13:59 ` Arnd Bergmann
2021-02-18 15:38 ` Geert Uytterhoeven [this message]
2021-02-18 22:11 ` Michael Schmitz
2021-02-19 8:10 ` Geert Uytterhoeven
2021-02-19 22:30 ` Brad Boyer
2021-02-20 6:32 ` Finn Thain
2021-02-20 7:08 ` Brad Boyer
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=CAMuHMdVD+BhxXcmZYvVK5QgtNsmbgyzS_Yx+dbFYmN8xdw0kDA@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=corbet@lwn.net \
--cc=fthain@telegraphics.com.au \
--cc=funaho@jurai.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=mingo@redhat.com \
--cc=philb@gnu.org \
--cc=song.bao.hua@hisilicon.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;
as well as URLs for NNTP newsgroup(s).