linux.git/include/asm-s390/cpcmd.h, branch master Linux kernel source tree [S390] move include/asm-s390 to arch/s390/include/asm 2008-08-01T18:42:05+00:00 Martin Schwidefsky schwidefsky@de.ibm.com 2008-08-01T18:42:05+00:00 c6557e7f2b6ae76a44653d38f835174074c42e05 Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com> 
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
[S390] cpcmd <-> __cpcmd calling issues 2006-12-04T14:40:30+00:00 Heiko Carstens heiko.carstens@de.ibm.com 2006-12-04T14:40:30+00:00 740b5706b9c4b3767f597b3ea76654c6f2a800b2 In case of reipl cpcmd gets called when all other cpus are not running anymore. To prevent deadlocks change __cpcmd so that it doesn't take any locks and call cpcmd or __cpcmd, whatever is correct in the current context. Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com> 
In case of reipl cpcmd gets called when all other cpus are not running
anymore. To prevent deadlocks change __cpcmd so that it doesn't take
any locks and call cpcmd or __cpcmd, whatever is correct in the current
context.

Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
[PATCH] s390: add vmcp interface 2005-06-25T23:24:37+00:00 Christian Borntraeger cborntra@de.ibm.com 2005-06-25T21:55:32+00:00 6b979de395c7e1b7e59f74a870e1d1911853eccb Add interface to issue VM control program commands. Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org> 
Add interface to issue VM control program commands.

Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Linux-2.6.12-rc2 2005-04-16T22:20:36+00:00 Linus Torvalds torvalds@ppc970.osdl.org 2005-04-16T22:20:36+00:00 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip! 
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!