search for: 2.6.16

Isolate some of the non-VMI timer related changes in Linux. This patch moves the cyc_2_ns conversion code into a common location, eliminating redundant code in hpet and tsc timer implementations, and introduces some macros that may be redefined by the sub-architecture to avoid dependence on APIC routing, CMOS time sync, and testing for broken time hardware (which presumably, does not happen in a

Isolate some of the non-VMI timer related changes in Linux. This patch moves the cyc_2_ns conversion code into a common location, eliminating redundant code in hpet and tsc timer implementations, and introduces some macros that may be redefined by the sub-architecture to avoid dependence on APIC routing, CMOS time sync, and testing for broken time hardware (which presumably, does not happen in a

This patch removes disk heartbeat's modularity which makes it the default. Without this patch, userspace changes are required. This patch is not intended for permanent application, just to make it easier for users not interested in testing the userspace clustering implementation to use ocfs2. In order to switch to user clustering, use "o2cb offline" to shut down the cluster,

MMU code movement. Unfortunately, this one is a little bit more complicated than the rest. We have to override the default accessors that directly write to page table entries. Because of the 2/3-level PAE split in Linux, this turned out to be really ugly at first, but by allowing the sub-arch layer to override the definitions and keeping the native definitions in place, the code becomes much

MMU code movement. Unfortunately, this one is a little bit more complicated than the rest. We have to override the default accessors that directly write to page table entries. Because of the 2/3-level PAE split in Linux, this turned out to be really ugly at first, but by allowing the sub-arch layer to override the definitions and keeping the native definitions in place, the code becomes much

Processing commands for control@bugs.debian.org: > severity 384638 important Bug#384638: Dom0 dows not boot with kernel package linux-image-2.6.16-2-xen-686 version 2.6.16-18 Severity set to `important' from `critical' > reassign 384638 xen-3.0 Bug#384638: Dom0 dows not boot with kernel package linux-image-2.6.16-2-xen-686 version 2.6.16-18 Bug reassigned from package

A NO_IDLE_HZ implementation is provided for i386 VMI builds. When a VCPU enters its idle loop, it disables its periodic alarm and sets up a one shot alarm for the next time event. That way, it does not become ready to run just to service the periodic alarm interrupt. Instead, it can remain halted until there is some real work pending for it. This allows the hypervisor to use the physical

A NO_IDLE_HZ implementation is provided for i386 VMI builds. When a VCPU enters its idle loop, it disables its periodic alarm and sets up a one shot alarm for the next time event. That way, it does not become ready to run just to service the periodic alarm interrupt. Instead, it can remain halted until there is some real work pending for it. This allows the hypervisor to use the physical

This is a really long email...my apologies. Hardware platform: Dell Poweredge 1855 (blade), Dual Xeon 2.8 GHz; 12 MB RAM; PERC 4/IM; mirrored 73 GB U320 SCSI; qLogic 2312 PCI Fibre Channel HBAs. OS: (currently) CentOS 4.3, gcc 3.4.5 Software: Xen 3.0.2-2 Attempting to boot off local SCSI RAID (mirror)...not the SAN. I am more of a Solaris person, so forgive me if I don''t know all

Hi, I''m getting a kernel panic when booting a Dell PowerEdge 1850 with kernel 2.6.16-xen3_86.1 which I installed from the xen-3.0-x86_32-rhel4.1.bin.tar package I got from XenSource. My /boot/grub/grub.conf configuration is this: title Xen (2.6.16-xen3_86.1) root (hd0,0) kernel /xen-3.gz com1=115200,8n1 noreboot module /vmlinuz-2.6.16-xen3_86.1_rhel4.1

Make the Linux kernel able to run at CPL 0, 1, or 2. There are a few limited places where CPL-0 is assumed, and they can be converted very efficiently into a supervisor CPL check instead of a CPL-0 check. This step prepares the kernel for running in direct execution under a hypervisor. Note the user_mode_vm macro used in ptrace.h is very similar to the flag mixing of EFLAGS and CS used to test

Make the Linux kernel able to run at CPL 0, 1, or 2. There are a few limited places where CPL-0 is assumed, and they can be converted very efficiently into a supervisor CPL check instead of a CPL-0 check. This step prepares the kernel for running in direct execution under a hypervisor. Note the user_mode_vm macro used in ptrace.h is very similar to the flag mixing of EFLAGS and CS used to test

Hello, Is there some things removed from the kernel.org kernels before the get into xen-unstable? I was just about to compile a new dom0 kernel, and couldn''t find the option for Buslogic SCSI driver i xen-unstable kernel synced earlier this morning. I find this a bit strange, as I know the option is there in kernel.org''s 2.6.16-rc2. The config option was somehow lost in 2.6.15

SMP bootstrapping support. Just as in the physical platform model, the BSP is responsible for initializing the AP state prior to execution. The dependence on lots of processor state information is a design choice of our implementation. Conceivably, this could be a hypercall that awakens the same start of day state on APs as on the BSP. It is likely the AP startup and the start-of-day model will

SMP bootstrapping support. Just as in the physical platform model, the BSP is responsible for initializing the AP state prior to execution. The dependence on lots of processor state information is a design choice of our implementation. Conceivably, this could be a hypercall that awakens the same start of day state on APs as on the BSP. It is likely the AP startup and the start-of-day model will

All, I am running xen3.0.2 and xen unstable on RHEL 4, and get this error when trying to boot Xen kernel(domain0) ...... Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempting to kill init! Then system reboot.In grub.conf,I have

All, I am running xen3.0.2 and xen unstable on RHEL 4, and get this error when trying to boot Xen kernel(domain0) ...... Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempting to kill init! Then system reboot.In grub.conf,I have

https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=444 Summary: REDIRECT not working in kernel 2.6.16-rc[12] as before (<= 2.6.15.x) Product: netfilter/iptables Version: linux-2.6.x Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: NAT

hallo, I've chanced packages and now I don't get the strange behaviour I noticed yesterday but a more common problem: kernel panic my grub stanza is: title Xen 3.0.2-1-i386 / Debian GNU/Linux, kernel 2.6.16-2-xen-k7 root (hd0,0) kernel /xen-3.0.2-1-i386.gz module /vmlinuz-2.6.16-2-xen-k7 root=/dev/hda2 ro console=tty0 savedefault and I consider it

Linker changes to add the VMI MACH_TEXT area into the kernel text section. This area layout is heavily influenced by magic to overlap exactly with the 32-byte VMI ROM entry points, allowing the kernel to copy the VMI ROM over the native section. As use of magic is on the decline, this approach is being phased out in favor of the more modern approach of the inline implementation. The translation