search for: __fn

...linux.cc:315:22: error: no matching function for call to 'clone' pid_t tracer_pid = clone(TracerThread, tracer_stack.Bottom(), ^~~~~ /usr/include/bits/sched.h:71:12: note: candidate function not viable: requires 4 arguments, but 7 were provided extern int clone (int (*__fn) (void *__arg), void *__child_stack, Inside sched.h, clone is indeed declared with four arguments, but, interestingly, the man page for clone provides this prototype: #include <sched.h> int clone(int (*fn)(void *), void *child_stack, int flags, void *arg, ......

...linux.cc:315:22: error: no matching function for call to 'clone' pid_t tracer_pid = clone(TracerThread, tracer_stack.Bottom(), ^~~~~ /usr/include/bits/sched.h:71:12: note: candidate function not viable: requires 4 arguments, but 7 were provided extern int clone (int (*__fn) (void *__arg), void *__child_stack, Inside sched.h, clone is indeed declared with four arguments, but, interestingly, the man page for clone provides this prototype: #include <sched.h> int clone(int (*fn)(void *), void *child_stack, int flags, void *arg, ......

...;clone'**** > > pid_t tracer_pid = clone(TracerThread, tracer_stack.Bottom(),**** > > ^~~~~**** > > /usr/include/bits/sched.h:71:12: note: candidate function not viable: > requires 4 arguments, but 7 were provided**** > > extern int clone (int (*__fn) (void *__arg), void *__child_stack,**** > > ** ** > > Inside sched.h, clone is indeed declared with four arguments, but, > interestingly, the man page for clone provides this prototype:**** > > ** ** > > #include <sched.h>**** > > ** ** > >...

This series consists of improvements to Xen''s ability to print traces of its own stack, and specifically for the stack overflow case to be able to use frame pointers in a debug build. I have dev tested the series in debug and non-debug cases, with and without memory guards, and I believe that all the stack traces look correct. However, I would greatly appreciate a second opinion on the

This series consists of improvements to Xen''s ability to print traces of its own stack, and specifically for the stack overflow case to be able to use frame pointers in a debug build. I have dev tested the series in debug and non-debug cases, with and without memory guards, and I believe that all the stack traces look correct (given the available information Xen has), and that the

This patch series implements SMP boot for arch/arm, as far as getting all CPUs up and running the idle loop. Changes from v1: - moved barriers out of loop in udelay() - dropped broken GIC change in favour of explanatory comment - made the increment of ready_cpus atomic (I couldn''t move the increment to before signalling the next CPU because the PT switch has to happen between

Hello everyone, this is the fourth version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See

Hello everyone, this is the very first version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See