From: Pavel Machek <pavel@ucw.cz>
To: Joerg Roedel <joro@8bytes.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, "H . Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>,
Dave Hansen <dave.hansen@intel.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Juergen Gross <jgross@suse.com>,
Peter Zijlstra <peterz@infradead.org>,
Borislav Petkov <bp@alien8.de>, Jiri Kosina <jkosina@suse.cz>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Brian Gerst <brgerst@gmail.com>,
David Laight <David.Laight@aculab.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
Eduardo Valentin <eduval@amazon.com>,
Greg KH <gregkh@linuxfoundation.org>,
Will Deacon <will.deacon@arm.com>,
aliguori@amazon.com, daniel.gruss@iaik.tugraz.at,
hughd@google.com, keescook@google.com,
Andrea Arcangeli <aarcange@redhat.com>,
Waiman Long <llong@redhat.com>,
"David H . Gutteridge" <dhgutteridge@sympatico.ca>,
jroedel@suse.de, Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH 0/3] PTI for x86-32 Fixes and Updates
Date: Mon, 23 Jul 2018 16:09:25 +0200 [thread overview]
Message-ID: <20180723140925.GA4285@amd> (raw)
In-Reply-To: <1532103744-31902-1-git-send-email-joro@8bytes.org>
[-- Attachment #1: Type: text/plain, Size: 2489 bytes --]
Hi!
> here are 3 patches which update the PTI-x86-32 patches recently merged
> into the tip-tree. The patches are ordered by importance:
It seems PTI is now in -next. I'll test that soon.
Meanwhile... it looks like gcc is not slowed down significantly, but
other stuff sees 30% .. 40% slowdowns... which is rather
significant.
Would it be possible to have per-process control of kpti? I have
some processes where trading of speed for security would make sense.
Best regards,
Pavel
cd ~/g/tui/nowcast
time ./nowcast -x (30%)
KPTI: 139.25user 73.65system 269.90 (4m29.901s) elapsed 78.88%CPU
133.35user 73.15system 228.80 (3m48.802s) elapsed 90.25%CPU
140.51user 74.21system 218.33 (3m38.338s) elapsed 98.34%CPU
133.85user 75.89system 212.02 (3m32.026s) elapsed 98.93%CPU (no chromium)
139.34user 75.00system 235.75 (3m55.752s) elapsed 90.92%CPU
4.18: 116.99user 43.79system 217.65 (3m37.653s) elapsed 73.87%CPU
115.14user 43.97system 178.85 (2m58.855s) elapsed 88.96%CPU
128.47user 47.22system 178.24 (2m58.245s) elapsed 98.57%CPU
132.30user 49.27system 184.40 (3m4.408s) elapsed 98.46%CPU
134.88user 48.59system 186.67 (3m6.673s) elapsed 98.29%CPU
132.15user 48.65system 524.68 (8m44.684s) elapsed 34.46%CPU
120.38user 45.45system 168.72 (2m48.720s) elapsed 98.29%CPU
time cat /dev/urandom | head -c 10000000 | bzip2 -9 - | wc -c (40%)
v4.18: 4.57user 0.23system 4.64 (0m4.644s) elapsed 103.53%CPU
4.86user 0.23system 4.95 (0m4.952s) elapsed 102.81%CPU
5.13user 0.22system 5.19 (0m5.190s) elapsed 103.14%CPU
KPTI: 6.39user 0.48system 6.74 (0m6.747s) elapsed 101.96%CPU
6.66user 0.41system 6.91 (0m6.912s) elapsed 102.51%CPU
6.53user 0.51system 6.91 (0m6.919s) elapsed 101.99%CPU
v4l-utils: make clean, time make
v4.18: 191.93user 11.00system 211.19 (3m31.191s) elapsed 96.09%CPU
221.21user 14.69system 248.73 (4m8.734s) elapsed 94.84%CPU
198.35user 11.61system 211.39 (3m31.392s) elapsed 99.32%CPU
204.87user 11.69system 217.97 (3m37.971s) elapsed 99.35%CPU
203.68user 11.88system 217.29 (3m37.291s) elapsed 99.20%CPU
KPTI: 156.45user 40.08system 204.77 (3m24.777s) elapsed 95.97%CPU
183.32user 38.64system 225.03 (3m45.031s) elapsed 98.63%CPU
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-07-23 14:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 16:22 [PATCH 0/3] PTI for x86-32 Fixes and Updates Joerg Roedel
2018-07-20 16:22 ` [PATCH 1/3] perf/core: Make sure the ring-buffer is mapped in all page-tables Joerg Roedel
2018-07-20 17:06 ` Andy Lutomirski
2018-07-20 17:48 ` Joerg Roedel
2018-07-20 19:32 ` Andy Lutomirski
2018-07-20 21:37 ` Joerg Roedel
2018-07-20 22:20 ` Andy Lutomirski
2018-07-21 21:06 ` Linus Torvalds
2018-07-20 19:27 ` Thomas Gleixner
2018-07-20 19:33 ` Andy Lutomirski
2018-07-20 19:43 ` Thomas Gleixner
2018-07-20 19:53 ` Thomas Gleixner
2018-07-20 16:22 ` [PATCH 2/3] x86/entry/32: Check for VM86 mode in slow-path check Joerg Roedel
2018-07-21 16:06 ` Pavel Machek
2018-07-20 16:22 ` [PATCH 3/3] x86/entry/32: Copy only ptregs on paranoid entry/exit path Joerg Roedel
2018-07-20 17:09 ` Andy Lutomirski
2018-07-20 21:42 ` Joerg Roedel
2018-07-23 3:49 ` [PATCH 0/3] PTI for x86-32 Fixes and Updates David H. Gutteridge
2018-07-23 7:29 ` Joerg Roedel
2018-07-26 3:47 ` David H. Gutteridge
2018-07-23 14:09 ` Pavel Machek [this message]
2018-07-23 19:00 ` Linus Torvalds
2018-07-23 21:38 ` Pavel Machek
2018-07-23 21:50 ` Andy Lutomirski
2018-07-23 21:55 ` Pavel Machek
2018-07-24 21:18 ` Pavel Machek
2018-07-23 21:59 ` Josh Poimboeuf
2018-07-23 22:07 ` Dave Hansen
2018-07-24 13:39 ` Pavel Machek
2018-07-24 14:39 ` Andy Lutomirski
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=20180723140925.GA4285@amd \
--to=pavel@ucw.cz \
--cc=David.Laight@aculab.com \
--cc=aarcange@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=aliguori@amazon.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=daniel.gruss@iaik.tugraz.at \
--cc=dave.hansen@intel.com \
--cc=dhgutteridge@sympatico.ca \
--cc=dvlasenk@redhat.com \
--cc=eduval@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=hughd@google.com \
--cc=jgross@suse.com \
--cc=jkosina@suse.cz \
--cc=jolsa@redhat.com \
--cc=joro@8bytes.org \
--cc=jpoimboe@redhat.com \
--cc=jroedel@suse.de \
--cc=keescook@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llong@redhat.com \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
--cc=x86@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 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).