On Thu, Apr 17, 2025 at 8:30 PM Fugang Duan <fugang.d...@cixtech.com> wrote:
>
> 发件人: Alex Deucher <alexdeuc...@gmail.com> 发送时间: 2025年4月17日 21:08
> >On Wed, Apr 16, 2025 at 8:43 PM Fugang Duan <fugang.d...@cixtech.com> wrote:
> >>
> >> 发件人: Alex Deucher <alexdeuc...@gmail.com> 发送时间: 2025年4月16日
> >22:49
> >> >收件人: Alexey Klimov <alexey.kli...@linaro.org> On Wed, Apr 16, 2025 at
> >> >9:48 AM Alexey Klimov <alexey.kli...@linaro.org> wrote:
> >> >>
> >> >> On Wed Apr 16, 2025 at 4:12 AM BST, Fugang Duan wrote:
> >> >> > 发件人: Alexey Klimov <alexey.kli...@linaro.org> 发送时间: 2025年4
> >月16
> >> >日 2:28
> >> >> >>#regzbot introduced: v6.12..v6.13
> >> >>
> >> >> [..]
> >> >>
> >> >> >>The only change related to hdp_v5_0_flush_hdp() was
> >> >> >>cf424020e040 drm/amdgpu/hdp5.0: do a posting read when flushing
> >> >> >>HDP
> >> >> >>
> >> >> >>Reverting that commit ^^ did help and resolved that problem.
> >> >> >>Before sending revert as-is I was interested to know if there
> >> >> >>supposed to be a proper fix for this or maybe someone is
> >> >> >>interested to debug this or
> >> >have any suggestions.
> >> >> >>
> >> >> > Can you revert the change and try again
> >> >> > https://gitlab.com/linux-kernel/linux/-/commit/cf424020e040be35df
> >> >> > 05b
> >> >> > 682b546b255e74a420f
> >> >>
> >> >> Please read my email in the first place.
> >> >> Let me quote just in case:
> >> >>
> >> >> >The only change related to hdp_v5_0_flush_hdp() was
> >> >> >cf424020e040 drm/amdgpu/hdp5.0: do a posting read when flushing
> >> >> >HDP
> >> >>
> >> >> >Reverting that commit ^^ did help and resolved that problem.
> >> >
> >> >We can't really revert the change as that will lead to coherency
> >> >problems.  What is the page size on your system?  Does the attached patch
> >fix it?
> >> >
> >> >Alex
> >> >
> >> 4K page size.  We can try the fix if we got the environment.
> >
> >OK.  that patch won't change anything then.  Can you try this patch instead?
> >
> >Alex
> >
> Alex, it is very sorry that our team don't have the GPU card in hands.
> It is better to ask amd gfx team help to try the fixes.

Sorry, we don't have the problematic arm board.  This code works as
expected on x86.

Alex

>
> >>
> >> Fugang
> >>
> >>
> >>
> >> This email (including its attachments) is intended only for the person or 
> >> entity
> >to which it is addressed and may contain information that is privileged,
> >confidential or otherwise protected from disclosure. Unauthorized use,
> >dissemination, distribution or copying of this email or the information 
> >herein
> >or taking any action in reliance on the contents of this email or the 
> >information
> >herein, by anyone other than the intended recipient, or an employee or agent
> >responsible for delivering the message to the intended recipient, is strictly
> >prohibited. If you are not the intended recipient, please do not read, copy,
> >use or disclose any part of this e-mail to others. Please notify the sender
> >immediately and permanently delete this e-mail and any attachments if you
> >received it in error. Internet communications cannot be guaranteed to be 
> >timely,
> >secure, error-free or virus-free. The sender does not accept liability for 
> >any
> >errors or omissions.
>
>
> This email (including its attachments) is intended only for the person or 
> entity to which it is addressed and may contain information that is 
> privileged, confidential or otherwise protected from disclosure. Unauthorized 
> use, dissemination, distribution or copying of this email or the information 
> herein or taking any action in reliance on the contents of this email or the 
> information herein, by anyone other than the intended recipient, or an 
> employee or agent responsible for delivering the message to the intended 
> recipient, is strictly prohibited. If you are not the intended recipient, 
> please do not read, copy, use or disclose any part of this e-mail to others. 
> Please notify the sender immediately and permanently delete this e-mail and 
> any attachments if you received it in error. Internet communications cannot 
> be guaranteed to be timely, secure, error-free or virus-free. The sender does 
> not accept liability for any errors or omissions.

Reply via email to