From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Voegtle <tv@lio96.de>
Cc: "David Woodhouse" <dwmw@amazon.co.uk>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Jim Mattson" <jmattson@google.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
"KarimAllah Ahmed" <karahmed@amazon.de>,
stable@vger.kernel.org
Subject: Re: [STABLE 4.9.y PATCH 0/9] Backport of KVM Speculation Control support
Date: Thu, 15 Feb 2018 14:57:14 +0100 [thread overview]
Message-ID: <20180215135714.GA30750@kroah.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1802151148570.14387@er-systems.de>
On Thu, Feb 15, 2018 at 11:49:54AM +0100, Thomas Voegtle wrote:
> On Thu, 15 Feb 2018, Greg KH wrote:
>
> > On Thu, Feb 15, 2018 at 11:15:41AM +0100, Thomas Voegtle wrote:
> > >
> > > Hello,
> > >
> > > On Tue, 6 Feb 2018, David Woodhouse wrote:
> > >
> > > > I've put together a linux-4.9.y branch at
> > > > http://git.infradead.org/retpoline-stable.git/shortlog/refs/heads/linux-4.9.y
> > >
> > >
> > > Are there any plans for a backport to v4.4?
> > >
> > > I would volunteer for testing ;)
> >
> > Care to volunteer to do the backport? :)
> >
> > Why do you need/want this type of thing for 4.4.y? What is keeping you
> > from moving to 4.9.y instead? Or even better yet, 4.14.y or 4.15, where
> > everything is fixed "correctly"?
>
>
> Puhh, I would love to do the backport but I had a quick look at the patch
> series and that is beyond my scope, I'm afraid. I'm a tester ;)
>
> If there are no plans I know I have to move to a newer kernel, sadly.
You should always move to a newer kernel, what is holding you back from
doing that today? Please, move to 4.14.y if you want a "LTS" kernel to
survive you for the year, and if not, then use 4.15.y please.
Seriously, staying on old kernels should not happen, unless you are
paying someone for support of such a thing (i.e. you have specific
hardware support only for an old kernel version.)
thanks,
greg k-h
prev parent reply other threads:[~2018-02-15 13:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 17:29 [STABLE 4.9.y PATCH 0/9] Backport of KVM Speculation Control support David Woodhouse
2018-02-06 17:29 ` [PATCH 1/9] KVM: nVMX: vmx_complete_nested_posted_interrupt() can't fail David Woodhouse
2018-02-06 17:29 ` [PATCH 2/9] KVM: nVMX: mark vmcs12 pages dirty on L2 exit David Woodhouse
2018-02-06 17:29 ` [PATCH 3/9] KVM: nVMX: Eliminate vmcs02 pool David Woodhouse
2018-02-06 17:29 ` [PATCH 4/9] KVM: VMX: introduce alloc_loaded_vmcs David Woodhouse
2018-02-06 17:29 ` [PATCH 5/9] KVM: VMX: make MSR bitmaps per-VCPU David Woodhouse
2018-02-06 17:29 ` [PATCH 6/9] KVM/x86: Add IBPB support David Woodhouse
2018-02-06 17:29 ` [PATCH 7/9] KVM/VMX: Emulate MSR_IA32_ARCH_CAPABILITIES David Woodhouse
2018-02-16 14:18 ` Paolo Bonzini
2018-02-16 16:29 ` Jim Mattson
2018-02-16 16:33 ` David Woodhouse
2018-02-06 17:29 ` [PATCH 8/9] KVM/VMX: Allow direct access to MSR_IA32_SPEC_CTRL David Woodhouse
2018-02-16 4:02 ` Jim Mattson
2018-02-16 4:16 ` Jim Mattson
2018-02-06 17:29 ` [PATCH 9/9] KVM/SVM: " David Woodhouse
2018-02-06 18:01 ` [STABLE 4.9.y PATCH 0/9] Backport of KVM Speculation Control support Paolo Bonzini
2018-02-06 21:05 ` Woodhouse, David
2018-02-08 2:49 ` Greg KH
2018-02-08 17:14 ` Greg KH
2018-02-08 17:42 ` Paolo Bonzini
2018-02-08 17:57 ` Greg KH
2018-02-09 7:58 ` Greg KH
2018-02-15 10:15 ` Thomas Voegtle
2018-02-15 10:23 ` Greg KH
2018-02-15 10:49 ` Thomas Voegtle
2018-02-15 13:57 ` Greg KH [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=20180215135714.GA30750@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dwmw@amazon.co.uk \
--cc=jmattson@google.com \
--cc=karahmed@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tv@lio96.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