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 ; 08 Oct 2019 02:57:17 -0000 Received: from mx1.redhat.com ([209.132.183.28]) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1iHfga-00009k-17 for speck@linutronix.de; Tue, 08 Oct 2019 04:57:16 +0200 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 28C6D6907A for ; Tue, 8 Oct 2019 02:57:09 +0000 (UTC) Received: from treble (ovpn-121-70.rdu2.redhat.com [10.10.121.70]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D0C97600C1 for ; Tue, 8 Oct 2019 02:57:08 +0000 (UTC) Date: Mon, 7 Oct 2019 21:57:07 -0500 From: Josh Poimboeuf Subject: [MODERATED] Re: [PATCH v5 09/11] TAAv5 9 Message-ID: <20191008025707.ykeeheocguh6jl52@treble> References: =?utf-8?q?=3C359ce9cf9388518b5b18a0d79583cb97063c2f80=2E1570255065=2Egi?= =?utf-8?q?t=2Epawan=2Ekumar=2Egupta=40linux=2Eintel=2Ecom=3E?= MIME-Version: 1.0 In-Reply-To: =?utf-8?q?=3C359ce9cf9388518b5b18a0d79583cb97063c2f80=2E15702?= =?utf-8?q?55065=2Egit=2Epawan=2Ekumar=2Egupta=40linux=2Eintel=2Ecom=3E?= Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: On Fri, Oct 04, 2019 at 11:34:31PM -0700, speck for Pawan Gupta wrote: > Transactional Synchronization Extensions (TSX) is an extension to the > x86 instruction set architecture (ISA) that adds Hardware Transactional > Memory (HTM) support. Changing TSX state currently requires a reboot. > This may not be desirable when rebooting imposes a huge penalty. This is still missing a real world justification for the added complexity. Don't production users typically know at boot time whether they plan to use TSX? It looks like this patch should be combined with patch 10, since otherwise this patch causes a regression in the sysfs mitigation reporting, right? And again... this patch needs to be last. Even after the documentation. If it triggers documentation changes then those changes should be separated out and included in this patch. Otherwise, this patch may block the merging of the documentation patch. -- Josh