similar to: [PATCH net-next 10/12] tools/virtio: more stubs to fix tools build

The condition to test is unlikely() to be true. Add the hint. Signed-off-by: Igor Stoppa <igor.stoppa at huawei.com> Cc: "Michael S. Tsirkin" <mst at redhat.com> Cc: Jason Wang <jasowang at redhat.com> Cc: Virtualization at lists.linux-foundation.org Cc: linux-kernel at vger.kernel.org --- tools/virtio/linux/kernel.h | 2 +- 1 file changed, 1 insertion(+), 1

Hi Jason, I love your patch! Perhaps something to improve: [auto build test WARNING on net/master] url: https://github.com/0day-ci/linux/commits/Jason-Wang/Fix-various-issue-of-vhost/20181210-223236 config: i386-randconfig-x072-201849 (attached as .config) compiler: gcc-7 (Debian 7.3.0-1) 7.3.0 reproduce: # save the attached .config to linux build tree make ARCH=i386 All

tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost head: 84d40e4b4bc64456abf5ef5663871053b40e84ac commit: fee8fe6bd8ccacd27e963b71b4f943be3721779e [38/45] vdpa: make sure set_features in invoked for legacy config: m68k-randconfig-r022-20200727 (attached as .config) compiler: m68k-linux-gcc (GCC) 9.3.0 reproduce (this is a W=1 build): wget

Some details that may be useful in analysis of the bug: 1. lspci -nn -d 10de: 2. What displays, if any, you have plugged into the NVIDIA board when this happens? 3. Any boot parameters, esp relating to ACPI, PM, or related? Cheers, -ilia On Tue, Jul 11, 2017 at 1:32 PM, Mike Galbraith <efault at gmx.de> wrote: > Greetings, > > I met $subject in master-rt post drm merge, but

Greetings, I met $subject in master-rt post drm merge, but taking the config (attached) to virgin v4.12-10624-g9967468c0a10, it's reproducible. KERNEL: vmlinux-4.12.0.g9967468-preempt.gz DUMPFILE: vmcore CPUS: 8 DATE: Tue Jul 11 18:55:28 2017 UPTIME: 00:02:03 LOAD AVERAGE: 3.43, 1.39, 0.52 TASKS: 467 NODENAME: homer RELEASE:

Hi Armin! I have problems on debian sarge with standard 2.6.8-2-386 kernel. I've installed the packages: kernel-headers-2.6.8-2 kernel-headers-2.6.8-2-386 kernel-image-2.6.8-2-386 kernel-kbuild-2.6-3 kernel-source-2.6.8 Then I unpacked the kernel sources into /usr/src/kernel-source-2.6.8 and made a symlink from /usr/src/linux --> kernel-source-2.6.8 Then I entered

tree: git://github.com/ablock84/linux-btrfs.git btrfs-far head: f9a5bb450a8cc7aa5fd4f11d0306b3f48cf2771d commit: 29aefeaaf482ab396ff53c2bbf5c35ce237b91c0 [19/20] fs: add libfarstream support config: make ARCH=s390 allmodconfig All error/warnings: In file included from include/linux/byteorder/big_endian.h:4:0, from arch/s390/include/uapi/asm/byteorder.h:4,

Greetings, I''m unable to build current (Sun Feb 26 18:14:23 UTC 2006) linux-2.6-xen.hg on Debian sarge AMD64 host. Following error messgaes appears: -- CUT HERE -- sunfire:/usr/src/xen-subarch/linux-2.6-xen.hg# make CHK include/linux/version.h SPLIT include/linux/autoconf.h -> include/config/* CC arch/x86_64/kernel/asm-offsets.s In file included from

Hi I am writing a freestanding statically linked x86_64 kernel. And now I want to load and use thread-local storage. As I have a freestanding binary I can't use libc/Linux kernel thread-local mechanism and need to implement initialization code by myself. I am trying to find a clear explanation of what is the memory layout for x86 TLS but can't find anything useful. Maybe LLVM developers

