All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com,
	george.dunlap@eu.citrix.com, ian.jackson@eu.citrix.com,
	xen-devel@lists.xen.org, xumengpanda@gmail.com,
	Meng Xu <mengxu@cis.upenn.edu>
Subject: Re: [PATCH] xen: sanity check input and serialize vcpu data in sched_rt.c
Date: Mon, 29 Sep 2014 15:26:37 +0200	[thread overview]
Message-ID: <1411997197.4336.66.camel@Solace.lan> (raw)
In-Reply-To: <54292FC9020000780003A440@mail.emea.novell.com>


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

On lun, 2014-09-29 at 09:09 +0100, Jan Beulich wrote:
> >>> On 26.09.14 at 20:29, <mengxu@cis.upenn.edu> wrote:
> > Sanity check input params in rt_dom_cntl();
> > Serialize rt_dom_cntl() against the global lock;
> > Move the call to rt_update_deadline() from _alloc to _insert.
> 
> Regarding this last sentence - the patch clearly does more in this
> regard than just move the call from _alloc or _insert. Please make
> sure your description matches the patch (which doesn't necessarily
> mean enumerating all places it gets moved from - all I'd like to see
> is that description and implementation don't disagree).
> 
> And aren't the two changes here independent anyway? In which
> case submitting them as two patches might be better?
> 
Indeed, two patch is what we want.

Also, the threading. According to my MUA, the mail with the patch is a
reply to a message from the v4 patch series. Meng, as this is a new
submission, the best thing is always to start a new thread.

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

  reply	other threads:[~2014-09-29 13:26 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
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 [this message]
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=1411997197.4336.66.camel@Solace.lan \
    --to=dario.faggioli@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=mengxu@cis.upenn.edu \
    --cc=stefano.stabellini@eu.citrix.com \
    --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.