search for: __jiffies

...easily emulate the BIOS_timer at 0x046C but it has problems emulating a "real" timer interrupt to be hooked... That's the real problem. Just testing I have replaced the timing functions #define BIOS_timer 0x046C // Timer ticks typedef uint32_t jiffies_t; extern volatile jiffies_t __jiffies, __ms_timer; static inline jiffies_t jiffies(void) { return (*(volatile uint32_t *)BIOS_timer); } typedef uint32_t mstime_t; typedef int32_t mstimediff_t; static inline mstime_t ms_timer(void) { return ((*(volatile uint32_t *)BIOS_timer) * 55); } lpxelinux.0 hangs while legacy works OK. I thi...

On 03/01/16 21:11, H. Peter Anvin via Syslinux wrote: > On 03/01/16 07:21, Patrick Masotta via Syslinux wrote: >> >> At the moment I'm seeing timing issues on TFTP transfers (lwIP depends >> on the new interrupt based timer). I have consistently detected >> >> multiple Requests, double ACKs, etc. All these problems seem to be >> >> sourced on the

Hi, This series corresponds do older patches in the paravirt series that was neither already applied, nor I will touch again. In general, they do not touch code that can be unified (at least, without being the unification a big problem on its own). They passed through this list a lot of times, so I feel them ready for inclusion, unless someone opposes. As with the other patches, they apply to

Hi, This series corresponds do older patches in the paravirt series that was neither already applied, nor I will touch again. In general, they do not touch code that can be unified (at least, without being the unification a big problem on its own). They passed through this list a lot of times, so I feel them ready for inclusion, unless someone opposes. As with the other patches, they apply to

...han 24s, not in over 5 minutes. So, there's something else going on, but what? I tried to figure out why a UDP packet on a virtual network with unlimited bandwidth and zero packet-loss would hit a 15ms timeout. The comment says it waits for 15ms, but it does this by counting volatile uint32_t __jiffies, which gets incremented from efi/main.c by an event initiated from the UEFI API. According to the comment near the #define DEFAULT_TIMER_TICK_DURATION, the jiffies should increment every 50 msec. So a jiffie is not 1 msec but 50 times longer. If this comment is correct, the actual timeout isn't...

...ited bandwidth and zero packet-loss would hit a 15ms timeout. The You'd be surprised how much CPU and RAM speed influence this. Handling a sustained 2Gbps for example doesn't do well on most servers. > comment says it waits for 15ms, but it does this by counting volatile > uint32_t __jiffies, which gets incremented from efi/main.c by an event > initiated from the UEFI API. According to the comment near the #define > DEFAULT_TIMER_TICK_DURATION, the jiffies should increment every 50 msec. > So a jiffie is not 1 msec but 50 times longer. If this comment is > correct, the actu...

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths