From: Alex Deucher <alexdeucher@gmail.com>
To: mchehab@kernel.org
Cc: markus.dobel@gmx.de, Brad Love <brad@nextdimension.cc>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH] Revert 95f408bb Ryzen DMA related RiSC engine stall fixes
Date: Thu, 6 Dec 2018 13:36:24 -0500 [thread overview]
Message-ID: <CADnq5_P-jQWQMLnJcESZf8ygPheE3F5XUq8isB9jXzCKa=L=Og@mail.gmail.com> (raw)
In-Reply-To: <20181206160145.2d23ac0e@coco.lan>
On Thu, Dec 6, 2018 at 1:05 PM Mauro Carvalho Chehab <mchehab@kernel.org> wrote:
>
> Em Thu, 06 Dec 2018 18:18:23 +0100
> Markus Dobel <markus.dobel@gmx.de> escreveu:
>
> > Hi everyone,
> >
> > I will try if the hack mentioned fixes the issue for me on the weekend (but I assume, as if effectively removes the function).
>
> It should, but it keeps a few changes. Just want to be sure that what
> would be left won't cause issues. If this works, the logic that would
> solve Ryzen DMA fixes will be contained into a single point, making
> easier to maintain it.
>
> >
> > Just in case this is of interest, I neither have Ryzen nor Intel, but an HP Microserver G7 with an AMD Turion II Neo N54L, so the machine is more on the slow side.
>
> Good to know. It would probably worth to check if this Ryzen
> bug occors with all versions of it or with just a subset.
> I mean: maybe it is only at the first gen or Ryzen and doesn't
> affect Ryzen 2 (or vice versa).
The original commit also mentions some Xeons are affected too. Seems
like this is potentially an issue on the device side rather than the
platform.
>
> The PCI quirks logic will likely need to detect the PCI ID of
> the memory controllers found at the buggy CPUs, in order to enable
> the quirk only for the affected ones.
>
> It could be worth talking with AMD people in order to be sure about
> the differences at the DMA engine side.
>
It's not clear to me what the pci or platform quirk would do. The
workaround seems to be in the driver, not on the platform.
Alex
next prev parent reply other threads:[~2018-12-06 18:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-21 13:45 [PATCH] Revert 95f408bb Ryzen DMA related RiSC engine stall fixes Markus Dobel
2018-12-05 11:07 ` Mauro Carvalho Chehab
2018-12-06 16:37 ` Brad Love
2018-12-06 17:18 ` Markus Dobel
2018-12-06 18:01 ` Mauro Carvalho Chehab
2018-12-06 18:36 ` Alex Deucher [this message]
2018-12-06 19:07 ` Mauro Carvalho Chehab
2018-12-06 19:32 ` Mauro Carvalho Chehab
2018-12-18 22:59 ` [PATCH v2] cx23885: only reset DMA on problematic CPUs Brad Love
2018-12-18 23:49 ` Alex Deucher
2018-12-19 17:26 ` Brad Love
2018-12-19 17:40 ` Brad Love
2018-12-19 11:08 ` Matthias Schwarzott
2018-12-19 17:09 ` Brad Love
2018-12-19 17:07 ` [PATCH v3] " Brad Love
2018-12-20 13:43 ` Mauro Carvalho Chehab
2018-12-16 10:37 ` [PATCH] Revert 95f408bb Ryzen DMA related RiSC engine stall fixes Markus Dobel
2018-12-16 14:23 ` Mauro Carvalho Chehab
2018-12-18 2:05 ` Alex Deucher
2018-12-18 6:32 ` Markus Dobel
2018-12-18 12:45 ` Mauro Carvalho Chehab
2018-12-18 23:11 ` Brad Love
2018-12-18 23:46 ` Alex Deucher
2018-12-19 0:05 ` Brad Love
2018-12-19 0:08 ` Brad Love
2018-12-19 19:07 ` Alex Deucher
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='CADnq5_P-jQWQMLnJcESZf8ygPheE3F5XUq8isB9jXzCKa=L=Og@mail.gmail.com' \
--to=alexdeucher@gmail.com \
--cc=brad@nextdimension.cc \
--cc=linux-media@vger.kernel.org \
--cc=markus.dobel@gmx.de \
--cc=mchehab@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.