Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
Cc: <igt-dev@lists.freedesktop.org>,
	<kamil.konieczny@linux.intel.com>, <krzysztof.karas@intel.com>,
	<krzysztof.niemiec@intel.com>
Subject: Re: [PATCH i-g-t 00/25] tools: remove unnecessary shared library
Date: Wed, 24 Jun 2026 09:33:22 -0700	[thread overview]
Message-ID: <878q83q4od.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <cover.1782288071.git.sebastian.brzezinka@intel.com>

On Wed, 24 Jun 2026 01:47:07 -0700, Sebastian Brzezinka wrote:
>
> Standalone tools linked libigt.so as a side effect, pulling in cairo,
> pixman and libX11 even without framebuffer use.
>
> Following intel_gpu_top's approach, each tool now links only the static
> sub-libraries it needs. Five new ones are introduced:
>
> lib_igt_tools_stub, lib_igt_drm_stub, lib_igt_halffloat,
> lib_i915_decode, lib_igt_reg_tools.

So I am trying to figure out what is the "real" reason for doing this.

If tomorrow the tool uses a function which is not present in the tiny
library but in the big library, what are we going to do? So, isn't it
better to link against one big library, rather than tiny libraries?

Since it should use dynamic linking, it is not that the size of the
executable will change one way or the other.

So what is driving this change? Maybe I am missing something.

Thanks.
--
Ashutosh

  parent reply	other threads:[~2026-06-24 16:33 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-24  8:47 [PATCH i-g-t 00/25] tools: remove unnecessary shared library Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 01/25] tools: igt_stats: drop libigt.so, link against minimal sub-libraries Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 02/25] tools: intel_firmware_decode: " Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 03/25] lib: extend igt_tools_stub with additional stubs needed by tools Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 04/25] lib: introduce lib_igt_drm_stub for tools needing driver detection Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 05/25] lib: introduce lib_igt_halffloat static sub-library for tools Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 06/25] lib: introduce lib_i915_decode " Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 07/25] lib: introduce lib_igt_reg_tools " Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 08/25] tools: intel_gpu_frequency: drop libigt.so, link against minimal sub-libraries Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 09/25] lib/i915: intel_decode: replace igt.h with minimal headers Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 10/25] tools: intel_stepping: drop libigt.so, link against minimal sub-libraries Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 11/25] tools: intel_gtt: " Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 12/25] tools: intel_error_decode: " Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 13/25] tools: intel_vbt_decode: " Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 14/25] tools: intel_backlight: " Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 15/25] tools: intel_lid: " Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 16/25] tools: intel_gpu_time: " Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 17/25] tools: intel_audio_dump: " Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 18/25] tools: intel_forcewaked: " Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 19/25] tools: intel_guc_logger: " Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 20/25] tools: intel_infoframes: " Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 21/25] tools: intel_panel_fitter: " Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 22/25] tools: intel_watermark: " Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 23/25] tools: intel_display_poller: " Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 24/25] tools: intel_gvtg_test: " Sebastian Brzezinka
2026-06-24  8:47 ` [PATCH i-g-t 25/25] tools: lsgpu: " Sebastian Brzezinka
2026-06-24 10:35 ` ✓ i915.CI.BAT: success for tools: remove unnecessary shared library Patchwork
2026-06-24 10:39 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-24 12:10 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-06-24 16:33 ` Dixit, Ashutosh [this message]
2026-06-24 18:33 ` ✗ i915.CI.Full: " 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=878q83q4od.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=krzysztof.karas@intel.com \
    --cc=krzysztof.niemiec@intel.com \
    --cc=sebastian.brzezinka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox