From: Jens Axboe <axboe@kernel.dk>
To: Stephen Cameron <smcameron@yahoo.com>
Cc: "Stephen M. Cameron" <scameron@beardog.cce.hp.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
mike.miller@hp.com, thenzl@redhat.com
Subject: Re: [PATCH 3/5] cciss: Use kernel provided PCI state save and restore functions
Date: Fri, 22 Oct 2010 21:49:32 +0200 [thread overview]
Message-ID: <4CC1EACC.9040500@kernel.dk> (raw)
In-Reply-To: <402956.74986.qm@web33003.mail.mud.yahoo.com>
On 2010-10-22 21:36, Stephen Cameron wrote:
> --- On Fri, 10/22/10, Stephen M. Cameron <scameron@beardog.cce.hp.com> wrote:
>
>> From: Stephen M. Cameron <scameron@beardog.cce.hp.com>
>> Subject: [PATCH 3/5] cciss: Use kernel provided PCI state save and restore functions
>> To: axboe@kernel.dk
>> Cc: akpm@linux-foundation.org, smcameron@yahoo.com, linux-kernel@vger.kernel.org, mike.miller@hp.com, thenzl@redhat.com
>> Date: Friday, October 22, 2010, 2:21 PM
>> From: Stephen M. Cameron <scameron@beardog.cce.hp.com>
>>
>> and use the doorbell reset method if available (which doesn't
>> lock up the controller if you properly save and restore
>> all the PCI registers that you're supposed to.)
>
>
> This patch, and all these cciss patches in this series, are vs. the jens/for-2.6.37/drivers branch.
>
> One difference I noticed between linux-2.6.36 and jens/for-2.6.37/drivers is that linux-2.6.36 contains this in drivers/block/cciss.c
> in the function cciss_kdump_hard_reset_controller:
>
> /* The doorbell reset seems to cause lockups on some Smart
> * Arrays (e.g. P410, P410i, maybe others). Until this is
> * fixed or at least isolated, avoid the doorbell reset.
> */
> use_doorbell = 0;
>
> This is not present in jens/for-2.6.37/drivers.
>
> That was added to linus tree by me, because I'd noticed we were
> getting controller lockups and subsequent data corruption when
> attempting kdumps using the doorbell reset when (unbeknownst to me at
> the time) the pci state saving and restoring code wasn't quite right.
> So these patches fix the pci state saving and restoring code, so the
> above "use_doorbell = 0" needs to come out when these patches go into
> Linus's tree. But such a patch cannot be made vs. Jens's tree,
> because that code isn't in Jens's tree.
I sent a pull request to Linus earlier today and I know the drivers
branch merges cleanly into -git, so we should be fine.
I'll get this series queued up as well, but it'll be for a later round
early next week. JFYI.
--
Jens Axboe
next prev parent reply other threads:[~2010-10-22 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 19:20 [PATCH 0/5] cciss updates, PCI ID changes, kdump reset fixes Stephen M. Cameron
2010-10-22 19:21 ` [PATCH 1/5] cciss: remove controllers supported by hpsa Stephen M. Cameron
2010-10-22 19:46 ` Bruno Prémont
2010-10-22 19:21 ` [PATCH 2/5] cciss: fix board status waiting code Stephen M. Cameron
2010-10-22 19:21 ` [PATCH 3/5] cciss: Use kernel provided PCI state save and restore functions Stephen M. Cameron
2010-10-22 19:36 ` Stephen Cameron
2010-10-22 19:49 ` Jens Axboe [this message]
2010-10-22 19:21 ` [PATCH 4/5] cciss: limit commands allocated on reset_devices Stephen M. Cameron
2010-10-22 19:21 ` [PATCH 5/5] cciss: use usleep_range not msleep for small sleeps Stephen M. Cameron
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=4CC1EACC.9040500@kernel.dk \
--to=axboe@kernel.dk \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.miller@hp.com \
--cc=scameron@beardog.cce.hp.com \
--cc=smcameron@yahoo.com \
--cc=thenzl@redhat.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