From: Keir Fraser <keir.xen@gmail.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
xen-devel@lists.xensource.com
Cc: julien.grall@citrix.com, tim@xen.org, Ian.Campbell@citrix.com
Subject: Re: [PATCH v6 1/2] xen: introduce vcpu_block, use it instead of do_block
Date: Thu, 18 Apr 2013 21:43:24 +0100 [thread overview]
Message-ID: <CD96197C.220F3%keir.xen@gmail.com> (raw)
In-Reply-To: <1366310951-15455-1-git-send-email-stefano.stabellini@eu.citrix.com>
On 18/04/2013 19:49, "Stefano Stabellini" <stefano.stabellini@eu.citrix.com>
wrote:
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Why? Patch 2/2 only passes current, and the changes here still leave
vcpu_block() implicitly assuming v==current (through use of local_event_*
calls). You may as well leave this as do_block(void).
-- Keir
> ---
> xen/common/schedule.c | 14 ++++++--------
> xen/include/xen/sched.h | 1 +
> 2 files changed, 7 insertions(+), 8 deletions(-)
>
> diff --git a/xen/common/schedule.c b/xen/common/schedule.c
> index c1cd3d0..89e4b7f 100644
> --- a/xen/common/schedule.c
> +++ b/xen/common/schedule.c
> @@ -676,11 +676,9 @@ int vcpu_set_affinity(struct vcpu *v, const cpumask_t
> *affinity)
> return 0;
> }
>
> -/* Block the currently-executing domain until a pertinent event occurs. */
> -static long do_block(void)
> +/* Block a vcpu until a pertinent event occurs. */
> +void vcpu_block(struct vcpu *v)
> {
> - struct vcpu *v = current;
> -
> local_event_delivery_enable();
> set_bit(_VPF_blocked, &v->pause_flags);
>
> @@ -694,8 +692,6 @@ static long do_block(void)
> TRACE_2D(TRC_SCHED_BLOCK, v->domain->domain_id, v->vcpu_id);
> raise_softirq(SCHEDULE_SOFTIRQ);
> }
> -
> - return 0;
> }
>
> static long do_poll(struct sched_poll *sched_poll)
> @@ -870,7 +866,8 @@ long do_sched_op_compat(int cmd, unsigned long arg)
>
> case SCHEDOP_block:
> {
> - ret = do_block();
> + vcpu_block(current);
> + ret = 0;
> break;
> }
>
> @@ -907,7 +904,8 @@ ret_t do_sched_op(int cmd, XEN_GUEST_HANDLE_PARAM(void)
> arg)
>
> case SCHEDOP_block:
> {
> - ret = do_block();
> + vcpu_block(current);
> + ret = 0;
> break;
> }
>
> diff --git a/xen/include/xen/sched.h b/xen/include/xen/sched.h
> index ad971d2..e74f0d7 100644
> --- a/xen/include/xen/sched.h
> +++ b/xen/include/xen/sched.h
> @@ -691,6 +691,7 @@ static inline int vcpu_runnable(struct vcpu *v)
> }
>
> void vcpu_unblock(struct vcpu *v);
> +void vcpu_block(struct vcpu *v);
> void vcpu_pause(struct vcpu *v);
> void vcpu_pause_nosync(struct vcpu *v);
> void domain_pause(struct domain *d);
next prev parent reply other threads:[~2013-04-18 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 18:49 [PATCH v6 1/2] xen: introduce vcpu_block, use it instead of do_block Stefano Stabellini
2013-04-18 20:43 ` Keir Fraser [this message]
2013-04-19 9:34 ` Stefano Stabellini
2013-04-19 16:33 ` Keir Fraser
2013-04-22 7:00 ` Jan Beulich
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=CD96197C.220F3%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=julien.grall@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--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.