From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45139)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <shlomopongratz@gmail.com>) id 1YqHbF-0007Qk-T5
	for qemu-devel@nongnu.org; Thu, 07 May 2015 04:56:11 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <shlomopongratz@gmail.com>) id 1YqHbB-0008HN-NC
	for qemu-devel@nongnu.org; Thu, 07 May 2015 04:56:09 -0400
Received: from mail-yk0-x22a.google.com ([2607:f8b0:4002:c07::22a]:34340)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <shlomopongratz@gmail.com>) id 1YqHbB-0008HG-JP
	for qemu-devel@nongnu.org; Thu, 07 May 2015 04:56:05 -0400
Received: by ykft189 with SMTP id t189so9755251ykf.1
	for <qemu-devel@nongnu.org>; Thu, 07 May 2015 01:56:05 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <00e201d0889d$7537ab50$5fa701f0$@samsung.com>
References: <1430921082-16779-1-git-send-email-shlomopongratz@gmail.com>
	<1430921082-16779-5-git-send-email-shlomopongratz@gmail.com>
	<00bd01d08890$b4d60f20$1e822d60$@samsung.com>
	<CAHzK-V0X5AG9zNupK93wJ2jXNdGbxZZNn=13ZhRFgSTx0z3+Eg@mail.gmail.com>
	<00e201d0889d$7537ab50$5fa701f0$@samsung.com>
Date: Thu, 7 May 2015 11:56:05 +0300
Message-ID: <CAHzK-V19rG+ZxXZ+JRQ-qVENj938Dg_zszxtHtKsews6NJfvtQ@mail.gmail.com>
From: Shlomo Pongratz <shlomopongratz@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c115ccf18a9605157a14d6
Subject: Re: [Qemu-devel] [PATCH RFC V2 4/4] Add virtv2 machine that uses
	GIC-500
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: "peter.maydell@linaro.org" <peter.maydell@linaro.org>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, Shlomo Pongratz <shlomo.pongratz@huawei.com>

--001a11c115ccf18a9605157a14d6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thursday, May 7, 2015, Pavel Fedin <p.fedin@samsung.com> wrote:

>  Hello!
>
> =E2=9E=A2 Thank you for your comment, I might do it after solving the sta=
bility
> 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 on=
e
> 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) an=
d
> 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
>
> Hi Pavel,

The stability issue is described in patch 0000.
The issue is similar to what you have noticed.
The larger the number of smp cores it is more likely that the boot will get
stuck.
I've commuted this patch series as an RFC because of this issue.

Best regards,

S.P.

--001a11c115ccf18a9605157a14d6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br><br>On Thursday, May 7, 2015, Pavel Fedin &lt;<a href=3D"mailto:p.fedin=
@samsung.com">p.fedin@samsung.com</a>&gt; wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">=C2=A0Hello!<br>
<br>
=E2=9E=A2 Thank you for your comment, I might do it after solving the stabi=
lity issues.<br>
<br>
=C2=A0What kind of stability issues do you have ?<br>
=C2=A0You 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 t=
he console, then it continues. This happens if i try to use more than one C=
PU. This has to do with guest kernel version, in v4.1rc2 this is gone, whil=
e still present in v4.0rc1. Originally i discovered this issue on v3.19. So=
, perhaps it&#39;s some guest kernel flaw, having to do with interrupts.<br=
>
=C2=A0The first place where it is stuck is after initializing usbcore. Afte=
r hitting enter it says &quot;switching clocksource to...&quot; (i don&#39;=
t remember) and goes on. After this it can stop like this again, in some ra=
ndom moment.<br>
=C2=A0Which kernel version do you use for guest ?<br>
<br>
Kind regards,<br>
Pavel Fedin<br>
Expert Engineer<br>
Samsung Electronics Research center Russia<br>
<br></blockquote><div>Hi Pavel,</div><div><br></div><div>The stability issu=
e is described in patch 0000.</div><div>The issue is similar to what you ha=
ve noticed.</div><div>The larger the number of smp cores it is more likely =
that the boot will get stuck.</div><div>I&#39;ve commuted this patch series=
 as an RFC because of this issue.</div><div><br></div><div>Best regards,</d=
iv><div><br></div><div>S.P.</div><div><br></div>

--001a11c115ccf18a9605157a14d6--