From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v6 07/11] [PATCH v6 07/10] Linux Patch #7
Date: Sun, 29 Apr 2018 08:42:12 -0400 [thread overview]
Message-ID: <20180429124207.GA9972@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.21.1804290917330.1595@nanos.tec.linutronix.de>
..giant snip..
> > Taking this one step further - the init_amd or init_intel could
> > call the ssb_latch_mitigation_boot_cpu() function (which now should be
> > called ssb_latch_mitigation) - and that would put all the bit/MSR
> > fiddling code in one location (bugs.c).
> >
> > I think this is what you had in mind. I will do those changes tomorrow
> > night and try them out, unless you had in mind a different way?.
>
> Very close. I just integrate it with a sane version of the prctl stuff and
> I should have something later today. Untested obviously because I have no
> access to the magic ucode ...
I would be more than happy to test it and do the fixes up (just in case
some gremlin came by) tonight on the Intel box. Please send a tarball.
Or alternatively if you would like to send me your public SSH key
I have an Skylake monster beast in the cloud (the SSH key would be used
for SSH in the machine and in the serial console).
>
> Thanks,
>
> tglx
next prev parent reply other threads:[~2018-04-29 12:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 23:48 [MODERATED] [PATCH v6 07/11] [PATCH v6 07/10] Linux Patch #7 konrad.wilk
2018-04-28 19:38 ` Thomas Gleixner
2018-04-29 2:13 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-04-29 7:22 ` Thomas Gleixner
2018-04-29 12:42 ` Konrad Rzeszutek Wilk [this message]
2018-04-29 16:19 ` [MODERATED] " Jon Masters
2018-04-29 16:57 ` Thomas Gleixner
2018-04-29 17:05 ` [MODERATED] " Linus Torvalds
2018-04-29 18:08 ` Thomas Gleixner
2018-04-29 18:09 ` Thomas Gleixner
2018-04-29 18:29 ` [MODERATED] " Jon Masters
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=20180429124207.GA9972@localhost.localdomain \
--to=konrad.wilk@oracle.com \
--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.