From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linutronix.de (193.142.43.55:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 27 Feb 2020 16:43:46 -0000 Received: from mga18.intel.com ([134.134.136.126]) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1j7MGG-0000yx-3F for speck@linutronix.de; Thu, 27 Feb 2020 17:43:45 +0100 Received: from localhost (mtg-dev.jf.intel.com [10.54.74.10]) by smtp.ostc.intel.com (Postfix) with ESMTP id 001056361 for ; Thu, 27 Feb 2020 16:43:28 +0000 (UTC) Date: Thu, 27 Feb 2020 08:43:29 -0800 From: mark gross Subject: [MODERATED] Re: [PATCH v2 1/2] v2: more sampling fun 1 Message-ID: <20200227164329.GH116192@mtg-dev.jf.intel.com> Reply-To: mgross@linux.intel.com References: <20200226110737.GB17448@zn.tnic> <20200226171103.GA114268@mtg-dev.jf.intel.com> <20200226175950.GD17448@zn.tnic> <87h7zdi58e.fsf@nanos.tec.linutronix.de> <20200226221355.GC116192@mtg-dev.jf.intel.com> <875zfsoqgd.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 In-Reply-To: <875zfsoqgd.fsf@nanos.tec.linutronix.de> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: On Thu, Feb 27, 2020 at 12:53:54AM +0100, speck for Thomas Gleixner wrote: > speck for mark gross writes: > > On Wed, Feb 26, 2020 at 07:16:33PM +0100, speck for Thomas Gleixner wrote: > >> speck for Borislav Petkov writes: > >> > What you should actually be doing is setting those bug flags in > >> > early_init_intel() where you can go wild with the steppings checking and > >> > then you won't need to touch x86_cpu_id at all. > >> > >> Either that or add a new cpu_vuln_shitlist beside the whitelist and > >> stick the new stuff into that. It kinda makes sense to keep all this > >> vulnerability nonsense in one place. > > > > I'm ok with either way. is there a consensus for making annother > > cpu_vuln_list? > > Go for the extra list at the same place so all that stuff is in one > place. I will do that. --mark