From: Andrew Theurer <habanero@linux.vnet.ibm.com>
To: alex <tomorrowanewday@gmail.com>
Cc: avi@redhat.com, anthony@codemonkey.ws, kvm@vger.kernel.org,
mingo@elte.hu
Subject: Re: patch for virtual machine oriented scheduling(1)
Date: Thu, 23 Apr 2009 11:18:37 -0500 [thread overview]
Message-ID: <49F094DD.6080703@linux.vnet.ibm.com> (raw)
In-Reply-To: <820ac2e90904220749p70564f5bof51eb975a5b80959@mail.gmail.com>
alex wrote:
> the following patchs provide an extra control(besides the control of
> Linux scheduler) over the execution of vcpu threads.
>
> In this patch, Xen's credit
> scheduler(http://wiki.xensource.com/xenwiki/CreditScheduler) is used.
> User can use "cat" and
> "echo" command to view and control a guest os' credit.
> e.g.,
> [root@localhost ~]# echo "weight=500" > /proc/kvm/12345
> will change the credit of guest whose qemu process has the pid 12345 to be 500.
>
> The patch consists of 3 parts:
> 1. modification to the standard KVM
> 2. modification to the Xen scheduler
> 3. helper functions
>
Just wondering, was it not possible to introduce a new scheduling class
in the current scheduler? My impression was that the current scheduler
was fairly modular and should allow this.
-Andrew
> However, some are unnecessary in the latest Linux kernel.
>
> The difficulties in the ports lie in:
> 1. Linux does not provide timer mechanism that the timer function is
> bind to a dedicate CPU:
> in case of one cpu receives another cpu's schedule timer
> expiration, IPI is used to relay it.
> 2. before linux 2.6.27, the smp_call_function_xxx() can not be re-entered.
> if kvm is sending ipi at the time of relaying timer expiration
> information, deadlock would occur in kernel versions below 2.6.27
>
> In my implementation, tasklets are used to run the function of
> scheduling, and kernel thread is used to send IPI(in kernels above
> 2.6.27, this is unnecessary)
>
> Originally, this code is developed at the release version of KVM-83.
> In order to post it, I ported to the latest .git tree. As a result,
> modifications to files like external-module-compat-comm.h are omited.
>
> NOTE:
> 1. Because my not having an AMD machine, only intel platforms are tested.
> 2. Because sched_setaffinity() is used (while Linux does not export
> this symbol), the way of loading kvm modules are changed to be
> ./myins <directory that holds the kvm.ko and kvm-intel.ko>
> --
> 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:[~2009-04-23 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 14:49 patch for virtual machine oriented scheduling(1) alex
2009-04-23 16:18 ` Andrew Theurer [this message]
2009-04-23 23:24 ` alex
2009-04-26 9:48 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2009-04-23 2:39 alex
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=49F094DD.6080703@linux.vnet.ibm.com \
--to=habanero@linux.vnet.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tomorrowanewday@gmail.com \
/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.