From: Thomas Garnier <thgarnie@google.com> To: Ingo Molnar <mingo@kernel.org> Cc: "Herbert Xu" <herbert@gondor.apana.org.au>, "David S . Miller" <davem@davemloft.net>, "Thomas Gleixner" <tglx@linutronix.de>, "Ingo Molnar" <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>, "Peter Zijlstra" <peterz@infradead.org>, "Josh Poimboeuf" <jpoimboe@redhat.com>, "Arnd Bergmann" <arnd@arndb.de>, "Matthias Kaehlcke" <mka@chromium.org>, "Boris Ostrovsky" <boris.ostrovsky@oracle.com>, "Juergen Gross" <jgross@suse.com>, "Paolo Bonzini" <pbonzini@redhat.com>, "Radim Krčmář" <rkrcmar@redhat.com>, "Joerg Roedel" <joro@8bytes.org>, "Tom Lendacky" <thomas.lendacky@amd.com>, "Andy Lutomirski" <luto@kernel.org>, "Borislav Petkov" <bp@suse.de>, "Brian Gerst" <brgerst@gmail.com>, "Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>, "Rafael J . Wysocki" <rjw@rjwysocki.net>, "Len Brown" <len.brown@intel.com>, "Pavel Machek" <pavel@ucw.cz>, "Tejun Heo" <tj@kernel.org> Subject: Re: x86: PIE support and option to extend KASLR randomization Date: Tue, 29 Aug 2017 12:34:04 -0700 [thread overview] Message-ID: <CAJcbSZH6hwaWKrvUZR33ExYaZaWKMSv4tJJA3yZkniLvLbTFMw@mail.gmail.com> (raw) In-Reply-To: <CAJcbSZFJQMKw21kLwr4QGoSM7DMgKRzzjWxkYBF2c1HciCzvGg@mail.gmail.com> On Fri, Aug 25, 2017 at 8:05 AM, Thomas Garnier <thgarnie@google.com> wrote: > On Fri, Aug 25, 2017 at 1:04 AM, Ingo Molnar <mingo@kernel.org> wrote: >> >> * Thomas Garnier <thgarnie@google.com> wrote: >> >>> With the fix for function tracing, the hackbench results have an >>> average of +0.8 to +1.4% (from +8% to +10% before). With a default >>> configuration, the numbers are closer to 0.8%. >>> >>> On the .text size, with gcc 4.9 I see +0.8% on default configuration >>> and +1.180% on the ubuntu configuration. >> >> A 1% text size increase is still significant. Could you look at the disassembly, >> where does the size increase come from? > > I will take a look, in this current iteration I added the .got and > .got.plt so removing them will remove a big (even if they are small, > we don't use them to increase perf). > > What do you think about the perf numbers in general so far? I looked at the size increase. I could identify two common cases: 1) PIE sometime needs two instructions to represent a single instruction on mcmodel=kernel. For example, this instruction plays on the sign extension (mcmodel=kernel): mov r9,QWORD PTR [r11*8-0x7e3da060] (8 bytes) The address 0xffffffff81c25fa0 can be represented as -0x7e3da060 using a 32S relocation. with PIE: lea rbx,[rip+<off>] (7 bytes) mov r9,QWORD PTR [rbx+r11*8] (6 bytes) 2) GCC does not optimize switches in PIE in order to reduce relocations: For example the switch in phy_modes [1]: static inline const char *phy_modes(phy_interface_t interface) { switch (interface) { case PHY_INTERFACE_MODE_NA: return ""; case PHY_INTERFACE_MODE_INTERNAL: return "internal"; case PHY_INTERFACE_MODE_MII: return "mii"; Without PIE (gcc 7.2.0), the whole table is optimize to be one instruction: 0x000000000040045b <+27>: mov rdi,QWORD PTR [rax*8+0x400660] With PIE (gcc 7.2.0): 0x0000000000000641 <+33>: movsxd rax,DWORD PTR [rdx+rax*4] 0x0000000000000645 <+37>: add rax,rdx 0x0000000000000648 <+40>: jmp rax .... 0x000000000000065d <+61>: lea rdi,[rip+0x264] # 0x8c8 0x0000000000000664 <+68>: jmp 0x651 <main+49> 0x0000000000000666 <+70>: lea rdi,[rip+0x2bc] # 0x929 0x000000000000066d <+77>: jmp 0x651 <main+49> 0x000000000000066f <+79>: lea rdi,[rip+0x2a8] # 0x91e 0x0000000000000676 <+86>: jmp 0x651 <main+49> 0x0000000000000678 <+88>: lea rdi,[rip+0x294] # 0x913 0x000000000000067f <+95>: jmp 0x651 <main+49> That's a deliberate choice, clang is able to optimize it (clang-3.8): 0x0000000000000963 <+19>: lea rcx,[rip+0x200406] # 0x200d70 0x000000000000096a <+26>: mov rdi,QWORD PTR [rcx+rax*8] I checked gcc and the code deciding to fold the switch basically do not do it for pic to reduce relocations [2]. The switches are the biggest increase on small functions but I don't think they represent a large portion of the difference (number 1 is). A side note, while testing gcc 7.2.0 on hackbench I have seen the PIE kernel being faster by 1% across multiple runs (comparing 50 runs done across 5 reboots twice). I don't think PIE is faster than a mcmodel=kernel but recent versions of gcc makes them fairly similar. [1] http://elixir.free-electrons.com/linux/v4.13-rc7/source/include/linux/phy.h#L113 [2] https://github.com/gcc-mirror/gcc/blob/7977b0509f07e42fbe0f06efcdead2b7e4a5135f/gcc/tree-switch-conversion.c#L828 > >> >> Thanks, >> >> Ingo > > > > -- > Thomas -- Thomas
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Garnier <thgarnie@google.com> To: Ingo Molnar <mingo@kernel.org> Cc: "Herbert Xu" <herbert@gondor.apana.org.au>, "David S . Miller" <davem@davemloft.net>, "Thomas Gleixner" <tglx@linutronix.de>, "Ingo Molnar" <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>, "Peter Zijlstra" <peterz@infradead.org>, "Josh Poimboeuf" <jpoimboe@redhat.com>, "Arnd Bergmann" <arnd@arndb.de>, "Matthias Kaehlcke" <mka@chromium.org>, "Boris Ostrovsky" <boris.ostrovsky@oracle.com>, "Juergen Gross" <jgross@suse.com>, "Paolo Bonzini" <pbonzini@redhat.com>, "Radim Krčmář" <rkrcmar@redhat.com>, "Joerg Roedel" <joro@8bytes.org>, "Tom Lendacky" <thomas.lendacky@amd.com>, "Andy Lutomirski" <luto@kernel.org>, "Borislav Petkov" <bp@suse.de>, "Brian Gerst" <brgerst@gmail.com>, "Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>, "Rafael J . Wysocki" <rjw@rjwysocki.net>, "Len Brown" <len.brown@intel.com>, "Pavel Machek" <pavel@ucw.cz>, "Tejun Heo" <tj@kernel.org>, "Christoph Lameter" <cl@linux.com>, "Paul Gortmaker" <paul.gortmaker@windriver.com>, "Chris Metcalf" <cmetcalf@mellanox.com>, "Andrew Morton" <akpm@linux-foundation.org>, "Paul E . McKenney" <paulmck@linux.vnet.ibm.com>, "Nicolas Pitre" <nicolas.pitre@linaro.org>, "Christopher Li" <sparse@chrisli.org>, "Rafael J . Wysocki" <rafael.j.wysocki@intel.com>, "Lukas Wunner" <lukas@wunner.de>, "Mika Westerberg" <mika.westerberg@linux.intel.com>, "Dou Liyang" <douly.fnst@cn.fujitsu.com>, "Daniel Borkmann" <daniel@iogearbox.net>, "Alexei Starovoitov" <ast@kernel.org>, "Masahiro Yamada" <yamada.masahiro@socionext.com>, "Markus Trippelsdorf" <markus@trippelsdorf.de>, "Steven Rostedt" <rostedt@goodmis.org>, "Kees Cook" <keescook@chromium.org>, "Rik van Riel" <riel@redhat.com>, "David Howells" <dhowells@redhat.com>, "Waiman Long" <longman@redhat.com>, "Kyle Huey" <me@kylehuey.com>, "Peter Foley" <pefoley2@pefoley.com>, "Tim Chen" <tim.c.chen@linux.intel.com>, "Catalin Marinas" <catalin.marinas@arm.com>, "Ard Biesheuvel" <ard.biesheuvel@linaro.org>, "Michal Hocko" <mhocko@suse.com>, "Matthew Wilcox" <mawilcox@microsoft.com>, "H . J . Lu" <hjl.tools@gmail.com>, "Paul Bolle" <pebolle@tiscali.nl>, "Rob Landley" <rob@landley.net>, "Baoquan He" <bhe@redhat.com>, "Daniel Micay" <danielmicay@gmail.com>, "the arch/x86 maintainers" <x86@kernel.org>, "Linux Crypto Mailing List" <linux-crypto@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>, xen-devel <xen-devel@lists.xenproject.org>, "kvm list" <kvm@vger.kernel.org>, "Linux PM list" <linux-pm@vger.kernel.org>, linux-arch <linux-arch@vger.kernel.org>, "Sparse Mailing-list" <linux-sparse@vger.kernel.org>, "Kernel Hardening" <kernel-hardening@lists.openwall.com>, "Linus Torvalds" <torvalds@linux-foundation.org>, "Peter Zijlstra" <a.p.zijlstra@chello.nl>, "Borislav Petkov" <bp@alien8.de> Subject: [kernel-hardening] Re: x86: PIE support and option to extend KASLR randomization Date: Tue, 29 Aug 2017 12:34:04 -0700 [thread overview] Message-ID: <CAJcbSZH6hwaWKrvUZR33ExYaZaWKMSv4tJJA3yZkniLvLbTFMw@mail.gmail.com> (raw) In-Reply-To: <CAJcbSZFJQMKw21kLwr4QGoSM7DMgKRzzjWxkYBF2c1HciCzvGg@mail.gmail.com> On Fri, Aug 25, 2017 at 8:05 AM, Thomas Garnier <thgarnie@google.com> wrote: > On Fri, Aug 25, 2017 at 1:04 AM, Ingo Molnar <mingo@kernel.org> wrote: >> >> * Thomas Garnier <thgarnie@google.com> wrote: >> >>> With the fix for function tracing, the hackbench results have an >>> average of +0.8 to +1.4% (from +8% to +10% before). With a default >>> configuration, the numbers are closer to 0.8%. >>> >>> On the .text size, with gcc 4.9 I see +0.8% on default configuration >>> and +1.180% on the ubuntu configuration. >> >> A 1% text size increase is still significant. Could you look at the disassembly, >> where does the size increase come from? > > I will take a look, in this current iteration I added the .got and > .got.plt so removing them will remove a big (even if they are small, > we don't use them to increase perf). > > What do you think about the perf numbers in general so far? I looked at the size increase. I could identify two common cases: 1) PIE sometime needs two instructions to represent a single instruction on mcmodel=kernel. For example, this instruction plays on the sign extension (mcmodel=kernel): mov r9,QWORD PTR [r11*8-0x7e3da060] (8 bytes) The address 0xffffffff81c25fa0 can be represented as -0x7e3da060 using a 32S relocation. with PIE: lea rbx,[rip+<off>] (7 bytes) mov r9,QWORD PTR [rbx+r11*8] (6 bytes) 2) GCC does not optimize switches in PIE in order to reduce relocations: For example the switch in phy_modes [1]: static inline const char *phy_modes(phy_interface_t interface) { switch (interface) { case PHY_INTERFACE_MODE_NA: return ""; case PHY_INTERFACE_MODE_INTERNAL: return "internal"; case PHY_INTERFACE_MODE_MII: return "mii"; Without PIE (gcc 7.2.0), the whole table is optimize to be one instruction: 0x000000000040045b <+27>: mov rdi,QWORD PTR [rax*8+0x400660] With PIE (gcc 7.2.0): 0x0000000000000641 <+33>: movsxd rax,DWORD PTR [rdx+rax*4] 0x0000000000000645 <+37>: add rax,rdx 0x0000000000000648 <+40>: jmp rax .... 0x000000000000065d <+61>: lea rdi,[rip+0x264] # 0x8c8 0x0000000000000664 <+68>: jmp 0x651 <main+49> 0x0000000000000666 <+70>: lea rdi,[rip+0x2bc] # 0x929 0x000000000000066d <+77>: jmp 0x651 <main+49> 0x000000000000066f <+79>: lea rdi,[rip+0x2a8] # 0x91e 0x0000000000000676 <+86>: jmp 0x651 <main+49> 0x0000000000000678 <+88>: lea rdi,[rip+0x294] # 0x913 0x000000000000067f <+95>: jmp 0x651 <main+49> That's a deliberate choice, clang is able to optimize it (clang-3.8): 0x0000000000000963 <+19>: lea rcx,[rip+0x200406] # 0x200d70 0x000000000000096a <+26>: mov rdi,QWORD PTR [rcx+rax*8] I checked gcc and the code deciding to fold the switch basically do not do it for pic to reduce relocations [2]. The switches are the biggest increase on small functions but I don't think they represent a large portion of the difference (number 1 is). A side note, while testing gcc 7.2.0 on hackbench I have seen the PIE kernel being faster by 1% across multiple runs (comparing 50 runs done across 5 reboots twice). I don't think PIE is faster than a mcmodel=kernel but recent versions of gcc makes them fairly similar. [1] http://elixir.free-electrons.com/linux/v4.13-rc7/source/include/linux/phy.h#L113 [2] https://github.com/gcc-mirror/gcc/blob/7977b0509f07e42fbe0f06efcdead2b7e4a5135f/gcc/tree-switch-conversion.c#L828 > >> >> Thanks, >> >> Ingo > > > > -- > Thomas -- Thomas
next prev parent reply other threads:[~2017-08-29 19:34 UTC|newest] Thread overview: 221+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-08-10 17:25 x86: PIE support and option to extend KASLR randomization Thomas Garnier 2017-08-10 17:25 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:25 ` [RFC v2 01/23] x86/crypto: Adapt assembly for PIE support Thomas Garnier 2017-08-10 17:25 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:25 ` [RFC v2 02/23] x86: Use symbol name on bug table " Thomas Garnier 2017-08-10 17:25 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:25 ` [RFC v2 03/23] x86: Use symbol name in jump " Thomas Garnier 2017-08-10 17:25 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:25 ` [RFC v2 04/23] x86: Add macro to get symbol address " Thomas Garnier 2017-08-10 17:25 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:25 ` [RFC v2 05/23] xen: Adapt assembly " Thomas Garnier 2017-08-10 17:25 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:25 ` [RFC v2 06/23] kvm: " Thomas Garnier 2017-08-10 17:25 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:25 ` [RFC v2 07/23] x86: relocate_kernel - " Thomas Garnier 2017-08-10 17:25 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:26 ` [RFC v2 08/23] x86/entry/64: " Thomas Garnier 2017-08-10 17:26 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:26 ` [RFC v2 09/23] x86: pm-trace - " Thomas Garnier 2017-08-10 17:26 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:26 ` [RFC v2 10/23] x86/CPU: " Thomas Garnier 2017-08-10 17:26 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:26 ` [RFC v2 11/23] x86/acpi: " Thomas Garnier 2017-08-10 17:26 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:26 ` [RFC v2 12/23] x86/boot/64: " Thomas Garnier 2017-08-10 17:26 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:26 ` [RFC v2 13/23] x86/power/64: " Thomas Garnier 2017-08-10 17:26 ` [kernel-hardening] " Thomas Garnier 2017-08-11 12:36 ` Pavel Machek 2017-08-11 12:36 ` Pavel Machek 2017-08-11 12:36 ` [kernel-hardening] " Pavel Machek 2017-08-11 15:09 ` Thomas Garnier 2017-08-11 15:09 ` [kernel-hardening] " Thomas Garnier 2017-08-11 15:09 ` Thomas Garnier 2017-08-10 17:26 ` [RFC v2 14/23] x86/paravirt: " Thomas Garnier 2017-08-10 17:26 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:26 ` [RFC v2 15/23] x86/boot/64: Use _text in a global " Thomas Garnier 2017-08-10 17:26 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:26 ` [RFC v2 16/23] x86/percpu: Adapt percpu " Thomas Garnier 2017-08-10 17:26 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:26 ` [RFC v2 17/23] compiler: Option to default to hidden symbols Thomas Garnier 2017-08-10 17:26 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:26 ` [RFC v2 18/23] x86/relocs: Handle DYN relocations for PIE support Thomas Garnier 2017-08-10 17:26 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:26 ` [RFC v2 19/23] x86: Support global stack cookie Thomas Garnier 2017-08-10 17:26 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:26 ` [RFC v2 20/23] x86/pie: Add option to build the kernel as PIE for x86_64 Thomas Garnier 2017-08-10 17:26 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:26 ` [RFC v2 21/23] x86/relocs: Add option to generate 64-bit relocations Thomas Garnier 2017-08-10 17:26 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:26 ` [RFC v2 22/23] x86/module: Add support for mcmodel large and PLTs Thomas Garnier 2017-08-10 17:26 ` [kernel-hardening] " Thomas Garnier 2017-08-10 17:26 ` [RFC v2 23/23] x86/kaslr: Add option to extend KASLR range from 1GB to 3GB Thomas Garnier 2017-08-10 17:26 ` [kernel-hardening] " Thomas Garnier 2017-08-11 12:41 ` x86: PIE support and option to extend KASLR randomization Ingo Molnar 2017-08-11 12:41 ` [kernel-hardening] " Ingo Molnar 2017-08-11 15:09 ` Thomas Garnier 2017-08-11 15:09 ` Thomas Garnier 2017-08-11 15:09 ` [kernel-hardening] " Thomas Garnier 2017-08-15 7:56 ` Ingo Molnar 2017-08-15 7:56 ` Ingo Molnar 2017-08-15 7:56 ` [kernel-hardening] " Ingo Molnar 2017-08-15 12:15 ` Jordan Glover 2017-08-15 13:42 ` Rik van Riel 2017-08-15 14:20 ` Thomas Garnier 2017-08-15 14:20 ` Thomas Garnier 2017-08-15 14:20 ` [kernel-hardening] " Thomas Garnier 2017-08-15 14:47 ` Daniel Micay 2017-08-15 14:47 ` Daniel Micay 2017-08-15 14:47 ` [kernel-hardening] " Daniel Micay 2017-08-15 14:58 ` Thomas Garnier 2017-08-15 14:58 ` Thomas Garnier 2017-08-15 14:58 ` [kernel-hardening] " Thomas Garnier 2017-08-16 15:12 ` Ingo Molnar 2017-08-16 15:12 ` Ingo Molnar 2017-08-16 15:12 ` [kernel-hardening] " Ingo Molnar 2017-08-16 16:09 ` Christopher Lameter 2017-08-16 16:09 ` Christopher Lameter 2017-08-16 16:09 ` [kernel-hardening] " Christopher Lameter 2017-08-16 16:26 ` Daniel Micay 2017-08-16 16:26 ` [kernel-hardening] " Daniel Micay 2017-08-16 16:32 ` Ard Biesheuvel 2017-08-16 16:32 ` Ard Biesheuvel 2017-08-16 16:32 ` [kernel-hardening] " Ard Biesheuvel 2017-08-16 16:26 ` Daniel Micay 2017-08-16 16:57 ` Thomas Garnier 2017-08-16 16:57 ` Thomas Garnier 2017-08-16 16:57 ` [kernel-hardening] " Thomas Garnier 2017-08-17 8:09 ` Ingo Molnar 2017-08-17 8:09 ` Ingo Molnar 2017-08-17 8:09 ` [kernel-hardening] " Ingo Molnar 2017-08-17 14:10 ` Thomas Garnier 2017-08-17 14:10 ` Thomas Garnier 2017-08-17 14:10 ` [kernel-hardening] " Thomas Garnier 2017-08-24 21:13 ` Thomas Garnier 2017-08-24 21:13 ` Thomas Garnier 2017-08-24 21:13 ` [kernel-hardening] " Thomas Garnier 2017-08-24 21:42 ` Linus Torvalds 2017-08-24 21:42 ` Linus Torvalds 2017-08-24 21:42 ` [kernel-hardening] " Linus Torvalds 2017-08-25 15:35 ` Thomas Garnier 2017-08-25 15:35 ` [kernel-hardening] " Thomas Garnier 2017-08-25 15:35 ` Thomas Garnier 2017-08-25 1:07 ` Steven Rostedt 2017-08-25 1:07 ` [kernel-hardening] " Steven Rostedt 2017-08-25 8:04 ` Ingo Molnar 2017-08-25 8:04 ` Ingo Molnar 2017-08-25 8:04 ` [kernel-hardening] " Ingo Molnar 2017-08-25 15:05 ` Thomas Garnier 2017-08-25 15:05 ` Thomas Garnier 2017-08-25 15:05 ` [kernel-hardening] " Thomas Garnier 2017-08-29 19:34 ` Thomas Garnier [this message] 2017-08-29 19:34 ` Thomas Garnier 2017-09-21 15:59 ` Ingo Molnar 2017-09-21 15:59 ` [kernel-hardening] " Ingo Molnar 2017-09-21 16:10 ` Ard Biesheuvel 2017-09-21 16:10 ` Ard Biesheuvel 2017-09-21 16:10 ` [kernel-hardening] " Ard Biesheuvel 2017-09-21 21:21 ` Thomas Garnier 2017-09-21 21:21 ` Thomas Garnier 2017-09-21 21:21 ` [kernel-hardening] " Thomas Garnier 2017-09-22 4:24 ` Markus Trippelsdorf 2017-09-22 4:24 ` [kernel-hardening] " Markus Trippelsdorf 2017-09-22 14:38 ` Thomas Garnier 2017-09-22 14:38 ` [kernel-hardening] " Thomas Garnier 2017-09-22 14:38 ` Thomas Garnier 2017-09-22 23:55 ` Thomas Garnier 2017-09-22 23:55 ` Thomas Garnier 2017-09-22 23:55 ` [kernel-hardening] " Thomas Garnier 2017-09-21 21:16 ` Thomas Garnier 2017-09-21 21:16 ` [kernel-hardening] " Thomas Garnier 2017-09-22 0:06 ` Thomas Garnier 2017-09-22 0:06 ` Thomas Garnier 2017-09-22 0:06 ` [kernel-hardening] " Thomas Garnier 2017-09-22 16:32 ` Ingo Molnar 2017-09-22 16:32 ` [kernel-hardening] " Ingo Molnar 2017-09-22 18:08 ` Thomas Garnier 2017-09-22 18:08 ` Thomas Garnier 2017-09-22 18:08 ` [kernel-hardening] " Thomas Garnier 2017-09-23 9:43 ` Ingo Molnar 2017-09-23 9:43 ` [kernel-hardening] " Ingo Molnar 2017-10-02 20:28 ` Thomas Garnier 2017-10-02 20:28 ` Thomas Garnier 2017-10-02 20:28 ` [kernel-hardening] " Thomas Garnier 2017-09-23 9:43 ` Ingo Molnar 2017-09-22 18:38 ` H. Peter Anvin 2017-09-22 18:38 ` [kernel-hardening] " H. Peter Anvin 2017-09-22 18:57 ` Kees Cook 2017-09-22 18:57 ` [kernel-hardening] " Kees Cook 2017-09-22 19:06 ` H. Peter Anvin 2017-09-22 19:06 ` [kernel-hardening] " H. Peter Anvin 2017-09-22 22:19 ` hjl.tools 2017-09-22 22:30 ` hjl.tools 2017-09-22 19:06 ` H. Peter Anvin 2017-09-22 18:57 ` Kees Cook 2017-09-22 18:59 ` Thomas Garnier 2017-09-22 18:59 ` Thomas Garnier 2017-09-22 18:59 ` [kernel-hardening] " Thomas Garnier 2017-09-23 9:49 ` Ingo Molnar 2017-09-23 9:49 ` Ingo Molnar 2017-09-23 9:49 ` [kernel-hardening] " Ingo Molnar 2017-09-22 18:38 ` H. Peter Anvin 2017-09-22 16:32 ` Ingo Molnar 2017-09-21 21:16 ` Thomas Garnier 2017-09-21 15:59 ` Ingo Molnar 2017-08-29 19:34 ` Thomas Garnier 2017-08-17 14:12 ` Boris Lukashev 2017-08-17 14:12 ` [kernel-hardening] " Boris Lukashev 2017-08-25 15:38 ` Christopher Lameter 2017-08-25 15:38 ` [kernel-hardening] " Christopher Lameter 2017-08-27 22:39 ` Boris Lukashev 2017-08-27 22:39 ` Boris Lukashev 2017-08-27 22:39 ` [kernel-hardening] " Boris Lukashev 2017-08-25 15:38 ` Christopher Lameter 2017-08-28 9:59 ` Pavel Machek 2017-08-28 9:59 ` Pavel Machek 2017-08-28 9:59 ` [kernel-hardening] " Pavel Machek 2017-08-17 14:12 ` Boris Lukashev 2017-08-21 13:32 ` Peter Zijlstra 2017-08-21 13:32 ` [kernel-hardening] " Peter Zijlstra 2017-08-21 14:28 ` Peter Zijlstra 2017-08-21 14:28 ` Peter Zijlstra 2017-08-21 14:28 ` [kernel-hardening] " Peter Zijlstra 2017-09-22 18:27 ` H. Peter Anvin 2017-09-22 18:27 ` [kernel-hardening] " H. Peter Anvin 2017-09-23 10:00 ` Ingo Molnar 2017-09-23 10:00 ` [kernel-hardening] " Ingo Molnar 2017-09-24 22:37 ` Pavel Machek 2017-09-24 22:37 ` [kernel-hardening] " Pavel Machek 2017-09-25 7:33 ` Ingo Molnar 2017-09-25 7:33 ` Ingo Molnar 2017-09-25 7:33 ` [kernel-hardening] " Ingo Molnar 2017-10-06 10:39 ` Pavel Machek 2017-10-06 10:39 ` Pavel Machek 2017-10-06 10:39 ` [kernel-hardening] " Pavel Machek 2017-10-20 8:13 ` Ingo Molnar 2017-10-20 8:13 ` [kernel-hardening] " Ingo Molnar 2017-10-20 8:13 ` Ingo Molnar 2017-09-24 22:37 ` Pavel Machek 2017-09-23 10:00 ` Ingo Molnar 2017-09-22 18:27 ` H. Peter Anvin 2017-08-21 13:32 ` Peter Zijlstra 2017-08-21 14:31 ` Peter Zijlstra 2017-08-21 14:31 ` [kernel-hardening] " Peter Zijlstra 2017-08-21 15:57 ` Thomas Garnier 2017-08-21 15:57 ` Thomas Garnier 2017-08-21 15:57 ` [kernel-hardening] " Thomas Garnier 2017-08-28 1:26 ` H. Peter Anvin 2017-08-28 1:26 ` [kernel-hardening] " H. Peter Anvin 2017-08-28 1:26 ` H. Peter Anvin 2017-08-21 14:31 ` Peter Zijlstra 2017-08-11 12:41 ` Ingo Molnar -- strict thread matches above, loose matches on Subject: below -- 2017-10-04 21:19 Thomas Garnier 2017-10-04 21:19 Thomas Garnier via Virtualization 2017-10-04 21:19 Thomas Garnier 2017-10-04 21:19 ` Thomas Garnier 2017-08-10 17:25 Thomas Garnier 2017-07-18 22:33 Thomas Garnier 2017-07-19 14:08 ` Christopher Lameter 2017-07-19 14:08 ` Christopher Lameter 2017-07-18 22:33 Thomas Garnier
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=CAJcbSZH6hwaWKrvUZR33ExYaZaWKMSv4tJJA3yZkniLvLbTFMw@mail.gmail.com \ --to=thgarnie@google.com \ --cc=arnd@arndb.de \ --cc=boris.ostrovsky@oracle.com \ --cc=bp@suse.de \ --cc=brgerst@gmail.com \ --cc=davem@davemloft.net \ --cc=herbert@gondor.apana.org.au \ --cc=hpa@zytor.com \ --cc=jgross@suse.com \ --cc=joro@8bytes.org \ --cc=jpoimboe@redhat.com \ --cc=kirill.shutemov@linux.intel.com \ --cc=len.brown@intel.com \ --cc=luto@kernel.org \ --cc=mingo@kernel.org \ --cc=mingo@redhat.com \ --cc=mka@chromium.org \ --cc=pavel@ucw.cz \ --cc=pbonzini@redhat.com \ --cc=peterz@infradead.org \ --cc=rjw@rjwysocki.net \ --cc=rkrcmar@redhat.com \ --cc=tglx@linutronix.de \ --cc=thomas.lendacky@amd.com \ --cc=tj@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.