From: Tejun Heo <tj@kernel.org>
To: Tim Small <tim@buttersideup.com>
Cc: linux-ide@vger.kernel.org, kristen.c.accardi@intel.com
Subject: Re: AHCI link power management and surprise hotplug
Date: Fri, 20 Mar 2009 10:56:26 +0900 [thread overview]
Message-ID: <49C2F7CA.6090908@kernel.org> (raw)
In-Reply-To: <49C22689.9050005@buttersideup.com>
Hello,
Tim Small wrote:
> "
> For reliable device removal notification while in AHCI operation without
> the use of interlock switches (surprise removal), interface power
> management should be disabled for the associated port. See Section 7.3.1
> of the AHCI Specification for more information.
> "
>
> Is this actually an issue from a libata point of view? Do I need to
> ensure that link power management is disabled prior to hot-removal, and
> if so, I suppose link_power_management_policy.txt should be updated to
> reflect this...
Yeap, libata wouldn't know the device is yanked out. It will find out
later when it tries to issue a command later tho. It could be a
problem if you hot-swap the drive. libata wouldn't know that devices
have been exchanged.
> On a related topic, is there any way to do anything other than
> "surprise" removal with libata? It'd be nice to put a drive to sleep
> (e.g. with "hdparm -Y"), and ensure that nothing comes along and causes
> the drive to be reset and spin the drive attached to that SATA port back
> up prior to a removal and reinsertion.
echo 1 > /sys/block/sdX/device/delete
> I'm assuming that physically unplugging a non-spinning drive is
> preferable to unplugging a spinning one from a drive longevity point of
> view (I use SATA drives as removable backup medium in some cases).
Yeah, you'll induce an emergency unload if you remove power while the
drive is spinning, but drives are designed to deal with certain number
of those events and if it doesn't happen regularly, you don't need to
worry about it.
Thanks.
--
tejun
next prev parent reply other threads:[~2009-03-20 1:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 11:03 AHCI link power management and surprise hotplug Tim Small
2009-03-19 18:06 ` Jeff Garzik
2009-03-20 1:56 ` Tejun Heo [this message]
2009-03-20 17:42 ` Kristen Carlson Accardi
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=49C2F7CA.6090908@kernel.org \
--to=tj@kernel.org \
--cc=kristen.c.accardi@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=tim@buttersideup.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;
as well as URLs for NNTP newsgroup(s).