From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Paul Turner <pjt@google.com>, Andrew Hunter <ahh@google.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
linux-api <linux-api@vger.kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Andi Kleen <andi@firstfloor.org>,
Dave Watson <davejwatson@fb.com>, Chris Lameter <cl@linux.com>,
Ingo Molnar <mingo@redhat.com>, Ben Maurer <bmaurer@fb.com>,
rostedt <rostedt@goodmis.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Josh Triplett <josh@joshtriplett.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [RFC PATCH v2 2/3] getcpu_cache: wire up ARM system call
Date: Wed, 27 Jan 2016 18:46:39 +0000 (UTC) [thread overview]
Message-ID: <1011987684.6168.1453920399905.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <20160127181915.GA10826@n2100.arm.linux.org.uk>
----- On Jan 27, 2016, at 1:19 PM, Russell King - ARM Linux linux@arm.linux.org.uk wrote:
> On Wed, Jan 27, 2016 at 11:54:42AM -0500, Mathieu Desnoyers wrote:
>> Wire up the getcpu cache system call on 32-bit ARM. Call the
>
> You should note that your chosen system call number of 391 is temporary
> here and can't be relied upon as we have to wire up the new
> copy_file_range() call on ARM (which I've just committed the patch for.)
>
> I'd much prefer the wiring up to be either an entirely separate patch
> (which must be submitted to me, and I'll merge between -rc1 and -rc2
> along with any other syscall updates) or you leave the wiring up to me.
>
> This is so that I can ensure that (a) system calls numbers are not
> duplicated and (b) ensure that we follow the same logical order as x86
> where possible.
Just to make sure I understand: you would perfer if I split this
patch into two: one that adds the getcpu_cache_handle_notify_resume()
call in the resume notifier ("getcpu_cache ARM architecture support"),
and a separate patch for wiring up the system call ?
Thanks,
Mathieu
>
> Thanks.
>
> --
> RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
> FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
> according to speedtest.net.
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2016-01-27 18:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 16:54 [RFC PATCH v2 0/3] getcpu_cache " Mathieu Desnoyers
2016-01-27 16:54 ` [RFC PATCH v2 1/3] getcpu_cache system call: cache CPU number of running thread Mathieu Desnoyers
2016-01-27 17:20 ` Josh Triplett
2016-01-27 17:24 ` Thomas Gleixner
2016-01-27 17:36 ` Mathieu Desnoyers
2016-01-27 18:02 ` Andrew Hunter
2016-01-27 18:03 ` Josh Triplett
2016-01-27 18:43 ` Mathieu Desnoyers
2016-01-27 19:16 ` Josh Triplett
2016-01-27 21:02 ` Mathieu Desnoyers
2016-01-27 21:30 ` Josh Triplett
2016-01-27 17:22 ` Thomas Gleixner
2016-01-27 17:31 ` Mathieu Desnoyers
2016-01-27 17:34 ` Thomas Gleixner
2016-01-27 17:37 ` Thomas Gleixner
2016-01-27 21:34 ` Mathieu Desnoyers
2016-01-27 22:11 ` Josh Triplett
2016-01-27 22:47 ` Mathieu Desnoyers
2016-01-28 11:12 ` Heiko Carstens
2016-01-28 13:33 ` Mathieu Desnoyers
2016-01-28 3:12 ` Alexei Starovoitov
2016-01-28 17:41 ` Mathieu Desnoyers
2016-01-27 16:54 ` [RFC PATCH v2 2/3] getcpu_cache: wire up ARM system call Mathieu Desnoyers
2016-01-27 18:19 ` Russell King - ARM Linux
2016-01-27 18:46 ` Mathieu Desnoyers [this message]
2016-01-27 23:03 ` Mathieu Desnoyers
2016-01-27 16:54 ` [RFC PATCH v2 3/3] getcpu_cache: wire up x86 32/64 " Mathieu Desnoyers
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=1011987684.6168.1453920399905.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=ahh@google.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=bmaurer@fb.com \
--cc=catalin.marinas@arm.com \
--cc=cl@linux.com \
--cc=davejwatson@fb.com \
--cc=josh@joshtriplett.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.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
Powered by JetHome