All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Meng Xu <mengxu@cis.upenn.edu>
Cc: george.dunlap@eu.citrix.com,
	"konrad.r.wilk" <konrad.r.wilk@gmail.com>,
	xumengpanda@gmail.com, JBeulich@suse.com,
	xen-devel@lists.xen.org
Subject: Re: Sanity check input and serialize vcpu data in sched_rt.c
Date: Wed, 29 Oct 2014 11:06:26 +0100	[thread overview]
Message-ID: <1414577186.20696.52.camel@Abyss> (raw)
In-Reply-To: <1414246599-3914-1-git-send-email-mengxu@cis.upenn.edu>


[-- Attachment #1.1: Type: text/plain, Size: 1994 bytes --]

On Sat, 2014-10-25 at 10:16 -0400, Meng Xu wrote:
> These two patches are to solve the issues found by Jan Beulich at http://lists.xen.org/archives/html/xen-devel/2014-09/msg03554.html.
> 
> The solution is summarized by Dario Faggioli at http://lists.xen.org/archives/html/xen-devel/2014-09/msg03603.html.
> 
> Here is the solution:
>      - sanity checking input params in rt_dom_cntl()
>      - serialize rt_dom_cntl() itself against the global lock
>      - move the call to rt_update_deadline() from _alloc to _insert
> 
Ok, thanks Meng for the patches, and for this summary.

I've already reviewed the patches, and they look fine to me. If I can
add a few things about the submission:
 - threading is ok this time, good job with that :-D
 - cover letter subject summarizes properly the series content, but 
   should contain the [PATCH xxx xxx] prefix as regular patches, as if
   it were patch 0 of the series
 - since this is v2, it is really useful to include, in each patch, a
   quick summary of what changed wrt previous version. You usually do it
   in the changelog of each patch itself, after a "---" mark, below the
   Signed-off and similar tags

Finally, since we're in freeze, we should 'convince' Konrad that these
patches really need to be merged right now, instead of waiting for 4.6.

See Konrad's development update emails for more details. About that,
Konrad, my take is as follows:
 - this is a bugfix, so, always a good one to have :-)
 - this only touches the new scheduler's code, with basically zero
   chances of causing issues to others
 - the new scheduler is marked as experimental

So, yes, I think these patches should be considered for 4.5

Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  parent reply	other threads:[~2014-10-29 10:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-25 14:16 Sanity check input and serialize vcpu data in sched_rt.c Meng Xu
2014-10-25 14:16 ` [PATCH for Xen 4.5 v2 1/2] xen: sanity check input and serialization " Meng Xu
2014-10-29  9:41   ` Dario Faggioli
2014-10-29 14:27     ` Meng Xu
2014-11-10 12:54   ` George Dunlap
2014-10-25 14:16 ` [PATCH for Xen 4.5 v2 2/2] xen: serialize vcpu data " Meng Xu
2014-10-29  9:26   ` Dario Faggioli
2014-11-10 12:53   ` George Dunlap
2014-11-10 15:29     ` Meng Xu
2014-11-10 15:36       ` Dario Faggioli
2014-11-10 15:38         ` George Dunlap
2014-11-10 15:40       ` George Dunlap
2014-11-10 16:04         ` Meng Xu
2014-11-10 16:15           ` George Dunlap
2014-10-29 10:06 ` Dario Faggioli [this message]
2014-10-29 14:23   ` Sanity check input and " Meng Xu
2014-10-29 17:52     ` Konrad Rzeszutek Wilk

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=1414577186.20696.52.camel@Abyss \
    --to=dario.faggioli@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=konrad.r.wilk@gmail.com \
    --cc=mengxu@cis.upenn.edu \
    --cc=xen-devel@lists.xen.org \
    --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.