linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sinan Kaya <okaya@kernel.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Dennis Dalessandro <dennis.dalessandro@intel.com>,
	Linux PCI <linux-pci@vger.kernel.org>
Subject: Re: RFC on PCI Device Lock
Date: Tue, 4 Sep 2018 20:09:16 -0700	[thread overview]
Message-ID: <571b8341-f6fd-d92a-7091-f4fb02a2aadf@kernel.org> (raw)
In-Reply-To: <20180904204649.415491f8@t450s.home>

On 9/4/2018 7:46 PM, Alex Williamson wrote:
> #define PCI_RESET_DEV_SPECIFIC	(1 << 0)
> #define PCI_RESET_FLR		(1 << 1)
> #define PCI_RESET_PM		(1 << 2)
> #define PCI_RESET_SLOT		(1 << 3)
> #define PCI_RESET_BUS		(1 << 4)
> 
> #define PCI_RESET_ANY		(~0)
> #define PCI_RESET_FUNC		(PCI_RESET_DEV_SPECIFIC | \
> 				 PCI_RESET_FLR | PCI_RESET_PM)
> #define PCI_RESET_LINK		(PCI_RESET_SLOT | PCI_RESET_BUS)

I should be able to put something together using __pci_reset_function_locked()
shortly.

This is not that difficult to implement.

  reply	other threads:[~2018-09-05  7:37 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 [this message]
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

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=571b8341-f6fd-d92a-7091-f4fb02a2aadf@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).