search for: boot_successes

....14-rc6. >>> >>> 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 > >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 sor...

....14-rc6. >>> >>> 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 > >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 sor...

...-------------------------------------------------------+------------+------------+ > | | d658aa6259 | 0c5a9920fb | > +-----------------------------------------------------------------------+------------+------------+ > | boot_successes | 2 | 0 | > | boot_failures | 6 | 8 | > | WARNING:at_arch/x86/mm/dump_pagetables.c:#note_page | 6 | 8 | > |...

...warnings when testing v4.14-rc6. >> >> 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 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 pendi...

...we see the below boot error/warnings when testing v4.14-rc6. > >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: 19109699403...

...we see the below boot error/warnings when testing v4.14-rc6. > >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: 19109699403...

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

...files for 20170929 +----------------------+------------+------------+------------+------------+---------------+ | | f57091767a | c6ef89421e | 24e700e291 | 0f380715e5 | next-20170929 | +----------------------+------------+------------+------------+------------+---------------+ | boot_successes | 320 | 320 | 101 | 28 | 5 | | boot_failures | 0 | 0 | 15 | 2 | 1 | | WARNING:kernel_stack | 0 | 0 | 15 | 2 | 1 | +----------------------+------------+...

...files for 20170929 +----------------------+------------+------------+------------+------------+---------------+ | | f57091767a | c6ef89421e | 24e700e291 | 0f380715e5 | next-20170929 | +----------------------+------------+------------+------------+------------+---------------+ | boot_successes | 320 | 320 | 101 | 28 | 5 | | boot_failures | 0 | 0 | 15 | 2 | 1 | | WARNING:kernel_stack | 0 | 0 | 15 | 2 | 1 | +----------------------+------------+...

...used below changes (please refer to attached dmesg/kmsg for entire log/backtrace): +------------------------------------------+------------+------------+ | | b4b818b1f7 | c8bf448ff3 | +------------------------------------------+------------+------------+ | boot_successes | 8 | 0 | | boot_failures | 0 | 8 | | kernel_BUG_at_arch/x86/mm/physaddr.c | 0 | 8 | | invalid_opcode:#[##] | 0 | 8 | | RIP:__phys_addr...

...43ee9 virtio_blk: Fix an SG_IO regression +-------------------------------------------+------------+------------+------------+ | | 875397464a | a570843ee9 | a570843ee9 | +-------------------------------------------+------------+------------+------------+ | boot_successes | 37 | 4 | 4 | | boot_failures | 0 | 11 | 11 | | kernel_BUG_at_include/linux/scatterlist.h | 0 | 11 | 11 | | invalid_opcode:#[##] | 0 | 11...

...43ee9 virtio_blk: Fix an SG_IO regression +-------------------------------------------+------------+------------+------------+ | | 875397464a | a570843ee9 | a570843ee9 | +-------------------------------------------+------------+------------+------------+ | boot_successes | 37 | 4 | 4 | | boot_failures | 0 | 11 | 11 | | kernel_BUG_at_include/linux/scatterlist.h | 0 | 11 | 11 | | invalid_opcode:#[##] | 0 | 11...

This patch series aims to move the logical block size checking to the block code. This was inspired by missing check for valid logical block size in virtio-blk which causes the kernel to crash in a weird way later on when it is invalid. I added blk_is_valid_logical_block_size which returns true iff the block size is one of supported sizes. I added this check to virtio-blk, and also converted

This patch series aims to move the logical block size checking to the block code. This was inspired by missing check for valid logical block size in virtio-blk which causes the kernel to crash in a weird way later on when it is invalid. I added blk_is_valid_logical_block_size which returns true iff the block size is one of supported sizes. I added this check to virtio-blk, and also converted

Hi, here is the next version of changes to enable Linux to run as an SEV-ES guest. The code was rebased to v5.7-rc3 and got a fair number of changes since the last version. What is SEV-ES ============== SEV-ES is an acronym for 'Secure Encrypted Virtualization - Encrypted State' and means a hardware feature of AMD processors which hides the register state of VCPUs to the hypervisor by

Hi, here is the next version of changes to enable Linux to run as an SEV-ES guest. The code was rebased to v5.7-rc3 and got a fair number of changes since the last version. What is SEV-ES ============== SEV-ES is an acronym for 'Secure Encrypted Virtualization - Encrypted State' and means a hardware feature of AMD processors which hides the register state of VCPUs to the hypervisor by