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 10:50:25 -0000 Received: from mx2.suse.de ([195.135.220.15] helo=mx1.suse.de) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1iHn4R-0007Sm-IO for speck@linutronix.de; Tue, 08 Oct 2019 12:50:24 +0200 Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id F210BAF62 for ; Tue, 8 Oct 2019 10:50:17 +0000 (UTC) Date: Tue, 8 Oct 2019 12:49:44 +0200 (CEST) From: Jiri Kosina Subject: [MODERATED] Re: [PATCH v5 09/11] TAAv5 9 In-Reply-To: <20191008061040.GH5154@guptapadev.amr> Message-ID: References: <20191008025707.ykeeheocguh6jl52@treble> <20191008061040.GH5154@guptapadev.amr> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: On Mon, 7 Oct 2019, 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? > > I am not sure about this. We finally got a clearance to talk to one of the few potential heavy users of TSX. We should know more about the usecase and their expectations tomorrow. Either myself or Michal Hocko can then send an update to speck@. Thanks, -- Jiri Kosina SUSE Labs