ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.com>
To: Matthew Wilcox <willy6545@gmail.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] (PCI) driver rebinding
Date: Mon, 26 Jun 2017 07:54:52 +0200	[thread overview]
Message-ID: <85e0d92f-628b-8c10-30c3-d8b28b8a1dcf@suse.com> (raw)
In-Reply-To: <CAFhKne8QN1jcATr_xTCWb7Jn-=UoZmsbf4GTDLzM0V=kgWvB3A@mail.gmail.com>

On 06/25/2017 11:38 PM, Matthew Wilcox wrote:
> Is udev the solution here?
> 
(Top posting; tsk. Probably the new job environment :-)

> Have ->probe do common initialisation and return success. Then udev says
> something to the driver to make it choose one or the other modes.
> 
Which would be option 2 from my proposal.
(And, incidentally, is what zSeries does.)
Plus you essentially spanning off your own bus from the PCI device,
which would solve the PCI binding problem.
But you just delegated the problem one level higher, as you then have to
configure your private bus. So I don't think it solves the underlying
problem, namely how to get the configuration to the driver.

Another problem here is that you rely on udev to do the binding, ie you
have to configure the device first before it can used. Which requires
the use of an initrd, and I'm not sure if everyone can agree to that.

Or come up with a commandline parameter instructing the driver on which
devices to bind.

So it's far from being clear-cut; hence this proposal.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		               zSeries & Storage
hare@suse.com			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)

  reply	other threads:[~2017-06-26  5:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-25 15:39 Hannes Reinecke
2017-06-25 21:38 ` Matthew Wilcox
2017-06-26  5:54   ` Hannes Reinecke [this message]
2017-06-26  4:59 ` Greg KH
2017-06-26  6:05   ` Hannes Reinecke
2017-06-26  6:57     ` Greg KH
2017-06-26  5:37 ` Leon Romanovsky
2017-06-26  5:44 ` Bart Van Assche
2017-06-26 17:40 ` Lee Duncan

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=85e0d92f-628b-8c10-30c3-d8b28b8a1dcf@suse.com \
    --to=hare@suse.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=willy6545@gmail.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