From: Ben Hutchings <ben@decadent.org.uk>
To: speck@linutronix.de
Subject: [MODERATED] Re: The Annnoying Affair has No eXcuses - Bulletin #4
Date: Sat, 09 Nov 2019 19:59:48 +0000 [thread overview]
Message-ID: <ca9bd2c36ed33ff7948d9df486d7dd7094b74a11.camel@decadent.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.21.1911072112150.27903@nanos.tec.linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1387 bytes --]
On Thu, 2019-11-07 at 21:17 +0100, speck for Thomas Gleixner wrote:
> Folks,
>
> I've picked up Paolos backports and updated the stable branches
> linux-5.3.y, linux-4.19.y and linix-4.14.y, which also have been rebased to
> the latest stable versions.
>
> The changes are available as usual from:
>
> cvs.ou.linutronix.de:linux/speck/linux
>
> Git bundles for the linux-5.3.y, linux-4.19.y and linix-4.14.y branches
> against their upstream versions are attached.
Comparing my linux-4.19.y branch with yours:
- "KVM: x86: adjust kvm_mmu_page member to save 8 bytes"
OK, that's not important.
+ "KVM: x86: use Intel speculation bugs and features as derived in generic x86 code"
Probably a worthwhile improvement. I don't know.
+ "x86/cpu: Add Tremont to the cpu vulnerability whitelist"
OK, also not important.
+ "x86/speculation/taa: Fix printing of TAA_MSG_SMT on IBRS_ALL CPUs"
and beyond that there are small differences in member ordering in
struct kvm_mmu_page and whitespace.
Comparing my linux-4.14.y branch with yours, there are the same
differences plus:
- "KVM: MMU: drop vcpu param in gpte_access" (commit 42522d08cdba)
I think you should add this.
Ben.
--
Ben Hutchings
Everything should be made as simple as possible, but not simpler.
- Albert Einstein
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-11-09 20:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 20:17 The Annnoying Affair has No eXcuses - Bulletin #4 Thomas Gleixner
2019-11-08 10:35 ` [MODERATED] " Greg KH
2019-11-09 19:59 ` Ben Hutchings [this message]
2019-11-09 20:04 ` Ben Hutchings
2019-11-11 11:27 ` Thomas Gleixner
2019-11-11 13:03 ` [MODERATED] " Paolo Bonzini
2019-11-11 15:41 ` Thomas Gleixner
2019-11-09 22:39 ` [MODERATED] " Ben Hutchings
2019-11-09 23:57 ` Ben Hutchings
2019-11-10 0:30 ` Ben Hutchings
2019-11-11 17:22 ` mark gross
2019-11-11 19:03 ` mark gross
2019-11-12 2:26 ` Pawan Gupta
2019-11-14 6:12 ` Greg KH
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=ca9bd2c36ed33ff7948d9df486d7dd7094b74a11.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--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 NNTP newsgroup(s).