From: Tejun Heo <htejun@gmail.com>
To: Tejun Heo <htejun@gmail.com>
Cc: jgarzik@pobox.com, lkml@rtr.ca, axboe@suse.de,
forrest.zhao@intel.com, alan@lxorguk.ukuu.org.uk,
linux-ide@vger.kernel.org
Subject: Re: [RFT][PATCHSET] hotplug polling
Date: Wed, 05 Jul 2006 05:28:01 +0900 [thread overview]
Message-ID: <44AACF51.7070204@gmail.com> (raw)
In-Reply-To: <11520225771424-git-send-email-htejun@gmail.com>
Tejun Heo wrote:
> Well, the port-exclusive case is dumb but understandable; however,
> sata_via (vt8237) takes it to the next level and may lock up if any
> available port in the host_set is active when a SCR reg is accessed,
> so it needs host_set-exclusive version. It took me two days of
> boredom to figure out that things can be made THAT dumb. Their new
> AHCI controller also seems to require host_set-wide EH ops to recover
> from errors. Well, I guess they consider requiring host_set-wide ops
> a feature or something. :-( Note that this means that the current
> libata EH may lock up the whole machine on vt8237 if EH occurs at a
> bad time.
Update: vt8237 failed to survive over-night test. It died even with
host_set-wide exclusion. I'm dropping hp-poll support from sata_via.
--
tejun
prev parent reply other threads:[~2006-07-04 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 14:16 [RFT][PATCHSET] hotplug polling Tejun Heo
2006-07-04 14:16 ` [PATCH 1/3] libata: implement hotplug by polling Tejun Heo
2006-07-04 14:16 ` [PATCH 2/3] libata: add hp-poll support to controllers with hotplug interrutps Tejun Heo
2006-07-04 14:16 ` [PATCH 3/3] libata: add hp-poll support to controllers without hotplug interrupts Tejun Heo
2006-07-04 20:28 ` Tejun Heo [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=44AACF51.7070204@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=forrest.zhao@intel.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=lkml@rtr.ca \
/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).