s390/traps: do not test MONITOR CALL without CONFIG_BUG
[ Upstream commit b8e9cc20b8 ]
tinyconfig fails to boot, because without CONFIG_BUG report_bug()
always returns BUG_TRAP_TYPE_BUG, which causes mc 0,0 in
test_monitor_call() to panic. Fix by skipping the test without
CONFIG_BUG.
Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:
parent
9beba14699
commit
be10fff3a4
1 changed files with 2 additions and 0 deletions
|
|
@ -272,6 +272,8 @@ static void __init test_monitor_call(void)
|
|||
{
|
||||
int val = 1;
|
||||
|
||||
if (!IS_ENABLED(CONFIG_BUG))
|
||||
return;
|
||||
asm volatile(
|
||||
" mc 0,0\n"
|
||||
"0: xgr %0,%0\n"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue