qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
Cc: Benjamin Herrenschmidt <benh@au1.ibm.com>,
	"aik@ozlabs.ru" <aik@ozlabs.ru>,
	Tyrel Datwyler <turtle.in.the.kernel@gmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
	Anton Blanchard <anton@samba.org>
Subject: Re: [Qemu-devel] [PATCH v5] ppc: spapr-rtas - implement os-term rtas call
Date: Mon, 30 Jun 2014 14:05:34 +0200	[thread overview]
Message-ID: <53B1528E.8060407@suse.de> (raw)
In-Reply-To: <87oaxawxy7.fsf@abhimanyu.in.ibm.com>


On 30.06.14 11:25, Nikunj A Dadhania wrote:
> Alexander Graf <agraf@suse.de> writes:
>
>>> Am 30.06.2014 um 10:35 schrieb Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>:
>>>
>>> +static void rtas_ibm_os_term(PowerPCCPU *cpu,
>>> +                            sPAPREnvironment *spapr,
>>> +                            uint32_t token, uint32_t nargs,
>>> +                            target_ulong args,
>>> +                            uint32_t nret, target_ulong rets)
>>> +{
>>> +    target_ulong ret = 0;
>>> +
>>> +    qapi_event_send_guest_panicked(GUEST_PANIC_ACTION_PAUSE, &error_abort);
>> The guest doesn't pause.
> I see the event reaching libvirt and a dump taken and the guest
> restarts.
>
>> Since the guest will call os-term in a loop, this will also flood the
>> event listener with lots and lots of panic messages.
> 	do {
> 		status = rtas_call(rtas_token("ibm,os-term"), 1, 1, NULL,
> 				   __pa(rtas_os_term_buf));
> 	} while (rtas_busy_delay(status));
>
> So when status from the rtas call is success, the loop should exit.
>
> Am I missing something?

No, I think you're right. I'll queue it for 2.2.


Alex

  reply	other threads:[~2014-06-30 12:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30  8:35 [Qemu-devel] [PATCH v5] ppc: spapr-rtas - implement os-term rtas call Nikunj A Dadhania
2014-06-30  9:11 ` Alexander Graf
2014-06-30  9:25   ` Nikunj A Dadhania
2014-06-30 12:05     ` Alexander Graf [this message]
2014-06-30 15:49 ` Tyrel Datwyler
2014-06-30 16:24   ` Alexander Graf
2014-07-01  3:20     ` Nikunj A Dadhania
2014-07-01  5:10       ` Alexander Graf
2014-07-03  3:41 ` Alexey Kardashevskiy
2014-07-03  3:48   ` Alexey Kardashevskiy
2014-07-03  5:27   ` Nikunj A Dadhania

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=53B1528E.8060407@suse.de \
    --to=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=anton@samba.org \
    --cc=benh@au1.ibm.com \
    --cc=nikunj@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=turtle.in.the.kernel@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).