From: Zhi Wang <zhi.wang.linux@gmail.com> To: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org, intel-gvt-dev@lists.freedesktop.org Cc: Zhi Wang <zhi.a.wang@intel.com> Subject: [PATCH v9 0/3] Refactor GVT-g MMIO tracking table and handlers Date: Thu, 7 Apr 2022 03:19:42 -0400 [thread overview] Message-ID: <20220407071945.72148-1-zhi.a.wang@intel.com> (raw) To support the new mdev interfaces and the re-factor patches from Christoph, which moves the GVT-g code into a dedicated module, the GVT-g initialization path has to be separated into two phases: a) Early initialization. The early initialization of GVT requires to be done when loading i915. Mostly it's because the initial clean HW state needs to be saved before i915 touches the HW. b) Late initalization. This phases of initalization will setup the rest components of GVT-g, which can be done later when the dedicated module is being loaded. To initialize the GVT-g MMIO tracking table in the early initalization stage, which will be done in i915, the GVT-g MMIO tracking table needs to be sperated accordingly and moved into i915. v9: - Fix a problem might casue kernel panic. v8: - Use SPDX header in the intel_gvt_mmio_table.c - Reference the gvt.h with path. (Jani) - Add a missing fix on mmio emulation path during my debug. - Fix a building problem on refreshed gvt-staging branch. (Christoph) v7: - Keep the marcos of device generation in GVT-g. (Christoph, Jani) v6: - Move the mmio_table.c into i915. (Christoph) - Keep init_device_info and related structures in GVT-g. (Christoph) - Refine the callbacks of the iterator. (Christoph) - Move the flags of MMIO register defination to GVT-g. (Chrsitoph) - Move the mmio block handling to GVT-g. v5: - Re-design the mmio table framework. (Christoph) v4: - Fix the errors of patch checking scripts. v3: - Fix the errors when CONFIG_DRM_I915_WERROR is turned on. (Jani) v2: - Implement a mmio table instead of generating it by marco in i915. (Jani) Zhi Wang (3): i915/gvt: Separate the MMIO tracking table from GVT-g i915/gvt: Save the initial HW state snapshot in i915 i915/gvt: Use the initial HW state snapshot saved in i915 drivers/gpu/drm/i915/Makefile | 2 +- drivers/gpu/drm/i915/gvt/firmware.c | 25 +- drivers/gpu/drm/i915/gvt/gvt.h | 3 +- drivers/gpu/drm/i915/gvt/handlers.c | 1033 ++------------- drivers/gpu/drm/i915/gvt/mmio.h | 1 - drivers/gpu/drm/i915/gvt/reg.h | 9 +- drivers/gpu/drm/i915/i915_drv.h | 2 + drivers/gpu/drm/i915/intel_gvt.c | 92 +- drivers/gpu/drm/i915/intel_gvt.h | 21 + drivers/gpu/drm/i915/intel_gvt_mmio_table.c | 1290 +++++++++++++++++++ 10 files changed, 1561 insertions(+), 917 deletions(-) create mode 100644 drivers/gpu/drm/i915/intel_gvt_mmio_table.c -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Zhi Wang <zhi.wang.linux@gmail.com> To: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org, intel-gvt-dev@lists.freedesktop.org Subject: [Intel-gfx] [PATCH v9 0/3] Refactor GVT-g MMIO tracking table and handlers Date: Thu, 7 Apr 2022 03:19:42 -0400 [thread overview] Message-ID: <20220407071945.72148-1-zhi.a.wang@intel.com> (raw) To support the new mdev interfaces and the re-factor patches from Christoph, which moves the GVT-g code into a dedicated module, the GVT-g initialization path has to be separated into two phases: a) Early initialization. The early initialization of GVT requires to be done when loading i915. Mostly it's because the initial clean HW state needs to be saved before i915 touches the HW. b) Late initalization. This phases of initalization will setup the rest components of GVT-g, which can be done later when the dedicated module is being loaded. To initialize the GVT-g MMIO tracking table in the early initalization stage, which will be done in i915, the GVT-g MMIO tracking table needs to be sperated accordingly and moved into i915. v9: - Fix a problem might casue kernel panic. v8: - Use SPDX header in the intel_gvt_mmio_table.c - Reference the gvt.h with path. (Jani) - Add a missing fix on mmio emulation path during my debug. - Fix a building problem on refreshed gvt-staging branch. (Christoph) v7: - Keep the marcos of device generation in GVT-g. (Christoph, Jani) v6: - Move the mmio_table.c into i915. (Christoph) - Keep init_device_info and related structures in GVT-g. (Christoph) - Refine the callbacks of the iterator. (Christoph) - Move the flags of MMIO register defination to GVT-g. (Chrsitoph) - Move the mmio block handling to GVT-g. v5: - Re-design the mmio table framework. (Christoph) v4: - Fix the errors of patch checking scripts. v3: - Fix the errors when CONFIG_DRM_I915_WERROR is turned on. (Jani) v2: - Implement a mmio table instead of generating it by marco in i915. (Jani) Zhi Wang (3): i915/gvt: Separate the MMIO tracking table from GVT-g i915/gvt: Save the initial HW state snapshot in i915 i915/gvt: Use the initial HW state snapshot saved in i915 drivers/gpu/drm/i915/Makefile | 2 +- drivers/gpu/drm/i915/gvt/firmware.c | 25 +- drivers/gpu/drm/i915/gvt/gvt.h | 3 +- drivers/gpu/drm/i915/gvt/handlers.c | 1033 ++------------- drivers/gpu/drm/i915/gvt/mmio.h | 1 - drivers/gpu/drm/i915/gvt/reg.h | 9 +- drivers/gpu/drm/i915/i915_drv.h | 2 + drivers/gpu/drm/i915/intel_gvt.c | 92 +- drivers/gpu/drm/i915/intel_gvt.h | 21 + drivers/gpu/drm/i915/intel_gvt_mmio_table.c | 1290 +++++++++++++++++++ 10 files changed, 1561 insertions(+), 917 deletions(-) create mode 100644 drivers/gpu/drm/i915/intel_gvt_mmio_table.c -- 2.25.1
next reply other threads:[~2022-04-07 7:19 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-07 7:19 Zhi Wang [this message] 2022-04-07 7:19 ` [Intel-gfx] [PATCH v9 0/3] Refactor GVT-g MMIO tracking table and handlers Zhi Wang 2022-04-07 7:19 ` [Intel-gfx] [PATCH v9 1/3] i915/gvt: Separate the MMIO tracking table from GVT-g Zhi Wang 2022-04-07 7:19 ` Zhi Wang 2022-04-07 7:19 ` Zhi Wang 2022-04-07 8:06 ` [Intel-gfx] " Christoph Hellwig 2022-04-07 8:06 ` Christoph Hellwig 2022-04-07 10:24 ` Wang, Zhi A 2022-04-07 10:24 ` [Intel-gfx] " Wang, Zhi A 2022-04-07 10:24 ` Wang, Zhi A 2022-04-07 13:20 ` Zhenyu Wang 2022-04-07 13:20 ` Zhenyu Wang 2022-04-07 13:20 ` [Intel-gfx] " Zhenyu Wang 2022-04-07 15:03 ` Jani Nikula 2022-04-07 15:03 ` [Intel-gfx] " Jani Nikula 2022-04-07 15:03 ` Jani Nikula 2022-04-08 14:07 ` Wang, Zhi A 2022-04-08 14:07 ` [Intel-gfx] " Wang, Zhi A 2022-04-08 14:07 ` Wang, Zhi A 2022-04-12 5:42 ` Wang, Zhi A 2022-04-12 5:42 ` [Intel-gfx] " Wang, Zhi A 2022-04-12 5:42 ` Wang, Zhi A 2022-04-13 9:31 ` Jani Nikula 2022-04-13 9:31 ` Jani Nikula 2022-04-13 9:31 ` [Intel-gfx] " Jani Nikula 2022-04-13 9:53 ` Wang, Zhi A 2022-04-13 9:53 ` [Intel-gfx] " Wang, Zhi A 2022-04-13 9:53 ` Wang, Zhi A 2022-04-13 10:18 ` Jani Nikula 2022-04-13 10:18 ` [Intel-gfx] " Jani Nikula 2022-04-13 10:18 ` Jani Nikula 2022-08-08 20:27 ` Alex Williamson 2022-08-08 20:27 ` [Intel-gfx] " Alex Williamson 2022-08-08 20:27 ` Alex Williamson 2022-04-07 7:19 ` [PATCH v9 2/3] i915/gvt: Save the initial HW state snapshot in i915 Zhi Wang 2022-04-07 7:19 ` Zhi Wang 2022-04-07 7:19 ` [Intel-gfx] " Zhi Wang 2022-04-07 7:19 ` [Intel-gfx] [PATCH v9 3/3] i915/gvt: Use the initial HW state snapshot saved " Zhi Wang 2022-04-07 7:19 ` Zhi Wang 2022-04-07 7:19 ` Zhi Wang 2022-04-07 7:48 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Refactor GVT-g MMIO tracking table and handlers (rev2) Patchwork
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=20220407071945.72148-1-zhi.a.wang@intel.com \ --to=zhi.wang.linux@gmail.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=intel-gfx@lists.freedesktop.org \ --cc=intel-gvt-dev@lists.freedesktop.org \ --cc=linux-kernel@vger.kernel.org \ --cc=zhi.a.wang@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: linkBe 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.