linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@redhat.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, alex.williamson@redhat.com,
	darcari@redhat.com, mstowe@redhat.com, bhelgaas@google.com,
	lukas@wunner.de, keith.busch@intel.com,
	mika.westerberg@linux.intel.com
Subject: Re: [PATCH] pci: Only disable MSI/X and enable INTx if shutdown function has been called
Date: Wed, 25 Jan 2017 08:23:21 -0500	[thread overview]
Message-ID: <5888A6C9.6010708@redhat.com> (raw)
In-Reply-To: <20170119143804.GB12124@bhelgaas-glaptop.roam.corp.google.com>



On 01/19/2017 09:38 AM, Bjorn Helgaas wrote:
> On Fri, Dec 16, 2016 at 11:48:06AM -0500, Prarit Bhargava wrote:
>> On 11/09/2016 12:05 PM, Bjorn Helgaas wrote:
>>> Hi Prarit,
>>>
>>> Is there a bugzilla or other archive of configuration/dmesg/other info
>>> related to this problem?  I'd really like to connect this fix to a
>>> problem report, and it would help me review the patch as well.
>>
>> Bjorn, have you had a chance to look at this?
>>
>> I had opened
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=187351
> 
> Hi Prarit,
> 
> Sorry, I've not had a chance to dig into this yet.  What I'd *like* to do
> is figure out what the kexec/kdump/shutdown strategy really is and make
> sure this is all coherent.  It seems like we've gone back and forth on this
> a couple times because this or that is broken, but I don't really
> understand why.
> 

Bjorn,

Let me start from the beginning with a new patch and explanation.  I think
that as time went on, some of the details and explanation were lost ...

I'll post a v2 shortly.

P.

  reply	other threads:[~2017-01-25 13:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-08 17:57 [PATCH] pci: Only disable MSI/X and enable INTx if shutdown function has been called Prarit Bhargava
2016-11-09 17:05 ` Bjorn Helgaas
2016-11-09 19:36   ` Prarit Bhargava
2016-11-09 19:54     ` Keith Busch
2016-11-09 19:49       ` Prarit Bhargava
2016-12-16 16:48   ` Prarit Bhargava
2017-01-19 14:38     ` Bjorn Helgaas
2017-01-25 13:23       ` Prarit Bhargava [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-01-26 19:07 Prarit Bhargava
2017-03-09 21:57 ` Bjorn Helgaas
2017-03-10 12:30   ` Prarit Bhargava
2017-03-30 11:59     ` Prarit Bhargava
2017-03-30 21:52       ` Bjorn Helgaas

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=5888A6C9.6010708@redhat.com \
    --to=prarit@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=darcari@redhat.com \
    --cc=helgaas@kernel.org \
    --cc=keith.busch@intel.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=mika.westerberg@linux.intel.com \
    --cc=mstowe@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;
as well as URLs for NNTP newsgroup(s).