From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH/RFC] KVM: Plan obsolescence of kernel allocated slots, paravirt mmu
Date: Wed, 27 Jan 2010 15:23:36 -0200 [thread overview]
Message-ID: <20100127172336.GA5807@amt.cnet> (raw)
In-Reply-To: <1264516474-11575-1-git-send-email-avi@redhat.com>
On Tue, Jan 26, 2010 at 04:34:34PM +0200, Avi Kivity wrote:
> These features are unused by modern userspace and can go away. Paravirt
> mmu needs to stay a little longer for live migration.
>
> Signed-off-by: Avi Kivity <avi@redhat.com>
> ---
> Documentation/feature-removal-schedule.txt | 23 +++++++++++++++++++++++
> 1 files changed, 23 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
> index 870d190..88ca110 100644
> --- a/Documentation/feature-removal-schedule.txt
> +++ b/Documentation/feature-removal-schedule.txt
> @@ -493,3 +493,26 @@ Why: These two features use non-standard interfaces. There are the
> Who: Corentin Chary <corentin.chary@gmail.com>
>
> ----------------------------
> +What: KVM memory aliases support
> +When: July 2010
> +Why: Memory aliasing support is used for speeding up guest vga access
> + through the vga windows.
> +
> + Modern userspace no longer uses this feature, so it's just bitrotted
> + code and can be removed with no impact.
> +Who: Avi Kivity <avi@redhat.com>
> +----------------------------
> +What: KVM kernel-allocated memory slots
> +When: July 2010
> +Why: Since 2.6.25, kvm supports user-allocated memory slots, which are
> + much more flexible than kernel-allocated slots. All current userspace
> + supports the newer interface and this code can be removed with no
> + impact.
Just a note: can block userspace usage but can't really remove code
since there are in-kernel users (special purpose vmx pages).
Otherwise looks good to me.
> +Who: Avi Kivity <avi@redhat.com>
> +----------------------------
> +What: KVM paravirt mmu host support
> +When: January 2011
> +Why: The paravirt mmu host support is slower than non-paravirt mmu, both
> + on newer and older hardware. It is already not exposed to the guest,
> + and kept only for live migration purposes.
> +Who: Avi Kivity <avi@redhat.com>
> --
> 1.6.5.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-01-27 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 14:34 [PATCH/RFC] KVM: Plan obsolescence of kernel allocated slots, paravirt mmu Avi Kivity
2010-01-27 17:23 ` Marcelo Tosatti [this message]
2010-02-11 10:24 ` Avi Kivity
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=20100127172336.GA5807@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.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 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.