From: Lizhi Hou <lizhi.hou@amd.com>
To: "Taimuraz Kaitmazov" <taimuraz@kaitmazov.com>,
"Alex Deucher" <alexdeucher@gmail.com>,
"Christian König" <christian.koenig@amd.com>
Cc: Min Ma <mamin506@gmail.com>, Oded Gabbay <ogabbay@kernel.org>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
Max Zhen <max.zhen@amd.com>, Sonal Santan <sonal.santan@amd.com>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<linux-media@vger.kernel.org>
Subject: Re: [PATCH v2 0/5] accel/amdxdna: honour the SYNC_BO range
Date: Thu, 13 Aug 2026 14:02:27 -0700 [thread overview]
Message-ID: <9e7444c7-7a2a-5946-6197-86676de0cbb2@amd.com> (raw)
In-Reply-To: <20260813201416.158728-1-taimuraz@kaitmazov.com>
On 8/13/26 13:14, Taimuraz Kaitmazov wrote:
> On 8/13/26 23:06, Alex Deucher wrote:
>> I wonder if there is some device config option to enable snooped vs.
>> non-snooped DMAs?
> I tried the PCIe one. Clearing Enable No Snoop in DevCtl, with lspci then showing NoSnoop-, changes nothing: same 20 out of 20 stale both ways. So the array either isn't carrying the attribute or isn't looking at it.
Yes. It is known that the legacy hardware has problem to support snoop.
In your case, the XRT's buffer::sync() could be used.
Lizhi
>
> Taimuraz
>
>
next prev parent reply other threads:[~2026-08-13 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260811231351.1011244-1-taimuraz@kaitmazov.com>
2026-08-12 8:57 ` [PATCH v2 0/5] accel/amdxdna: honour the SYNC_BO range Christian König
2026-08-12 15:45 ` Lizhi Hou
2026-08-13 7:44 ` Christian König
2026-08-13 18:08 ` Lizhi Hou
2026-08-13 18:54 ` Alex Deucher
[not found] ` <20260813195059.149991-1-taimuraz@kaitmazov.com>
2026-08-13 20:06 ` Alex Deucher
[not found] ` <20260813201416.158728-1-taimuraz@kaitmazov.com>
2026-08-13 21:02 ` Lizhi Hou [this message]
[not found] ` <20260813182905.124248-1-taimuraz@kaitmazov.com>
2026-08-13 19:01 ` Lizhi Hou
2026-08-14 7:59 ` Christian König
2026-08-17 17:56 ` 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=9e7444c7-7a2a-5946-6197-86676de0cbb2@amd.com \
--to=lizhi.hou@amd.com \
--cc=alexdeucher@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mamin506@gmail.com \
--cc=max.zhen@amd.com \
--cc=ogabbay@kernel.org \
--cc=sonal.santan@amd.com \
--cc=sumit.semwal@linaro.org \
--cc=taimuraz@kaitmazov.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