From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm list <kvm@vger.kernel.org>,
virtualization@lists.linux-foundation.org,
Glauber Costa <glommer@redhat.com>, Nick Piggin <npiggin@suse.de>
Subject: Re: [PATCH 0/3] Split up pv-ops
Date: Thu, 19 Nov 2009 09:42:10 +0200 [thread overview]
Message-ID: <4B04F6D2.8080805@redhat.com> (raw)
In-Reply-To: <1258503192-14246-1-git-send-email-agraf@suse.de>
On 11/18/2009 02:13 AM, Alexander Graf wrote:
> Paravirt ops is currently only capable of either replacing a lot of Linux
> internal code or none at all. The are users that don't need all of the
> possibilities pv-ops delivers though.
>
> On KVM for example we're perfectly fine not using the PV MMU, thus not
> touching any MMU code. That way we don't have to improve pv-ops to become
> fast, we just don't compile the MMU parts in!
>
> This patchset splits pv-ops into several smaller config options split by
> feature category and then converts the KVM pv-ops code to use only the
> bits that are required, lowering overhead.
>
> Alexander Graf (3):
> Split paravirt ops by functionality
> Only export selected pv-ops feature structs
> Split the KVM pv-ops support by feature
>
>
The whole thing looks good to me. Let's wait for Jeremy to ack though.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-11-19 7:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 0:13 [PATCH 0/3] Split up pv-ops Alexander Graf
2009-11-18 0:13 ` [PATCH 1/3] Split paravirt ops by functionality Alexander Graf
2009-11-19 14:59 ` Jeremy Fitzhardinge
2009-11-19 15:21 ` Alexander Graf
2009-11-18 0:13 ` [PATCH 2/3] Only export selected pv-ops feature structs Alexander Graf
2009-11-18 0:13 ` [PATCH 3/3] Split the KVM pv-ops support by feature Alexander Graf
2009-11-18 1:33 ` Rusty Russell
2009-11-18 1:37 ` Alexander Graf
2009-11-19 7:42 ` Avi Kivity [this message]
2009-12-03 14:52 ` [PATCH 0/3] Split up pv-ops Alexander Graf
2009-12-03 15:00 ` Avi Kivity
2009-12-03 15:04 ` Alexander Graf
2009-12-03 15:07 ` 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=4B04F6D2.8080805@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=glommer@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=virtualization@lists.linux-foundation.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