From: Catalin Marinas <catalin.marinas@arm.com>
To: Shijith Thotton <sthotton@marvell.com>
Cc: "Wangkefeng \(Kevin\)" <wangkefeng.wang@huawei.com>,
Ganapatrao Kulkarni <gkulkarni@marvell.com>,
"anshuman.khandual@arm.com" <anshuman.khandual@arm.com>,
Will Deacon <will.deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jayachandran Chandrasekharan Nair <jnair@marvell.com>,
chenwandun <chenwandun@huawei.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [Qestion] Softlockup when send IPI to other CPUs
Date: Thu, 24 Jan 2019 16:37:44 +0000 [thread overview]
Message-ID: <20190124163743.GK253679@arrakis.emea.arm.com> (raw)
In-Reply-To: <DM6PR18MB24607427B3B2BEAD80A75780D99A0@DM6PR18MB2460.namprd18.prod.outlook.com>
Hi Shijith,
On Thu, Jan 24, 2019 at 07:00:42AM +0000, Shijith Thotton wrote:
> On 01/23/2019 11:45 PM, Catalin Marinas wrote:
> > diff --git a/arch/arm64/mm/flush.c b/arch/arm64/mm/flush.c
> > index 30695a868107..5c9073bace83 100644
> > --- a/arch/arm64/mm/flush.c
> > +++ b/arch/arm64/mm/flush.c
> > @@ -33,7 +33,11 @@ void sync_icache_aliases(void *kaddr, unsigned long len)
> > __clean_dcache_area_pou(kaddr, len);
> > __flush_icache_all();
> > } else {
> > - flush_icache_range(addr, addr + len);
> > + /*
> > + * Don't issue kick_all_cpus_sync() after I-cache invalidation
> > + * for user mappings.
> > + */
> > + __flush_icache_range(addr, addr + len);
> > }
> > }
>
> We also faced similar issue with LTP test migrate_pages03 in past and this patch
> fixes the issue.
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2019-January/623574.html
Thanks for confirming. I presume I can add your tested-by.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-24 16:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <95C141B25E7AB14BA042DCCC556C0E6501620A47@dggeml529-mbx.china.huawei.com>
2019-01-19 23:58 ` [Qestion] Softlockup when send IPI to other CPUs Will Deacon
2019-01-21 14:21 ` Catalin Marinas
2019-01-22 5:44 ` Will Deacon
2019-01-22 14:55 ` Mark Rutland
2019-01-23 10:21 ` Will Deacon
2019-01-23 18:15 ` Catalin Marinas
2019-01-24 7:00 ` Shijith Thotton
2019-01-24 16:37 ` Catalin Marinas [this message]
2019-01-25 9:57 ` Shijith Thotton
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=20190124163743.GK253679@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=chenwandun@huawei.com \
--cc=gkulkarni@marvell.com \
--cc=jnair@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sthotton@marvell.com \
--cc=wangkefeng.wang@huawei.com \
--cc=will.deacon@arm.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