All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo@kvack.org>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [patch 1/5] KVM: add basic paravirt support (v2)
Date: Thu, 21 Feb 2008 12:55:31 -0300	[thread overview]
Message-ID: <20080221155530.GA30590@dmt> (raw)
In-Reply-To: <47BD9AF6.7020206@qumranet.com>

On Thu, Feb 21, 2008 at 05:38:30PM +0200, Avi Kivity wrote:
> Marcelo Tosatti wrote:
> >Add basic KVM paravirt support. Avoid vm-exits on IO delays.
> >
> >Add KVM_GET_PARA_FEATURES ioctl so paravirt features can be reported in a
> >single bitmask. This allows the host to disable features on runtime if 
> >appropriate, which would require one ioctl per feature otherwise.
> >
> >The limit of 32 features can be extended to 64 if needed, beyond that a 
> >new MSR is required.
> >
> >v1->v2:
> >- replace KVM_CAP_CLOCKSOURCE with KVM_CAP_PARA_FEATURES
> >- cover FEATURE_CLOCKSOURCE
> >
> >
> >  
> 
> I don't understand the motivation for this.  A handful of ioctl()s at 
> init time are hardly time consuming.
> 
> There is the advantage that paravirt kernel advances are reflected 
> automatically without changes in userspace, but sometimes this is a 
> disadvantage (it means there is no way to disable it, for instance).

One ioctl per feature sounded like unnecessary code duplication. I have
no problems with it though. So you prefer that way?

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  reply	other threads:[~2008-02-21 15:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 19:47 [patch 0/5] KVM paravirt MMU updates and cr3 caching (v2) Marcelo Tosatti
2008-02-20 19:47 ` [patch 1/5] KVM: add basic paravirt support (v2) Marcelo Tosatti
2008-02-21 15:38   ` Avi Kivity
2008-02-21 15:55     ` Marcelo Tosatti [this message]
2008-02-21 18:31       ` Avi Kivity
2008-02-20 19:47 ` [patch 2/5] KVM: hypercall based pte updates and TLB flushes (v2) Marcelo Tosatti
2008-02-21 15:43   ` Avi Kivity
2008-02-20 19:47 ` [patch 3/5] KVM: hypercall batching (v2) Marcelo Tosatti
2008-02-21 15:52   ` Avi Kivity
2008-02-21 18:05     ` Marcelo Tosatti
2008-02-21 18:30       ` Avi Kivity
2008-02-21 19:31         ` Marcelo Tosatti
2008-02-22  7:10           ` Avi Kivity
2008-02-20 19:47 ` [patch 4/5] KVM: ignore zapped root pagetables (v2) Marcelo Tosatti
2008-02-21 15:57   ` Avi Kivity
2008-02-20 19:47 ` [patch 5/5] KVM: VMX cr3 cache support (v2) Marcelo Tosatti

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=20080221155530.GA30590@dmt \
    --to=marcelo@kvack.org \
    --cc=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    /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.