public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Uwe Kleine-König (The Capable Hub)"
	<u.kleine-koenig@baylibre.com>
Cc: "Matthew Brost" <matthew.brost@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/xe: Don't emit UTS_RELEASE as part of device coredump
Date: Tue, 28 Apr 2026 11:08:21 +0300	[thread overview]
Message-ID: <9c7244e954a12e2026d1148e4e9c75f02f9d6071@intel.com> (raw)
In-Reply-To: <ae_dpnVNS4liMfxe@intel.com>

On Mon, 27 Apr 2026, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> On Mon, Apr 27, 2026 at 06:09:03PM +0200, Uwe Kleine-König (The Capable Hub) wrote:
>> UTS_RELEASE changes quite easily (e.g. uncommitted changes in the source
>
> we know, this is exactly why we use it ;)
> We want to be able to differentiate if it is a distro build versus custom build.
>
>> tree or new commits). So when checking if a patch introduces changes to the
>> resulting binary each usage of UTS_RELEASE is a source of annoyance as
>> it introduces changes not caused by the change under test.

Would it help to use init_uts_ns.name.release from
init/version-timestamp.c instead of UTS_RELEASE? No rebuilds, info
retained.

BR,
Jani.



>> 
>> It's little helpful to emit the kernel version in the device coredump, so
>> drop the kernel version line from it.
>
> That's a driver decision, no?!
> We think it is useful and this change breaks the tools that are parsing it.
> So, please drop this patch.
>
> Thanks,
> Rodrigo.
>
>> 
>> Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
>> ---
>> Hello,
>> 
>> I'm not really sure if my assertion above that the kernel version isn't
>> helpful is actually true.
>> 
>> If yes, there are a few more very similar changes to make:
>> 
>> 	$ git grep -E 'drm_p.*UTS_RELEASE' v7.1-rc1 drivers/gpu/
>> 	v7.1-rc1:drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.c:      drm_printf(&p, "kernel: " UTS_RELEASE "\n");
>> 	v7.1-rc1:drivers/gpu/drm/msm/disp/msm_disp_snapshot_util.c:     drm_printf(p, "kernel: " UTS_RELEASE "\n");
>> 	v7.1-rc1:drivers/gpu/drm/msm/msm_gpu.c: drm_printf(&p, "kernel: " UTS_RELEASE "\n");
>> 	v7.1-rc1:drivers/gpu/drm/xe/xe_devcoredump.c:   drm_puts(&p, "kernel: " UTS_RELEASE "\n");
>> 
>> Best regards
>> Uwe
>> 
>>  drivers/gpu/drm/xe/xe_devcoredump.c | 1 -
>>  1 file changed, 1 deletion(-)
>> 
>> diff --git a/drivers/gpu/drm/xe/xe_devcoredump.c b/drivers/gpu/drm/xe/xe_devcoredump.c
>> index 558a1a9841a0..260e3f19286b 100644
>> --- a/drivers/gpu/drm/xe/xe_devcoredump.c
>> +++ b/drivers/gpu/drm/xe/xe_devcoredump.c
>> @@ -101,7 +101,6 @@ static ssize_t __xe_devcoredump_read(char *buffer, ssize_t count,
>>  
>>  	drm_puts(&p, "**** Xe Device Coredump ****\n");
>>  	drm_printf(&p, "Reason: %s\n", ss->reason);
>> -	drm_puts(&p, "kernel: " UTS_RELEASE "\n");
>>  	drm_puts(&p, "module: " KBUILD_MODNAME "\n");
>>  
>>  	ts = ktime_to_timespec64(ss->snapshot_time);
>> 
>> base-commit: 254f49634ee16a731174d2ae34bc50bd5f45e731
>> -- 
>> 2.47.3
>> 

-- 
Jani Nikula, Intel

      reply	other threads:[~2026-04-28  8:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260427160902.1126027-2-u.kleine-koenig@baylibre.com>
2026-04-27 22:05 ` [PATCH] drm/xe: Don't emit UTS_RELEASE as part of device coredump Rodrigo Vivi
2026-04-28  8:08   ` Jani Nikula [this message]

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=9c7244e954a12e2026d1148e4e9c75f02f9d6071@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.brost@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=u.kleine-koenig@baylibre.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