search for: at_kernel

...s >>> auto bisection. So I manually list them here and CC the likely easy to >>> debug ones to the corresponding maintainers in the followup emails. >>> >>> boot_successes: 4700 >>> boot_failures: 247 >> >> [...] >> >>> WARNING:at_kernel/jump_label.c:#static_key_disable_cpuslocked: 7 > >This patch is in the tip tree only, it will be merged in 4.15. So I >don't understand why you are reporting this for 4.14-rc6. Ah sorry, I simply checked recent bisects for that warning. Then I'll need to carry out some new bisect...

...s >>> auto bisection. So I manually list them here and CC the likely easy to >>> debug ones to the corresponding maintainers in the followup emails. >>> >>> boot_successes: 4700 >>> boot_failures: 247 >> >> [...] >> >>> WARNING:at_kernel/jump_label.c:#static_key_disable_cpuslocked: 7 > >This patch is in the tip tree only, it will be merged in 4.15. So I >don't understand why you are reporting this for 4.14-rc6. Ah sorry, I simply checked recent bisects for that warning. Then I'll need to carry out some new bisect...

...various imperfections in 0day's >> auto bisection. So I manually list them here and CC the likely easy to >> debug ones to the corresponding maintainers in the followup emails. >> >> boot_successes: 4700 >> boot_failures: 247 > > [...] > >> WARNING:at_kernel/jump_label.c:#static_key_disable_cpuslocked: 7 This patch is in the tip tree only, it will be merged in 4.15. So I don't understand why you are reporting this for 4.14-rc6. There is a patch by Dou Liyang pending since 28th October addressing that issue: [PATCH tip v2] x86/paravirt: Make the...

...; >They hit the RC release mainly due to various imperfections in 0day's >auto bisection. So I manually list them here and CC the likely easy to >debug ones to the corresponding maintainers in the followup emails. > >boot_successes: 4700 >boot_failures: 247 [...] >WARNING:at_kernel/jump_label.c:#static_key_disable_cpuslocked: 7 The call trace is [ 0.000000] Booting paravirtualized kernel on bare hardware [ 0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns [ 0.000000] setup_percpu: NR_CPUS:8192 nr_cpuma...

...; >They hit the RC release mainly due to various imperfections in 0day's >auto bisection. So I manually list them here and CC the likely easy to >debug ones to the corresponding maintainers in the followup emails. > >boot_successes: 4700 >boot_failures: 247 [...] >WARNING:at_kernel/jump_label.c:#static_key_disable_cpuslocked: 7 The call trace is [ 0.000000] Booting paravirtualized kernel on bare hardware [ 0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns [ 0.000000] setup_percpu: NR_CPUS:8192 nr_cpuma...

Setting the IF flag can cause an VM exit. So we should avoid touching the IF flag until absolutely necessary. This patch change the way the paravirt arch_local_irq_restore() works by checking the previous flags value and call arch_local_irq_enable() only if the IF flag was set previously. On a 32 vCPUs KVM guest running the AIM7 five-sec workload, the performance increased slightly from 302136.32

Setting the IF flag can cause an VM exit. So we should avoid touching the IF flag until absolutely necessary. This patch change the way the paravirt arch_local_irq_restore() works by checking the previous flags value and call arch_local_irq_enable() only if the IF flag was set previously. On a 32 vCPUs KVM guest running the AIM7 five-sec workload, the performance increased slightly from 302136.32

Greetings, I got the below dmesg and the first bad commit is commit cf39c8e5352b4fb9efedfe7e9acb566a85ed847c Merge: 3398d25 23b7eaf Author: Linus Torvalds <torvalds@linux-foundation.org> Date: Wed Sep 4 17:45:39 2013 -0700 Merge tag ''stable/for-linus-3.12-rc0-tag'' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip Pull Xen updates from Konrad