similar to: [PATCH] convert #include "linux/..." and #include "asm/..." to #include <...>

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

(untested) There are several files that #include "linux/file" not #include <linux/file> #include "asm/file" not #include <asm/file> Here's a little script that converts 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#

> > Hi, > > I'm running a 2.4.18-14 kernel with a heavy IO profile using > ext3 over RAID 0+1 volumes. > > From time to time I get a black screen stuck machine while > trying to umount a volume during an IO workload (as part of a > failback solution - but after killing all IO processes ), > with ping still responding, but everything else mostly dead. >

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

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

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

In-Reply-To: <20060803002518.190834642@xensource.com> On Wed, 02 Aug 2006 17:25:13 -0700, Jeremy Fitzhardinge wrote: > We allow for the fact that the guest kernel may not run in ring 0. > This requires some abstraction in a few places when setting %cs or > checking privilege level (user vs kernel). I made some changes: a. Added some comments about the SEGMENT_IS_*_CODE() macros.

In-Reply-To: <20060803002518.190834642@xensource.com> On Wed, 02 Aug 2006 17:25:13 -0700, Jeremy Fitzhardinge wrote: > We allow for the fact that the guest kernel may not run in ring 0. > This requires some abstraction in a few places when setting %cs or > checking privilege level (user vs kernel). I made some changes: a. Added some comments about the SEGMENT_IS_*_CODE() macros.

Hi ! Compiling kernel linux 2.4.10pre4 without ext3 works. After patching the kernel sources with cd /usr/src/ext3 scripts/add-to-kernel.sh scripts/file-manifest linux compile fails: gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -DEXPORT_SYMTAB -c

IA-32 linear address translation is loads of fun. While cleaning up the LDT code, I noticed that kprobes code was very bogus with respect to segment handling. Many, many bugs are fixed here. I chose to combine the three separate functions that try to do linear address conversion into one, nice and working functions. All of the versions had bugs. 1) Taking an int3 from v8086 mode could cause

IA-32 linear address translation is loads of fun. While cleaning up the LDT code, I noticed that kprobes code was very bogus with respect to segment handling. Many, many bugs are fixed here. I chose to combine the three separate functions that try to do linear address conversion into one, nice and working functions. All of the versions had bugs. 1) Taking an int3 from v8086 mode could cause

OK, I''ve been fritzing around with something I noticed last night, thinking that I understood what was going on, but now it''s getting confusing again. A system that has been running for a couple of months had a hole in the probe ID list near the end in the middle of the fbt probes. And then a couple of syscall probes were stuck in the hole. It looked like this: ... 40311

Well I decided that 2am on a thursday night would be a good time to try this and I've hit a wall... most of the other errors were pretty easy to fix. I just don't understand this one: --snip--snip--snip-- gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -D__linux__ -pipe -fno-strength-reduce

Hi, I've tried to compile an ext3 extended 2.4.5 kernel but I got no luck. After applying the ext3 patch from the gkernel/ext3 (download today) (symlinks are created) I run into following problem: gcc -D__KERNEL__ -I/usr/local/src/kernel/linux-2.4.5-ext3cvs/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686 -DEXPORT_SYMTAB -c ksyms.c

Hi Ext3! I'm running about 30 dedicated MySQL machines under quite decent loads, and they are occassionally crashing. I've been logging console messages recently in an effort to find the cause, and some appear to be related to I perused your lists and found the message I'm replying to. If you don't mind, I've included messages and ksymoops from two crashes that I had