From: Paolo Bonzini <pbonzini@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: eager FPU backport for 2.6.32
Date: Mon, 11 Jun 2018 18:18:46 +0200 [thread overview]
Message-ID: <85e9fe2d-dc93-c765-cc58-16c27d052bc1@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.21.999.1806110855580.11010@xps13.linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
On 11/06/2018 17:59, speck for Linus Torvalds wrote:
>
> On Mon, 11 Jun 2018, speck for Josh Poimboeuf wrote:
>> Welcome to our nightmare. And let's not even mention RHEL5...
> Heh.
>
> Does the support contract really say "no package version changes"?
No, but there are some (not full of course) guarantees about drivers ABI
(not just API), and given stable-api-nonsense.txt there aren't many ways
to do it. Not that I disagree with stable-api-nonsense.txt, of course.
> Because after all it _is_ called "RHEL6", not "RHEL2.6.32".
>
> At some point, backporting stuff is just way more dangerous than just
> upgrading to a well-tested kernel.
It certainly is, but things get progressively calmer---and until they
don't, the backporting pace is crazy enough that conflicts are pretty
rare. It's somewhat self-regulating; at some point people start seeing
conflicts, that causes push back against new features, and luckily the
pointy-haired people do listen.
It usually works out fine, except when people discover everything is
broken in your CPUs and you have to backport 300-ish core MM and arch
patches eight years into the product lifetime. That's when the job
security part kicks in.
Paolo
next prev parent reply other threads:[~2018-06-11 16:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 8:33 [MODERATED] eager FPU backport for 2.6.32 Paolo Bonzini
2018-06-11 15:18 ` [MODERATED] " Linus Torvalds
2018-06-11 15:44 ` Peter Zijlstra
2018-06-11 15:51 ` Paolo Bonzini
2018-06-11 16:33 ` Jiri Kosina
2018-06-11 15:51 ` Josh Poimboeuf
2018-06-11 15:59 ` Linus Torvalds
2018-06-11 16:18 ` Paolo Bonzini [this message]
2018-07-31 7:35 ` Jiri Kosina
2018-07-31 8:15 ` Paolo Bonzini
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=85e9fe2d-dc93-c765-cc58-16c27d052bc1@redhat.com \
--to=pbonzini@redhat.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.