From: Keir Fraser <keir.xen@gmail.com>
To: Juergen Gross <juergen.gross@ts.fujitsu.com>,
xen-devel@lists.xensource.com
Cc: George Dunlap <George.Dunlap@eu.citrix.com>
Subject: Re: [PATCH] Avoid endless loop for vcpu migration
Date: Mon, 14 Mar 2011 15:06:21 +0000 [thread overview]
Message-ID: <C9A3DF6D.14C0E%keir.xen@gmail.com> (raw)
In-Reply-To: <9d164ce877a75cab847b.1300113594@nehalem1>
I'm not versed enough in this aspect of the scheduler to ack or commit this.
It just looks a bit ugly and confusing to me. Needs an Ack from George
therefore.
-- Keir
On 14/03/2011 14:39, "Juergen Gross" <juergen.gross@ts.fujitsu.com> wrote:
> On multi-thread multi-core systems an endless loop can occur in vcpu_migrate()
> with credit scheduler. Avoid this loop by changing the interface of pick_cpu
> to indicate a repeated call in this case.
>
> Signed-off-by: juergen.gross@ts.fujitsu.com
>
>
> 6 files changed, 11 insertions(+), 15 deletions(-)
> xen/common/sched_arinc653.c | 2 +-
> xen/common/sched_credit.c | 12 +++---------
> xen/common/sched_credit2.c | 2 +-
> xen/common/sched_sedf.c | 2 +-
> xen/common/schedule.c | 6 ++++--
> xen/include/xen/sched-if.h | 2 +-
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-03-14 15:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 14:39 [PATCH] Avoid endless loop for vcpu migration Juergen Gross
2011-03-14 15:03 ` Jan Beulich
2011-03-14 15:06 ` Tim Deegan
2011-03-15 5:50 ` Juergen Gross
2011-03-15 7:57 ` Jan Beulich
2011-03-15 8:46 ` Juergen Gross
2011-03-15 8:50 ` Keir Fraser
2011-03-15 8:53 ` Juergen Gross
2011-03-15 9:01 ` Jan Beulich
2011-03-15 9:21 ` Juergen Gross
2011-03-15 9:34 ` Jan Beulich
2011-03-15 9:58 ` Keir Fraser
2011-03-15 10:29 ` Juergen Gross
2011-03-14 15:06 ` Keir Fraser [this message]
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=C9A3DF6D.14C0E%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=juergen.gross@ts.fujitsu.com \
--cc=xen-devel@lists.xensource.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.