All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <keith.busch@intel.com>
To: Alex_Gagniuc@Dellteam.com
Cc: helgaas@kernel.org, oohall@gmail.com, gregkh@linuxfoundation.org,
	mr.nuke.me@gmail.com, linux-pci@vger.kernel.org,
	Austin.Bolen@dell.com, Shyam.Iyer@dell.com,
	linux-kernel@vger.kernel.org, jonathan.derrick@intel.com,
	lukas@wunner.de, ruscur@russell.cc, sbobroff@linux.ibm.com,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] PCI/MSI: Don't touch MSI bits when the PCI device is disconnected
Date: Wed, 14 Nov 2018 13:58:55 -0700	[thread overview]
Message-ID: <20181114205855.GF11416@localhost.localdomain> (raw)
In-Reply-To: <644fd16cf02c4fe5b7e250c226c80f2e@ausx13mps321.AMER.DELL.COM>

On Wed, Nov 14, 2018 at 08:52:10PM +0000, Alex_Gagniuc@Dellteam.com wrote:
> But it does in portdrv_core.c:
> 
> 	if (dev->aer_cap && pci_aer_available() &&
> 	    (pcie_ports_native || host->native_aer)) {
> 		services |= PCIE_PORT_SERVICE_AER;
> 
> That flag later creates a pcie device that allows aerdrv to attach to.

Oh, right. I saw negotiate_os_control() just uses a stack variable for
the _OSC response, but if I had looked one level deeper, I'd see it
cached in a different structure.

WARNING: multiple messages have this Message-ID (diff)
From: Keith Busch <keith.busch@intel.com>
To: Alex_Gagniuc@Dellteam.com
Cc: gregkh@linuxfoundation.org, sbobroff@linux.ibm.com,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shyam.Iyer@dell.com, lukas@wunner.de, oohall@gmail.com,
	mr.nuke.me@gmail.com, Austin.Bolen@dell.com, helgaas@kernel.org,
	linuxppc-dev@lists.ozlabs.org, jonathan.derrick@intel.com
Subject: Re: [PATCH v2] PCI/MSI: Don't touch MSI bits when the PCI device is disconnected
Date: Wed, 14 Nov 2018 13:58:55 -0700	[thread overview]
Message-ID: <20181114205855.GF11416@localhost.localdomain> (raw)
In-Reply-To: <644fd16cf02c4fe5b7e250c226c80f2e@ausx13mps321.AMER.DELL.COM>

On Wed, Nov 14, 2018 at 08:52:10PM +0000, Alex_Gagniuc@Dellteam.com wrote:
> But it does in portdrv_core.c:
> 
> 	if (dev->aer_cap && pci_aer_available() &&
> 	    (pcie_ports_native || host->native_aer)) {
> 		services |= PCIE_PORT_SERVICE_AER;
> 
> That flag later creates a pcie device that allows aerdrv to attach to.

Oh, right. I saw negotiate_os_control() just uses a stack variable for
the _OSC response, but if I had looked one level deeper, I'd see it
cached in a different structure.

  reply	other threads:[~2018-11-14 21:02 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-18 22:15 [PATCH v2] PCI/MSI: Don't touch MSI bits when the PCI device is disconnected Alexandru Gagniuc
2018-11-06  0:32 ` Alex G.
2018-11-07 17:04   ` Derrick, Jonathan
2018-11-07 23:42 ` Bjorn Helgaas
2018-11-08 20:09   ` Bjorn Helgaas
2018-11-08 20:09     ` Bjorn Helgaas
2018-11-08 21:49     ` Keith Busch
2018-11-08 21:49       ` Keith Busch
2018-11-08 22:01     ` Greg Kroah-Hartman
2018-11-08 22:01       ` Greg Kroah-Hartman
2018-11-08 22:32       ` Keith Busch
2018-11-08 22:32         ` Keith Busch
2018-11-08 22:42         ` Greg Kroah-Hartman
2018-11-08 22:42           ` Greg Kroah-Hartman
2018-11-08 22:49           ` Alex_Gagniuc
2018-11-08 22:49             ` Alex_Gagniuc
2018-11-08 22:51             ` Greg KH
2018-11-08 22:51               ` Greg KH
2018-11-08 23:06               ` Alex_Gagniuc
2018-11-08 23:06                 ` Alex_Gagniuc
2018-11-12  5:49                 ` Oliver O'Halloran
2018-11-12  5:49                   ` Oliver O'Halloran
2018-11-12 20:05                   ` Alex_Gagniuc
2018-11-12 20:05                     ` Alex_Gagniuc
2018-11-13  5:02                     ` Bjorn Helgaas
2018-11-13  5:02                       ` Bjorn Helgaas
2018-11-13 22:39                       ` Alex_Gagniuc
2018-11-13 22:39                         ` Alex_Gagniuc
2018-11-13 22:52                         ` Keith Busch
2018-11-13 22:52                           ` Keith Busch
2018-11-14  0:31                           ` Alex_Gagniuc
2018-11-14  0:31                             ` Alex_Gagniuc
2018-11-14  5:59                         ` Bjorn Helgaas
2018-11-14  5:59                           ` Bjorn Helgaas
2018-11-14 19:22                           ` Alex_Gagniuc
2018-11-14 19:22                             ` Alex_Gagniuc
2018-11-14 19:41                             ` Derrick, Jonathan
2018-11-14 19:41                               ` Derrick, Jonathan
2018-11-14 20:23                             ` Keith Busch
2018-11-14 20:23                               ` Keith Busch
2018-11-14 20:52                               ` Alex_Gagniuc
2018-11-14 20:52                                 ` Alex_Gagniuc
2018-11-14 20:58                                 ` Keith Busch [this message]
2018-11-14 20:58                                   ` Keith Busch
2018-11-15  6:24                             ` Bjorn Helgaas
2018-11-15  6:24                               ` Bjorn Helgaas
2018-11-16  0:19                               ` Alex_Gagniuc
2018-11-16  0:19                                 ` Alex_Gagniuc
2018-11-08 23:03           ` Keith Busch
2018-11-08 23:03             ` Keith Busch
2018-11-09  7:29       ` Lukas Wunner
2018-11-09 11:32         ` Greg Kroah-Hartman
2018-11-09 11:32           ` Greg Kroah-Hartman
2018-11-09 16:36           ` Keith Busch
2018-11-09 16:36             ` Keith Busch
2018-11-08 22:20     ` Alex_Gagniuc
2018-11-08 22:20       ` Alex_Gagniuc
2018-11-09  7:11     ` Lukas Wunner
2018-11-12  5:48       ` Oliver O'Halloran
2018-11-12  5:48         ` Oliver O'Halloran
2018-12-27 19:28     ` Alex_Gagniuc
2018-12-27 19:28       ` Alex_Gagniuc

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=20181114205855.GF11416@localhost.localdomain \
    --to=keith.busch@intel.com \
    --cc=Alex_Gagniuc@Dellteam.com \
    --cc=Austin.Bolen@dell.com \
    --cc=Shyam.Iyer@dell.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=helgaas@kernel.org \
    --cc=jonathan.derrick@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lukas@wunner.de \
    --cc=mr.nuke.me@gmail.com \
    --cc=oohall@gmail.com \
    --cc=ruscur@russell.cc \
    --cc=sbobroff@linux.ibm.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 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.