From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42666)
by lists.gnu.org with esmtp (Exim 4.71)
(envelope-from
) id 1ZosYu-00072l-Ft
for qemu-devel@nongnu.org; Wed, 21 Oct 2015 08:32:21 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
(envelope-from ) id 1ZosYq-0002E4-FC
for qemu-devel@nongnu.org; Wed, 21 Oct 2015 08:32:12 -0400
Received: from mailout4.w1.samsung.com ([210.118.77.14]:44406)
by eggs.gnu.org with esmtp (Exim 4.71)
(envelope-from ) id 1ZosYq-0002E0-8z
for qemu-devel@nongnu.org; Wed, 21 Oct 2015 08:32:08 -0400
Received: from eucpsbgm1.samsung.com (unknown [203.254.199.244])
by mailout4.w1.samsung.com
(Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5
2014)) with ESMTP id <0NWK00K5LLHHYA30@mailout4.w1.samsung.com> for
qemu-devel@nongnu.org; Wed, 21 Oct 2015 13:32:05 +0100 (BST)
From: Pavel Fedin
References: <1445396964-21189-1-git-send-email-shlomopongratz@gmail.com>
<009e01d10bcc$8c4326a0$a4c973e0$@samsung.com>
<00f601d10bed$fd8ac5e0$f8a051a0$@samsung.com>
In-reply-to:
Date: Wed, 21 Oct 2015 15:32:03 +0300
Message-id: <013501d10bfc$7e0dc1f0$7a2945d0$@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 V5 1/9] hw/intc: Implement GIC-500
support files
List-Id:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
To: 'Shlomo Pongratz'
Cc: peter.maydell@linaro.org, eric.auger@linaro.org, 'Shlomo Pongratz' , qemu-devel@nongnu.org, shannon.zhao@linaro.org, ashoks@broadcom.com, imammedo@redhat.com
Hello!
>> See this: =
http://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg02349.html. =
This is also a part of my live migration RFC.
>> I remember that Peter told long time ago that "it should really be a =
property", when i integrated full affinity support. But, he currently
>> refused to accept this small standalone patch because there are no =
users for now. My GICv3 live migration is waiting for kernel API to be
>> ready. And kernel API is waiting for kernel 4.5 development cycle to =
begin.
> So please resubmit it and mention me as a client.
Ok, i'll PING, but you can also include it into your patchset. BTW, why =
is it still RFC?
> But I wonder if accessing the property in real time (not in only in =
initialization) from the GIC code will have impact on performance.
It can, but you can cache them during realize. For example, if you =
accept my data layout, then you can just add "uint64_t mp_affinity" to =
GICv3CPUState.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia