From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id D2483138206 for ; Tue, 2 Jan 2018 22:58:23 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 04284E089A; Tue, 2 Jan 2018 22:58:18 +0000 (UTC) Received: from mail-oi0-x242.google.com (mail-oi0-x242.google.com [IPv6:2607:f8b0:4003:c06::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 978CCE088B for ; Tue, 2 Jan 2018 22:58:17 +0000 (UTC) Received: by mail-oi0-x242.google.com with SMTP id t81so34164498oih.13 for ; Tue, 02 Jan 2018 14:58:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=xB8uqxp7DIoL8zkz6mQBhF960IgVOlsWhahGbxQYJec=; b=fAXkYiZMMLVZMD6sup0jmm8L8dlJlKder9J/FGwBKaMbhif4Q0occiM1q1tb46CFXj KfwDBLyeVZkVsu96uBR1a6FpOdBWOScE2vlTPRpOca0o7hAX20v4SDFdHeTRNq1qiYJ4 evt6hGvX+2Pd8URRKcCucxqtmIIt8nO0qZnBScCosUtl4A0tVuh3W3Hhxa9nkTchcmZ9 ZYi6lplDzcemx0HFYdDIEdX6yfrnt/iVxid2PqRP07UDUCM3K2Dmj5GGZDXya1EVlijU aW9QeEPbJtjb6vYOI8O35PmMgjPFmKc3Wg2rcQjbu44IFIjJQEIn9QrMQ4QNChKuAGq4 lpWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=xB8uqxp7DIoL8zkz6mQBhF960IgVOlsWhahGbxQYJec=; b=VnAcwIQXvno875/P6BCaNfSwBLKl9dcwIG39lFeYsn+8q+0NzVae8N9lggF95wcb1C +A4SwesTJYuw7av9evmRj1PDuw3vSO20rU/msDjLDdjAWs7hMmdUiGcKm6PVDGafBh14 nPjgXD7jFg6Qodumumleu4zCLjpjBlWu4UzG2uQrMUIfkui7fhO6Osd0VmGCHBpMyzYT ADsh5KSsgh4KXZZpN+QiJOCvqJJFiYWDSKA8uneiSCTgtM1aMdd8z3XN3LUu5kdvuVNQ oYT++jyQ+cGu20Ix2hsJRW/shTsCdiWsV8w+EJ+wII1GWo3UZPLMuK1weu7+W80DGc2m uAYA== X-Gm-Message-State: AKGB3mIHiOg7Z7U8aJw1rMBLLae2bO1jAtRPR6lfr+FOer/JETRtsP30 /KGDjjkaLvDj2MJ6PMojsEp1vMMgkyLWNSUU/JmhMJOZ X-Google-Smtp-Source: ACJfBotxy123uh8WNx0T/o4aIYh/wFYtyh7FW5p4AEmN2xcyILU71S2mj9imwFsmvhXrpZXHMQMYJ6Y7+q5k/GPbMt4= X-Received: by 10.202.198.203 with SMTP id w194mr29824781oif.132.1514933896503; Tue, 02 Jan 2018 14:58:16 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.157.19.65 with HTTP; Tue, 2 Jan 2018 14:58:16 -0800 (PST) In-Reply-To: References: <2CA973AB-B583-4F4F-A0B3-0FE347A672BD@stellar.eclipse.co.uk> From: Adam Carter Date: Wed, 3 Jan 2018 09:58:16 +1100 Message-ID: Subject: Re: [gentoo-user] Re: old kernels are installed during the upgrade To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary="001a1134fc7ec2659c0561d308bd" X-Archives-Salt: fa37e192-6660-490a-aa23-c8761f166605 X-Archives-Hash: fbf80fa16ccec57f424c92365785be35 --001a1134fc7ec2659c0561d308bd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > > And on that note I see that upstream just released 4.14.11 containing > what is widely speculated as a fix for an Intel CPU security > vulnerability. I noticed that it doesn't disable the > performance-impacting setting on AMD CPUs. Though, right now only AMD > could say whether this is necessary (their lkml post suggests it is > not). This is an upstream release - I don't know when Gentoo plans to > release it. I'm sure it will be making the rounds in the various news > sites any day. > https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/ "The effects are still being benchmarked, however we're looking at a ballpark figure of five to 30 per cent slow down, depending on the task and the processor model. More recent Intel chips have features =E2=80=93 specif= ically, PCID =E2=80=93 to re= duce the performance hit." AMD coder's patch to disable the new code (to avoid the performance hit) where he states the issue doesnt exist on AMD processors; https://lkml.org/lkml/2017/12/27/2 --001a1134fc7ec2659c0561d308bd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
<= div class=3D"gmail_quote">
And on that note I see that upstream just released 4.14.11 containing
what is widely speculated as a fix for an Intel CPU security
vulnerability.=C2=A0 I noticed that it doesn't disable the
performance-impacting setting on AMD CPUs.=C2=A0 Though, right now only AMD=
could say whether this is necessary (their lkml post suggests it is
not).=C2=A0 This is an upstream release - I don't know when Gentoo plan= s to
release it.=C2=A0 I'm sure it will be making the rounds in the various = news
sites any day.

<= /div>
https://www.theregister.co.uk/2018/01/02/i= ntel_cpu_design_flaw/

"The effects are still being benchmarked, however = we're looking at a=20 ballpark figure of five to 30 per cent slow down, depending on the task=20 and the processor model. More recent Intel chips have features =E2=80=93=20 specifically, PCID =E2=80=93 to reduce the= performance hit."

AMD coder's patch to disable the new code (to avoid t= he performance hit) where he states the issue doesnt exist on AMD processor= s;
https://lkml.org/lkml/2017/12/27/2


--001a1134fc7ec2659c0561d308bd--