From: Luca <kronos.it@gmail.com>
To: "Avi Kivity" <avi@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [kvm-devel] [PATCH 2/2] KVM: Use the scheduler preemption hooks to make kvm preemptible
Date: Wed, 11 Jul 2007 22:10:07 +0200 [thread overview]
Message-ID: <68676e00707111310v4862974am37dc7c723486b96c@mail.gmail.com> (raw)
In-Reply-To: <1184169333786-git-send-email-avi@qumranet.com>
On 7/11/07, Avi Kivity <avi@qumranet.com> wrote:
> Current kvm disables preemption while the new virtualization registers are
> in use. This of course is not very good for latency sensitive workloads (one
> use of virtualization is to offload user interface and other latency
> insensitive stuff to a container, so that it is easier to analyze the
> remaining workload). This patch re-enables preemption for kvm; preemption
> is now only disabled when switching the registers in and out, and during
> the switch to guest mode and back.
[...]
> diff --git a/drivers/kvm/Kconfig b/drivers/kvm/Kconfig
> index 33fa28a..92644b5 100644
> --- a/drivers/kvm/Kconfig
> +++ b/drivers/kvm/Kconfig
> @@ -10,7 +10,7 @@ if VIRTUALIZATION
>
> config KVM
> tristate "Kernel-based Virtual Machine (KVM) support"
> - depends on X86 && EXPERIMENTAL
> + depends on X86 && EXPERIMENTAL && PREEMPT_HOOKS
> depends on X86_CMPXCHG64 || 64BIT
select PREEMPT_HOOKS maybe?
Luca
next prev parent reply other threads:[~2007-07-11 20:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 15:55 [PATCH 0/2][RFC] Scheduler preemption hooks, #2 Avi Kivity
2007-07-11 15:55 ` [PATCH 1/2] SCHED: Generic hooks for trapping task preemption Avi Kivity
2007-07-12 2:56 ` Rusty Russell
2007-07-12 5:14 ` Rusty Russell
2007-07-12 5:48 ` Avi Kivity
2007-07-11 15:55 ` [PATCH 2/2] KVM: Use the scheduler preemption hooks to make kvm preemptible Avi Kivity
2007-07-11 20:10 ` Luca [this message]
2007-07-12 5:43 ` [kvm-devel] " 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=68676e00707111310v4862974am37dc7c723486b96c@mail.gmail.com \
--to=kronos.it@gmail.com \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®