Thread (27 messages) flat view 27 messages, 7 authors, 2016-01-28

Re: [RFC PATCH v2 2/3] getcpu_cache: wire up ARM system call

From: Mathieu Desnoyers <hidden>
Date: 2016-01-27 18:46:50
Also in: lkml

----- On Jan 27, 2016, at 1:19 PM, Russell King - ARM Linux linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org wrote:
On Wed, Jan 27, 2016 at 11:54:42AM -0500, Mathieu Desnoyers wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help