From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Greg KH <greg@kroah.com>
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 12:43:52 -0400 [thread overview]
Message-ID: <135393.1597855432@turing-police> (raw)
In-Reply-To: <20200819104254.GA41946@kroah.com>
[-- Attachment #1.1: Type: text/plain, Size: 338 bytes --]
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... :)
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
WARNING: multiple messages have this Message-ID (diff)
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Greg KH <greg@kroah.com>
Cc: Muni Sekhar <munisekharrms@gmail.com>,
peter enderborg <peter.enderborg@sony.com>,
kernelnewbies <kernelnewbies@kernelnewbies.org>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: Scheduler benchmarks
Date: Wed, 19 Aug 2020 12:43:52 -0400 [thread overview]
Message-ID: <135393.1597855432@turing-police> (raw)
In-Reply-To: <20200819104254.GA41946@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 338 bytes --]
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... :)
[-- Attachment #2: Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-08-19 16:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 14:30 Scheduler benchmarks Muni Sekhar
2020-08-18 14:30 ` Muni Sekhar
2020-08-18 14:36 ` Greg KH
2020-08-18 14:36 ` Greg KH
2020-08-18 16:01 ` Muni Sekhar
2020-08-18 16:50 ` Muni Sekhar
2020-08-18 16:54 ` Muni Sekhar
2020-08-18 16:54 ` Muni Sekhar
2020-08-18 17:14 ` Greg KH
2020-08-18 17:14 ` Greg KH
2020-08-18 17:31 ` Muni Sekhar
2020-08-18 17:31 ` Muni Sekhar
2020-08-18 17:36 ` Greg KH
2020-08-18 17:36 ` Greg KH
2020-08-18 17:53 ` Muni Sekhar
2020-08-18 17:53 ` Muni Sekhar
2020-08-18 18:15 ` peter enderborg
2020-08-18 18:15 ` peter enderborg
2020-08-18 18:15 ` peter enderborg
2020-08-19 10:16 ` Muni Sekhar
2020-08-19 10:16 ` Muni Sekhar
2020-08-19 10:21 ` Bernd Petrovitsch
2020-08-19 10:21 ` Bernd Petrovitsch
2020-08-19 14:36 ` David Laight
2020-08-19 14:36 ` David Laight
2020-08-19 10:42 ` Greg KH
2020-08-19 10:42 ` Greg KH
2020-08-19 16:43 ` Valdis Klētnieks [this message]
2020-08-19 16:43 ` Valdis Klētnieks
2020-08-19 16:47 ` Greg KH
2020-08-19 16:47 ` Greg KH
2021-04-29 21:32 ` Arnaldo Carvalho de Melo
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=135393.1597855432@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=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 \
/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.