From: Tejun Heo <tj@kernel.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Phillip Susi <psusi@cfl.rr.com>,
Ben Hutchings <ben@decadent.org.uk>,
Jeff Garzik <jgarzik@redhat.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: libata: implement on-demand HPA unlocking
Date: Wed, 9 Feb 2011 16:36:01 +0100 [thread overview]
Message-ID: <20110209153601.GJ3770@htj.dyndns.org> (raw)
In-Reply-To: <20110209153714.558133d7@lxorguk.ukuu.org.uk>
On Wed, Feb 09, 2011 at 03:37:14PM +0000, Alan Cox wrote:
> Probably the fakeraid layers need a way to see the geometry reported
> before unlock, then they can make their own decisions. The lock/unlock in
> hardware is just a hardware hack. We can still do the unlocking of
> hardware and using whatever values we choose in software at different
> points.
>
> "Should we unlock" is almost an academic debate given we are the OS and
> control the commands sent to the drive anyway.
Agreed. We're screwed whether we unlock or leave it alone. I think
the best way is to export the original size via sysfs and always
unlock and let dmraid and whatever stuff which expects metadata at the
end use the bios size. I seem to recall actually implementing it.
Wondering where it went....
--
tejun
next prev parent reply other threads:[~2011-02-09 15:36 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 20:23 libata: implement on-demand HPA unlocking Phillip Susi
2011-02-09 8:59 ` Tejun Heo
2011-02-09 15:20 ` Phillip Susi
2011-02-09 15:37 ` Alan Cox
2011-02-09 15:36 ` Tejun Heo [this message]
2011-02-09 18:48 ` Jeff Garzik
2011-02-09 19:45 ` Phillip Susi
2011-02-10 9:44 ` Tejun Heo
2011-02-10 18:47 ` Phillip Susi
2011-02-10 19:07 ` Tejun Heo
2011-02-09 19:39 ` Phillip Susi
2011-02-09 19:36 ` Phillip Susi
2011-02-09 20:47 ` Greg Freemyer
2011-02-09 21:12 ` Phillip Susi
2011-02-09 21:13 ` Alan Cox
2011-02-09 21:28 ` Phillip Susi
2011-02-09 21:39 ` Alan Cox
2011-02-10 0:23 ` Phillip Susi
2011-02-10 12:46 ` Alan Cox
2011-02-10 18:58 ` Phillip Susi
2011-02-10 19:19 ` Tejun Heo
2011-02-11 18:16 ` Phillip Susi
2011-02-10 12:49 ` Bartlomiej Zolnierkiewicz
2011-02-10 19:20 ` Phillip Susi
2011-02-10 19:35 ` Alan Cox
2011-02-11 18:22 ` Phillip Susi
2011-02-10 19:37 ` Alan Cox
2011-02-09 21:41 ` Tejun Heo
2011-02-10 0:35 ` Phillip Susi
2011-02-10 1:46 ` Robert Hancock
2011-02-10 9:13 ` Tejun Heo
2011-02-10 19:11 ` Phillip Susi
2011-02-10 19:31 ` Alan Cox
2011-02-11 18:18 ` Phillip Susi
2011-02-11 18:25 ` Alan Cox
2011-02-11 18:38 ` Phillip Susi
2011-02-10 19:32 ` Tejun Heo
2011-02-10 19:34 ` Tejun Heo
2011-02-11 18:30 ` Phillip Susi
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=20110209153601.GJ3770@htj.dyndns.org \
--to=tj@kernel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ben@decadent.org.uk \
--cc=jgarzik@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=psusi@cfl.rr.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 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.