Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754215AbbGWTDI (ORCPT ); Thu, 23 Jul 2015 15:03:08 -0400 Received: from mail-oi0-f45.google.com ([209.85.218.45]:36324 "EHLO mail-oi0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753504AbbGWTDF (ORCPT ); Thu, 23 Jul 2015 15:03:05 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Thu, 23 Jul 2015 15:03:04 -0400 Message-ID: Subject: Re: [PATCH] x86/entry/32: Initialize ss1 (SYSENTER_CS shadow) even on non-SEP CPUs From: Brian Gerst To: Andy Lutomirski Cc: X86 ML , Linux Kernel Mailing List , Steven Rostedt , Willy Tarreau , Borislav Petkov , Thomas Gleixner , Peter Zijlstra , Linus Torvalds Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 523 Lines: 13 On Thu, Jul 23, 2015 at 2:56 PM, Andy Lutomirski 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/