From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Chris Zankel <chris@zankel.net>,
linux-xtensa@linux-xtensa.org
Subject: Re: [PATCH] Fix: xtensa: add missing sync_core
Date: Tue, 29 Aug 2017 18:55:37 +0000 (UTC) [thread overview]
Message-ID: <1616508443.22335.1504032937518.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <CAMo8BfJw-dYcpbduUiF9=4J6_kLw+0itZVyr9ys7k=+BvwYbWA@mail.gmail.com>
----- On Aug 28, 2017, at 1:12 PM, Max Filippov jcmvbkbc@gmail.com wrote:
> Hi Mathieu,
>
> On Mon, Aug 28, 2017 at 12:36 AM, Mathieu Desnoyers
> <mathieu.desnoyers@efficios.com> wrote:
>> The membarrier system call now requires all architectures to implement
>> sync_core(). On Xtensa, it is provided by the EXTW instruction.
>>
>> [ Completely untested! Can someone on the xtensa side confirm whether
>> EXTW is the right way to serialize core execution and try it out ? ]
>
> Thanks for the patch. I'm currently travelling, I'll give it a try next week
> once I'm back at work.
Hi Max,
I think we may need to flush the icache to make it consistent with the dcache
too on xtensa, in addition to the EXTW. The goal here is to allow JIT engines
to reclaim and re-use memory after they discard dynamically generated code.
This is similar to what we'd need to do on arm32, where they have inconsistent
d/i-caches.
Thoughts ?
Thanks,
Mathieu
>
> --
> Thanks.
> -- Max
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2017-08-29 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 21:36 [PATCH] Fix: xtensa: add missing sync_core Mathieu Desnoyers
2017-08-28 17:12 ` Max Filippov
2017-08-29 18:55 ` Mathieu Desnoyers [this message]
2017-09-12 4:37 ` Max Filippov
2017-09-12 13:05 ` Mathieu Desnoyers
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=1616508443.22335.1504032937518.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=chris@zankel.net \
--cc=jcmvbkbc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@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