From: Jan.Glauber@cavium.com (Jan Glauber)
To: linux-arm-kernel@lists.infradead.org
Subject: DMA remote memcpy requests
Date: Mon, 22 Oct 2018 15:33:08 +0000 [thread overview]
Message-ID: <20181022153300.GB10359@hc> (raw)
In-Reply-To: <DM6PR04MB40594025419A9A12707C7BB6F2F40@DM6PR04MB4059.namprd04.prod.outlook.com>
On Mon, Oct 22, 2018 at 02:39:00PM +0000, Adam Cottrel wrote:
> Dear Jan,
>
> As I understand this, to turn off I need to re-compile without SMMU driver support via the kernel config flags.
>
> However, if I turn the SMU off, how will the system cope?
The SMMU should be optional, but I didn't try it myselfs so bad things
might happen...
Regards,
Jan
> Best,
> Adam
>
> > -----Original Message-----
> > From: Jan Glauber <Jan.Glauber@cavium.com>
> > Sent: 22 October 2018 15:29
> > To: Adam Cottrel <adam.cottrel@veea.com>
> > Cc: Nair, Jayachandran <Jayachandran.Nair@cavium.com>; rric at kernel.org;
> > Goutham, Sunil <Sunil.Goutham@cavium.com>; Will Deacon
> > <will.deacon@arm.com>; Robin Murphy <robin.murphy@arm.com>; linux-
> > arm-kernel at lists.infradead.org
> > Subject: Re: DMA remote memcpy requests
> >
> > On Thu, Oct 18, 2018 at 03:36:25PM +0000, Adam Cottrel wrote:
> > > Dear Jan,
> > >
> > > Sorry for the delay in getting back to you - the patch took longer than
> > expected to finish.
> > >
> > > $ cat /proc/config.gz | gunzip | grep ERRATUM
> > > CONFIG_ARM64_ERRATUM_826319=y
> > CONFIG_ARM64_ERRATUM_827319=y
> > > CONFIG_ARM64_ERRATUM_824069=y
> > CONFIG_ARM64_ERRATUM_819472=y
> > > CONFIG_ARM64_ERRATUM_832075=y
> > CONFIG_ARM64_ERRATUM_834220=y
> > > CONFIG_ARM64_ERRATUM_845719=y
> > CONFIG_ARM64_ERRATUM_843419=y
> > > CONFIG_CAVIUM_ERRATUM_22375=y
> > CONFIG_CAVIUM_ERRATUM_23144=y
> > > CONFIG_CAVIUM_ERRATUM_23154=y
> > CONFIG_CAVIUM_ERRATUM_27456=y
> > > CONFIG_CAVIUM_ERRATUM_28168=y <---------------------
> > HERE!!
> > > CONFIG_CAVIUM_ERRATUM_30115=y
> > > CONFIG_QCOM_FALKOR_ERRATUM_1003=y
> > > CONFIG_QCOM_FALKOR_ERRATUM_1009=y
> > > CONFIG_QCOM_QDF2400_ERRATUM_0065=y
> > > CONFIG_FSL_ERRATUM_A008585=y
> > > CONFIG_HISILICON_ERRATUM_161010101=y
> > > CONFIG_ARM64_ERRATUM_858921=y
> > >
> > > As you can see, the fix is enabled, but when I test, it is not making any
> > difference to the original issue. The ath10k driver is still dropping inward DMA
> > under memory pressure.
> >
> > OK, it was just a guess from my side.
> >
> > > As an aside, I had to make one small change to the patch due to differences
> > between earlier kernel versions. Please see cavium.diff attached. Is this an
> > acceptable change?
> >
> > Your resolution looks fine.
> >
> > > Before we discount this as being a fix, please can you tell me how I can
> > prove that the patch is actually working on my platform?
> >
> > It looks like it doesn't solve your issue. I just wanted to rule this one out.
> >
> > Have you tried the other suggestion of completely turning of the SMMU?
> >
> > Regards,
> > Jan
> >
> >
> > > Best,
> > > Adam
> > >
> > > > -----Original Message-----
> > > > From: linux-arm-kernel
> > > > <linux-arm-kernel-bounces@lists.infradead.org> On Behalf Of Adam
> > > > Cottrel
> > > > Sent: 15 October 2018 16:51
> > > > To: Jan Glauber <Jan.Glauber@cavium.com>
> > > > Cc: Nair, Jayachandran <Jayachandran.Nair@cavium.com>;
> > > > rric at kernel.org; Goutham, Sunil <Sunil.Goutham@cavium.com>; Will
> > > > Deacon <will.deacon@arm.com>; Robin Murphy
> > <robin.murphy@arm.com>;
> > > > linux- arm-kernel at lists.infradead.org
> > > > Subject: RE: DMA remote memcpy requests
> > > >
> > > > Dear Jan,
> > > >
> > > > > I'm not sure where that point would be where DMA request could be
> > > > > lost here.
> > > > > The MMC and PCIe only meet in the NCB (near coprocessor bus) which
> > > > > goes to the Coherent memory interconnect and L2 cache.
> > > > >
> > > > > I've looked for any known errata but didn't find anything that
> > > > > would match your problem.
> > > >
> > > > For the purposes of debug, is it possible for me to turn off the
> > > > MMC? Or the
> > > > L2 cache? Or put it into pass through mode? Or get any kind of stack
> > > > trace on its operation?
> > > >
> > > > Best,
> > > > Adam
> > > >
> > > > _______________________________________________
> > > > linux-arm-kernel mailing list
> > > > linux-arm-kernel at lists.infradead.org
> > > > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> >
next prev parent reply other threads:[~2018-10-22 15:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 7:28 DMA remote memcpy requests Adam Cottrel
2018-10-12 9:09 ` Will Deacon
2018-10-12 9:48 ` Adam Cottrel
2018-10-12 10:46 ` Robin Murphy
2018-10-12 11:06 ` Adam Cottrel
2018-10-15 14:34 ` Adam Cottrel
2018-10-15 15:09 ` Jan Glauber
2018-10-15 15:24 ` Adam Cottrel
2018-10-15 15:39 ` Jan Glauber
2018-10-15 15:51 ` Adam Cottrel
2018-10-18 15:36 ` Adam Cottrel
2018-10-22 14:28 ` Jan Glauber
2018-10-22 14:39 ` Adam Cottrel
2018-10-22 15:33 ` Jan Glauber [this message]
[not found] ` <DM6PR07MB4923F3328079199090D6D2CA9EFE0@DM6PR07MB4923.namprd07.prod.outlook.com>
2018-10-16 16:52 ` Adam Cottrel
2018-10-16 17:08 ` Robin Murphy
2018-10-12 11:03 ` Jan Glauber
2018-10-12 11:07 ` Adam Cottrel
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=20181022153300.GB10359@hc \
--to=jan.glauber@cavium.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).