[PATCH RFC] module-setup.sh: install usb serial driver for ttyUSB0
by Dave Young
In case one want to use usb serial console, we need to pack the usb serial
driver into kdump initramfs so that one can see the console output on the usb
console.
I only handled ttyUSB0, this is like a hard code, but it should be enough for
most cases. Also only install the driver for the ttyUSB0 device.
Tested with adding "console=ttyUSB0" in 2nd kernel commandline.
Tested latest F22 kernel, there's CONFIG_USB_SERIAL_CONSOLE=y, kdump work ok.
Signed-off-by: Dave Young <dyoung(a)redhat.com>
---
dracut-module-setup.sh | 8 ++++++++
1 file changed, 8 insertions(+)
--- kexec-tools.orig/dracut-module-setup.sh
+++ kexec-tools/dracut-module-setup.sh
@@ -626,4 +626,12 @@ installkernel() {
[ "$wdt" = "iTCO_wdt" ] && instmods lpc_ich
instmods $wdt
fi
+
+ if [ -c /dev/ttyUSB0 ]; then
+ _majmin=$(get_maj_min /dev/ttyUSB0)
+
+ _driver=$(readlink /sys/dev/char/$_majmin/device/driver)
+ _driver=$(basename $_driver)
+ instmods $_driver
+ fi
}
7 years
[PATCH] kexec-kdump-howto: Add the description of parallel dump's limitation.
by Zhou Wenjian
In the current implementation, parallel dump won't perform well in
--num-threads 1 or -d 31. So this patch add the description of it.
Signed-off-by: Zhou Wenjian <zhouwj-fnst(a)cn.fujitsu.com>
---
kexec-kdump-howto.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/kexec-kdump-howto.txt b/kexec-kdump-howto.txt
index b4cdc22..00ab96b 100644
--- a/kexec-kdump-howto.txt
+++ b/kexec-kdump-howto.txt
@@ -627,6 +627,9 @@ For example:
1 has better performance than 2, if THREAD_NUM is larger than two
and the usable cpus number is larger than THREAD_NUM.
+Limitation: Parallel feature will introduce extra costs to each page(including
+filtered page). So it will always have worse performance when the THREAD_NUM
+is 1 or -d 31 is specified.
Notes on how to use multiple cpus on a capture kernel on x86 system:
--
1.8.3.1
7 years, 4 months
