All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Dario Faggioli <dario.faggioli@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH v4 0/6] xen: sched: fix locking of {insert, remove}_vcpu()
Date: Mon, 23 Nov 2015 14:50:13 +0000	[thread overview]
Message-ID: <565327A5.7020208@citrix.com> (raw)
In-Reply-To: <5653337E02000078000B7E17@prv-mh.provo.novell.com>

On 23/11/15 14:40, Jan Beulich wrote:
>>>> On 23.11.15 at 15:03, <George.Dunlap@eu.citrix.com> wrote:
>>> ---
>>> Dario Faggioli (6):
>>>       xen: sched: fix locking of remove_vcpu() in credit1
>>>       xen: sched: fix locking for insert_vcpu() in credit1 and RTDS
>>>       xen: sched: clarify use cases of schedule_cpu_switch()
>>>       xen: sched: better handle (not) inserting idle vCPUs in runqueues
>>>       xen: sched: get rid of the per domain vCPU list in RTDS
>>>       xen: sched: get rid of the per domain vCPU list in Credit2
>>
>> Committers,
>>
>> It looks to me like this series has all the Acks and Reviews it needs
>> to be checked in, but (as far as I can see) hasn't yet.  Can someone
>> double-check and check it in?  (See the git tree above if you want to
>> make it easier.)
> 
> I've been waiting for an ack on patch 2 (and I've just checked again
> and still can't find any); with this diffstat
> 
>  xen/common/sched_credit.c |    6 ++++++
>  xen/common/sched_rt.c     |    3 +++
>  xen/common/schedule.c     |    6 ++----
> 
> Meng's alone isn't sufficient afaict. I've once made an attempt to
> commit later patches in this series, but failed and then didn't want
> to waste time retrying.

What are the rules again, then?  Dario is a scheduler maintainer, and
Meng is an established contributor.  I thought that was enough.

 -George

  reply	other threads:[~2015-11-23 14:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 17:17 [PATCH v4 0/6] xen: sched: fix locking of {insert, remove}_vcpu() Dario Faggioli
2015-11-04 17:17 ` [PATCH v4 1/6] xen: sched: fix locking of remove_vcpu() in credit1 Dario Faggioli
2015-11-04 17:22   ` George Dunlap
2015-11-04 17:17 ` [PATCH v4 2/6] xen: sched: fix locking for insert_vcpu() in credit1 and RTDS Dario Faggioli
2015-11-24 11:34   ` George Dunlap
2015-11-04 17:17 ` [PATCH v4 3/6] xen: sched: clarify use cases of schedule_cpu_switch() Dario Faggioli
2015-11-04 17:17 ` [PATCH v4 4/6] xen: sched: better handle (not) inserting idle vCPUs in runqueues Dario Faggioli
2015-11-04 17:18 ` [PATCH v4 5/6] xen: sched: get rid of the per domain vCPU list in RTDS Dario Faggioli
2015-11-04 17:18 ` [PATCH v4 6/6] xen: sched: get rid of the per domain vCPU list in Credit2 Dario Faggioli
2015-11-23 14:03 ` [PATCH v4 0/6] xen: sched: fix locking of {insert, remove}_vcpu() George Dunlap
2015-11-23 14:40   ` Jan Beulich
2015-11-23 14:50     ` George Dunlap [this message]
2015-11-23 15:00       ` Jan Beulich
2015-11-24  3:27         ` Meng Xu
2015-11-24  8:05           ` Jan Beulich
2015-11-24 11:03 ` George Dunlap
2015-11-24 11:49   ` Dario Faggioli

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=565327A5.7020208@citrix.com \
    --to=george.dunlap@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=dario.faggioli@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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 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.