From: Greg KH <greg@kroah.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: linux-perf-users@vger.kernel.org,
Muni Sekhar <munisekharrms@gmail.com>,
linux-kernel@vger.kernel.org,
peter enderborg <peter.enderborg@sony.com>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Scheduler benchmarks
Date: Wed, 19 Aug 2020 18:47:35 +0200 [thread overview]
Message-ID: <20200819164735.GA3698439@kroah.com> (raw)
In-Reply-To: <135393.1597855432@turing-police>
On Wed, Aug 19, 2020 at 12:43:52PM -0400, Valdis Klētnieks wrote:
> On Wed, 19 Aug 2020 12:42:54 +0200, Greg KH said:
> > Look up Spectre and Meltdown for many many examples of what happened and
> > what went wrong with chip designs and how we had to fix these things in
> > the kernel a few years ago.
>
> And I'm sure that nobody sane thinks we're done with security holes
> caused by speculative execution... :)
Hah, not at all, the patches keep flowing in, as do the microcode
updates...
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-08-19 16:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 14:30 Scheduler benchmarks Muni Sekhar
2020-08-18 14:36 ` Greg KH
2020-08-18 16:54 ` Muni Sekhar
2020-08-18 17:14 ` Greg KH
2020-08-18 17:31 ` Muni Sekhar
2020-08-18 17:36 ` Greg KH
2020-08-18 17:53 ` Muni Sekhar
2020-08-18 18:15 ` peter enderborg
2020-08-19 10:16 ` Muni Sekhar
2020-08-19 10:21 ` Bernd Petrovitsch
2020-08-19 14:36 ` David Laight
2020-08-19 10:42 ` Greg KH
2020-08-19 16:43 ` Valdis Klētnieks
2020-08-19 16:47 ` Greg KH [this message]
2021-04-29 21:32 ` Arnaldo Carvalho de Melo
2020-08-25 17:06 ` Mulyadi Santosa
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=20200819164735.GA3698439@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=munisekharrms@gmail.com \
--cc=peter.enderborg@sony.com \
--cc=valdis.kletnieks@vt.edu \
/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 NNTP newsgroup(s).