From: Lizhi Hou <lizhi.hou@amd.com>
To: Mario Limonciello <superm1@kernel.org>, <ogabbay@kernel.org>,
<quic_jhugo@quicinc.com>, <dri-devel@lists.freedesktop.org>,
<karol.wachowski@linux.intel.com>
Cc: <linux-kernel@vger.kernel.org>, <max.zhen@amd.com>,
<sonal.santan@amd.com>
Subject: Re: [PATCH V1] accel/amdxdna: Disable device buffer exporting
Date: Thu, 28 May 2026 21:26:56 -0700 [thread overview]
Message-ID: <6817ecd8-cbf7-8ade-6926-7375bda20e73@amd.com> (raw)
In-Reply-To: <28dc206a-695d-482f-b434-c27eda960bfe@kernel.org>
Applied to drm-misc-next
On 5/28/26 14:19, Mario Limonciello wrote:
>
>
> On 5/26/26 19:50, Lizhi Hou wrote:
>> Device buffers are never intended to be exported. Disable exporting
>> support explicitly.
>>
>> Signed-off-by: Lizhi Hou <lizhi.hou@amd.com>
> Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>
>> ---
>> drivers/accel/amdxdna/amdxdna_gem.c | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/drivers/accel/amdxdna/amdxdna_gem.c
>> b/drivers/accel/amdxdna/amdxdna_gem.c
>> index 2dfdc56ba91d..2727e48afc0a 100644
>> --- a/drivers/accel/amdxdna/amdxdna_gem.c
>> +++ b/drivers/accel/amdxdna/amdxdna_gem.c
>> @@ -725,9 +725,15 @@ static int amdxdna_gem_dev_obj_vmap(struct
>> drm_gem_object *obj, struct iosys_map
>> return 0;
>> }
>> +static struct dma_buf *amdxdna_gem_dev_obj_export(struct
>> drm_gem_object *gobj, int flags)
>> +{
>> + return ERR_PTR(-EOPNOTSUPP);
>> +}
>> +
>> static const struct drm_gem_object_funcs amdxdna_gem_dev_obj_funcs = {
>> .free = amdxdna_gem_dev_obj_free,
>> .vmap = amdxdna_gem_dev_obj_vmap,
>> + .export = amdxdna_gem_dev_obj_export,
>> };
>> static const struct drm_gem_object_funcs amdxdna_gem_shmem_funcs = {
>
prev parent reply other threads:[~2026-05-29 4:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 18:50 Lizhi Hou
2026-05-28 21:19 ` Mario Limonciello
2026-05-29 4:26 ` Lizhi Hou [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=6817ecd8-cbf7-8ade-6926-7375bda20e73@amd.com \
--to=lizhi.hou@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=karol.wachowski@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=max.zhen@amd.com \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.com \
--cc=sonal.santan@amd.com \
--cc=superm1@kernel.org \
/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
all inboxes | Powered by JetHome®