linux-toradex.git/arch/s390/kernel/setup.c, branch v3.10.61

s390: add support for IBM zBC12 machine

2013-08-12T01:35:25+00:00

commit 594712276e737961d30e11eae80d403b2b3815df upstream.

Just add the new model number where appropiate.

Signed-off-by: Heiko Carstens 
Signed-off-by: Martin Schwidefsky 
Signed-off-by: Greg Kroah-Hartman

s390/mem_detect: remove artificial kdump memory types

2013-05-03T12:21:15+00:00

Simplify the memory detection code a bit by removing the CHUNK_OLDMEM
and CHUNK_CRASHK memory types.
They are not needed. Everything that is needed is a mechanism to
insert holes into the detected memory.

Reviewed-by: Michael Holzheu 
Signed-off-by: Heiko Carstens 
Signed-off-by: Martin Schwidefsky

s390/mem_detect: limit memory detection loop to "mem=" parameter

2013-05-02T13:50:26+00:00

The current memory detection loop will detect all present memory of
a machine. This is true even if the user specified the "mem=" parameter
on the kernel command line.
This can be a problem since the memory detection may cause a fully
populated host page table for the guest, even for those parts of the
memory that the guest will never use afterwards.

So fix this and only detect memory up to a user supplied "mem=" limit
if specified.

Reported-by: Michael Johanssen 
Reviewed-by: Michael Holzheu 
Signed-off-by: Heiko Carstens 
Signed-off-by: Martin Schwidefsky

s390/kdump,bootmem: fix bootmem allocator bitmap size

2013-05-02T13:50:25+00:00

When in kdump mode the kernel may access only the first couple of
megabytes for execution, the rest contains the dump. However
the size of the bitmap used by the bootmem allocator was calculated
for the whole amount of memory of the machine.

For very large machines this can lead to the situation that the kdump
kernel will not come up because not enough memory is available.

So fix this and calculate the size of the bitmap only for the piece
of memory that the kdump kernel actually uses.

Call reserve_oldmem() before setup_memory_end() so that the memory_chunk
array already has been updated with respect to oldmem chunks.
Afterwards setup_memory_end() will ignore those chunks.

Reviewed-by: Michael Holzheu 
Signed-off-by: Heiko Carstens 
Signed-off-by: Martin Schwidefsky

s390: get rid of odd global real_memory_size

2013-05-02T13:50:25+00:00

The variable real_memory_size has odd semantics and has been used in
a broken way by e.g. the old kvm code.
Therefore get rid of it before anybody else makes use of it.

Reviewed-by: Michael Holzheu 
Signed-off-by: Heiko Carstens 
Signed-off-by: Martin Schwidefsky

s390/zfcpdump: exploit new cio_ignore keywords

2013-05-02T13:50:21+00:00

Use the 'ipldev' and 'condev' cio_ignore keywords to setup the
command line for zfcpdump.

Reviewed-by: Michael Holzheu 
Signed-off-by: Sebastian Ott 
Signed-off-by: Martin Schwidefsky

s390: lowcore stack pointer offsets

2013-04-26T07:07:01+00:00

Store the stack pointers in the lowcore for the kernel stack, the async
stack and the panic stack with the offset required for the first user.
This avoids an unnecessary add instruction on the system call path.

Signed-off-by: Martin Schwidefsky

s390/mm: fix vmemmap size calculation

2013-03-05T09:21:35+00:00

The size of the vmemmap must be a multiple of PAGES_PER_SECTION, since the
common code always initializes the vmemmap in such pieces.
So we must round up in order to not have a too small vmemmap.

Fixes an IPL crash on 31 bit with more than 1920MB.

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

s390/pm: export pm_power_off

2013-01-08T09:57:09+00:00

Export pm_power_off symbol. Needed by at least one of the new device
drivers that come with CONFIG_PCI.
And all other architectures export that symbol as well.

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

s390: add zEC12 code generation support

2012-11-23T10:14:31+00:00

Allow to generate code that only runs on zEC12 machines.

Also add a check which prevents the kernel to run on machines which
do not have any of the following new facilities installed:

- (48) decimal-floating-point zoned-conversion
- (49) execution-hint
- (49) load-and-trap
- (49) miscellaneous-instruction-extensions
- (49) processor-assist
- (50) constrained transactional-execution
- (73) transactional-execution

48, 49, 50 and 73 are the bit numbers of the facility indications for
each of the required facilities.

Note that we assume that user-space gets compiled with the same
compiler options, therefore we also test for a dfp facility even
if the kernel doesn't make use of it.

Signed-off-by: Heiko Carstens