similar to: [PATCH 1/5] um/... convert #include "linux/..." to #include <linux/...>

There are several files that: #include "linux/file" not #include <linux/file> #include "asm/file" not #include <asm/file> Here's the little script that converted them: egrep -i -r -l --include=*.[ch] \ "^[[:space:]]*\#[[:space:]]*include[[:space:]]*\"(linux|asm)/(.*)\"" * \ | xargs sed -i -e

There are several files that: #include "linux/file" not #include <linux/file> #include "asm/file" not #include <asm/file> Here's the little script that converted them: egrep -i -r -l --include=*.[ch] \ "^[[:space:]]*\#[[:space:]]*include[[:space:]]*\"(linux|asm)/(.*)\"" * \ | xargs sed -i -e

I have been trying to compile Zaptel 1.0-RC1 that I just downloaded via tarball on my debian 3.0 system running a 2.4.26 kernel. I have all the headers, libraries and sources installed for the kernel along with the latest versions of GCC. I dont know what else to do to trouble shoot this so I have included the entire output below. Thanks a lot! -James Freire linux1:/usr/src/zaptel-1.0-RC1#

In a hosted VMM like LinuxOnLinux or UML, context switch time can be a major problem (as mmap when repeated for each guest page frame takes a long time). One solution is to allow the host kernel to keep a cache of address space contexts, and switch between them in a single operation. The attached patch is a start at this. It works well for LinuxOnLinux; but I'd be interested from the

In a hosted VMM like LinuxOnLinux or UML, context switch time can be a major problem (as mmap when repeated for each guest page frame takes a long time). One solution is to allow the host kernel to keep a cache of address space contexts, and switch between them in a single operation. The attached patch is a start at this. It works well for LinuxOnLinux; but I'd be interested from the

The patch below fixes the recent UML compilation failure in -rc5-mm1 without making the UML build reach further into the i386 headers. It splits the i386 ptrace.h and system.h into UML-usable and UML-unusable pieces. The string "abi" is in there because I did ptrace.h first, and that involves separating the ptrace ABI stuff from everything else (if pt_regs is not considered part of

The patch below fixes the recent UML compilation failure in -rc5-mm1 without making the UML build reach further into the i386 headers. It splits the i386 ptrace.h and system.h into UML-usable and UML-unusable pieces. The string "abi" is in there because I did ptrace.h first, and that involves separating the ptrace ABI stuff from everything else (if pt_regs is not considered part of

drivers/xen/balloon.c:50: WARNING: Use #include <linux/uaccess.h> instead of <asm/uaccess.h> drivers/xen/balloon.c:158: ERROR: else should follow close brace '}' drivers/xen/balloon.c:277: ERROR: do not use assignment in if condition drivers/xen/balloon.c:293: ERROR: code indent should use tabs where possible drivers/xen/balloon.c:364: ERROR: that open brace { should be on the

drivers/xen/balloon.c:50: WARNING: Use #include <linux/uaccess.h> instead of <asm/uaccess.h> drivers/xen/balloon.c:158: ERROR: else should follow close brace '}' drivers/xen/balloon.c:277: ERROR: do not use assignment in if condition drivers/xen/balloon.c:293: ERROR: code indent should use tabs where possible drivers/xen/balloon.c:364: ERROR: that open brace { should be on the

drivers/xen/balloon.c:50: WARNING: Use #include <linux/uaccess.h> instead of <asm/uaccess.h> drivers/xen/balloon.c:158: ERROR: else should follow close brace '}' drivers/xen/balloon.c:277: ERROR: do not use assignment in if condition drivers/xen/balloon.c:293: ERROR: code indent should use tabs where possible drivers/xen/balloon.c:364: ERROR: that open brace { should be on the

Author: tha-guest Date: 2006-02-24 23:45:10 +0000 (Fri, 24 Feb 2006) New Revision: 56 Modified: trunk/debian/README.Debian trunk/debian/changelog trunk/debian/control trunk/debian/linux-2.6.12-xen.patch Log: hopefully for the last commit before release ;-P - xen-hypervisor & -pae now recommends grub (besides PXE-Boot there is no alternative) - updated & added some more to

Most of asm-x86_64/bugs.h is code which should be in a C file, so put it there. Signed-off-by: Jeremy Fitzhardinge <jeremy@xensource.com> Cc: Andi Kleen <ak@suse.de> Cc: Linus Torvalds <torvalds@linux-foundation.org> --- arch/x86_64/kernel/Makefile | 3 ++- arch/x86_64/kernel/bugs.c | 28 ++++++++++++++++++++++++++++ include/asm-x86_64/alternative.h | 1 +

Most of asm-x86_64/bugs.h is code which should be in a C file, so put it there. Signed-off-by: Jeremy Fitzhardinge <jeremy@xensource.com> Cc: Andi Kleen <ak@suse.de> Cc: Linus Torvalds <torvalds@linux-foundation.org> --- arch/x86_64/kernel/Makefile | 3 ++- arch/x86_64/kernel/bugs.c | 28 ++++++++++++++++++++++++++++ include/asm-x86_64/alternative.h | 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

From: Martin Schwidefsky <schwidefsky@de.ibm.com> From: Hubertus Franke <frankeh@watson.ibm.com> From: Himanshu Raj <rhim@cc.gatech.edu> [patch 9/9] Guest page hinting: full s390 support. s390 uses the milli-coded ESSA instruction to set the page state. The page state is formed by four guest page states called block usage states and three host page states called block content

From: Martin Schwidefsky <schwidefsky@de.ibm.com> From: Hubertus Franke <frankeh@watson.ibm.com> From: Himanshu Raj <rhim@cc.gatech.edu> [patch 9/9] Guest page hinting: full s390 support. s390 uses the milli-coded ESSA instruction to set the page state. The page state is formed by four guest page states called block usage states and three host page states called block content

On Sat 18-06-16 03:09:02, Michael S. Tsirkin wrote: > On Fri, Jun 17, 2016 at 11:00:17AM +0200, Michal Hocko wrote: [...] > > It seems that vhost usage would suffer from this problem because > > it reads from the userspace to get (status) flags and makes some > > decisions based on the read value. I do not understand the code so I > > couldn't evaluate whether that

On Sat 18-06-16 03:09:02, Michael S. Tsirkin wrote: > On Fri, Jun 17, 2016 at 11:00:17AM +0200, Michal Hocko wrote: [...] > > It seems that vhost usage would suffer from this problem because > > it reads from the userspace to get (status) flags and makes some > > decisions based on the read value. I do not understand the code so I > > couldn't evaluate whether that

Hi, I want to run a i386 domU on my AMD64. I created a LVM partition with Debian Sarge i386 on it, and set everything up. Now for the compilation of the kernel for i386. In "linux-2.6.12-xenU/" , make ARCH=xen menuconfig, i did: Processor Type (X86) (which was selected, and compiled with X86_64 before) Processor family (Opteron/Athlon64/Hammer/K8) [*] Generic x86 support if

Hi, I want to run a i386 domU on my AMD64. I created a LVM partition with Debian Sarge i386 on it, and set everything up. Now for the compilation of the kernel for i386. In "linux-2.6.12-xenU/" , make ARCH=xen menuconfig, i did: Processor Type (X86) (which was selected, and compiled with X86_64 before) Processor family (Opteron/Athlon64/Hammer/K8) [*] Generic x86 support if