From: Randy Dunlap <randy.dunlap@oracle.com> Since Voyager and Visual WS already define ARCH_SETUP, it looks like PARAVIRT shouldn't be offered for them. In file included from arch/i386/kernel/setup.c:63: include/asm-i386/mach-visws/setup_arch.h:8:1: warning: "ARCH_SETUP" redefined In file included from include/asm/msr.h:5, from include/asm/processor.h:17,

From: Randy Dunlap <randy.dunlap@oracle.com> Since Voyager and Visual WS already define ARCH_SETUP, it looks like PARAVIRT shouldn't be offered for them. In file included from arch/i386/kernel/setup.c:63: include/asm-i386/mach-visws/setup_arch.h:8:1: warning: "ARCH_SETUP" redefined In file included from include/asm/msr.h:5, from include/asm/processor.h:17,

tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/mst/vhost.git linux-next head: 39c226b6b576b23d6d558331e6895f02b0892555 commit: 990055c63121520ad29deca72b1167b392563ddd [16/17] virtio-balloon: Add support for providing unused page reports to host config: riscv-allmodconfig (attached as .config) compiler: riscv64-linux-gcc (GCC) 7.4.0 reproduce: wget

Hello, I am trying to run xen-3.0 in some of my dell servers. I have tried the binary distribution of xen, but it doesn''t boot in my test system (a dell poweredge 750) because a module driver problem (I get an error message during booting saying it doesn''t load a NFS root filesystem). So I am trying to compile a custom kernel. So I have downloaded linux source 2.6.12. I am

So, is everyone happy with this smerge of Ingo and Gerd's work? Reposted below. Thanks, Rusty. -------- Forwarded Message -------- From: Linus Torvalds <torvalds@osdl.org> To: Rusty Russell <rusty@rustcorp.com.au> Cc: Andrew Morton <akpm@osdl.org> Subject: Re: [Fwd: [Fwd: FW: argh]] Date: Wed, 17 May 2006 21:35:51 -0700 (PDT) On Thu, 18 May 2006, Rusty Russell wrote: >

So, is everyone happy with this smerge of Ingo and Gerd's work? Reposted below. Thanks, Rusty. -------- Forwarded Message -------- From: Linus Torvalds <torvalds@osdl.org> To: Rusty Russell <rusty@rustcorp.com.au> Cc: Andrew Morton <akpm@osdl.org> Subject: Re: [Fwd: [Fwd: FW: argh]] Date: Wed, 17 May 2006 21:35:51 -0700 (PDT) On Thu, 18 May 2006, Rusty Russell wrote: >

[ Expand, correct and clarify comments; minor code change. ] Most of the time we can simply use the iret instruction to exit the kernel, rather than having to use the iret hypercall - the only exception is if we're returning into vm86 mode, or from delivering an NMI (which we don't support yet). When running native, iret has the behaviour of testing for a pending interrupt atomically

[ Expand, correct and clarify comments; minor code change. ] Most of the time we can simply use the iret instruction to exit the kernel, rather than having to use the iret hypercall - the only exception is if we're returning into vm86 mode, or from delivering an NMI (which we don't support yet). When running native, iret has the behaviour of testing for a pending interrupt atomically

Hi, I have successfully installed Xen unstable binary on SuSE 9.3. I am trying to do a source install and I got the following error. Will be glad for any help or guidance. In file included from include/asm-xen/asm/processor.h:18, from include/asm/thread_info.h:17, from include/linux/thread_info.h:21, from include/linux/spinlock.h:12, from include/linux/capability.h:45, from

xen: use iret directly where possible Most of the time we can simply use the iret instruction to exit the kernel, rather than having to use the iret hypercall - the only exception is if we're returning into vm86 mode, or from delivering an NMI (which we don't support yet). When running native, iret has the behaviour of testing for a pending interrupt atomically with re-enabling

xen: use iret directly where possible Most of the time we can simply use the iret instruction to exit the kernel, rather than having to use the iret hypercall - the only exception is if we're returning into vm86 mode, or from delivering an NMI (which we don't support yet). When running native, iret has the behaviour of testing for a pending interrupt atomically with re-enabling