From: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
To: Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org, Anton Blanchard <anton@samba.org>
Cc: aik@au1.ibm.com, Benjamin Herrenschmidt <benh@au1.ibm.com>,
qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] ppc: spapr-rtas - implement os-term rtas call
Date: Thu, 26 Jun 2014 13:25:04 +0530 [thread overview]
Message-ID: <87simsw1ev.fsf@abhimanyu.in.ibm.com> (raw)
In-Reply-To: <53AAB335.1070608@suse.de>
Alexander Graf <agraf@suse.de> writes:
> On 25.06.14 13:27, Nikunj A Dadhania wrote:
>> Alexander Graf <agraf@suse.de> writes:
>>
>> Let me put down my understanding:
>>
>> There are two possible way to handle kernel panic:
>> 1) Kdump service running in guest - already working
>> 2) Pass the kernel panic information to hypervisor - not there in Qemu
>> pseries
>>
>> So without kdump service running, if linux kernel hits a panic, its going
>> to check os-term and extended-os-term, only then its going to call
>> os-term.
>
> It's checking both for a reason. Find that reason.
Here is what I figured out from PAPR:
rtas ibm,os-term, does not gaurantee a return back to the guest cpu.
If ibm,extended-os-term property is set rtas call return will always
occur.
Regards
Nikunj
next prev parent reply other threads:[~2014-06-26 7:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 12:09 [Qemu-devel] [PATCH v2] ppc: spapr-rtas - implement os-term rtas call Nikunj A Dadhania
2014-06-17 9:13 ` Alexander Graf
2014-06-17 9:30 ` Nikunj A Dadhania
2014-06-17 9:53 ` Alexander Graf
2014-06-17 9:59 ` Nikunj A Dadhania
2014-06-17 10:02 ` Alexander Graf
2014-06-17 10:19 ` Nikunj A Dadhania
2014-06-25 4:36 ` Nikunj A Dadhania
2014-06-25 11:03 ` Alexander Graf
2014-06-25 11:27 ` Nikunj A Dadhania
2014-06-25 11:32 ` Alexander Graf
2014-06-26 7:55 ` Nikunj A Dadhania [this message]
2014-06-26 8:04 ` Alexander Graf
2014-06-26 9:05 ` Nikunj A Dadhania
2014-06-26 9:22 ` Alexander Graf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87simsw1ev.fsf@abhimanyu.in.ibm.com \
--to=nikunj@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=aik@au1.ibm.com \
--cc=anton@samba.org \
--cc=benh@au1.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.