From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 044A5C3A5A6 for ; Wed, 28 Aug 2019 12:46:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C66CB22DA7 for ; Wed, 28 Aug 2019 12:46:28 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alien8.de header.i=@alien8.de header.b="ANJ2J/8Q" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726341AbfH1Mq2 (ORCPT ); Wed, 28 Aug 2019 08:46:28 -0400 Received: from mail.skyhub.de ([5.9.137.197]:47058 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726270AbfH1Mq2 (ORCPT ); Wed, 28 Aug 2019 08:46:28 -0400 Received: from zn.tnic (p200300EC2F0A5300B1A6357224C8EB83.dip0.t-ipconnect.de [IPv6:2003:ec:2f0a:5300:b1a6:3572:24c8:eb83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 596B01EC09E2; Wed, 28 Aug 2019 14:46:26 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1566996386; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=YotASNKG5TQSIo5/90ZJMMOo66u6rq+Oxb5MG7ExeFI=; b=ANJ2J/8Qgwxx2nKsfT3swocAsnLzRZS10vUSsL9UD+cLKvyOm49ULSHJl4vQTFa2Vwnp60 2tNRkKLRq05O9sokFKiG5dlleG3PLvhXaK++tvwHsGx84jexrhunszr8RoDIXSeJpWCoP5 kit090PCjxJItAS0rgxU07S8c5EvYRs= Date: Wed, 28 Aug 2019 14:46:21 +0200 From: Borislav Petkov To: Pavel Machek Cc: Thomas Gleixner , Greg Kroah-Hartman , linux-kernel@vger.kernel.org, stable@vger.kernel.org, Tom Lendacky , Andrew Cooper , Andrew Morton , Chen Yu , "H. Peter Anvin" , Ingo Molnar , Jonathan Corbet , Josh Poimboeuf , Juergen Gross , Kees Cook , "linux-doc@vger.kernel.org" , "linux-pm@vger.kernel.org" , Nathan Chancellor , Paolo Bonzini , "Rafael J. Wysocki" , "x86@kernel.org" Subject: Re: [PATCH 4.19 72/98] x86/CPU/AMD: Clear RDRAND CPUID bit on AMD family 15h/16h Message-ID: <20190828124621.GI4920@zn.tnic> References: <20190827072722.020603090@linuxfoundation.org> <20190827113604.GB18218@amd> <20190828103113.GA14677@amd> <20190828114947.GC8052@amd> <20190828120024.GF4920@zn.tnic> <20190828120935.GD8052@amd> <20190828121628.GG4920@zn.tnic> <20190828122913.GE8052@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190828122913.GE8052@amd> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org On Wed, Aug 28, 2019 at 02:29:13PM +0200, Pavel Machek wrote: > This is not a way to have an inteligent conversation. No, this *is* the way to keep the conversation sane, without veering off into some absurd claims. So, to cut to the chase: you can simply add "rdrand=force" to your cmdline parameters and get back to using RDRAND. And yet if you still feel this fix does not meet your expectations, you were told already to either produce patches or who to contact. I'm afraid complaining on this thread won't get you anywhere but that's your call. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.