From: Laurent Vivier <lvivier@redhat.com>
To: Greg Kurz <groug@kaod.org>
Cc: Thomas Huth <thuth@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>,
qemu-ppc@nongnu.org, Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, Andrea Arcangeli <aarcange@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] tests/postcopy: Use KVM on ppc64 only if it is KVM-HV
Date: Fri, 18 Nov 2016 14:03:44 +0100 [thread overview]
Message-ID: <bb3cf9ad-4e15-c0cd-cae9-f7b16640ba09@redhat.com> (raw)
In-Reply-To: <20161118135303.0b4f9006@bahia>
On 18/11/2016 13:53, Greg Kurz wrote:
> Hi Laurent,
Hi Greg,
> On Thu, 17 Nov 2016 21:22:33 +0100
> Laurent Vivier <lvivier@redhat.com> wrote:
>
>> On 16/11/2016 15:17, Greg Kurz wrote:
>>> On Wed, 16 Nov 2016 14:17:47 +0100
>>> Thomas Huth <thuth@redhat.com> wrote:
>>>
>>>> On 16.11.2016 13:37, Greg Kurz wrote:
>>>>> On Wed, 16 Nov 2016 12:24:50 +0000
>>>>> "Dr. David Alan Gilbert" <dgilbert@redhat.com> wrote:
>>>>>
>>>>>> * Greg Kurz (groug@kaod.org) wrote:
>>>>>>> On Wed, 16 Nov 2016 09:39:31 +0100
>>>>>>> Thomas Huth <thuth@redhat.com> wrote:
>>>>>>>
>>>>>>>> The ppc64 postcopy test does not work with KVM-PR, and it is also
>>>>>>>> causing annoying warning messages when run on a x86 host. So let's
>>>>>>>> use KVM here only if we know that we're running with KVM-HV (which
>>>>>>>> automatically also means that we're running on a ppc64 host), and
>>>>>>>> fall back to TCG otherwise.
>>>>>>>>
>> [..]
>>> The changes to the code look ok and I prefer to spend time chasing the
>>> KVM PR issue rather than arguing on a comment...
>>
>> For the problem itself, it seems to appear only after a
>> BOOK3S_INTERRUPT_SYSCALL interrupt for an KVM_EXIT_PAPR_HCALL
>> (H_PUT_TERM_CHAR). In this case, KVM has to exit to QEMU to manage the
>> output. The following interrupt is always an BOOK3S_INTERRUPT_PROGRAM
>> with an emulation failure.
>>
>
> Which specific problem are you referring to ?
..
> 2) "Unexpected 32 on dest_serial serial" accompanied by the following in dmesg
>
> [131613.428616] Couldn't emulate instruction 0x00000000 (op 0 xop 0)
> [131613.503515] kvmppc_handle_exit_pr: emulation at d8 failed (00000000)
This one, test running on a bare metal PowerMac G5 (F24), 4.9.0-rc5
kernel. And I have only and everytime this error.
Laurent
next prev parent reply other threads:[~2016-11-18 13:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 8:39 [Qemu-devel] [PATCH] tests/postcopy: Use KVM on ppc64 only if it is KVM-HV Thomas Huth
2016-11-16 9:19 ` Laurent Vivier
2016-11-16 9:43 ` Thomas Huth
2016-11-16 10:37 ` Laurent Vivier
2016-11-16 12:13 ` Greg Kurz
2016-11-16 12:24 ` Dr. David Alan Gilbert
2016-11-16 12:37 ` Greg Kurz
2016-11-16 13:17 ` Thomas Huth
2016-11-16 14:17 ` Greg Kurz
2016-11-17 20:22 ` Laurent Vivier
2016-11-18 12:53 ` Greg Kurz
2016-11-18 13:03 ` Laurent Vivier [this message]
2016-11-17 3:13 ` David Gibson
2016-11-16 14:18 ` Greg Kurz
2016-11-17 3:18 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2016-11-17 7:46 ` Laurent Vivier
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=bb3cf9ad-4e15-c0cd-cae9-f7b16640ba09@redhat.com \
--to=lvivier@redhat.com \
--cc=aarcange@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=stefanha@gmail.com \
--cc=thuth@redhat.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).