All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: speck@linutronix.de
Subject: [MODERATED] Re: Date/Time?
Date: Mon, 21 May 2018 18:46:55 +0200	[thread overview]
Message-ID: <20180521164655.GI17976@kroah.com> (raw)
In-Reply-To: <ab610f46-9e42-a9f6-5a79-65be1f3dc552@redhat.com>

On Sun, May 20, 2018 at 04:59:04PM -0400, speck for Jon Masters wrote:
> * ARM. They have a new SMCC (Secure Monitor Call) interface (similar to
> the one they did for branch predictor invalidation for Spectre-v2) that
> will be wired up with kernel patches. Each of the vendors will implement
> the new SMCC in ATF (Arm Trusted Firmware) on their parts, using the
> best back-end mitigation (similar to microcode). Arm know to ping Thomas
> with those patches, yet this has not happened yet (to my knowledge), nor
> to Greg. Will has point on this in any case. He and the team are working
> hard on this. Still, I am saddened by these patches not being available
> prior to disclosure since this is not how we do things in the server
> space. But in anticipation that this would happen, I worked directly
> with Cavium (the only server-class CPU vendor with production RHEL
> support for which we need an answer tomorrow on our end) to create a
> firmware knob that can be used in the short term until this is fixed. I
> also have pinged all of the Arm server vendors to let them know I expect
> all of the SMCC wiring to be in place within the next few weeks.

Just heard from ARM, they are going to wait a week or so and then send
patches for inclusion in 4.18 and then send some backports for the older
kernels then.  The kernel patches are useless without firmware updates
and I don't know what the state of them are.

They also complained that they can not finalize their patches as they do
not know what we agreed on for the prctl() interface.  Which sucks as
that was hashed out here weeks ago.

Another proof of how when we are not "allowed" to talk to the right
people, Linux users suffer.  That is not ok.

thanks,

greg k-h

  parent reply	other threads:[~2018-05-21 16:47 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-19 17:26 [MODERATED] Date/Time? Greg KH
2018-05-19 17:51 ` [MODERATED] Date/Time? Borislav Petkov
2018-05-19 18:45   ` Linus Torvalds
2018-05-19 19:07     ` [MODERATED] " Borislav Petkov
2018-05-19 19:48       ` Linus Torvalds
2018-05-19 20:22         ` [MODERATED] " Borislav Petkov
2018-05-20 20:58     ` Jon Masters
2018-05-19 18:21 ` David Woodhouse
2018-05-19 19:05   ` Greg KH
2018-05-20 19:23   ` David Woodhouse
2018-05-20 23:01   ` David Woodhouse
2018-05-21  8:35     ` Greg KH
2018-05-20 17:45 ` Jiri Kosina
2018-05-20 18:19   ` Greg KH
2018-05-20 18:35     ` Borislav Petkov
2018-05-20 19:57       ` Greg KH
2018-05-20 18:36     ` Linus Torvalds
2018-05-20 18:48       ` Jiri Kosina
2018-05-20 20:59 ` Jon Masters
2018-05-20 21:09   ` Jiri Kosina
2018-05-21  6:11     ` Greg KH
2018-05-20 21:48   ` Linus Torvalds
2018-05-20 21:56     ` David Woodhouse
2018-05-21  6:16   ` Greg KH
2018-05-21  7:18     ` David Woodhouse
2018-05-21 15:23       ` Date/Time? Thomas Gleixner
2018-05-21 16:46   ` Greg KH [this message]
2018-05-21 17:12     ` [MODERATED] Date/Time? Konrad Rzeszutek Wilk
2018-05-21 19:42       ` Greg KH
2018-05-21 19:48         ` Jiri Kosina
2018-05-21 20:30           ` Jon Masters
2018-05-22  8:00             ` Peter Zijlstra
2018-05-22  9:26               ` Greg KH
2018-05-22 16:32                 ` Andi Kleen
2018-05-23 14:15                 ` Jon Masters
2018-05-21 17:22     ` Jon Masters
2018-05-21 18:56       ` Date/Time? Thomas Gleixner
2018-05-21 19:16         ` [MODERATED] Date/Time? Jon Masters
2018-05-21 20:43           ` Greg KH
2018-05-21 17:31     ` Jon Masters
2018-05-21 18:53     ` Date/Time? Thomas Gleixner

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=20180521164655.GI17976@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=speck@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.