linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sinan Kaya <okaya@kernel.org>
To: Dennis Dalessandro <dennis.dalessandro@intel.com>,
	Alex Williamson <alex.williamson@redhat.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Linux PCI <linux-pci@vger.kernel.org>
Subject: Re: RFC on PCI Device Lock
Date: Tue, 4 Sep 2018 20:10:57 -0700	[thread overview]
Message-ID: <b85dab5a-62f0-78b0-0b7c-29af362784d9@kernel.org> (raw)
In-Reply-To: <3428a4e6-0095-3eb8-a6d2-c889e201ab98@intel.com>

On 9/4/2018 7:59 PM, Dennis Dalessandro wrote:
> It sounds like all that is being done is put a band-aid on things and there is 
> some redesign work needed. Perhaps the best thing to do is back this out for 
> 4.19 and revisit with a more general solution for 4.20. That's a call for you 
> folks to make. My concern is getting our HW functioning again with 4.19 and 
> Sinan's patch along with my 1/1 seems to allow that at least.

Alex proposed another solution. That looks better IMO.
I think we can close this issue shortly. We have not exhausted bug fixing window
unless Bjorn thinks otherwise.

I'll upload another patch to bugzilla soon.

      reply	other threads:[~2018-09-05  7:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31 23:03 RFC on PCI Device Lock Sinan Kaya
2018-09-04 22:52 ` Alex Williamson
2018-09-05  1:12   ` Sinan Kaya
2018-09-05  2:46     ` Alex Williamson
2018-09-05  3:09       ` Sinan Kaya
2018-09-05  3:41         ` Sinan Kaya
2018-09-05  4:13           ` Alex Williamson
2018-09-05 14:26             ` Sinan Kaya
2018-09-05 17:37               ` Alex Williamson
2018-09-05 17:50                 ` Sinan Kaya
2018-09-05  2:59   ` Dennis Dalessandro
2018-09-05  3:10     ` Sinan Kaya [this message]

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=b85dab5a-62f0-78b0-0b7c-29af362784d9@kernel.org \
    --to=okaya@kernel.org \
    --cc=alex.williamson@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=dennis.dalessandro@intel.com \
    --cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).