From: Jani Nikula <jani.nikula@linux.intel.com>
To: Karolina Stolarek <karolina.stolarek@intel.com>,
dri-devel@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Karolina Stolarek" <karolina.stolarek@intel.com>,
"Christian König" <christian.koenig@amd.com>,
"kernel test robot" <lkp@intel.com>
Subject: Re: [PATCH v2 1/5] drm/ttm: Update Makefile for KUnit
Date: Mon, 11 Sep 2023 13:49:34 +0300 [thread overview]
Message-ID: <87fs3lf0ht.fsf@intel.com> (raw)
In-Reply-To: <3782fd55e8479296daab7041430fe7b0848bf621.1694422112.git.karolina.stolarek@intel.com>
On Mon, 11 Sep 2023, Karolina Stolarek <karolina.stolarek@intel.com> wrote:
> Update Makefile so it can produce a module that consists of TTM tests.
> This will allow us to test non-exported functions when KUnit tests
> are built as a module. Remove the tests' Makefile.
I'm asking questions instead of making assertions, because I'm not 100%
confident, but I don't feel like this Makefile could work right.
>
> Signed-off-by: Karolina Stolarek <karolina.stolarek@intel.com>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202309010358.50gYLkmw-lkp@intel.com/
> Closes: https://lore.kernel.org/oe-kbuild-all/202309011134.bwvpuyOj-lkp@intel.com/
> Closes: https://lore.kernel.org/oe-kbuild-all/202309011935.bBpezbUQ-lkp@intel.com/
> ---
> drivers/gpu/drm/ttm/Makefile | 18 +++++++++++++-----
> drivers/gpu/drm/ttm/tests/Makefile | 6 ------
> 2 files changed, 13 insertions(+), 11 deletions(-)
> delete mode 100644 drivers/gpu/drm/ttm/tests/Makefile
>
> diff --git a/drivers/gpu/drm/ttm/Makefile b/drivers/gpu/drm/ttm/Makefile
> index dad298127226..6322a33e65ed 100644
> --- a/drivers/gpu/drm/ttm/Makefile
> +++ b/drivers/gpu/drm/ttm/Makefile
> @@ -2,10 +2,18 @@
> #
> # Makefile for the drm device driver. This driver provides support for the
>
> -ttm-y := ttm_tt.o ttm_bo.o ttm_bo_util.o ttm_bo_vm.o ttm_module.o \
> - ttm_execbuf_util.o ttm_range_manager.o ttm_resource.o ttm_pool.o \
> - ttm_device.o ttm_sys_manager.o
> +ttm := ttm_tt.o ttm_bo.o ttm_bo_util.o ttm_bo_vm.o ttm_module.o \
> + ttm_execbuf_util.o ttm_range_manager.o ttm_resource.o ttm_pool.o \
> + ttm_device.o ttm_sys_manager.o
> +obj-$(CONFIG_DRM_TTM) += $(ttm)
Does that not lead to each object in $(ttm) becoming its own module?
> ttm-$(CONFIG_AGP) += ttm_agp_backend.o
Does this not create a ttm.o with just one object, depending on
CONFIG_AGP?
>
> -obj-$(CONFIG_DRM_TTM) += ttm.o
> -obj-$(CONFIG_DRM_TTM_KUNIT_TEST) += tests/
> +ttm-tests := tests/ttm_kunit_helpers.o tests/ttm_device_test.o \
> + tests/ttm_pool_test.o
I'd preserve the one object per line syntax. It's nicer for the diffs in
subsequent updates.
> +
> +ifeq ($(CONFIG_DRM_TTM_KUNIT_TEST),m)
> + ttm-test-objs := $(ttm) $(ttm-tests)
Isn't the -objs syntax for host/userspace programs? And if not, doesn't
it lead to objects with exported symbols being present in two places?
Confused.
BR,
Jani.
> + obj-m := ttm-test.o
> +else
> + obj-$(CONFIG_DRM_TTM_KUNIT_TEST) += $(ttm-tests)
> +endif
> diff --git a/drivers/gpu/drm/ttm/tests/Makefile b/drivers/gpu/drm/ttm/tests/Makefile
> deleted file mode 100644
> index ec87c4fc1ad5..000000000000
> --- a/drivers/gpu/drm/ttm/tests/Makefile
> +++ /dev/null
> @@ -1,6 +0,0 @@
> -# SPDX-License-Identifier: GPL-2.0 AND MIT
> -
> -obj-$(CONFIG_DRM_TTM_KUNIT_TEST) += \
> - ttm_device_test.o \
> - ttm_pool_test.o \
> - ttm_kunit_helpers.o
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-09-11 10:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 10:17 [PATCH v2 0/5] Improve test coverage of TTM Karolina Stolarek
2023-09-11 10:17 ` [PATCH v2 1/5] drm/ttm: Update Makefile for KUnit Karolina Stolarek
2023-09-11 10:49 ` Jani Nikula [this message]
2023-09-11 11:47 ` Karolina Stolarek
2023-09-11 13:12 ` Christian König
2023-09-11 13:33 ` Karolina Stolarek
2023-09-11 13:42 ` Christian König
2023-09-12 9:51 ` Karolina Stolarek
2023-09-12 9:59 ` Christian König
2023-09-11 10:17 ` [PATCH v2 2/5] drm/ttm/tests: Add tests for ttm_resource and ttm_sys_man Karolina Stolarek
2023-09-11 10:17 ` [PATCH v2 3/5] drm/ttm/tests: Add tests for ttm_tt Karolina Stolarek
2023-09-11 10:17 ` [PATCH v2 4/5] drm/ttm/tests: Add tests for ttm_bo functions Karolina Stolarek
2023-09-11 10:18 ` [PATCH v2 5/5] drm/ttm/tests: Don't pass order as page flags Karolina Stolarek
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=87fs3lf0ht.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=karolina.stolarek@intel.com \
--cc=lkp@intel.com \
--cc=thomas.hellstrom@linux.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 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.