similar to: Re: [PATCH] qemu-traditional: update configure check for -lrt changes in glibc 2.17

configure uses clock_gettime to check whether -lrt is needed - and don''t check other functions. With glibc 2.17 clock_gettime is part of libc, so use timer_gettime instead, which is in -lrt in old and new versions of glibc. Signed-off-by: Olaf Hering <olaf@aepfle.de> --- configure | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure b/configure index

Signed-off-by: Olaf Hering <olaf@aepfle.de> Acked-by: Matt Wilson <msw@amazon.com> --- Makefile | 2 +- Makefile.target | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index 37c7066..594f0ef 100644 --- a/Makefile +++ b/Makefile @@ -243,7 +243,7 @@ endif install: all $(if $(BUILD_DOCS),install-doc) mkdir -p

Matt attempted to add CLOCK_TAI support to the VDSO clock_gettime() implementation, which extended the clockid switch case and added yet another slightly different copy of the same code. Especially the extended switch case is problematic as the compiler tends to generate a jump table which then requires to use retpolines. If jump tables are disabled it adds yet another conditional to the existing

Matt attempted to add CLOCK_TAI support to the VDSO clock_gettime() implementation, which extended the clockid switch case and added yet another slightly different copy of the same code. Especially the extended switch case is problematic as the compiler tends to generate a jump table which then requires to use retpolines. If jump tables are disabled it adds yet another conditional to the existing

Matt attempted to add CLOCK_TAI support to the VDSO clock_gettime() implementation, which extended the clockid switch case and added yet another slightly different copy of the same code. Especially the extended switch case is problematic as the compiler tends to generate a jump table which then requires to use retpolines. If jump tables are disabled it adds yet another conditional to the existing

Commit-ID: df7b02bd5c9af14c6efbe39ee4c313e368dfe967 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=df7b02bd5c9af14c6efbe39ee4c313e368dfe967 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 14 Jan 2023 00:17:45 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 14 Jan 2023 18:10:12 +0100 [klibc] time: Use 64-bit time

On my setup with glibc-2.8, benchmark_residual linkage fails with undefines references to clock_gettime(). Adding -lrt fixes that. The following is a small patch for it. Regards. -- O.S. diff --git a/configure.ac b/configure.ac index 993ac33..392485e 100644 --- a/configure.ac +++ b/configure.ac @@ -437,6 +437,11 @@ if test x$enable_stack_smash_protection = "xyes" ; then

Commit-ID: 8b44cc180f664532821211e8261534b0c9e6c01c Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=8b44cc180f664532821211e8261534b0c9e6c01c Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 14 Jan 2023 02:15:10 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sun, 15 Jan 2023 21:28:18 +0100 [klibc] time: Use clock_* system

with some dirty hack , I've made xray runtime 'built' on windows , but unfortunately I haven't enough knowledge about linker and the runtime, and finally built executable didn't run. I'd like to share my changes here , hopes somebody help me to make it run on windows. in AsmPrinter, copy/paster xray for coff target InstMap =

I'm learning the xray library and try if it can be built on windows, in xray_fdr_logging_impl.h line 152 , comment written as // Using pthread_once(...) to initialize the thread-local data structures but at line 175, 183, code written as thread_local pthread_key_t key; // Ensure that we only actually ever do the pthread initialization once. thread_local bool UNUSED Unused = [] {

Hi Armin! I have problems on debian sarge with standard 2.6.8-2-386 kernel. I've installed the packages: kernel-headers-2.6.8-2 kernel-headers-2.6.8-2-386 kernel-image-2.6.8-2-386 kernel-kbuild-2.6-3 kernel-source-2.6.8 Then I unpacked the kernel sources into /usr/src/kernel-source-2.6.8 and made a symlink from /usr/src/linux --> kernel-source-2.6.8 Then I entered

On Wed, Jul 30, 2014 at 03:58:43PM -0700, Zetan Drableg wrote: > [00183ms] /usr/libexec/qemu-kvm \ > -global virtio-blk-pci.scsi=off \ > -nodefconfig \ > -nodefaults \ > -nographic \ > -machine accel=kvm:tcg \ > -cpu host,+kvmclock \ > -m 500 \ > -no-reboot \ > -kernel /var/tmp/.guestfs-0/kernel.47903 \

Peter, typedef __kernel_timer_t timer_t will fail with Arjans glibc headers, they do not define __kernel_timer_t in asm/posix_types.h. All archs supported by Linux have typedef int __kernel_timer_t. Can we just get rid of the __kernel_timer_t? --- klibc-0.171/klibc/include/sys/types.h.orig 2004-06-08 07:32:48.000000000 +0200 +++ klibc-0.171/klibc/include/sys/types.h 2004-09-02

Hi Richard thanks for the info. I took the strace approach and ran into this looping over and over again. Is it failing to get time? timer_gettime(0x8, {it_interval={0, 0}, it_value={0, 0}}) = 0 timer_settime(0x8, 0, {it_interval={0, 0}, it_value={0, 250000}}, NULL) = 0 timer_gettime(0x8, {it_interval={0, 0}, it_value={0, 204443}}) = 0 select(16, [0 6 9 13 15], [], [], {1, 0}) = 2 (in [6 13],

Still trying to migrate to CentOS 7. I used to use qemu-kvm on centos 6. tried to compile on centos 7 and get error about undefined reference to timer_gettime searching for that says basically use virt-manager so I installed virt-manager - I have file images and those work. some times I do directly to a USB connected disk. I do not see how to do that in virt-manager ??? How do I use a device

I''m continuing to investigate the usage of rdtsc in userspace and whether there are programs "out there" that use it "unsafely" that might randomly break under Xen if rdtsc is not emulated, e.g. across a migration. Some have argued that nobody should use rdtsc and any programs that use rdtsc directly are "fundamentally broken" so the default for rdtsc

Hi, Trying to compile tcng on 64bit server (centos-5 64bit), I''m getting: -------------- cc -g -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -I../shared -DVERSION=\"`cat ../VERSION`\" -DTOPDIR=\"/usr/local/src/tcng-non-patched\" -DDOLLAR -DCONFIRM_EXCEED -c -o f_fw.o f_fw.c In file included from ../shared/memutil.h:13, from

Thanks for answer. I am very sad to see that. I had examined samba behavior with tracer and had seen too many poll, fcntl and stat system calls by samba task[ldapsrv] process Elapsed Times for PID 1423, SYSCALL TIME (ns) dup 2653 flock 5811 lseek 33513 geteuid 42747

The attached patches are against the v0.114 release and cover some of the tweaks I made while playing about testing ARM and Thumb support. Please review and consider applying. Even with the patches, ARM dynamic linking doesn't seem to work and the Thumb test applications seem to have shaken out a Thumb bug in the 2.4.21-rmk2 kernel which I'm still trying to track down. Still more fun to

On Nov 2, 2023, at 4:39 PM, Grant Erickson <gerickson at nuovations.com> wrote: > On Nov 2, 2023, at 4:32 PM, Damien Miller <djm at mindrot.org> wrote: >> On Mon, 30 Oct 2023, Grant Erickson wrote: >> >>> I have an NXP i.MX6-based armv7l-dey-linux-gnueabihf system in which I >>> am seeing some as-yet-unaccountable behavior in sshd when compiled with