search for: itimerspec

...on(-) diff --git a/configure b/configure index 904e019..ace3c3e 100755 --- a/configure +++ b/configure @@ -1097,7 +1097,7 @@ fi cat > $TMPC <<EOF #include <signal.h> #include <time.h> -int main(void) { clockid_t id; return clock_gettime(id, NULL); } +int main(void) { struct itimerspec v; timer_t t; return timer_gettime (t, &v); } EOF rt=no -- 1.8.0.1

...gt; @@ -1097,7 +1097,7 @@ fi > > > > cat > $TMPC <<EOF > > > > #include <signal.h> > > > > #include <time.h> > > > > -int main(void) { clockid_t id; return clock_gettime(id, NULL); } > > > > +int main(void) { struct itimerspec v; timer_t t; return timer_gettime (t, &v); } > > > > EOF > > > > > > > > rt=no At least 2 acked patches were not committed to qemu-traditional before the RC1 freeze & tag. The above patch (against qemu-traditional - qemu-upstream is OK) was acked a c...

...Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 14 Jan 2023 18:10:12 +0100 [klibc] time: Use 64-bit time types on all architectures - Define time_t as __kernel_time64_t - In <sys/time.h>, replace <linux/time.h> with suitable definitions: - Define struct timespec and itimerspec to match the kernel's 64-bit structures - Define struct timeval using __kernel_time64_t (although there are no new system calls using struct timeval) - Keep the old struct itimerval definition, because there aren't simple replacements available for the {get,set}itimer() syst...

...from client/smbmount.c:25: /usr/include/linux/time.h:9: error: redefinition of ?struct timespec? /usr/include/linux/time.h:15: error: redefinition of ?struct timeval? /usr/include/linux/time.h:20: error: redefinition of ?struct timezone? /usr/include/linux/time.h:42: error: redefinition of ?struct itimerspec? /usr/include/linux/time.h:47: error: redefinition of ?struct itimerval? client/smbmount.c: In function ?init_mount?: client/smbmount.c:496: warning: the address of ?options? will always evaluate as ?true? The following command failed: i486-linux-gnu-gcc -I. -I/usr/src/samba-3.0.32/source -gstabs...

...osted recently [1], I introduce new system calls to deal with modified data structures, but left the question open on how these should be best accessed from libc. The patches introduce a new __kernel_time64_t type and based on that five new data structured: struct __kernel_timespec, struct __kernel_itimerspec, struct __kernel_stat, struct __kernel_rusage, and struct __kernel_timex. This works fine for the case when all libc implementations provide their own definitions to user space, but not for the simplest case (e.g. klibc) where the user-visible structures come directly from the kernel uapi headers....

...UX_MAGIC_H__ */ diff -r 99132ad16999 include/linux/syscalls.h --- a/include/linux/syscalls.h Sat Apr 05 21:20:32 2008 +1100 +++ b/include/linux/syscalls.h Sat Apr 05 21:31:40 2008 +1100 @@ -614,6 +614,7 @@ asmlinkage long sys_timerfd_gettime(int asmlinkage long sys_timerfd_gettime(int ufd, struct itimerspec __user *otmr); asmlinkage long sys_eventfd(unsigned int count); asmlinkage long sys_fallocate(int fd, int mode, loff_t offset, loff_t len); +asmlinkage long sys_vringfd(void __user *, unsigned num, u16 __user *); int kernel_execve(const char *filename, char *const argv[], char *const envp[]);...

...UX_MAGIC_H__ */ diff -r 99132ad16999 include/linux/syscalls.h --- a/include/linux/syscalls.h Sat Apr 05 21:20:32 2008 +1100 +++ b/include/linux/syscalls.h Sat Apr 05 21:31:40 2008 +1100 @@ -614,6 +614,7 @@ asmlinkage long sys_timerfd_gettime(int asmlinkage long sys_timerfd_gettime(int ufd, struct itimerspec __user *otmr); asmlinkage long sys_eventfd(unsigned int count); asmlinkage long sys_fallocate(int fd, int mode, loff_t offset, loff_t len); +asmlinkage long sys_vringfd(void __user *, unsigned num, u16 __user *); int kernel_execve(const char *filename, char *const argv[], char *const envp[]);...