From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: boris.ostrovsky@oracle.com, david.vrabel@citrix.com
Subject: [Ksummit-discuss] Topic: Removal of code that is still in use by users but there is a better code.
Date: Tue, 10 Jun 2014 16:12:36 -0400 [thread overview]
Message-ID: <20140610201236.GA21729@laptop.dumpdata.com> (raw)
Hey,
I would want to propose a topic on removing code in Linux that
users are using - but they are doing it less and less and it
mostly is tied in with older hardware. Specifically how to do
this transition properly - and if we want to define some checklist
/policy to do it via.
Specifically in the Xen virtualization world there is in pipeline code
that is going to obsolete some of the existing pvops code - and also
make lguest obsolete. It makes the Linux kernel run faster, less code to
deal with, makes x86 folks happy, and requires newer hardware.
This is known as PVH (ParaVirtualization Hardware).
So, from one hand - with newer hardware - we can remove some of the
code. On the other hand - with older hardware (pre EPT/NPT capable) or
low-powered ones - we would making their life difficult and slower (as now
the hypervisor has to do the emulation, probably has some bugs, code
bitrotten, etc).
In essence it boils down to removing code in X years that users do use.
There is a nice migration path, but I am sure the moment we rip out the
code folks will come out of the woodwork, chase us down, and hit us with clubs.
I do enjoy hiking and don't want to have to look behind my back as I am
hiking.
What I want to propose is a topic to discuss what is the right way to do
this? I presume other platforms have had similar issues in the past (or
will be) and what is the best way of doing this. Are there any policies
in place?
P.S.
I say in pipeline because it is still experimental, the ABI hasn't been
bolted down, and we have tons of outstanding bugs before we let
enterprise customers take a stab at it, etc.
P.S.S.
Peter (hpa) is going to hate that I put 'X' instead of the '5' number. We
figured that in 5 years since we get this stable we can start the
count-down timer - but the 'getting' stable seems to take longer than I
am happy with (#@)@#$ bugs). Hence, X = stable + 5. If there are any
next reply other threads:[~2014-06-10 20:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 20:12 Konrad Rzeszutek Wilk [this message]
2014-06-10 20:19 ` H. Peter Anvin
2014-06-11 0:36 ` josh
2014-06-11 15:56 ` H. Peter Anvin
2014-06-11 20:02 ` josh
2014-06-11 17:54 ` Guenter Roeck
2014-06-11 19:43 ` Bjorn Helgaas
2014-06-11 21:53 ` Stephen Rothwell
2014-06-11 22:01 ` Andy Lutomirski
2014-06-11 22:17 ` James Bottomley
2014-06-11 22:26 ` Roland Dreier
2014-06-11 22:36 ` James Bottomley
2014-06-12 11:41 ` Rafael J. Wysocki
2014-06-12 13:27 ` John W. Linville
2014-06-13 1:36 ` James Bottomley
2014-06-19 13:01 ` Linus Walleij
2014-06-11 23:22 ` Guenter Roeck
2014-06-12 2:48 ` Steven Rostedt
2014-06-12 7:16 ` Geert Uytterhoeven
2014-06-12 0:07 ` H. Peter Anvin
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=20140610201236.GA21729@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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