From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Fajun Chen <fajunchen@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Mark Lord <liml@rtr.ca>, Tejun Heo <htejun@gmail.com>
Subject: Re: PATA Sil680 Disabling IRQ
Date: Fri, 29 Feb 2008 11:21:59 +0000 [thread overview]
Message-ID: <20080229112159.2e5adbd1@core> (raw)
In-Reply-To: <8202f4270802281707g6fb80dc4i6a8015cdd13035ec@mail.gmail.com>
> I agree with you and Jeff that we can not prevent superuser from
> corrupting the system. What I want to understand more is if there's
> room to harden PATA PIO code in libata. For instance, when I set
> wrong data transfer direction in DMA read, I got command timeout,
> which to me is a more graceful failure than IRQ disabling. I'm not
> sure if the difference of failure mode between PIO and DMA is caused
> by controller or software. If the cause is software, it would be
> nice to close the gap.
Its almost impossible to tell - I can't duplicate the case you see. When
I issue wrong commands I see the expected timeout/fail. It may be that
Tejun's drain patches for the PIO fifo are going to help in your case I
don't know. Nothing obvious in the SIL680 docs hit me
prev parent reply other threads:[~2008-02-29 11:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 0:47 PATA Sil680 Disabling IRQ Fajun Chen
2008-02-27 0:58 ` Jeff Garzik
2008-02-28 0:20 ` Fajun Chen
2008-02-28 20:22 ` Alan Cox
2008-02-28 22:11 ` Fajun Chen
2008-02-28 22:24 ` Jeff Garzik
2008-02-28 23:10 ` Alan Cox
2008-02-29 1:07 ` Fajun Chen
2008-02-29 11:21 ` Alan Cox [this message]
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=20080229112159.2e5adbd1@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=fajunchen@gmail.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-ide@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.