public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Nelson D'Souza <nelson.dsouza@linux.intel.com>, bp@alien8.de
Cc: mingo@redhat.com, x86@kernel.org, hpa@zytor.com,
	linux-kernel@vger.kernel.org, Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH v1] x86/cpu/tsx: Change the TSX default from "off" to "auto"
Date: Thu, 07 May 2020 03:11:25 +0200	[thread overview]
Message-ID: <877dxok0qq.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20200506221459.29104-1-nelson.dsouza@linux.intel.com>

Nelson D'Souza <nelson.dsouza@linux.intel.com> writes:
> There are now several commercially available processors that have h/w
> fixes for the TSX Async Abort (TAA) issue as indicated by enumerating
> the ARCH_CAPABILITIES "TAA_NO" bit.
>
> Change the default setting to "auto" so that these CPUs will leave
> TSX enabled by default.

You are telling WHAT the patch does, but not the WHY.

It's completely uninteresting whether TAA is fixed in a particular CPU
simply because:

   1) TAA is only one particular issue of TSX.

   2) The main use case for TSX is to accelerate all sorts of
      speculation attacks and other malignances

   3) There is excatly ONE known use case which cares about TSX and we
      already discussed to death that the machines on which that use
      case runs have admins which are capable of adding tsx=on on the
      command line.

So unless you come up with some really convincing argument why this
should be changed, this is not going to happen.

Thanks,

        tglx





      reply	other threads:[~2020-05-07  1:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 22:14 [PATCH v1] x86/cpu/tsx: Change the TSX default from "off" to "auto" Nelson D'Souza
2020-05-07  1:11 ` Thomas Gleixner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877dxok0qq.fsf@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nelson.dsouza@linux.intel.com \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox