From: Tejun Heo <tj@kernel.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
"Zhao, Richard" <Richard.Zhao@amd.com>,
shane.huang@amd.com
Subject: Re: [PATCH RFC] ahci: implement handoff quirk
Date: Tue, 14 Apr 2009 18:16:16 +0900 [thread overview]
Message-ID: <49E45460.8010809@kernel.org> (raw)
In-Reply-To: <49E0DB1E.8070701@garzik.org>
Jeff Garzik wrote:
> Tejun Heo wrote:
>> Jeff Garzik wrote:
>>> We probably need to do this...
>>>
>>> it's not a controller requirement but a BIOS one, so in theory even an
>>> existing, deployed AHCI 1.2 platform could suddenly require BIOS/OS
>>> handoff, if a BIOS update suddenly starts doing new and weird stuff
>>> in SMI.
>>>
>>> Note that we need to do BIOS/OS handoff upon resume as well as at boot
>>> time.
>>
>> Yeah, probably. Do you know of any system which makes use of this
>> feature? I'm a bit uneasy about committing it without any testing.
>
> I don't.
>
> But the purpose of the feature is to tell BIOS to cleanup and stop using
> the hardware. It's a dumb feature, because of compatibility realities,
> but hey, other network and SCSI drivers have been doing this sort of
> synchronization with their on-board firmwares for years.
>
> IMO the more dangerous route is to continue loading ahci, without first
> telling the BIOS to clean up and get out of our way.
Hmmm.... yeah, I'm just worried a bit about adding a chunk of
completely untested code. How about adding a big fat warning message
which gets triggered if the handoff thing seems to be active?
Thanks.
--
tejun
next prev parent reply other threads:[~2009-04-14 9:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 3:37 [PATCH RFC] ahci: implement handoff quirk Tejun Heo
2009-04-11 16:54 ` Jeff Garzik
2009-04-11 17:51 ` Tejun Heo
2009-04-11 18:02 ` Jeff Garzik
2009-04-14 9:16 ` Tejun Heo [this message]
2009-04-14 9:41 ` Jeff Garzik
2009-04-15 1:54 ` Huang, Shane
2009-12-17 6:34 ` Jeff Garzik
2009-12-18 3:54 ` Robert Hancock
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=49E45460.8010809@kernel.org \
--to=tj@kernel.org \
--cc=Richard.Zhao@amd.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=shane.huang@amd.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).