From: Juergen Gross <jgross@suse.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: x86@kernel.org, jeremy@goop.org, jdelvare@suse.com,
hpa@zytor.com, akataria@vmware.com, linux-kernel@vger.kernel.org,
rusty@rustcorp.com.au, virtualization@lists.linux-foundation.org,
chrisw@sous-sol.org, mingo@redhat.com, david.vrabel@citrix.com,
Douglas_Warzecha@dell.com, pali.rohar@gmail.com,
xen-devel@lists.xenproject.org, boris.ostrovsky@oracle.com,
tglx@linutronix.de, linux@roeck-us.net
Subject: Re: [PATCH v3 2/6] smp: add function to execute a function synchronously on a physical cpu
Date: Fri, 1 Apr 2016 09:40:00 +0200 [thread overview]
Message-ID: <56FE25D0.7040007__31907.5516112663$1459496481$gmane$org@suse.com> (raw)
In-Reply-To: <20160401073733.GB3448@twins.programming.kicks-ass.net>
On 01/04/16 09:37, Peter Zijlstra wrote:
> On Fri, Apr 01, 2016 at 09:14:30AM +0200, Juergen Gross wrote:
>> + if (cpu >= nr_cpu_ids)
>> + return -EINVAL;
>
>> + if (cpu != 0)
>> + return -EINVAL;
>
> The other functions return -ENXIO for this.
Aah, okay. Will change.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-01 7:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1459494874-12194-1-git-send-email-jgross@suse.com>
2016-04-01 7:14 ` [PATCH v3 1/6] xen: sync xen header Juergen Gross
2016-04-01 7:14 ` [PATCH v3 2/6] smp: add function to execute a function synchronously on a physical cpu Juergen Gross
2016-04-01 7:14 ` [PATCH v3 3/6] dcdbas: make use of smp_call_sync_on_phys_cpu() Juergen Gross
2016-04-01 7:14 ` [PATCH v3 4/6] hwmon: use smp_call_sync_on_phys_cpu() for dell-smm i8k Juergen Gross
2016-04-01 7:14 ` [PATCH v3 5/6] virt, sched: add cpu pinning to smp_call_sync_on_phys_cpu() Juergen Gross
2016-04-01 7:14 ` [PATCH v3 6/6] xen: add xen_pin_vcpu() to support calling functions on a dedicated pcpu Juergen Gross
[not found] ` <1459494874-12194-3-git-send-email-jgross@suse.com>
2016-04-01 7:37 ` [PATCH v3 2/6] smp: add function to execute a function synchronously on a physical cpu Peter Zijlstra
[not found] ` <20160401073733.GB3448@twins.programming.kicks-ass.net>
2016-04-01 7:40 ` Juergen Gross [this message]
[not found] ` <1459494874-12194-6-git-send-email-jgross@suse.com>
2016-04-01 7:43 ` [PATCH v3 5/6] virt, sched: add cpu pinning to smp_call_sync_on_phys_cpu() Peter Zijlstra
[not found] ` <20160401074325.GC12845@twins.programming.kicks-ass.net>
2016-04-01 8:28 ` Juergen Gross
[not found] ` <56FE313E.9060804@suse.com>
2016-04-01 8:44 ` Peter Zijlstra
[not found] ` <20160401084408.GF3448@twins.programming.kicks-ass.net>
2016-04-01 9:03 ` Juergen Gross
[not found] ` <56FE3959.2030508@suse.com>
2016-04-01 9:15 ` Peter Zijlstra
[not found] ` <20160401091507.GG3448@twins.programming.kicks-ass.net>
2016-04-01 9:26 ` Juergen Gross
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='56FE25D0.7040007__31907.5516112663$1459496481$gmane$org@suse.com' \
--to=jgross@suse.com \
--cc=Douglas_Warzecha@dell.com \
--cc=akataria@vmware.com \
--cc=boris.ostrovsky@oracle.com \
--cc=chrisw@sous-sol.org \
--cc=david.vrabel@citrix.com \
--cc=hpa@zytor.com \
--cc=jdelvare@suse.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mingo@redhat.com \
--cc=pali.rohar@gmail.com \
--cc=peterz@infradead.org \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).