X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=drivers%2Fs390%2FKconfig;h=96413c2cd1ade4b02137a29f664ac1d82f030914;hb=6a77f38946aaee1cd85eeec6cf4229b204c15071;hp=e190f21ed2ee9b143b7cf19b7eaa24bca01522df;hpb=87fc8d1bb10cd459024a742c6a10961fefcef18f;p=linux-2.6.git diff --git a/drivers/s390/Kconfig b/drivers/s390/Kconfig index e190f21ed..96413c2cd 100644 --- a/drivers/s390/Kconfig +++ b/drivers/s390/Kconfig @@ -51,6 +51,8 @@ config UNIX98_PTY_COUNT When not in use, each additional set of 256 PTYs occupy approximately 8 KB of kernel memory on 32-bit architectures. +source "drivers/char/watchdog/Kconfig" + comment "S/390 character device drivers" config TN3270 @@ -160,7 +162,7 @@ config S390_TAPE_BLOCK devices using the block device interface. This interface is similar to CD-ROM devices on other platforms. The tapes can only be accessed read-only when using this interface. Have a look at - Documentation/s390/TAPE for further information about creating + for further information about creating volumes for and using this interface. It is safe to say "Y" here. comment "S/390 tape hardware support" @@ -174,6 +176,23 @@ config S390_TAPE_34XX tape subsystems and 100% compatibles. It is safe to say "Y" here. + + +config VMLOGRDR + tristate "Support for the z/VM recording system services (VM only)" + depends on IUCV + help + Select this option if you want to be able to receive records collected + by the z/VM recording system services, eg. from *LOGREC, *ACCOUNT or + *SYMPTOM. + This driver depends on the IUCV support driver. + +config MONREADER + tristate "API for reading z/VM monitor service records" + depends on IUCV + help + Character device driver for reading z/VM monitor service records + endmenu menu "Cryptographic devices"