From: Charles Chiou <ch1102chiou@gmail.com>
To: Christoph Hellwig <hch@infradead.org>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: JBottomley@parallels.com, linux-pm@vger.kernel.org
Subject: Re: [V2 PATCH 3/4] scsi:stex.c Add reboot support
Date: Fri, 14 Nov 2014 10:23:10 +0800 [thread overview]
Message-ID: <5465678E.3070604@gmail.com> (raw)
In-Reply-To: <546482FC.2090207@gmail.com>
On 11/13/2014 06:07 PM, Charles Chiou wrote:
>
>
> On 11/13/2014 01:27 AM, Christoph Hellwig wrote:
>>> +static int stex_reboot_callback(struct notifier_block *self,
>>> + unsigned long val,
>>> + void *data)
>>> +{
>>> + if (val == SYS_RESTART)
>>> + isRestart = 1;
>>> + return NOTIFY_OK;
>>> +}
>>>
>>> @@ -1832,7 +1859,14 @@ static void stex_shutdown(struct pci_dev *pdev)
>>> {
>>> struct st_hba *hba = pci_get_drvdata(pdev);
>>>
>>> - stex_hba_stop(hba);
>>> + if (hba->yellowstone == 1)
>>> + stex_hba_stop(hba, ST_IGNORED);
>>> + else {
>>> + if (isRestart)
>>> + stex_hba_stop(hba, ST_S6);
>>> + else
>>> + stex_hba_stop(hba, ST_S5);
>>> + }
>>
>> This sort of check for reboot vs restart isn't really something
>> we want in drivers. I don't really know how we could find this
>> out assuming we even want drivers to behave differently.
>>
>> Maybe Greg or someone on lkml has an idea how to best handle this case.
Hi, we don't attempt to check for restart vs reboot,
sorry for confusing. When host is going to restart/reboot, Pegasus need
to restart too. Pegasus use same flow for restart and reboot.
Maybe I could change variable name "isRestart" to "isReboot"?
next prev parent reply other threads:[~2014-11-14 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5462D62C.50602@gmail.com>
2014-11-12 17:27 ` [V2 PATCH 3/4] scsi:stex.c Add reboot support Christoph Hellwig
2014-11-13 10:07 ` Charles Chiou
2014-11-14 2:23 ` Charles Chiou [this message]
2014-11-15 1:03 ` Greg Kroah-Hartman
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=5465678E.3070604@gmail.com \
--to=ch1102chiou@gmail.com \
--cc=JBottomley@parallels.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).