From: Jason Gunthorpe <jgg@nvidia.com>
To: "Nikolova, Tatyana E" <tatyana.e.nikolova@intel.com>
Cc: "dledford@redhat.com" <dledford@redhat.com>,
"leon@kernel.org" <leon@kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH] irdma: Add ice and irdma to kernel-boot rules
Date: Wed, 18 Aug 2021 13:45:57 -0300 [thread overview]
Message-ID: <20210818164557.GB5673@nvidia.com> (raw)
In-Reply-To: <DM6PR11MB4692C424F3B5AB513B0EBBDACBF99@DM6PR11MB4692.namprd11.prod.outlook.com>
On Thu, Aug 12, 2021 at 11:33:04PM +0000, Nikolova, Tatyana E wrote:
> > > @@ -12,6 +12,7 @@ ENV{ID_NET_DRIVER}=="bnxt_en",
> > RUN{builtin}+="kmod load bnxt_re"
> > > ENV{ID_NET_DRIVER}=="cxgb4", RUN{builtin}+="kmod load iw_cxgb4"
> > > ENV{ID_NET_DRIVER}=="hns", RUN{builtin}+="kmod load hns_roce"
> > > ENV{ID_NET_DRIVER}=="i40e", RUN{builtin}+="kmod load i40iw"
> > > +ENV{ID_NET_DRIVER}=="ice", RUN{builtin}+="kmod load irdma"
> >
> > This should not be needed, right? The auxbux stuff triggers proper module
> > autoloading?
>
> Hi Jason,
>
> Our module depends on the auxbus, but we don't know how the auxbus
> could trigger loading of irdma. Could you please explain?
It should simply happen automatically once the aux device is
created. If it doesn't something is missing in the kernel.
It works the same way as any loading a module for any other struct
device, the aux device exposes a modalias and the userspace matches it
to the modules.alias file and then loads the specified module.
Jason
next prev parent reply other threads:[~2021-08-18 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 17:58 [PATCH] irdma: Add ice and irdma to kernel-boot rules Tatyana Nikolova
2021-08-06 18:28 ` Jason Gunthorpe
2021-08-12 23:33 ` Nikolova, Tatyana E
2021-08-18 16:45 ` Jason Gunthorpe [this message]
2021-08-20 21:46 ` Nikolova, Tatyana E
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=20210818164557.GB5673@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=tatyana.e.nikolova@intel.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;
as well as URLs for NNTP newsgroup(s).