Historical speck list archives
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: speck@linutronix.de
Subject: Re: L1TF counter
Date: Mon, 20 Aug 2018 22:41:40 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1808202238060.1686@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20180820201809.GA16987@agluck-desk>

[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]

On Mon, 20 Aug 2018, speck for Luck, Tony wrote:
> On Mon, Aug 20, 2018 at 09:44:15PM +0200, speck for Thomas Gleixner wrote:
> > On Mon, 20 Aug 2018, speck for Konrad Rzeszutek Wilk wrote:
> > > On Mon, Aug 20, 2018 at 06:11:26PM +0100, speck for Andrew Cooper wrote:
> > > > On 20/08/2018 17:52, speck for Konrad Rzeszutek Wilk wrote:
> > > > > Hey,
> > > > >
> > > > > Intel has mentioned that they are working on a new microcode which can
> > > > > be used to detect L1TF conditions. 
> > > > >
> > > > > Anyone is working on it? I was thinking to start crafting patches
> > > > > based on the description of the MSR and post them here for review.
> > > > >
> > > > > But if someone is already busy with that I would rather review them :-)
> > > > >
> > > > 
> > > > There are no details currently available.  Intel are planning to get us
> > > > production signed alpha builds of microcode as soon as they've worked
> > > > out why the latest build isn't working.
> > > 
> > > Sure. But the PDF is there. Or are you saying it is pointless as they may
> > > change the PDF again?
> > 
> > 1) Which PDF?
> 
> It's been shared with some partners (but really doesn't say much yet, just
> that the MSR has a couple of counts that help to detect L1TF attacks).

Is there any reason why this PDF can't be distributed on that very list
where all people subscribed are briefed, rubberstamped and fumigated?

> > 2) Is this secrit sauce or can we just discuss that on LKML?
> 
> Yes secrit sauce. No discussion on public lists yet.

Oh well.

Thanks,

	tglx

      reply	other threads:[~2018-08-20 20:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-20 16:52 [MODERATED] L1TF counter Konrad Rzeszutek Wilk
2018-08-20 17:11 ` [MODERATED] " Andrew Cooper
2018-08-20 17:20   ` Konrad Rzeszutek Wilk
2018-08-20 19:44     ` Thomas Gleixner
2018-08-20 20:18       ` [MODERATED] " Luck, Tony
2018-08-20 20:41         ` 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=alpine.DEB.2.21.1808202238060.1686@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).