Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dennis Dalessandro <dennis.dalessandro@intel.com>
Cc: dledford@redhat.com, linux-rdma@vger.kernel.org,
	"Michael J. Ruhl" <michael.j.ruhl@intel.com>,
	Mike Marciniszyn <mike.marciniszyn@intel.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH for-rc] IB/hfi: Only read capability registers if the capability exists
Date: Fri, 22 Dec 2017 09:53:52 -0700	[thread overview]
Message-ID: <20171222165352.GD30884@ziepe.ca> (raw)
In-Reply-To: <20171222164717.31842.12554.stgit@scvm10.sc.intel.com>

On Fri, Dec 22, 2017 at 08:47:20AM -0800, Dennis Dalessandro wrote:
> From: Michael J. Ruhl <michael.j.ruhl@intel.com>
> 
> During driver init, various registers are saved to allow restoration
> after an FLR or gen3 bump.  Some of these registers are not available
> in some circumstances (i.e. Virtual machines).
> 
> Delete unnecessary register read/write, and only access register if
> the capability exists.
> 
> Cc: <stable@vger.kernel.org> # 4.14.x
> Fixes: a618b7e40af2 ("IB/hfi1: Move saving PCI values to a separate function")
> Reviewed-by: Mike Marciniszyn <mike.marciniszyn@intel.com>
> Signed-off-by: Michael J. Ruhl <michael.j.ruhl@intel.com>
> Signed-off-by: Dennis Dalessandro <dennis.dalessandro@intel.com>
>  drivers/infiniband/hw/hfi1/hfi.h  |    1 -
>  drivers/infiniband/hw/hfi1/pcie.c |   30 ++++++++++++------------------
>  2 files changed, 12 insertions(+), 19 deletions(-)

Since we are getting late in the RC cycle can you help me clarify the
user visible bug here? No need to resend

I'm guessing when hfi1 is used in a virtual machine with passthrough
(SRIOV?) it fails in ?? way?

Jason

  reply	other threads:[~2017-12-22 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22 16:47 [PATCH for-rc] IB/hfi: Only read capability registers if the capability exists Dennis Dalessandro
2017-12-22 16:53 ` Jason Gunthorpe [this message]
2017-12-22 17:11   ` Dennis Dalessandro

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=20171222165352.GD30884@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=dennis.dalessandro@intel.com \
    --cc=dledford@redhat.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=michael.j.ruhl@intel.com \
    --cc=mike.marciniszyn@intel.com \
    --cc=stable@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