dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Lizhi Hou <lizhi.hou@amd.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
	<ogabbay@kernel.org>, <quic_jhugo@quicinc.com>,
	<jacek.lawrynowicz@linux.intel.com>,
	<dri-devel@lists.freedesktop.org>
Cc: <linux-kernel@vger.kernel.org>, <max.zhen@amd.com>,
	<sonal.santan@amd.com>
Subject: Re: [PATCH V1] accel/amdxdna: Add ioctl DRM_IOCTL_AMDXDNA_GET_ARRAY
Date: Tue, 26 Aug 2025 11:10:25 -0700	[thread overview]
Message-ID: <b3874221-5b4f-9625-de8a-4e54dc6884a2@amd.com> (raw)
In-Reply-To: <b758a72f-e30e-42f9-a6aa-6f6297b8cce3@amd.com>


On 8/26/25 10:58, Mario Limonciello wrote:
> On 8/26/2025 12:55 PM, Lizhi Hou wrote:
>>
>> On 8/26/25 10:18, Mario Limonciello wrote:
>>> On 8/25/2025 11:48 PM, Lizhi Hou wrote:
>>>>
>>>> On 8/25/25 14:28, Mario Limonciello wrote:
>>>>> On 8/22/2025 12:23 PM, Lizhi Hou wrote:
>>>>>> Add interface for applications to get information array. The 
>>>>>> application
>>>>>> provides a buffer pointer along with information type, maximum 
>>>>>> number of
>>>>>> entries and maximum size of each entry. The buffer may also 
>>>>>> contain match
>>>>>> conditions based on the information type. After the ioctl 
>>>>>> completes, the
>>>>>> actual number of entries and entry size are returned.
>>>>>>
>>>>>> Signed-off-by: Lizhi Hou <lizhi.hou@amd.com>
>>>>>
>>>>> How does userspace discover whether or not the new IOCTL call is 
>>>>> supported?  Just a test call?
>>>> The kernel header version will be used to determine whether the 
>>>> application which uses new IOCTL will be compiled or not.
>>>>
>>>
>>> But it's not actually an application compile time decision, it's a 
>>> runtime decision.  IE I can compile an application with the headers 
>>> on kernel 6.18 that has this, but if I try to run it on 6.15 it's 
>>> going to barf.
>>>
>>> To some extent that comes with the territory, but I'm wondering if a 
>>> better solution going forward would be for there to be a dedicated 
>>> version command that you bump.
>>
>> For in-tree driver, I did not aware a common way for this other than 
>> checking the kernel version.
>>
>> And here is qaic patch of adding a new IOCTL.
>>
>> https://github.com/torvalds/linux/ 
>> commit/217b812364d360e1933d8485f063400e5dda7d66
>>
>>
>> I know there is major, minor, patchlevel in struct drm_driver. And I 
>> think that is not required for in-tree driver.
>>
>> Please let me know if I missed anything.
>>
>> Thanks,
>
> Right; so bump up one of those so that userspace can check it. Maybe 
> "minor"?

I meant for in-tree driver, is it good enough for userspace to just 
check kernel version?  E.g. The drm driver versions are not used by ivpu 
or qaic.

Thanks,

Lizhi


  reply	other threads:[~2025-08-26 18:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-22 17:23 [PATCH V1] accel/amdxdna: Add ioctl DRM_IOCTL_AMDXDNA_GET_ARRAY Lizhi Hou
2025-08-25 21:28 ` Mario Limonciello
2025-08-26  4:48   ` Lizhi Hou
2025-08-26 17:18     ` Mario Limonciello
2025-08-26 17:55       ` Lizhi Hou
2025-08-26 17:58         ` Mario Limonciello
2025-08-26 18:10           ` Lizhi Hou [this message]
2025-08-27  0:31             ` Mario Limonciello
2025-08-27 16:41               ` Lizhi Hou
2025-08-27 18:09                 ` Mario Limonciello
2025-08-27 20:06                   ` Lizhi Hou

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=b3874221-5b4f-9625-de8a-4e54dc6884a2@amd.com \
    --to=lizhi.hou@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jacek.lawrynowicz@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=max.zhen@amd.com \
    --cc=ogabbay@kernel.org \
    --cc=quic_jhugo@quicinc.com \
    --cc=sonal.santan@amd.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;
as well as URLs for NNTP newsgroup(s).