search for: preemtible

Hi, I'm in the process of migrating from clang5 to clang10. Unfortunately clang10 introduced a negative performance impact. The cause is an increase of PLT entries from this patch (first released in clang7): https://bugs.llvm.org/show_bug.cgi?id=36370 https://reviews.llvm.org/D43383 If I revert that clang patch locally, the additional PLT entries and the performance impact disappear. This

Hi, I am profiling some workloads for the voluntary and involuntary context switches. I am interested in finding out the reasons causing these two types of context switches. As far as I understand, involuntary context switch happens on expiration of time slice or when a higher priority process comes in. While the voluntary switch generally happens when a process is waiting for I/O etc. So to

...ns under which the PLT->PC relocation reduction should occur? >>>> >>>> Below there is a description of LLD linker behavior with links to source code, >>>> which also contains some usefull comments. >>>> >>>> 1) A symbol should be not preemtible. The responsible function that is used to set >>>> this flag is `bool elf::computeIsPreemptible(const Symbol &sym)` >>>> (https://github.com/llvm/llvm-project/blob/master/lld/ELF/Symbols.cpp#L353) >>>> >>>> When the configuration is `--shared` it...

I recently sent off a fix for lazy vmalloc faults which can happen under = paravirt when lazy mode is enabled. Unfortunately, I jumped the gun a = bit on fixing this. I neglected to notice that since the new call to = flush the MMU update queue is called from the page fault handler, it can = be pre-empted. Both VMI and Xen use per-cpu variables to track lazy = mode state, as all previous

I recently sent off a fix for lazy vmalloc faults which can happen under = paravirt when lazy mode is enabled. Unfortunately, I jumped the gun a = bit on fixing this. I neglected to notice that since the new call to = flush the MMU update queue is called from the page fault handler, it can = be pre-empted. Both VMI and Xen use per-cpu variables to track lazy = mode state, as all previous

I have noticed that many games (Farcry 2, Fallout 3, Fallout: New Vegas, Drakensang) crash with some form of out of memory messages. So obviously something is leaking memory (whether it is wine or the game or drivers, I cannot say). But it always happens as soon as wine uses ~1.5 GB of RAM. Also I wonder if it has something to do with this bug: http://bugs.winehq.org/show_bug.cgi?id=25428 I ran