From: Peter Zijlstra <peterz@infradead.org>
To: Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, boqun.feng@gmail.com
Subject: Re: [PATCH 1/2] kernel/sched: introduce vcpu preempted interface
Date: Mon, 27 Jun 2016 10:42:50 +0200 [thread overview]
Message-ID: <20160627084250.GZ30154@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1466937715-6683-2-git-send-email-xinhui.pan@linux.vnet.ibm.com>
On Sun, Jun 26, 2016 at 06:41:54AM -0400, Pan Xinhui wrote:
> +#ifdef arch_vcpu_is_preempted
> +static inline bool vcpu_is_preempted(int cpu)
> +{
> + return arch_vcpu_is_preempted(cpu);
> +}
> +#else
> +static inline bool vcpu_is_preempted(int cpu)
> +{
> + return 0;
> +}
> +#endif
> +
> +#ifdef arch_vcpu_get_yield_count
> +static inline unsigned int vcpu_get_yield_count(int cpu)
> +{
> + return arch_vcpu_get_yield_count(cpu);
> +}
> +#else
> +static inline unsigned int vcpu_get_yield_count(int cpu)
> +{
> + return 0;
> +}
> +#endif
Please, just do something like:
#ifndef vcpu_is_preempted
static inline bool vcpu_is_preempted(int cpu)
{
return false;
}
#endif
No point in making it more complicated.
> +static inline bool
> +need_yield_to(int vcpu, unsigned int old_yield_count)
namespace... this thing should be called: vcpu_something()
> +{
> + /* if we find the vcpu is preempted,
> + * then we may want to kick it, IOW, yield to it
> + */
> + return vcpu_is_preempted(vcpu) ||
> + (vcpu_get_yield_count(vcpu) != old_yield_count);
> +}
And can you make doubly sure (and mention in the Changelog) that the OSQ
code compiles all this away when using these definitions.
next prev parent reply other threads:[~2016-06-27 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-26 10:41 [PATCH 0/2] implement vcpu preempted check Pan Xinhui
2016-06-26 10:41 ` [PATCH 1/2] kernel/sched: introduce vcpu preempted interface Pan Xinhui
2016-06-27 8:42 ` Peter Zijlstra [this message]
2016-06-27 9:42 ` xinhui
2016-06-26 10:41 ` [PATCH 2/2] locking/osq: Drop the overload of osq_lock() Pan Xinhui
2016-06-26 7:12 ` panxinhui
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=20160627084250.GZ30154@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=xinhui.pan@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox