2023-03-30 17:31:57 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-23 16:37:06 +03:00
|
|
|
|
2023-12-14 13:39:54 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
|
|
|
|
|
kbuild: use $(src) instead of $(srctree)/$(src) for source directory
Kbuild conventionally uses $(obj)/ for generated files, and $(src)/ for
checked-in source files. It is merely a convention without any functional
difference. In fact, $(obj) and $(src) are exactly the same, as defined
in scripts/Makefile.build:
src := $(obj)
When the kernel is built in a separate output directory, $(src) does
not accurately reflect the source directory location. While Kbuild
resolves this discrepancy by specifying VPATH=$(srctree) to search for
source files, it does not cover all cases. For example, when adding a
header search path for local headers, -I$(srctree)/$(src) is typically
passed to the compiler.
This introduces inconsistency between upstream and downstream Makefiles
because $(src) is used instead of $(srctree)/$(src) for the latter.
To address this inconsistency, this commit changes the semantics of
$(src) so that it always points to the directory in the source tree.
Going forward, the variables used in Makefiles will have the following
meanings:
$(obj) - directory in the object tree
$(src) - directory in the source tree (changed by this commit)
$(objtree) - the top of the kernel object tree
$(srctree) - the top of the kernel source tree
Consequently, $(srctree)/$(src) in upstream Makefiles need to be replaced
with $(src).
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Reviewed-by: Nicolas Schier <nicolas@fjasle.eu>
2024-04-27 23:55:02 +09:00
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
2023-05-26 09:43:49 -07:00
|
|
|
|
2024-07-08 14:29:06 -07:00
|
|
|
|
2023-05-26 09:43:49 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-03-02 17:39:28 +02:00
|
|
|
|
kbuild: use $(src) instead of $(srctree)/$(src) for source directory
Kbuild conventionally uses $(obj)/ for generated files, and $(src)/ for
checked-in source files. It is merely a convention without any functional
difference. In fact, $(obj) and $(src) are exactly the same, as defined
in scripts/Makefile.build:
src := $(obj)
When the kernel is built in a separate output directory, $(src) does
not accurately reflect the source directory location. While Kbuild
resolves this discrepancy by specifying VPATH=$(srctree) to search for
source files, it does not cover all cases. For example, when adding a
header search path for local headers, -I$(srctree)/$(src) is typically
passed to the compiler.
This introduces inconsistency between upstream and downstream Makefiles
because $(src) is used instead of $(srctree)/$(src) for the latter.
To address this inconsistency, this commit changes the semantics of
$(src) so that it always points to the directory in the source tree.
Going forward, the variables used in Makefiles will have the following
meanings:
$(obj) - directory in the object tree
$(src) - directory in the source tree (changed by this commit)
$(objtree) - the top of the kernel object tree
$(srctree) - the top of the kernel source tree
Consequently, $(srctree)/$(src) in upstream Makefiles need to be replaced
with $(src).
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Reviewed-by: Nicolas Schier <nicolas@fjasle.eu>
2024-04-27 23:55:02 +09:00
|
|
|
|
2023-05-26 09:43:49 -07:00
|
|
|
|
|
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-18 17:12:39 -04:00
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
2023-07-18 13:37:01 +05:30
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
2023-09-14 17:25:14 +05:30
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
|
|
|
|
|
2023-08-01 12:28:14 +02:00
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-11-17 14:51:45 -08:00
|
|
|
|
2024-08-28 14:51:57 -07:00
|
|
|
|
2024-01-17 10:26:19 -08:00
|
|
|
|
2023-11-17 14:51:50 -08:00
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
2023-10-09 13:10:27 -07:00
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
2023-12-08 00:11:51 -05:00
|
|
|
|
2023-11-17 18:06:16 -08:00
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-17 21:36:58 -07:00
|
|
|
|
2023-01-17 20:31:24 -08:00
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-10-04 12:34:23 -07:00
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
2023-12-18 20:06:22 +01:00
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
2024-03-13 23:11:10 +01:00
|
|
|
|
2024-04-10 19:03:37 +02:00
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 19:24:03 +03:00
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
2023-08-04 17:17:56 +05:30
|
|
|
|
2024-08-09 17:51:26 +02:00
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-17 18:45:55 -07:00
|
|
|
|
2024-07-03 09:48:01 -07:00
|
|
|
|
2023-03-24 14:04:10 -07:00
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-07-09 09:54:59 -07:00
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-01 14:52:21 -07:00
|
|
|
|
2023-06-28 11:08:35 +05:30
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
2024-06-07 11:29:38 -07:00
|
|
|
|
2024-06-07 11:29:39 -07:00
|
|
|
|
2024-11-04 06:38:11 -08:00
|
|
|
|
2023-04-03 22:20:31 +00:00
|
|
|
|
2023-01-12 17:25:17 -05:00
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-30 15:35:26 +02:00
|
|
|
|
2024-01-09 16:34:18 +05:30
|
|
|
|
2024-12-03 10:36:39 -05:00
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-04-12 15:22:36 +05:30
|
|
|
|
|
|
|
|
|
2023-09-25 13:48:38 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-11-15 08:38:03 +01:00
|
|
|
|
2023-12-18 17:53:41 +01:00
|
|
|
|
2024-05-16 13:05:44 +02:00
|
|
|
|
2024-01-04 23:20:28 +01:00
|
|
|
|
2023-12-18 17:53:41 +01:00
|
|
|
|
drm/xe/vf: React to MIGRATED interrupt
To properly support VF Save/Restore procedure, fixups need to be
applied after PF driver finishes its part of VF Restore. The fixups
are required to adjust the ongoing execution for a hardware switch
that happened, because some GFX resources are not fully virtualized,
and assigned to a VF as range from a global pool. The VF on which
a VM is restored will often have different ranges provisioned than
the VF on which save process happened. Those resource fixups are
applied by the VF driver within a restored VM.
A VF driver gets informed that it was migrated by receiving an
interrupt from each GuC. The interrupt assigned for that purpose
is "GUC SW interrupt 0". Seeing that fields set from within the
irq handler should be the trigger for fixups.
The VF can safely do post-migration fixups on resources associated
to each GuC only after that GuC issued the MIGRATED interrupt.
This change introduces a worker to be used for post-migration fixups,
and a mechanism to schedule said worker when all GuCs sent the irq.
v2: renamed and moved functions, updated logged messages, removed
unused includes, used anon struct (Michal)
v3: ordering, kerneldoc, asserts, debug messages,
on_all_tiles -> on_all_gts (Michal)
v4: fixed missing header include
v5: Explained what fixups are, explained which IRQ is used, style
fixes (Michal)
Bspec: 50868
Signed-off-by: Tomasz Lis <tomasz.lis@intel.com>
Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20241104213449.1455694-2-tomasz.lis@intel.com
Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
2024-11-04 22:34:45 +01:00
|
|
|
|
|
|
|
|
|
2023-11-15 08:38:03 +01:00
|
|
|
|
2023-11-28 16:15:05 +01:00
|
|
|
|
2024-04-15 19:39:36 +02:00
|
|
|
|
2024-04-15 19:39:37 +02:00
|
|
|
|
2024-03-26 20:15:18 +01:00
|
|
|
|
2024-09-13 14:00:13 +02:00
|
|
|
|
2024-05-14 21:00:14 +02:00
|
|
|
|
2024-04-10 19:03:38 +02:00
|
|
|
|
2024-04-23 20:04:35 +02:00
|
|
|
|
2023-11-28 16:15:05 +01:00
|
|
|
|
|
|
|
|
|
2024-04-04 17:44:30 +02:00
|
|
|
|
2024-05-06 20:41:21 +02:00
|
|
|
|
2024-04-04 17:44:30 +02:00
|
|
|
|
2023-11-28 16:15:05 +01:00
|
|
|
|
2024-02-26 13:46:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-12-18 20:06:24 +01:00
|
|
|
|
2023-08-17 16:30:41 -04:00
|
|
|
|
|
|
|
|
|
kbuild: use $(src) instead of $(srctree)/$(src) for source directory
Kbuild conventionally uses $(obj)/ for generated files, and $(src)/ for
checked-in source files. It is merely a convention without any functional
difference. In fact, $(obj) and $(src) are exactly the same, as defined
in scripts/Makefile.build:
src := $(obj)
When the kernel is built in a separate output directory, $(src) does
not accurately reflect the source directory location. While Kbuild
resolves this discrepancy by specifying VPATH=$(srctree) to search for
source files, it does not cover all cases. For example, when adding a
header search path for local headers, -I$(srctree)/$(src) is typically
passed to the compiler.
This introduces inconsistency between upstream and downstream Makefiles
because $(src) is used instead of $(srctree)/$(src) for the latter.
To address this inconsistency, this commit changes the semantics of
$(src) so that it always points to the directory in the source tree.
Going forward, the variables used in Makefiles will have the following
meanings:
$(obj) - directory in the object tree
$(src) - directory in the source tree (changed by this commit)
$(objtree) - the top of the kernel object tree
$(srctree) - the top of the kernel source tree
Consequently, $(srctree)/$(src) in upstream Makefiles need to be replaced
with $(src).
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Reviewed-by: Nicolas Schier <nicolas@fjasle.eu>
2024-04-27 23:55:02 +09:00
|
|
|
|
|
|
|
|
|
2023-08-17 16:30:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-22 12:14:27 +02:00
|
|
|
|
|
|
|
|
|
2024-09-17 19:13:40 +03:00
|
|
|
|
2024-01-22 12:14:27 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-07-03 13:43:39 +01:00
|
|
|
|
2024-01-22 12:14:27 +02:00
|
|
|
|
2023-08-17 16:30:41 -04:00
|
|
|
|
|
|
|
|
|
2024-04-30 10:28:49 -07:00
|
|
|
|
|
|
|
|
|
2023-08-17 16:30:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-09-23 18:24:53 +03:00
|
|
|
|
|
|
|
|
|
2023-08-17 16:30:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-30 01:37:38 +05:30
|
|
|
|
2023-08-17 16:30:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-11-20 14:03:34 +02:00
|
|
|
|
2023-08-17 16:30:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-09-20 14:56:43 +03:00
|
|
|
|
2023-08-17 16:30:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-10 21:14:28 +03:00
|
|
|
|
2023-08-17 16:30:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-03-06 08:12:48 +05:30
|
|
|
|
2023-08-17 16:30:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-10-16 17:31:33 +03:00
|
|
|
|
2023-08-17 16:30:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-04-12 12:41:45 +03:00
|
|
|
|
2023-08-17 16:30:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-27 15:32:56 -07:00
|
|
|
|
2023-08-17 16:30:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-24 11:05:15 +02:00
|
|
|
|
2024-08-08 10:11:21 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-10 21:15:18 +02:00
|
|
|
|
2024-08-08 10:11:21 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-24 11:05:15 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-17 16:30:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
2023-04-27 15:32:56 -07:00
|
|
|
|
2023-08-17 16:30:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-27 15:32:56 -07:00
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
kbuild: use $(src) instead of $(srctree)/$(src) for source directory
Kbuild conventionally uses $(obj)/ for generated files, and $(src)/ for
checked-in source files. It is merely a convention without any functional
difference. In fact, $(obj) and $(src) are exactly the same, as defined
in scripts/Makefile.build:
src := $(obj)
When the kernel is built in a separate output directory, $(src) does
not accurately reflect the source directory location. While Kbuild
resolves this discrepancy by specifying VPATH=$(srctree) to search for
source files, it does not cover all cases. For example, when adding a
header search path for local headers, -I$(srctree)/$(src) is typically
passed to the compiler.
This introduces inconsistency between upstream and downstream Makefiles
because $(src) is used instead of $(srctree)/$(src) for the latter.
To address this inconsistency, this commit changes the semantics of
$(src) so that it always points to the directory in the source tree.
Going forward, the variables used in Makefiles will have the following
meanings:
$(obj) - directory in the object tree
$(src) - directory in the source tree (changed by this commit)
$(objtree) - the top of the kernel object tree
$(srctree) - the top of the kernel source tree
Consequently, $(srctree)/$(src) in upstream Makefiles need to be replaced
with $(src).
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Reviewed-by: Nicolas Schier <nicolas@fjasle.eu>
2024-04-27 23:55:02 +09:00
|
|
|
|
2023-03-30 17:31:57 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-07-08 14:29:06 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|