Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1191238
| From | Brian Gerst <brgerst@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] x86/entry/32: Initialize ss1 (SYSENTER_CS shadow) even on non-SEP CPUs |
| Date | 2015-07-23 21:10 +0200 |
| Message-ID | <pPu2u-7g6-23@gated-at.bofh.it> (permalink) |
| References | <pPtSO-6Pc-25@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, Jul 23, 2015 at 2:56 PM, Andy Lutomirski <luto@kernel.org> wrote: > native_load_sp0 relies on this. I'm not sure why we haven't seen > reports of crashes. Maybe no one tests new kernels on non-SEP CPUs. It's already statically initialized in cpu_tss. -- Brian Gerst -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH] x86/entry/32: Initialize ss1 (SYSENTER_CS shadow) even on non-SEP CPUs Andy Lutomirski <luto@kernel.org> - 2015-07-23 21:00 +0200 Re: [PATCH] x86/entry/32: Initialize ss1 (SYSENTER_CS shadow) even on non-SEP CPUs Brian Gerst <brgerst@gmail.com> - 2015-07-23 21:10 +0200
csiph-web