From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 55BB7C77B7C for ; Tue, 2 May 2023 01:27:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232233AbjEBB1Z (ORCPT ); Mon, 1 May 2023 21:27:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60962 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229863AbjEBB1W (ORCPT ); Mon, 1 May 2023 21:27:22 -0400 Received: from fanzine2.igalia.com (fanzine2.igalia.com [213.97.179.56]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3E0E91BD5 for ; Mon, 1 May 2023 18:27:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=igalia.com; s=20170329; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:Cc:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=Noh8dh1b4WPIoxf4HR9EfS1PEP8OXfWwFlkMnrqSJgA=; b=f/3itorim1T01FtfuNs/wyggyn thoXJ3Fm8vg3a/VFbFm0O1wkZRM9eCwj9L7wafJBUJw3K4U9DBzoIYlplwmRtpffjXS/zS4jBDt0E twbBqUi7W+7gQPzWlrwmd0uyc/cE4Dj0djgc26a1pEH8oj3kTljQ+G9buNhcp5eq8ayJRaZQdf/N8 iRXecYndjLmn3JsUs5HWekB0mnxx+zhxGhDCtRxYWYqI0vY6lHj2j4y24ITWaZa9DNQVe7uijjU7J NqQgcWjWZxSN9hS4L9n9UOEH9gZuPTSMqUqv19IwgK7XLL1RRZ+opuENlS4wdOZwPn3rEJINbkldH R1LVHDdA==; Received: from [179.113.250.147] (helo=[192.168.1.111]) by fanzine2.igalia.com with esmtpsa (Cipher TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_128_GCM:128) (Exim) id 1ptenS-00HByc-Ab; Tue, 02 May 2023 03:27:14 +0200 Message-ID: <6ab2ff76-4518-6fac-071e-5d0d5adc4fcd@igalia.com> Date: Mon, 1 May 2023 22:26:24 -0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 Subject: Re: [RFC PATCH 0/1] Add AMDGPU_INFO_GUILTY_APP ioctl To: Alex Deucher Cc: dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org, pierre-eric.pelloux-prayer@amd.com, =?UTF-8?B?TWFyZWsgT2zFocOhaw==?= , =?UTF-8?Q?Timur_Krist=c3=b3f?= , michel.daenzer@mailbox.org, Samuel Pitoiset , kernel-dev@igalia.com, Bas Nieuwenhuizen , alexander.deucher@amd.com, christian.koenig@amd.com References: <20230501185747.33519-1-andrealmeid@igalia.com> Content-Language: en-US From: =?UTF-8?Q?Andr=c3=a9_Almeida?= In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em 01/05/2023 16:24, Alex Deucher escreveu: > On Mon, May 1, 2023 at 2:58 PM André Almeida wrote: >> >> I know that devcoredump is also used for this kind of information, but I believe >> that using an IOCTL is better for interfacing Mesa + Linux rather than parsing >> a file that its contents are subjected to be changed. > > Can you elaborate a bit on that? Isn't the whole point of devcoredump > to store this sort of information? > I think that devcoredump is something that you could use to submit to a bug report as it is, and then people can read/parse as they want, not as an interface to be read by Mesa... I'm not sure that it's something that I would call an API. But I might be wrong, if you know something that uses that as an API please share. Anyway, relying on that for Mesa would mean that we would need to ensure stability for the file content and format, making it less flexible to modify in the future and probe to bugs, while the IOCTL is well defined and extensible. Maybe the dump from Mesa + devcoredump could be complementary information to a bug report.