RE: [Xen-users] xen-patches-2.6.31-11.tar.bz2

[Mike Viau <viaum@xxxxxxxxxxxxxxx>]

Thanks for clearing that patching step up.

Do you think you could share a copy of you kernel .config file?

I have been trying to extract the kernel configuration from openSUSE's kernel

kernel-xen-2.6.31.12-0.1.1.x86_64.rpm

I am running a Debian system so I am currently working through the differences in the distributions package management systems.

---

--- On Mon, 2/22/10, Boris <bderzhavets@xxxxxxxxx> wrote:

root@ServerKoala:/usr/src/build/linux-2.6.31.12# cat apply
#!/bin/bash
for P in `ls ../xen-patches-2.6.31-11/6*.patch1 | sort `
do
patch -p1 -s -i $P
if [ $? = 0 ]; then
echo $P applied
else
echo "Error processing "$P
exit 1
fi
done

Now run:-

root@ServerKoala:/usr/src/build/linux-2.6.31.12# ./apply
../xen-patches-2.6.31-11/60000_add-console-use-vt.patch1 applied
../xen-patches-2.6.31-11/60001_linux-2.6.19-rc1-kexec-move_segment_code-i386.patch1 applied
../xen-patches-2.6.31-11/60002_linux-2.6.19-rc1-kexec-move_segment_code-x86_64.patch1 applied
../xen-patches-2.6.31-11/60003_ipv6-no-autoconf.patch1 applied
../xen-patches-2.6.31-11/60004_pci-guestdev.patch1 applied
../xen-patches-2.6.31-11/60005_pci-reserve.patch1 applied
../xen-patches-2.6.31-11/60006_sfc-driverlink.patch1 applied
../xen-patches-2.6.31-11/60007_sfc-resource-driver.patch1 applied
../xen-patches-2.6.31-11/60008_sfc-driverlink-conditional.patch1 applied
../xen-patches-2.6.31-11/60009_sfc-external-sram.patch1 applied
../xen-patches-2.6.31-11/60010_xen3-auto-xen-arch.patch1 applied
../xen-patches-2.6.31-11/60011_xen3-auto-xen-drivers.patch1 applied
../xen-patches-2.6.31-11/60012_xen3-auto-include-xen-interface.patch1 applied
../xen-patches-2.6.31-11/60013_xen3-auto-xen-kconfig.patch1 applied
../xen-patches-2.6.31-11/60014_xen3-auto-common.patch1 applied
../xen-patches-2.6.31-11/60015_xen3-auto-arch-x86.patch1 applied
../xen-patches-2.6.31-11/60016_xen3-auto-arch-i386.patch1 applied
../xen-patches-2.6.31-11/60017_xen3-auto-arch-x86_64.patch1 applied
../xen-patches-2.6.31-11/60018_xen3-fixup-xen.patch1 applied
../xen-patches-2.6.31-11/60019_sfc-sync-headers.patch1 applied
../xen-patches-2.6.31-11/60020_sfc-endianness.patch1 applied
../xen-patches-2.6.31-11/60021_941-xenbus-transaction-mutex.patch1 applied
../xen-patches-2.6.31-11/60022_945-MSI-disable-check.patch1 applied
../xen-patches-2.6.31-11/60023_958-fbfront-resume.patch1 applied
../xen-patches-2.6.31-11/60024_959-netback-delayed-copy-cleanup.patch1 applied
../xen-patches-2.6.31-11/60025_983-blkfront-forced-detach.patch1 applied
../xen-patches-2.6.31-11/60026_986-blkback-flush-on-connect.patch1 applied
../xen-patches-2.6.31-11/60027_989-balloon-hvm-bias.patch1 applied
../xen-patches-2.6.31-11/60028_xen3-fixup-kconfig.patch1 applied
../xen-patches-2.6.31-11/60029_xen3-fixup-common.patch1 applied
../xen-patches-2.6.31-11/60030_xen3-fixup-arch-x86.patch1 applied
../xen-patches-2.6.31-11/60031_xen3-patch-2.6.18.patch1 applied
../xen-patches-2.6.31-11/60032_xen3-patch-2.6.19.patch1 applied
../xen-patches-2.6.31-11/60033_xen3-patch-2.6.20.patch1 applied
../xen-patches-2.6.31-11/60034_xen3-patch-2.6.21.patch1 applied
../xen-patches-2.6.31-11/60035_xen3-patch-2.6.22.patch1 applied
../xen-patches-2.6.31-11/60036_xen3-patch-2.6.23.patch1 applied
../xen-patches-2.6.31-11/60037_xen3-patch-2.6.24.patch1 applied
../xen-patches-2.6.31-11/60038_xen3-patch-2.6.25.patch1 applied
../xen-patches-2.6.31-11/60039_xen3-patch-2.6.26.patch1 applied
../xen-patches-2.6.31-11/60040_xen3-patch-2.6.27.patch1 applied
../xen-patches-2.6.31-11/60041_xen3-patch-2.6.28.patch1 applied
../xen-patches-2.6.31-11/60042_xen3-patch-2.6.29.patch1 applied
../xen-patches-2.6.31-11/60043_xen3-patch-2.6.30.patch1 applied
../xen-patches-2.6.31-11/60044_xen3-patch-2.6.31.patch1 applied
../xen-patches-2.6.31-11/60045_xen3-patch-2.6.31.1.patch1 applied
../xen-patches-2.6.31-11/60046_xen3-patch-2.6.31.1-2.patch1 applied
../xen-patches-2.6.31-11/60047_xen3-patch-2.6.31.3-4.patch1 applied
../xen-patches-2.6.31-11/60048_xen3-patch-2.6.31.5-6.patch1 applied
../xen-patches-2.6.31-11/60049_xen3-patch-2.6.31.8-9.patch1 applied
../xen-patches-2.6.31-11/60050_xen3-patch-2.6.31.9-10.patch1 applied
../xen-patches-2.6.31-11/60051_xen-balloon-max-target.patch1 applied
../xen-patches-2.6.31-11/60052_xen-blkback-cdrom.patch1 applied
../xen-patches-2.6.31-11/60053_xen-blktap-write-barriers.patch1 applied
../xen-patches-2.6.31-11/60054_xen-op-packet.patch1 applied
../xen-patches-2.6.31-11/60055_xen-blkfront-cdrom.patch1 applied
../xen-patches-2.6.31-11/60056_xen-sections.patch1 applied
../xen-patches-2.6.31-11/60057_xen-kconfig-compat.patch1 applied
../xen-patches-2.6.31-11/60058_xen-cpufreq-report.patch1 applied
../xen-patches-2.6.31-11/60059_xen-staging-build.patch1 applied
../xen-patches-2.6.31-11/60060_xen-sysdev-suspend.patch1 applied
../xen-patches-2.6.31-11/60061_xen-ipi-per-cpu-irq.patch1 applied
../xen-patches-2.6.31-11/60062_xen-virq-per-cpu-irq.patch1 applied
../xen-patches-2.6.31-11/60063_xen-configurable-guest-devices.patch1 applied
../xen-patches-2.6.31-11/60064_xen-netback-nr-irqs.patch1 applied
../xen-patches-2.6.31-11/60065_xen-netback-notify-multi.patch1 applied
../xen-patches-2.6.31-11/60066_xen-vmalloc_32.patch1 applied
../xen-patches-2.6.31-11/60067_xen-x86-panic-no-reboot.patch1 applied
../xen-patches-2.6.31-11/60068_xen-x86-dcr-fallback.patch1 applied
../xen-patches-2.6.31-11/60069_xen-x86-consistent-nmi.patch1 applied
../xen-patches-2.6.31-11/60070_xen-x86-no-lapic.patch1 applied
../xen-patches-2.6.31-11/60071_xen-x86-pmd-handling.patch1 applied
../xen-patches-2.6.31-11/60072_xen-x86-bigmem.patch1 applied
../xen-patches-2.6.31-11/60073_xen-x86-machphys-prediction.patch1 applied
../xen-patches-2.6.31-11/60074_xen-x86-exit-mmap.patch1 applied
../xen-patches-2.6.31-11/60075_xen-x86-per-cpu-vcpu-info.patch1 applied
../xen-patches-2.6.31-11/60076_xen-x86_64-pgd-pin.patch1 applied
../xen-patches-2.6.31-11/60077_xen-x86_64-pgd-alloc-order.patch1 applied
../xen-patches-2.6.31-11/60078_xen-x86_64-dump-user-pgt.patch1 applied
../xen-patches-2.6.31-11/60079_xen-x86_64-note-init-p2m.patch1 applied

