All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>,
	agraf@suse.de, qemu-devel <qemu-devel@nongnu.org>,
	qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] ppc64 not resuming with v2.3.0-rc3
Date: Thu, 16 Apr 2015 21:53:18 +0100	[thread overview]
Message-ID: <5530213E.7020704@ilande.co.uk> (raw)
In-Reply-To: <5530125A.8030408@linux.vnet.ibm.com>

On 16/04/15 20:49, Stefan Berger wrote:
>> Hmmmm the fix is correct in that internal MSR variables need to be
>> updated post-restore (as noted in the message above it was the exception
>> prefix variables that weren't updated by having MSR_EP set).
>>
>> Maybe on ppc64 there is another bit similar to MSR_TGPR that needs to be
>> excluded? Alex, any thoughts?
> 
> I want to add that I am running QEMU for ppc64 in emulation mode on a
> x86_64 host. The suspend/resume problem, while in SLOF, did not exist in
> QEMU v2.2, so I anticipate that this is a regression would also be
> visible on QEMU on kvm, though a simple test on such a machine may show
> different...
> 
> Removing the patch solves the problem while in SLOF. Once booting into
> Linux suspend/resume does not work - with qemu-system-ppc64 on x86_64
> host. Timestamps shown by Linux actually make a jump backwards and
> ultimately Linux hangs.

Just to clarify the terminology here, when you say suspend/resume are
you talking about a hardware suspend/resume or issuing a savevm/loadvm
sequence in the QEMU monitor? Are you able to provide further detail to
reproduce your test case?


ATB,

Mark.

  reply	other threads:[~2015-04-16 20:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 16:43 [Qemu-devel] ppc64 not resuming with v2.3.0-rc3 Stefan Berger
2015-04-16 19:42 ` Mark Cave-Ayland
2015-04-16 19:49   ` Stefan Berger
2015-04-16 20:53     ` Mark Cave-Ayland [this message]
2015-04-16 21:24       ` Stefan Berger
2015-04-16 21:53         ` Paolo Bonzini
2015-04-16 22:23           ` Mark Cave-Ayland

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=5530213E.7020704@ilande.co.uk \
    --to=mark.cave-ayland@ilande.co.uk \
    --cc=agraf@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=stefanb@linux.vnet.ibm.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 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.