search for: clock_realtim

Displaying 20 results from an estimated 49 matches for "clock_realtim".

Did you mean: clock_realtime
2012 Jun 25
6
puppet freezes on FUTEX_WAKE_PRIVATE
...ne and if it can be solved. Many of my ( 30+ ) puppet installation freeze up after some time. The process is waiting for some private futex, but it stays like that forever. This is what strace looks like when the problem occures: [pid 29173] futex(0x3d35ce7a84, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43406739, {1340611695, 739433265}, ffffffff) = -1 ETIMEDOUT (Connection timed out) [pid 29173] clock_gettime(CLOCK_REALTIME, {1340611695, 741431552}) = 0 [pid 29173] futex(0x3d35ce7ab0, FUTEX_WAKE_PRIVATE, 1) = 0 [pid 29173] futex(0x3d35ce7a84, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43...
2018 Sep 17
11
[patch V2 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
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
2009 Oct 23
3
rdtsc in userspace
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
2018 Sep 14
24
[patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
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
2018 Sep 14
24
[patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
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
2008 Nov 27
1
Re: RE: Re: Re: when timer go back in dom0 save and restore ormigrate, PV domain hung
...ens if someone changes wallclock using ''date''? That''s basically kind of what will appear to happen when s/r occurs. -- Keir On 26/11/08 14:32, "Tian, Kevin" <kevin.tian@intel.com> wrote: hrtimer supports two timer bases: CLOCK_MONOTONIC and CLOCK_REALTIME. wall_to_monotonic is only added in former case, and for latter instead TOD is used directly per my reading. I did a quick search, and it looks that futex and ntp are using CLOCK_REALTIME. Also there''s one vsyscall gate which can pass CLOCK_REALTIME from caller too. Thank...
2008 Nov 25
7
when timer go back in dom0 save and restore or migrate, PV domain hung
Hi, I find PV domin hung, When we take those steps 1, save PV domain 2, change system time of PV domain back 3, restore a PV domain or 1, migrate a PV domain from Machine A to Machine B 2, the system time of Machine B is slower than Machine A. the problem is wc_sec will be change when system-time chanaged in dom0 or restore in a
2018 Sep 14
0
[patch 11/11] x66/vdso: Add CLOCK_TAI support
...NIC]; base->sec = tk->xtime_sec + tk->wall_to_monotonic.tv_sec; nsec = tk->tkr_mono.xtime_nsec; --- a/arch/x86/include/asm/vgtod.h +++ b/arch/x86/include/asm/vgtod.h @@ -19,9 +19,13 @@ struct vgtod_ts { }; #define VGTOD_BASES (CLOCK_MONOTONIC_COARSE + 1) -#define VGTOD_HRES (BIT(CLOCK_REALTIME) | BIT(CLOCK_MONOTONIC)) +#define VGTOD_HRES (BIT(CLOCK_REALTIME) | BIT(CLOCK_MONOTONIC) | BIT(CLOCK_TAI)) #define VGTOD_COARSE (BIT(CLOCK_REALTIME_COARSE) | BIT(CLOCK_MONOTONIC_COARSE)) +/* Abuse CLOCK_THREAD_CPUTIME_ID for VGTOD CLOCK TAI */ +#define VGTOD_HRES_MASK 0x3 +#define VGTOD_TAI (CL...
2013 Jul 08
1
Samba4, NTP, and Ubuntu 12.04
Hello, I have a question regarding signed NTP support for Samba4 on Ubuntu 12.04. I have followed most of the steps outlined here: https://wiki.samba.org/index.php/Configure_NTP These steps I did differently are: * I did not install from source because the latest Ubuntu package for ntp available on Ubuntu 12.04 includes ntp-signd support already * I did not install Samba4 to /usr/local/samba, so
2018 Sep 14
2
[patch 11/11] x66/vdso: Add CLOCK_TAI support
...->wall_to_monotonic.tv_sec; > nsec = tk->tkr_mono.xtime_nsec; > --- a/arch/x86/include/asm/vgtod.h > +++ b/arch/x86/include/asm/vgtod.h > @@ -19,9 +19,13 @@ struct vgtod_ts { > }; > > #define VGTOD_BASES (CLOCK_MONOTONIC_COARSE + 1) > -#define VGTOD_HRES (BIT(CLOCK_REALTIME) | BIT(CLOCK_MONOTONIC)) > +#define VGTOD_HRES (BIT(CLOCK_REALTIME) | BIT(CLOCK_MONOTONIC) | BIT(CLOCK_TAI)) > #define VGTOD_COARSE (BIT(CLOCK_REALTIME_COARSE) | BIT(CLOCK_MONOTONIC_COARSE)) > > +/* Abuse CLOCK_THREAD_CPUTIME_ID for VGTOD CLOCK TAI */ > +#define VGTOD_HRES_MA...
2018 Sep 14
2
[patch 11/11] x66/vdso: Add CLOCK_TAI support
...->wall_to_monotonic.tv_sec; > nsec = tk->tkr_mono.xtime_nsec; > --- a/arch/x86/include/asm/vgtod.h > +++ b/arch/x86/include/asm/vgtod.h > @@ -19,9 +19,13 @@ struct vgtod_ts { > }; > > #define VGTOD_BASES (CLOCK_MONOTONIC_COARSE + 1) > -#define VGTOD_HRES (BIT(CLOCK_REALTIME) | BIT(CLOCK_MONOTONIC)) > +#define VGTOD_HRES (BIT(CLOCK_REALTIME) | BIT(CLOCK_MONOTONIC) | BIT(CLOCK_TAI)) > #define VGTOD_COARSE (BIT(CLOCK_REALTIME_COARSE) | BIT(CLOCK_MONOTONIC_COARSE)) > > +/* Abuse CLOCK_THREAD_CPUTIME_ID for VGTOD CLOCK TAI */ > +#define VGTOD_HRES_MA...
2018 Sep 14
0
[patch 09/11] x86/vdso: Simplify the invalid vclock case
...= VCLOCK_NONE) - return 0; + return do_hres(clock, ts); } else if (msk & VGTOD_COARSE) { do_coarse(clock, ts); return 0; @@ -268,8 +230,7 @@ notrace int __vdso_gettimeofday(struct t if (likely(tv != NULL)) { struct timespec *ts = (struct timespec *) tv; - if (unlikely(do_hres(CLOCK_REALTIME, ts) == VCLOCK_NONE)) - return vdso_fallback_gtod(tv, tz); + do_hres(CLOCK_REALTIME, ts); tv->tv_usec /= 1000; } if (unlikely(tz != NULL)) {
2023 Jan 26
0
[klibc:time64] time: Use clock_* system calls for time-of-day and sleep
...ibc/gettimeofday.c @@ -0,0 +1,22 @@ +#include <time.h> +#include <sys/time.h> +#include <sys/syscall.h> + +extern int __gettimeofday(void *, struct timezone *); + +int gettimeofday(struct timeval *tv, struct timezone *tz) +{ + struct timespec ts; + + if (tv) { + if (clock_gettime(CLOCK_REALTIME, &ts)) + return -1; + tv->tv_sec = ts.tv_sec; + tv->tv_usec = ts.tv_nsec / 1000; + } + + if (tz && __gettimeofday(NULL, tz)) + return -1; + + return 0; +} diff --git a/usr/klibc/nanosleep.c b/usr/klibc/nanosleep.c new file mode 100644 index 00000000..11412196 --- /dev/null +...
2018 Jul 19
0
[PATCH 1/3] [RFC V3] KVM: X86: Memory ROE documentation
...1 file changed, 14 insertions(+) diff --git a/Documentation/virtual/kvm/hypercalls.txt b/Documentation/virtual/kvm/hypercalls.txt index a890529c63ed..a9db68adb7c9 100644 --- a/Documentation/virtual/kvm/hypercalls.txt +++ b/Documentation/virtual/kvm/hypercalls.txt @@ -121,3 +121,17 @@ compute the CLOCK_REALTIME for its clock, at the same instant. Returns KVM_EOPNOTSUPP if the host does not use TSC clocksource, or if clock type is different than KVM_CLOCK_PAIRING_WALLCLOCK. + +7. KVM_HC_HMROE +---------------- +Architecture: x86 +Status: active +Purpose: Hypercall used to apply Read-Only Enforcement t...
2020 Jul 21
0
[PATCH v9 05/84] KVM: doc: fix the hypercall numbering
...1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/virt/kvm/hypercalls.rst b/Documentation/virt/kvm/hypercalls.rst index ed4fddd364ea..70e77c66b64c 100644 --- a/Documentation/virt/kvm/hypercalls.rst +++ b/Documentation/virt/kvm/hypercalls.rst @@ -137,7 +137,7 @@ compute the CLOCK_REALTIME for its clock, at the same instant. Returns KVM_EOPNOTSUPP if the host does not use TSC clocksource, or if clock type is different than KVM_CLOCK_PAIRING_WALLCLOCK. -6. KVM_HC_SEND_IPI +7. KVM_HC_SEND_IPI ------------------ :Architecture: x86 @@ -158,7 +158,7 @@ corresponds to the APIC ID...
2008 Jan 03
1
[PATCH] Use memset(0) instead of setting cb_mode explicitly
...rs/net/virtio_net.c @@ -434,9 +434,9 @@ static int virtnet_probe(struct virtio_device *vdev) netif_napi_add(dev, &vi->napi, virtnet_poll, napi_weight); vi->dev = dev; vi->vdev = vdev; + memset(&vi->tx_timer, 0, sizeof(vi->tx_timer)); hrtimer_init(&vi->tx_timer, CLOCK_REALTIME, HRTIMER_MODE_REL); vi->tx_timer.function = kick_xmit; - vi->tx_timer.cb_mode = HRTIMER_CB_SOFTIRQ; vi->out_max = -1U; tasklet_init(&vi->xmit_free, xmit_free, (unsigned long)vi);
2008 Jan 03
1
[PATCH] Use memset(0) instead of setting cb_mode explicitly
...rs/net/virtio_net.c @@ -434,9 +434,9 @@ static int virtnet_probe(struct virtio_device *vdev) netif_napi_add(dev, &vi->napi, virtnet_poll, napi_weight); vi->dev = dev; vi->vdev = vdev; + memset(&vi->tx_timer, 0, sizeof(vi->tx_timer)); hrtimer_init(&vi->tx_timer, CLOCK_REALTIME, HRTIMER_MODE_REL); vi->tx_timer.function = kick_xmit; - vi->tx_timer.cb_mode = HRTIMER_CB_SOFTIRQ; vi->out_max = -1U; tasklet_init(&vi->xmit_free, xmit_free, (unsigned long)vi);
2007 Dec 21
0
[kvm-devel] [Virtio-for-kvm] [PATCH 6/13] [Mostly resend] virtio additions
...me_set(0,500000), + HRTIMER_MODE_REL); return 0; } @@ -363,6 +398,10 @@ static int virtnet_probe(struct virtio_device *vdev) netif_napi_add(dev, &vi->napi, virtnet_poll, 16); vi->dev = dev; vi->vdev = vdev; + hrtimer_init(&vi->tx_timer, CLOCK_REALTIME, HRTIMER_MODE_REL); + vi->tx_timer.function = kick_xmit; + vi->tx_timer.cb_mode = HRTIMER_CB_SOFTIRQ; + vi->out_max = -1U; /* We expect two virtqueues, receive then send. */ vi->rvq = vdev->config->find_vq(vdev, 0, skb_recv_done); -- 1.5.3.3
2007 Dec 21
0
[kvm-devel] [Virtio-for-kvm] [PATCH 6/13] [Mostly resend] virtio additions
...me_set(0,500000), + HRTIMER_MODE_REL); return 0; } @@ -363,6 +398,10 @@ static int virtnet_probe(struct virtio_device *vdev) netif_napi_add(dev, &vi->napi, virtnet_poll, 16); vi->dev = dev; vi->vdev = vdev; + hrtimer_init(&vi->tx_timer, CLOCK_REALTIME, HRTIMER_MODE_REL); + vi->tx_timer.function = kick_xmit; + vi->tx_timer.cb_mode = HRTIMER_CB_SOFTIRQ; + vi->out_max = -1U; /* We expect two virtqueues, receive then send. */ vi->rvq = vdev->config->find_vq(vdev, 0, skb_recv_done); -- 1.5.3.3
2019 Apr 04
0
[Bug 1332] New: Time-matching extension (--match time) broken by timestamping changes in kernel 4.20 and later
...mp((struct sk_buff *)skb); The above code will check if the packet already has a timestamp or not. If the timestamp is missing, then the packet is timestamped with the current time. All subsequent time matching calculations then assume that the packet's timestamp is relative to the UNIX epoch (CLOCK_REALTIME reference). This all works fine, as long as the timestamp explicitly has been set in xt_time. But the same assumption on clock reference might not hold, if the packet comes in pre-timestamped. And this is exactly what is happening in kernel 4.20.x and later. Here the packets come in with a timesta...