| Server IP : 20.75.53.88 / Your IP : 216.73.217.72 [ Web Server : Apache System : Linux VMRALP-3 4.4.0-256-generic #290~14.04.1-Ubuntu SMP Thu Jun 20 09:24:50 UTC 2024 x86_64 User : www-data ( 33) PHP Version : 5.5.9-1ubuntu4.29+esm15 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority, Domains : 3 Domains MySQL : ON | cURL : OFF | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/src/linux-headers-4.4.0-256/arch/arm64/include/asm/ |
Upload File : |
#ifndef __ASM_SYNC_BITOPS_H__ #define __ASM_SYNC_BITOPS_H__ #include <asm/bitops.h> #include <asm/cmpxchg.h> /* sync_bitops functions are equivalent to the SMP implementation of the * original functions, independently from CONFIG_SMP being defined. * * We need them because _set_bit etc are not SMP safe if !CONFIG_SMP. But * under Xen you might be communicating with a completely external entity * who might be on another CPU (e.g. two uniprocessor guests communicating * via event channels and grant tables). So we need a variant of the bit * ops which are SMP safe even on a UP kernel. */ #define sync_set_bit(nr, p) set_bit(nr, p) #define sync_clear_bit(nr, p) clear_bit(nr, p) #define sync_change_bit(nr, p) change_bit(nr, p) #define sync_test_and_set_bit(nr, p) test_and_set_bit(nr, p) #define sync_test_and_clear_bit(nr, p) test_and_clear_bit(nr, p) #define sync_test_and_change_bit(nr, p) test_and_change_bit(nr, p) #define sync_test_bit(nr, addr) test_bit(nr, addr) #define sync_cmpxchg cmpxchg #endif