linux.git/drivers/s390/block/dasd_devmap.c, branch v2.6.29

[S390] dasd: bus_id -> dev_name() conversion.

2009-02-11T09:37:40+00:00

bus_id usage crept in again; fix it.

Signed-off-by: Cornelia Huck 
Signed-off-by: Heiko Carstens

[S390] dasd: add device attribute to disable blocking on lost paths

2009-01-09T11:15:05+00:00

When the connection between host and storage server is lost, the
dasd device driver usually blocks all I/O on affected devices and
waits for them to reappear. In some setups however it would be
better if the I/O is returned as error so that device can be
recovered by some other means, eg. in a raid or multipath setup.

Signed-off-by: Holger Smolinski 
Signed-off-by: Stefan Weinhuber 
Signed-off-by: Martin Schwidefsky

[S390] struct device - replace bus_id with dev_name(), dev_set_name()

2008-12-25T12:39:03+00:00

Acked-by: Cornelia Huck 
Acked-by: Greg Kroah-Hartman 
Signed-off-by: Kay Sievers 
Signed-off-by: Heiko Carstens 
Signed-off-by: Martin Schwidefsky

[S390] dasd: Use accessors instead of using driver_data directly.

2008-12-25T12:39:01+00:00

Signed-off-by: Cornelia Huck 
Signed-off-by: Martin Schwidefsky

[S390] bus_id -> dev_name conversions

2008-10-10T19:33:49+00:00

bus_id -> dev_name() conversions in s390 code.

[cornelia.huck@de.ibm.com: minor adaptions]
Signed-off-by: Kay Sievers 
Cc: Cornelia Huck 
Signed-off-by: Greg Kroah-Hartman 
Signed-off-by: Martin Schwidefsky

[S390] dasd: Add support for enhanced VM UID

2008-08-01T14:39:29+00:00

When z/VM provides two virtual devices (minidisks) that reside on the
same real device, both will receive the configuration data from the
real device and thus get the same uid. To fix this problem, z/VM
provides an additional configuration data record that allows to
distinguish between minidisks.
z/VM APAR VM64273 needs be installed so this fix has an effect.

Signed-off-by: Stefan Weinhuber 
Signed-off-by: Martin Schwidefsky

[S390] dasd: Use const in busid functions.

2008-05-15T14:52:39+00:00

We should use 'const char *' in the busid functions since the
strings are not modified anyway.

Signed-off-by: Cornelia Huck 
Signed-off-by: Martin Schwidefsky

[S390] dasd: add hyper PAV support to DASD device driver, part 1

2008-01-26T13:11:28+00:00

Parallel access volumes (PAV) is a storage server feature, that allows
to start multiple channel programs on the same DASD in parallel. It
defines alias devices which can be used as alternative paths to the
same disk. With the old base PAV support we only needed rudimentary
functionality in the DASD device driver. As the mapping between base
and alias devices was static, we just had to export an identifier
(uid) and could leave the combining of devices to external layers
like a device mapper multipath.
Now hyper PAV removes the requirement to dedicate alias devices to
specific base devices. Instead each alias devices can be combined with
multiple base device on a per request basis. This requires full
support by the DASD device driver as now each channel program itself
has to identify the target base device.
The changes to the dasd device driver and the ECKD discipline are:
- Separate subchannel device representation (dasd_device) from block
  device representation (dasd_block). Only base devices are block
  devices.
- Gather information about base and alias devices and possible
  combinations.
- For each request decide which dasd_device should be used (base or
  alias) and build specific channel program.
- Support summary unit checks, which allow the storage server to
  upgrade / downgrade between base and hyper PAV at runtime (support
  is mandatory).

Signed-off-by: Stefan Weinhuber 
Signed-off-by: Martin Schwidefsky

mm: Remove slab destructors from kmem_cache_create().

2007-07-20T01:11:58+00:00

Slab destructors were no longer supported after Christoph's
c59def9f222d44bb7e2f0a559f2906191a0862d7 change. They've been
BUGs for both slab and slub, and slob never supported them
either.

This rips out support for the dtor pointer from kmem_cache_create()
completely and fixes up every single callsite in the kernel (there were
about 224, not including the slab allocator definitions themselves,
or the documentation references).

Signed-off-by: Paul Mundt

[S390] dasd: Add ipldev parameter.

2007-04-27T14:01:44+00:00

Specifying 'ipldev' in the dasd= kernel parameter will automatically
activate the boot device for use by the dasd driver.

Signed-off-by: Peter Oberparleiter 
Signed-off-by: Heiko Carstens 
Signed-off-by: Martin Schwidefsky