From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Frans Pop <elendil@planet.nl>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] ide: add "ignore_hpa" module parameter
Date: Mon, 25 May 2009 23:36:43 +0100 [thread overview]
Message-ID: <20090525233643.0a47e950@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <200905260027.39330.elendil@planet.nl>
> It's also not obvious (at least not to a dumb user like me) that "ignore
> HPA limit" is equivalent to "preserving the Host Protected Area" as the
> commit commit says.
It isn't - its the exact reverse.
Ignoring the HPA limit tells the kernel to ignore the system BIOS and
firmware set defaults and to stomp the whole disk regardless. On a modern
system thats almost always a really bad idea. Unfortunately on ancient
boxes with disk jumpers set to lie about the disk size (32GB clipping
etc) its the right thing.
Having the same parameter in both stacks seems a good idea but really we
need Tejun's patch exposing the values and then to propogate the hpa
ignore into sysfs and trigger a revalidate of the disk if you change it.
Libata has all the framework for that ready just needing the final bits.
I don't see anything problematic in old IDE also having that interface.
next prev parent reply other threads:[~2009-05-25 22:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 21:44 Bartlomiej Zolnierkiewicz
2009-05-25 22:27 ` Frans Pop
2009-05-25 22:36 ` Alan Cox [this message]
2009-05-25 23:06 ` Frans Pop
2009-05-26 12:23 ` Bartlomiej Zolnierkiewicz
2009-05-26 12:53 ` Frans Pop
2009-05-26 13:01 ` Alan Cox
2009-05-26 18:08 ` Andries E. Brouwer
2009-05-27 9:49 ` Alan Cox
2009-05-26 17:32 ` Bartlomiej Zolnierkiewicz
2009-05-26 23:49 ` Robert Hancock
2009-05-26 12:53 ` Alan Cox
2009-05-26 17:15 ` Bartlomiej Zolnierkiewicz
2009-05-27 10:38 ` Alan Cox
2009-05-27 11:41 ` Bartlomiej Zolnierkiewicz
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=20090525233643.0a47e950@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=elendil@planet.nl \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®