From: Tejun Heo <tj@kernel.org>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: Jeff Garzik <jeff@garzik.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
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: Thu, 10 Feb 2011 10:44:40 +0100 [thread overview]
Message-ID: <20110210094440.GL3770@htj.dyndns.org> (raw)
In-Reply-To: <4D52EEEC.1020602@cfl.rr.com>
Hello,
On Wed, Feb 09, 2011 at 02:45:48PM -0500, Phillip Susi wrote:
> Then why did you have libata default to NOT unlocking it, which seems to
> be the correct thing to do? When Ubuntu switched to libata they patched
> it to default to unlocking the HPA because the old ide driver did. This
> seems wrong and causes breakage. Tejun's patch seems to be a good
> compromise between the two choices: unlock if you think it will help,
> otherwise, don't, since it might hurt.
I don't think that patch supports your argument to begin with but even
if it did don't get too hung up on the fact that I (or anyone else)
did something contrary in the past. I've done a lot of stupid and
horrible things and changed mind more times than anyone should care
about.
I thought it would be a good and safe compromise for distros which
don't want to unlock by default but look at where we are. We just
ended up with failures which are more obscure. Your proposed addition
will only push things further that direction. It might not
necessarily be a bad thing. Maybe the level of obscurity then goes
beyond certain level and we wouldn't have to care about that.
But much better solution seems to be exporting the bios size to others
and letting the ones which understand storage configuration better
deal with it. At the block or libata layer, we simply don't have
enough information to make those decisions in a reliable manner.
Thanks.
--
tejun
next prev parent reply other threads:[~2011-02-10 9:44 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
2011-02-09 18:48 ` Jeff Garzik
2011-02-09 19:45 ` Phillip Susi
2011-02-10 9:44 ` Tejun Heo [this message]
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=20110210094440.GL3770@htj.dyndns.org \
--to=tj@kernel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ben@decadent.org.uk \
--cc=jeff@garzik.org \
--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 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).