Boris.
--- On Mon, 2/22/10, Mike Viau <viaum@xxxxxxxxxxxxxxx> wrote:

From: Mike Viau <viaum@xxxxxxxxxxxxxxx>
Subject: [Xen-users] xen-patches-2.6.31-11.tar.bz2
To: andrew.lyon@xxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Date: Monday, February 22, 2010, 12:22 PM

Hello,

I was attempting to apply the xen patches to 2.6.31.12 kernel source with this script:


#!/bin/bash
for P in `ls ../xen-patches-2.6.31-11/6*.patch1 | sort `
do
patch -p1 -s -i $P
if [ $? = 0 ]; then
echo $P applied
else
echo "Error processing "$P
exit 1
fi
done


During execution (while in the top level directory of the kernel source) I was presented with:


root@localhost:/usr/local/src/linux-2.6.31.12-xen# sh xen-patching.sh
The text leading up to this was:
--------------------------
|Subject: add console_use_vt
|From: kraxel@xxxxxxx
|Patch-mainline: no
|
|$subject says all
|
|---
| drivers/char/tty_io.c   |    7 ++++++-
| include/linux/console.h |    1 +
| 2 files changed, 7 insertions(+), 1 deletion(-)
|
|--- head-2009-10-06.orig/drivers/char/tty_io.c 2009-10-06 14:51:58.000000000 +0200
|+++ head-2009-10-06/drivers/char/tty_io.c      2009-10-06 14:55:34.000000000 +0200
--------------------------
File to patch:


>> I was wondering what information I should provide on the console after the  "File to patch:" line?

Thanks.

 
-M

---

Windows® phone-your Windows stuff, on the go. See more.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users