From: "Michal Suchánek" <msuchanek@suse.de>
To: linuxppc-dev@ozlabs.org
Subject: barrier_nospec for POWER
Date: Mon, 5 Mar 2018 14:13:35 +0100 [thread overview]
Message-ID: <20180305141335.086c4a52@kitsune.suse.cz> (raw)
Hello,
there is x86 barrier_nospec which implements the same barrier as the
earlier out-of-tree gmb() barrier but instead of sprinkling the barrier
randomly in kernel code it put it in copy_from_user. We have the
firmware support for barrier_nospec already reported from the hcall
which is used for RFI flushes. So copy-pasting this from x86 should not
be that difficult.
However, there is separate patch which protects the NR_syscalls check of
syscall entry which does not apply on powerpc because the check is done
in assembly. I did not manage to write a barrier_nospec that compiles
both in C and asm so you are spared a RFC patch.
Is there some work in progress on addressing this?
Thanks
Michal
reply other threads:[~2018-03-05 13:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180305141335.086c4a52@kitsune.suse.cz \
--to=msuchanek@suse.de \
--cc=linuxppc-dev@ozlabs.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