From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pekka Paalanen Subject: Re: [PATCH] drm: Funnel drm logs to tracepoints Date: Thu, 17 Oct 2019 10:22:16 +0300 Message-ID: <20191017102216.20f98533@eldfell.localdomain> References: <20191010204823.195540-1-sean@poorly.run> <242462f0-ac8d-ab8a-e567-74678da3f68f@suse.de> <20191015191156.GW85762@art_vandelay> <20191015200233.GK1208@intel.com> <20191016160557.73b634c9@eldfell.localdomain> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1374107109==" Return-path: Received: from mail-lj1-x242.google.com (mail-lj1-x242.google.com [IPv6:2a00:1450:4864:20::242]) by gabe.freedesktop.org (Postfix) with ESMTPS id 543FB6E453 for ; Thu, 17 Oct 2019 07:22:28 +0000 (UTC) Received: by mail-lj1-x242.google.com with SMTP id b20so1382478ljj.5 for ; Thu, 17 Oct 2019 00:22:28 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Thomas Zimmermann Cc: David Airlie , Daniel Vetter , dri-devel , Sean Paul , Sean Paul List-Id: dri-devel@lists.freedesktop.org --===============1374107109== Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/ueu3hbQR1BEgUBw8zqwu85e"; protocol="application/pgp-signature" --Sig_/ueu3hbQR1BEgUBw8zqwu85e Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Wed, 16 Oct 2019 15:23:45 +0200 Thomas Zimmermann wrote: > Hi >=20 > Am 16.10.19 um 15:05 schrieb Pekka Paalanen: > > specifically be available in production. So a new file in some fs > > somewhere it should be, and userspace in production can read it at will > > to attach to a bug report. > >=20 > > Those semantics, "only use this content for attaching into a bug > > report" should be made very clear in the UAPI. =20 >=20 > Has this ever worked? As soon as a userspace program starts depending on > the content of this file, it becomes kabi. From the incidents I know, > Linus has always been quite strict about this. Even for broken interfaces. The kernel log content is not kabi, is it? I've seen it change plenty during the years. This would be just another similar log with free-form text. Thanks, pq --Sig_/ueu3hbQR1BEgUBw8zqwu85e Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEJQjwWQChkWOYOIONI1/ltBGqqqcFAl2oFqgACgkQI1/ltBGq qqdtgxAAhgLNYtWGWk8fEwO+DxtAMsqB6idCLwVIyNwAAzNKqX81vsoFthQGGHx5 69Jbo7M3n1EFJyff9V+8g5KRaUeI0tKDX/y4v+Dh1yo1c4CAtq+8QCsUmIdYmW6S se5Yykfrh49MNSmTReAj9JXN6uVCOVDs+eo/WRw19HRhNH85IqMoRm5JF64/bNB5 qj+uU6W7RISW5FPGognQcZrb5Ho+FRkbq4Ms6fJ/41hyB6+icdz+t6q3lnm0g0qv g07IEW9leiDc/KKV+4wkitYyq5+CLoat9ccYdee1krmMjHNyDfU9z6cepliHGmPQ Qt+KwOXS752Dw1nm0mXWD0onOWzcj5fS5CVIJhBg738tMWfcmMC6Ff6UY0w+6DC3 NRXaDKtn/ZOcju2X/eik7EAHmLFa92GikOF9OHmy46E9csikibg6FyvOrzGEmRvl w+2LuEKF54Ejs2cq/KUibe7EeenL1IdM868sdNx/A1zlYV6WnBluimeRrJ1kw3Mx lvumxIwDuaQd837WYv8I+xgqTq6yiOmYGbpMpkTOas621EUuK4F9OxvvrCJEhdEX tAxaLD9wH8gLjMQ1pUIoyP0+m452TgcUHLJ90ecdZCv3xpknL9zN/DzVRyBJj36C /eV6zGOaWGUDwAEM1F+rCfjuAq+o1kOxcbVnLWhoBenVZjKYaRk= =v/JI -----END PGP SIGNATURE----- --Sig_/ueu3hbQR1BEgUBw8zqwu85e-- --===============1374107109== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1374107109==--