From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:34098)
by lists.gnu.org with esmtp (Exim 4.71)
(envelope-from
) id 1YqGuR-0004Ge-PH
for qemu-devel@nongnu.org; Thu, 07 May 2015 04:11:56 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
(envelope-from ) id 1YqGuL-0001cf-1z
for qemu-devel@nongnu.org; Thu, 07 May 2015 04:11:55 -0400
Received: from mailout1.w1.samsung.com ([210.118.77.11]:8943)
by eggs.gnu.org with esmtp (Exim 4.71)
(envelope-from ) id 1YqGuK-0001bx-T3
for qemu-devel@nongnu.org; Thu, 07 May 2015 04:11:49 -0400
Received: from eucpsbgm2.samsung.com (unknown [203.254.199.245])
by mailout1.w1.samsung.com
(Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5
2014)) with ESMTP id <0NNZ00L2B03LZY90@mailout1.w1.samsung.com> for
qemu-devel@nongnu.org; Thu, 07 May 2015 09:11:45 +0100 (BST)
From: Pavel Fedin
References: <1430921082-16779-1-git-send-email-shlomopongratz@gmail.com>
<1430921082-16779-5-git-send-email-shlomopongratz@gmail.com>
<00bd01d08890$b4d60f20$1e822d60$@samsung.com>
In-reply-to:
Date: Thu, 07 May 2015 11:11:44 +0300
Message-id: <00e201d0889d$7537ab50$5fa701f0$@samsung.com>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: quoted-printable
Content-language: ru
Subject: Re: [Qemu-devel] [PATCH RFC V2 4/4] Add virtv2 machine that
uses GIC-500
List-Id:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
To: 'Shlomo Pongratz'
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org, 'Shlomo Pongratz'
Hello!
=E2=9E=A2 Thank you for your comment, I might do it after solving the =
stability issues.
What kind of stability issues do you have ?
You know, i was testing 64-bit qemu in TCG mode, and i have also seen =
weird behavior. The kernel just stops and waits until you hit any key on =
the console, then it continues. This happens if i try to use more than =
one CPU. This has to do with guest kernel version, in v4.1rc2 this is =
gone, while still present in v4.0rc1. Originally i discovered this issue =
on v3.19. So, perhaps it's some guest kernel flaw, having to do with =
interrupts.
The first place where it is stuck is after initializing usbcore. After =
hitting enter it says "switching clocksource to..." (i don't remember) =
and goes on. After this it can stop like this again, in some random =
moment.
Which kernel version do you use for guest ?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia