2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-10 20:55:19 -06:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-08-03 16:06:55 +03:00
|
|
|
|
IB/core: Add new ioctl interface
In this ioctl interface, processing the command starts from
properties of the command and fetching the appropriate user objects
before calling the handler.
Parsing and validation is done according to a specifier declared by
the driver's code. In the driver, all supported objects are declared.
These objects are separated to different object namepsaces. Dividing
objects to namespaces is done at initialization by using the higher
bits of the object ids. This initialization can mix objects declared
in different places to one parsing tree using in this ioctl interface.
For each object we list all supported methods. Similarly to objects,
methods are separated to method namespaces too. Namespacing is done
similarly to the objects case. This could be used in order to add
methods to an existing object.
Each method has a specific handler, which could be either a default
handler or a driver specific handler.
Along with the handler, a bunch of attributes are specified as well.
Similarly to objects and method, attributes are namespaced and hashed
by their ids at initialization too. All supported attributes are
subject to automatic fetching and validation. These attributes include
the command, response and the method's related objects' ids.
When these entities (objects, methods and attributes) are used, the
high bits of the entities ids are used in order to calculate the hash
bucket index. Then, these high bits are masked out in order to have a
zero based index. Since we use these high bits for both bucketing and
namespacing, we get a compact representation and O(1) array access.
This is mandatory for efficient dispatching.
Each attribute has a type (PTR_IN, PTR_OUT, IDR and FD) and a length.
Attributes could be validated through some attributes, like:
(*) Minimum size / Exact size
(*) Fops for FD
(*) Object type for IDR
If an IDR/fd attribute is specified, the kernel also states the object
type and the required access (NEW, WRITE, READ or DESTROY).
All uobject/fd management is done automatically by the infrastructure,
meaning - the infrastructure will fail concurrent commands that at
least one of them requires concurrent access (WRITE/DESTROY),
synchronize actions with device removals (dissociate context events)
and take care of reference counting (increase/decrease) for concurrent
actions invocation. The reference counts on the actual kernel objects
shall be handled by the handlers.
objects
+--------+
| |
| | methods +--------+
| | ns method method_spec +-----+ |len |
+--------+ +------+[d]+-------+ +----------------+[d]+------------+ |attr1+-> |type |
| object +> |method+-> | spec +-> + attr_buckets +-> |default_chain+--> +-----+ |idr_type|
+--------+ +------+ |handler| | | +------------+ |attr2| |access |
| | | | +-------+ +----------------+ |driver chain| +-----+ +--------+
| | | | +------------+
| | +------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+--------+
[d] = Hash ids to groups using the high order bits
The right types table is also chosen by using the high bits from
the ids. Currently we have either default or driver specific groups.
Once validation and object fetching (or creation) completed, we call
the handler:
int (*handler)(struct ib_device *ib_dev, struct ib_uverbs_file *ufile,
struct uverbs_attr_bundle *ctx);
ctx bundles attributes of different namespaces. Each element there
is an array of attributes which corresponds to one namespaces of
attributes. For example, in the usually used case:
ctx core
+----------------------------+ +------------+
| core: +---> | valid |
+----------------------------+ | cmd_attr |
| driver: | +------------+
|----------------------------+--+ | valid |
| | cmd_attr |
| +------------+
| | valid |
| | obj_attr |
| +------------+
|
| drivers
| +------------+
+> | valid |
| cmd_attr |
+------------+
| valid |
| cmd_attr |
+------------+
| valid |
| obj_attr |
+------------+
Signed-off-by: Matan Barak <matanb@mellanox.com>
Reviewed-by: Yishai Hadas <yishaih@mellanox.com>
Signed-off-by: Doug Ledford <dledford@redhat.com>
2017-08-03 16:06:57 +03:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-25 22:22:40 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-18 12:03:37 +03:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2020-01-13 14:33:10 +00:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
2020-01-08 19:21:53 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
2017-04-18 12:03:37 +03:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2020-01-08 19:21:53 +02:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2024-10-31 13:22:52 +02:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
2017-04-18 12:03:37 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-23 00:22:13 +08:00
|
|
|
|
2017-04-18 12:03:37 +03:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
|
|
|
|
|
atomics/treewide: Rename __atomic_add_unless() => atomic_fetch_add_unless()
While __atomic_add_unless() was originally intended as a building-block
for atomic_add_unless(), it's now used in a number of places around the
kernel. It's the only common atomic operation named __atomic*(), rather
than atomic_*(), and for consistency it would be better named
atomic_fetch_add_unless().
This lack of consistency is slightly confusing, and gets in the way of
scripting atomics. Given that, let's clean things up and promote it to
an official part of the atomics API, in the form of
atomic_fetch_add_unless().
This patch converts definitions and invocations over to the new name,
including the instrumented version, using the following script:
----
git grep -w __atomic_add_unless | while read line; do
sed -i '{s/\<__atomic_add_unless\>/atomic_fetch_add_unless/}' "${line%%:*}";
done
git grep -w __arch_atomic_add_unless | while read line; do
sed -i '{s/\<__arch_atomic_add_unless\>/arch_atomic_fetch_add_unless/}' "${line%%:*}";
done
----
Note that we do not have atomic{64,_long}_fetch_add_unless(), which will
be introduced by later patches.
There should be no functional change as a result of this patch.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Will Deacon <will.deacon@arm.com>
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Palmer Dabbelt <palmer@sifive.com>
Cc: Boqun Feng <boqun.feng@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/lkml/20180621121321.4761-2-mark.rutland@arm.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2018-06-21 13:13:04 +01:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
2018-07-25 21:40:14 -06:00
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
2018-07-25 21:40:14 -06:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2024-10-31 13:22:52 +02:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:12 -06:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:12 -06:00
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:14 -06:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
2018-07-25 21:40:12 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:15 -06:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:12 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-03-19 17:55:49 +08:00
|
|
|
|
2018-07-25 21:40:12 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-31 19:10:04 +03:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:12 -06:00
|
|
|
|
2019-04-01 17:08:24 -03:00
|
|
|
|
2018-07-25 21:40:12 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:15 -06:00
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
2018-07-25 21:40:12 -06:00
|
|
|
|
2020-01-08 19:21:56 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-31 19:10:04 +03:00
|
|
|
|
|
|
|
|
|
2020-11-04 16:45:55 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:12 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-27 16:55:34 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:12 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:20 -06:00
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
2018-07-25 21:40:12 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:14 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-27 16:55:34 +03:00
|
|
|
|
2018-07-25 21:40:14 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-31 19:10:04 +03:00
|
|
|
|
2018-07-25 21:40:14 -06:00
|
|
|
|
2019-04-01 17:08:24 -03:00
|
|
|
|
2018-07-25 21:40:14 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-27 16:55:34 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:14 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-31 19:10:04 +03:00
|
|
|
|
2018-07-25 21:40:14 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-25 22:22:40 -03:00
|
|
|
|
2018-07-25 21:40:14 -06:00
|
|
|
|
2018-07-04 11:32:06 +03:00
|
|
|
|
2018-07-25 21:40:11 -06:00
|
|
|
|
|
|
|
|
|
2020-05-27 16:55:34 +03:00
|
|
|
|
2018-07-04 11:32:06 +03:00
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
2019-03-31 19:10:03 +03:00
|
|
|
|
2018-07-04 11:32:06 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-11-25 20:51:13 +02:00
|
|
|
|
2019-03-31 19:10:03 +03:00
|
|
|
|
2018-07-25 21:40:11 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-31 19:10:04 +03:00
|
|
|
|
2018-07-25 21:40:11 -06:00
|
|
|
|
2018-07-25 21:40:14 -06:00
|
|
|
|
2018-07-25 21:40:11 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-25 22:22:40 -03:00
|
|
|
|
2018-07-25 21:40:11 -06:00
|
|
|
|
|
|
|
|
|
2018-11-25 20:51:14 +02:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:11 -06:00
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
2019-03-31 19:10:03 +03:00
|
|
|
|
2018-07-25 21:40:11 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-11-25 20:51:13 +02:00
|
|
|
|
2018-07-04 11:32:06 +03:00
|
|
|
|
|
|
|
|
|
2020-05-27 16:55:34 +03:00
|
|
|
|
2018-11-25 20:51:14 +02:00
|
|
|
|
2018-07-04 11:32:06 +03:00
|
|
|
|
2026-05-25 22:22:40 -03:00
|
|
|
|
2018-07-04 11:32:06 +03:00
|
|
|
|
2018-07-25 21:40:12 -06:00
|
|
|
|
2020-01-08 19:22:04 +02:00
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2020-01-08 19:22:04 +02:00
|
|
|
|
2018-07-10 13:43:06 -06:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2020-01-08 19:22:04 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-10 13:43:06 -06:00
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-04 11:32:08 +03:00
|
|
|
|
2020-01-08 19:22:04 +02:00
|
|
|
|
2018-07-10 20:55:16 -06:00
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
2018-02-13 12:18:36 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-20 16:20:45 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-04 11:32:08 +03:00
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
2018-07-10 20:55:14 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
2018-02-13 12:18:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-20 16:20:45 -08:00
|
|
|
|
|
|
|
|
|
2018-02-13 12:18:37 +02:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
|
|
|
|
|
2018-07-10 20:55:14 -06:00
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
2018-07-10 20:55:14 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
|
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-10 20:55:14 -06:00
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-08 19:21:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
2020-04-21 11:29:28 +03:00
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
2018-07-10 20:55:14 -06:00
|
|
|
|
2019-03-31 19:10:03 +03:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-20 16:20:45 -08:00
|
|
|
|
2018-11-26 08:28:33 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
2018-11-26 08:28:33 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2018-11-26 08:28:33 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:16 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
2018-07-10 20:55:19 -06:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2019-03-31 19:10:03 +03:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-11-26 08:28:33 +02:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-25 22:22:40 -03:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
|
|
|
|
|
2020-01-08 19:22:04 +02:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-08 19:22:04 +02:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-10 13:43:06 -06:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
2019-02-20 16:20:45 -08:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-20 16:20:45 -08:00
|
|
|
|
2020-01-08 19:22:04 +02:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
|
|
|
|
|
2020-01-08 19:22:04 +02:00
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
2020-06-17 09:18:26 +03:00
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
2020-06-17 09:18:26 +03:00
|
|
|
|
2020-01-08 19:21:56 +02:00
|
|
|
|
|
|
|
|
|
2020-01-08 19:22:04 +02:00
|
|
|
|
2020-01-08 19:21:56 +02:00
|
|
|
|
2020-06-17 09:18:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-25 22:22:39 -03:00
|
|
|
|
|
|
|
|
|
2020-06-17 09:18:26 +03:00
|
|
|
|
2020-01-08 19:21:56 +02:00
|
|
|
|
2020-06-17 09:18:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-08 19:21:56 +02:00
|
|
|
|
2026-02-01 16:34:04 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
|
|
|
|
|
2018-07-04 11:32:11 +03:00
|
|
|
|
2020-01-08 19:21:56 +02:00
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
2020-06-17 09:18:26 +03:00
|
|
|
|
2020-01-08 19:21:56 +02:00
|
|
|
|
2020-06-17 09:18:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
|
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
2019-03-31 19:10:03 +03:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2020-01-08 19:22:04 +02:00
|
|
|
|
2018-07-25 21:40:15 -06:00
|
|
|
|
|
|
|
|
|
2018-11-26 08:28:33 +02:00
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:15 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-08 19:22:04 +02:00
|
|
|
|
2018-07-25 21:40:15 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2026-05-25 22:22:40 -03:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2018-07-25 21:40:12 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-20 16:20:45 -08:00
|
|
|
|
2018-07-25 21:40:12 -06:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:20 -06:00
|
|
|
|
2019-03-31 19:10:04 +03:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
|
|
|
|
|
2019-03-31 19:10:04 +03:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2020-11-04 16:45:55 +02:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:12 -06:00
|
|
|
|
|
|
|
|
|
2018-07-10 20:55:16 -06:00
|
|
|
|
2018-07-25 21:40:20 -06:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2018-07-25 21:40:12 -06:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:20 -06:00
|
|
|
|
|
|
|
|
|
2019-02-20 16:20:45 -08:00
|
|
|
|
2018-07-25 21:40:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
|
|
|
|
|
2020-01-08 19:21:56 +02:00
|
|
|
|
|
|
|
|
|
2026-02-01 16:34:04 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-10 20:55:21 -06:00
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:20 -06:00
|
|
|
|
2019-03-31 19:10:04 +03:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
2020-11-04 16:45:56 +02:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-08 19:21:56 +02:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2018-07-10 20:55:15 -06:00
|
|
|
|
2019-02-20 16:20:45 -08:00
|
|
|
|
2018-07-10 20:55:15 -06:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2026-03-21 18:58:59 +08:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2018-07-10 20:55:15 -06:00
|
|
|
|
2019-02-20 16:20:45 -08:00
|
|
|
|
2026-03-21 18:58:59 +08:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2019-02-20 16:20:45 -08:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
2020-11-30 09:58:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-08 19:21:56 +02:00
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
2018-07-10 20:55:15 -06:00
|
|
|
|
2020-01-08 19:21:56 +02:00
|
|
|
|
2018-07-10 20:55:21 -06:00
|
|
|
|
2020-01-08 19:21:54 +02:00
|
|
|
|
2018-07-10 20:55:21 -06:00
|
|
|
|
2018-07-10 20:55:15 -06:00
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
2018-07-04 11:32:11 +03:00
|
|
|
|
2018-07-10 20:55:15 -06:00
|
|
|
|
2026-02-01 16:34:04 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-10 20:55:21 -06:00
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
|
|
|
|
|
2018-07-10 20:55:15 -06:00
|
|
|
|
|
|
|
|
|
2018-07-10 20:55:20 -06:00
|
|
|
|
|
|
|
|
|
2018-07-10 20:55:15 -06:00
|
|
|
|
2020-01-08 19:21:56 +02:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2019-04-01 17:08:24 -03:00
|
|
|
|
2018-07-04 11:32:07 +03:00
|
|
|
|
2018-07-10 20:55:16 -06:00
|
|
|
|
|
|
|
|
|
2018-07-10 20:55:18 -06:00
|
|
|
|
2018-07-04 11:32:07 +03:00
|
|
|
|
2018-07-10 20:55:18 -06:00
|
|
|
|
2018-02-13 12:18:39 +02:00
|
|
|
|
2018-07-10 20:55:21 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-16 13:20:59 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:15 -06:00
|
|
|
|
2018-07-10 20:55:18 -06:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2026-05-25 22:22:40 -03:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2020-11-30 09:58:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-25 22:22:40 -03:00
|
|
|
|
2020-11-30 09:58:37 +02:00
|
|
|
|
2018-07-10 20:55:16 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-31 19:10:04 +03:00
|
|
|
|
2020-05-19 10:27:05 +03:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2018-07-25 21:40:15 -06:00
|
|
|
|
2020-09-02 11:17:08 +03:00
|
|
|
|
2018-07-25 21:40:15 -06:00
|
|
|
|
2020-09-02 11:17:08 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:15 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2026-05-25 22:22:40 -03:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
2020-01-08 19:21:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
2017-04-18 12:03:37 +03:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
2018-07-25 21:40:14 -06:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2020-04-23 09:01:22 +03:00
|
|
|
|
2018-07-10 20:55:16 -06:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
2026-05-25 22:22:40 -03:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2018-07-25 21:40:20 -06:00
|
|
|
|
|
|
|
|
|
2019-02-20 16:20:45 -08:00
|
|
|
|
2018-07-25 21:40:20 -06:00
|
|
|
|
2026-05-25 22:22:40 -03:00
|
|
|
|
2018-07-25 21:40:20 -06:00
|
|
|
|
2026-05-25 22:22:40 -03:00
|
|
|
|
2018-07-25 21:40:20 -06:00
|
|
|
|
|
|
|
|
|
2019-02-20 16:20:45 -08:00
|
|
|
|
2018-07-25 21:40:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-20 16:20:45 -08:00
|
|
|
|
2018-07-25 21:40:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-20 16:20:45 -08:00
|
|
|
|
2018-07-25 21:40:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-20 16:20:45 -08:00
|
|
|
|
2018-07-25 21:40:20 -06:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:20 -06:00
|
|
|
|
|
|
|
|
|
2020-11-30 09:58:37 +02:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2018-06-17 12:59:50 +03:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
RDMA/uverbs: Add DMABUF object type and operations
Expose DMABUF functionality to userspace through the uverbs interface,
enabling InfiniBand/RDMA devices to export PCI based memory regions
(e.g. device memory) as DMABUF file descriptors. This allows
zero-copy sharing of RDMA memory with other subsystems that support the
dma-buf framework.
A new UVERBS_OBJECT_DMABUF object type and allocation method were
introduced.
During allocation, uverbs invokes the driver to supply the
rdma_user_mmap_entry associated with the given page offset (pgoff).
Based on the returned rdma_user_mmap_entry, uverbs requests the driver
to provide the corresponding physical-memory details as well as the
driver’s PCI provider information.
Using this information, dma_buf_export() is called; if it succeeds,
uobj->object is set to the underlying file pointer returned by the
dma-buf framework.
The file descriptor number follows the standard uverbs allocation flow,
but the file pointer comes from the dma-buf subsystem, including its own
fops and private data.
When an mmap entry is removed, uverbs iterates over its associated
DMABUFs, marks them as revoked, and calls dma_buf_move_notify() so that
their importers are notified.
The same procedure applies during the disassociate flow; final cleanup
occurs when the application closes the file.
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Edward Srouji <edwards@nvidia.com>
Link: https://patch.msgid.link/20260201-dmabuf-export-v3-2-da238b614fe3@nvidia.com
Signed-off-by: Leon Romanovsky <leon@kernel.org>
2026-02-01 16:34:05 +02:00
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
2020-01-08 19:21:56 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-10 20:55:17 -06:00
|
|
|
|
2018-07-10 20:55:18 -06:00
|
|
|
|
2020-01-08 19:21:56 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:12 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
2019-03-31 19:10:04 +03:00
|
|
|
|
2018-07-10 20:55:18 -06:00
|
|
|
|
2018-07-10 20:55:17 -06:00
|
|
|
|
|
|
|
|
|
2020-01-08 19:21:56 +02:00
|
|
|
|
2018-07-10 20:55:17 -06:00
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
2018-07-10 20:55:16 -06:00
|
|
|
|
2018-07-04 11:32:11 +03:00
|
|
|
|
2020-01-08 19:21:54 +02:00
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
2026-05-25 22:22:40 -03:00
|
|
|
|
RDMA/uverbs: Add DMABUF object type and operations
Expose DMABUF functionality to userspace through the uverbs interface,
enabling InfiniBand/RDMA devices to export PCI based memory regions
(e.g. device memory) as DMABUF file descriptors. This allows
zero-copy sharing of RDMA memory with other subsystems that support the
dma-buf framework.
A new UVERBS_OBJECT_DMABUF object type and allocation method were
introduced.
During allocation, uverbs invokes the driver to supply the
rdma_user_mmap_entry associated with the given page offset (pgoff).
Based on the returned rdma_user_mmap_entry, uverbs requests the driver
to provide the corresponding physical-memory details as well as the
driver’s PCI provider information.
Using this information, dma_buf_export() is called; if it succeeds,
uobj->object is set to the underlying file pointer returned by the
dma-buf framework.
The file descriptor number follows the standard uverbs allocation flow,
but the file pointer comes from the dma-buf subsystem, including its own
fops and private data.
When an mmap entry is removed, uverbs iterates over its associated
DMABUFs, marks them as revoked, and calls dma_buf_move_notify() so that
their importers are notified.
The same procedure applies during the disassociate flow; final cleanup
occurs when the application closes the file.
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Edward Srouji <edwards@nvidia.com>
Link: https://patch.msgid.link/20260201-dmabuf-export-v3-2-da238b614fe3@nvidia.com
Signed-off-by: Leon Romanovsky <leon@kernel.org>
2026-02-01 16:34:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-25 22:22:39 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
RDMA/uverbs: Add DMABUF object type and operations
Expose DMABUF functionality to userspace through the uverbs interface,
enabling InfiniBand/RDMA devices to export PCI based memory regions
(e.g. device memory) as DMABUF file descriptors. This allows
zero-copy sharing of RDMA memory with other subsystems that support the
dma-buf framework.
A new UVERBS_OBJECT_DMABUF object type and allocation method were
introduced.
During allocation, uverbs invokes the driver to supply the
rdma_user_mmap_entry associated with the given page offset (pgoff).
Based on the returned rdma_user_mmap_entry, uverbs requests the driver
to provide the corresponding physical-memory details as well as the
driver’s PCI provider information.
Using this information, dma_buf_export() is called; if it succeeds,
uobj->object is set to the underlying file pointer returned by the
dma-buf framework.
The file descriptor number follows the standard uverbs allocation flow,
but the file pointer comes from the dma-buf subsystem, including its own
fops and private data.
When an mmap entry is removed, uverbs iterates over its associated
DMABUFs, marks them as revoked, and calls dma_buf_move_notify() so that
their importers are notified.
The same procedure applies during the disassociate flow; final cleanup
occurs when the application closes the file.
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Edward Srouji <edwards@nvidia.com>
Link: https://patch.msgid.link/20260201-dmabuf-export-v3-2-da238b614fe3@nvidia.com
Signed-off-by: Leon Romanovsky <leon@kernel.org>
2026-02-01 16:34:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-25 22:22:39 -03:00
|
|
|
|
RDMA/uverbs: Add DMABUF object type and operations
Expose DMABUF functionality to userspace through the uverbs interface,
enabling InfiniBand/RDMA devices to export PCI based memory regions
(e.g. device memory) as DMABUF file descriptors. This allows
zero-copy sharing of RDMA memory with other subsystems that support the
dma-buf framework.
A new UVERBS_OBJECT_DMABUF object type and allocation method were
introduced.
During allocation, uverbs invokes the driver to supply the
rdma_user_mmap_entry associated with the given page offset (pgoff).
Based on the returned rdma_user_mmap_entry, uverbs requests the driver
to provide the corresponding physical-memory details as well as the
driver’s PCI provider information.
Using this information, dma_buf_export() is called; if it succeeds,
uobj->object is set to the underlying file pointer returned by the
dma-buf framework.
The file descriptor number follows the standard uverbs allocation flow,
but the file pointer comes from the dma-buf subsystem, including its own
fops and private data.
When an mmap entry is removed, uverbs iterates over its associated
DMABUFs, marks them as revoked, and calls dma_buf_move_notify() so that
their importers are notified.
The same procedure applies during the disassociate flow; final cleanup
occurs when the application closes the file.
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Edward Srouji <edwards@nvidia.com>
Link: https://patch.msgid.link/20260201-dmabuf-export-v3-2-da238b614fe3@nvidia.com
Signed-off-by: Leon Romanovsky <leon@kernel.org>
2026-02-01 16:34:05 +02:00
|
|
|
|
|
|
|
|
|
2026-05-25 22:22:39 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
RDMA/uverbs: Add DMABUF object type and operations
Expose DMABUF functionality to userspace through the uverbs interface,
enabling InfiniBand/RDMA devices to export PCI based memory regions
(e.g. device memory) as DMABUF file descriptors. This allows
zero-copy sharing of RDMA memory with other subsystems that support the
dma-buf framework.
A new UVERBS_OBJECT_DMABUF object type and allocation method were
introduced.
During allocation, uverbs invokes the driver to supply the
rdma_user_mmap_entry associated with the given page offset (pgoff).
Based on the returned rdma_user_mmap_entry, uverbs requests the driver
to provide the corresponding physical-memory details as well as the
driver’s PCI provider information.
Using this information, dma_buf_export() is called; if it succeeds,
uobj->object is set to the underlying file pointer returned by the
dma-buf framework.
The file descriptor number follows the standard uverbs allocation flow,
but the file pointer comes from the dma-buf subsystem, including its own
fops and private data.
When an mmap entry is removed, uverbs iterates over its associated
DMABUFs, marks them as revoked, and calls dma_buf_move_notify() so that
their importers are notified.
The same procedure applies during the disassociate flow; final cleanup
occurs when the application closes the file.
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Edward Srouji <edwards@nvidia.com>
Link: https://patch.msgid.link/20260201-dmabuf-export-v3-2-da238b614fe3@nvidia.com
Signed-off-by: Leon Romanovsky <leon@kernel.org>
2026-02-01 16:34:05 +02:00
|
|
|
|
2020-01-08 19:21:54 +02:00
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
2026-05-25 22:22:40 -03:00
|
|
|
|
|
|
|
|
|
2018-06-20 17:11:39 +03:00
|
|
|
|
2024-10-31 13:22:51 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-06-20 17:11:39 +03:00
|
|
|
|
|
|
|
|
|
2024-10-31 13:22:51 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-06-20 17:11:39 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-04 11:32:07 +03:00
|
|
|
|
2019-03-31 19:10:04 +03:00
|
|
|
|
2018-06-20 17:11:39 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
2020-11-04 16:45:55 +02:00
|
|
|
|
|
|
|
|
|
2019-03-31 19:10:04 +03:00
|
|
|
|
2018-07-25 21:40:12 -06:00
|
|
|
|
2018-08-28 14:40:32 +03:00
|
|
|
|
|
|
|
|
|
2018-06-20 17:11:39 +03:00
|
|
|
|
2020-11-04 16:45:55 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-06-20 17:11:39 +03:00
|
|
|
|
|
|
|
|
|
2026-05-25 22:22:40 -03:00
|
|
|
|
2017-04-04 13:31:42 +03:00
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:20 -06:00
|
|
|
|
|
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
2018-06-17 12:59:50 +03:00
|
|
|
|
2017-04-04 13:31:46 +03:00
|
|
|
|
2018-07-04 11:32:08 +03:00
|
|
|
|
2019-03-31 19:10:03 +03:00
|
|
|
|
|
|
|
|
|
2017-08-03 16:06:55 +03:00
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
2019-03-31 19:10:03 +03:00
|
|
|
|
2018-08-09 20:14:37 -06:00
|
|
|
|
2017-08-03 16:06:55 +03:00
|
|
|
|
|
|
|
|
|
2019-03-31 19:10:03 +03:00
|
|
|
|
|
|
|
|
|
2017-08-03 16:06:55 +03:00
|
|
|
|
2018-07-25 21:40:14 -06:00
|
|
|
|
2019-03-31 19:10:03 +03:00
|
|
|
|
|
|
|
|
|
2017-08-03 16:06:55 +03:00
|
|
|
|
2019-03-31 19:10:03 +03:00
|
|
|
|
|
|
|
|
|
2017-08-03 16:06:55 +03:00
|
|
|
|
2020-01-08 19:22:04 +02:00
|
|
|
|
2017-08-03 16:06:55 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-25 22:22:40 -03:00
|
|
|
|
2017-08-03 16:06:55 +03:00
|
|
|
|
2020-01-08 19:21:56 +02:00
|
|
|
|
2020-05-19 10:27:05 +03:00
|
|
|
|
|
|
|
|
|
2017-08-03 16:06:55 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
2017-08-03 16:06:55 +03:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:13 -06:00
|
|
|
|
2017-08-03 16:06:55 +03:00
|
|
|
|
|
|
|
|
|
2018-07-25 21:40:14 -06:00
|
|
|
|
|
|
|
|
|
2017-08-03 16:06:55 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-08 19:21:56 +02:00
|
|
|
|
2017-08-03 16:06:55 +03:00
|
|
|
|
2020-05-19 10:27:05 +03:00
|
|
|
|
2017-08-03 16:06:55 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-25 22:22:40 -03:00
|
|
|
|
2025-06-26 21:58:04 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-25 22:22:40 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|