public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Juergen Gross <jgross@suse.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
	konrad.wilk@oracle.com, boris.ostrovsky@oracle.com,
	david.vrabel@citrix.com, mingo@redhat.com,
	Douglas_Warzecha@dell.com, pali.rohar@gmail.com,
	jdelvare@suse.com, linux@roeck-us.net, tglx@linutronix.de,
	hpa@zytor.com, x86@kernel.org
Subject: Re: [PATCH 2/6] sched: add function to execute a function synchronously on a physical cpu
Date: Fri, 11 Mar 2016 13:19:50 +0100	[thread overview]
Message-ID: <20160311121950.GZ6344@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1457697574-6710-3-git-send-email-jgross@suse.com>

On Fri, Mar 11, 2016 at 12:59:30PM +0100, Juergen Gross wrote:
> +int call_sync_on_phys_cpu(unsigned cpu, int (*func)(void *), void *par)
> +{
> +	cpumask_var_t old_mask;
> +	int ret;
> +
> +	if (cpu >= nr_cpu_ids)
> +		return -EINVAL;
> +
> +	if (!alloc_cpumask_var(&old_mask, GFP_KERNEL))
> +		return -ENOMEM;
> +
> +	cpumask_copy(old_mask, &current->cpus_allowed);
> +	ret = set_cpus_allowed_ptr(current, cpumask_of(cpu));
> +	if (ret)
> +		goto out;

So what happens if someone does sched_setaffinity() right about here?

> +
> +	ret = func(par);
> +
> +	set_cpus_allowed_ptr(current, old_mask);
> +
> +out:
> +	free_cpumask_var(old_mask);
> +	return ret;
> +}
> +EXPORT_SYMBOL_GPL(call_sync_on_phys_cpu);

This is disgusting, and you're adding this to !Xen kernels too.

  reply	other threads:[~2016-03-11 12:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 11:59 [PATCH 0/6] Support calling functions on dedicated physical cpu Juergen Gross
2016-03-11 11:59 ` [PATCH 1/6] xen: sync xen header Juergen Gross
2016-03-11 11:59 ` [PATCH 2/6] sched: add function to execute a function synchronously on a physical cpu Juergen Gross
2016-03-11 12:19   ` Peter Zijlstra [this message]
2016-03-11 12:42     ` Peter Zijlstra
2016-03-11 12:48       ` Juergen Gross
2016-03-11 12:57         ` Peter Zijlstra
2016-03-11 13:07           ` Juergen Gross
2016-03-11 12:43     ` Juergen Gross
2016-03-11 12:45       ` Peter Zijlstra
2016-03-11 11:59 ` [PATCH 3/6] dcdbas: make use of call_sync_on_phys_cpu() Juergen Gross
2016-03-11 11:59 ` [PATCH 4/6] hwmon: use call_sync_on_phys_cpu() for dell-smm i8k Juergen Gross
2016-03-11 11:59 ` [PATCH 5/6] virt, sched: add cpu pinning to call_sync_on_phys_cpu() Juergen Gross
2016-03-11 11:59 ` [PATCH 6/6] xen: add xen_pin_vcpu() to support calling functions on a dedicated pcpu Juergen Gross
2016-03-11 12:25 ` [PATCH 0/6] Support calling functions on dedicated physical cpu Peter Zijlstra
2016-03-11 12:28   ` Pali Rohár
2016-03-11 13:15   ` One Thousand Gnomes
2016-03-11 13:19     ` Peter Zijlstra

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=20160311121950.GZ6344@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=Douglas_Warzecha@dell.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=hpa@zytor.com \
    --cc=jdelvare@suse.com \
    --cc=jgross@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mingo@redhat.com \
    --cc=pali.rohar@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox