From: Luck, Tony <tony.luck at intel.com>
To: accel-config@lists.01.org
Subject: [Accel-config] Re: [PATCH] accel-config/test: load/unload uacce module at cleanup
Date: Tue, 06 Apr 2021 20:11:15 +0000 [thread overview]
Message-ID: <b2c836c85a164f419d891c8ee3494aae@intel.com> (raw)
In-Reply-To: b673090b-b8bc-f48b-2190-dab125b64471@intel.com
[-- Attachment #1: Type: text/plain, Size: 671 bytes --]
-r, --remove
This option causes modprobe to remove rather than insert a
module. If the modules it depends on are also unused, modprobe will try to remove them
too. Unlike insertion, more than one module can be specified on the command line (it
does not make sense to specify module parameters when removing modules).
Maybe a bug in modprobe? It shouldn’t try to remove idxd when the first of the
dependent modules is removed (because idxd is still “in use” by the other).
Either that, or IDXD and these two dependent modules aren’t setting the right
bits to let modprobe know what is going on?
-Tony
[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 3265 bytes --]
next reply other threads:[~2021-04-06 20:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 20:11 Luck, Tony [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-06 20:21 [Accel-config] Re: [PATCH] accel-config/test: load/unload uacce module at cleanup Dave Jiang
2021-04-06 18:55 Dave Jiang
2021-04-06 18:43 Thomas, Ramesh
2021-04-06 17:44 Dave Jiang
2021-04-06 17:32 Thomas, Ramesh
2021-04-06 15:55 Dave Jiang
2021-04-06 15:54 Dave Jiang
2021-04-06 6:11 Thomas, Ramesh
2021-04-06 4:11 Dave Jiang
2021-04-06 1:10 Thomas, Ramesh
2021-04-06 0:53 Dave Jiang
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=b2c836c85a164f419d891c8ee3494aae@intel.com \
--to=accel-config@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.