From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH v2] nvme/pci: Log PCI_STATUS when the controller dies
Date: Fri, 2 Dec 2016 05:26:00 -0800 [thread overview]
Message-ID: <20161202132600.GA2827@infradead.org> (raw)
In-Reply-To: <f028ad4073488a571f2e19e19ccff0f6daa4af33.1480639321.git.luto@kernel.org>
On Thu, Dec 01, 2016@04:42:41PM -0800, Andy Lutomirski wrote:
> When debugging nvme controller crashes, it's nice to know whether
> the controller died cleanly so that the failure is just reflected in
> CSTS, it died and put an error in PCI_STATUS, or whether it died so
> badly that it stopped responding to PCI configuration space reads.
Just curious: what controller did this happen with?
> + /* Read a config register to help see what died. */
> + u16 pci_status;
> + int result;
> +
> + result = pci_read_config_word(to_pci_dev(dev->dev),
> + PCI_STATUS, &pci_status);
> + if (result == PCIBIOS_SUCCESSFUL)
> + dev_warn(dev->dev,
> + "controller is down; will reset: CSTS=0x%x, PCI_STATUS=0x%hx\n",
> + csts, pci_status);
> + else
> + dev_warn(dev->dev,
> + "controller is down; will reset: CSTS=0x%x, PCI_STATUS read failed (%d)\n",
> + csts, result);
> + }
Can you factor all this debug code into a separate function to keep
the main flow easier to read?
Except for that this patch looks fine to me:
Reviewed-by: Christoph Hellwig <hch at lst.de>
next prev parent reply other threads:[~2016-12-02 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 0:42 [PATCH v2] nvme/pci: Log PCI_STATUS when the controller dies Andy Lutomirski
2016-12-02 13:26 ` Christoph Hellwig [this message]
2016-12-02 16:57 ` Andy Lutomirski
2016-12-02 22:19 ` J Freyensee
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=20161202132600.GA2827@infradead.org \
--to=hch@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.