Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Ashutosh Sharma <ashutosh.dandora4@gmail.com>
Cc: linux-pci@vger.kernel.org, alex.williamson@redhat.com,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Timothy Redaelli <tredaelli@redhat.com>
Subject: Re: How to disable Linux kernel nvme driver for a particular PCI address ?
Date: Mon, 1 May 2023 11:31:28 -0500	[thread overview]
Message-ID: <20230501163128.GA587981@bhelgaas> (raw)
In-Reply-To: <CADOvten3LND2XnKbUuEmKni7c93DPXdP99ZbW84mouGtdBSHZw@mail.gmail.com>

[+cc Greg, Rafael, Timothy]

On Mon, May 01, 2023 at 12:19:39PM +0530, Ashutosh Sharma wrote:
> Hi,
> 
> I have multiple NVMe drives of same type (same vendor and same model)
> attached to my system running Ubuntu 22.04.2 LTS with Linux kernel
> version 5.19.0-35-generic.I have unbound one drive from 'nvme' driver
> and bound to the 'vfio-pci' driver using "driverctl
> set-override"command.
> 
> But when I perform the hot plugging on that particular drive, then
> after plugged in, the drive by default binds with 'nvme' driver. So, I
> want to permanently bypass/disable the 'nvme' driver only for a
> particular pci address/slot. I cannot blacklist the 'nvme' driver
> entirely, as other drives still need to be bound with 'nvme' driver.
> 
> So, Is there any way to disable the 'nvme' driver for a particular PCI
> address/slot ?

I think this is more of a device model or udev question than a PCI
subsystem question, so I cc'd some of those folks.

Bjorn

  reply	other threads:[~2023-05-01 16:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01  6:49 How to disable Linux kernel nvme driver for a particular PCI address ? Ashutosh Sharma
2023-05-01 16:31 ` Bjorn Helgaas [this message]
2023-05-01 23:47   ` Greg Kroah-Hartman

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=20230501163128.GA587981@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=alex.williamson@redhat.com \
    --cc=ashutosh.dandora4@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=tredaelli@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