From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
Dario Faggioli <dario.faggioli@citrix.com>
Cc: ian.campbell@citrix.com, xisisu@gmail.com,
stefano.stabellini@eu.citrix.com, lu@cse.wustl.edu,
ian.jackson@eu.citrix.com, xen-devel@lists.xen.org,
ptxlinh@gmail.com, xumengpanda@gmail.com,
Meng Xu <mengxu@cis.upenn.edu>,
chaowang@wustl.edu, lichong659@gmail.com, dgolomb@seas.upenn.edu
Subject: Re: [PATCH for 4.5 v4 1/4] xen: add real time scheduler rtds
Date: Wed, 24 Sep 2014 14:35:56 +0100 [thread overview]
Message-ID: <5422C8BC.3050807@eu.citrix.com> (raw)
In-Reply-To: <5422E4150200007800038454@mail.emea.novell.com>
On 09/24/2014 02:32 PM, Jan Beulich wrote:
>>>> On 24.09.14 at 15:14, <dario.faggioli@citrix.com> wrote:
>> On mer, 2014-09-24 at 13:09 +0100, Jan Beulich wrote:
>>> Furthermore the function appears to lack serialization with other
>>> scheduler operations.
>>>
>> Not sure what you mean here. There's only one lock serializing
>> everything in this scheduler, and it's already taken when this is
>> called, the only exception being when it's called from rt_alloc_vdata().
>>
>> Is it that one you're referring to?
> No. The call path do_domctl() -> sched_adjust() -> rt_dom_cntl()
> doesn't take any scheduler related locks afaics.
Indeed.
-George
next prev parent reply other threads:[~2014-09-24 13:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-20 22:13 [PATCH for 4.5 v4 1/4] xen: add real time scheduler rtds Meng Xu
2014-09-22 17:13 ` Dario Faggioli
2014-09-23 11:47 ` George Dunlap
2014-09-24 12:09 ` Jan Beulich
2014-09-24 13:14 ` Dario Faggioli
2014-09-24 13:25 ` Meng Xu
2014-09-24 13:33 ` George Dunlap
2014-09-24 13:32 ` Jan Beulich
2014-09-24 13:35 ` George Dunlap [this message]
2014-09-24 13:41 ` Dario Faggioli
2014-09-24 13:45 ` George Dunlap
2014-09-26 18:29 ` [PATCH] xen: sanity check input and serialize vcpu data in sched_rt.c Meng Xu
2014-09-26 18:49 ` Andrew Cooper
2014-09-29 8:09 ` Jan Beulich
2014-09-29 13:26 ` Dario Faggioli
2014-09-30 21:21 ` Meng Xu
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=5422C8BC.3050807@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=chaowang@wustl.edu \
--cc=dario.faggioli@citrix.com \
--cc=dgolomb@seas.upenn.edu \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=lichong659@gmail.com \
--cc=lu@cse.wustl.edu \
--cc=mengxu@cis.upenn.edu \
--cc=ptxlinh@gmail.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xisisu@gmail.com \
--cc=xumengpanda@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.