From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:34345)
by lists.gnu.org with esmtp (Exim 4.71)
(envelope-from
) id 1Z1rpN-0007YP-MG
for qemu-devel@nongnu.org; Mon, 08 Jun 2015 03:50:38 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
(envelope-from ) id 1Z1rpK-0001eT-4s
for qemu-devel@nongnu.org; Mon, 08 Jun 2015 03:50:37 -0400
Received: from mailout2.w1.samsung.com ([210.118.77.12]:38066)
by eggs.gnu.org with esmtp (Exim 4.71)
(envelope-from ) id 1Z1rpK-0001cf-0B
for qemu-devel@nongnu.org; Mon, 08 Jun 2015 03:50:34 -0400
Received: from eucpsbgm1.samsung.com (unknown [203.254.199.244])
by mailout2.w1.samsung.com
(Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5
2014)) with ESMTP id <0NPM00F878G6FR50@mailout2.w1.samsung.com> for
qemu-devel@nongnu.org; Mon, 08 Jun 2015 08:50:30 +0100 (BST)
From: Pavel Fedin
References: <1433436037-5476-1-git-send-email-shlomopongratz@gmail.com>
<1433436037-5476-2-git-send-email-shlomopongratz@gmail.com>
In-reply-to:
Date: Mon, 08 Jun 2015 10:50:28 +0300
Message-id: <01ca01d0a1bf$ca206310$5e612930$@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 V3 1/4] Use Aff1 with mpidr This is an
improved and KVM-aware alternative to
List-Id:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
To: 'Peter Maydell' , 'Shlomo Pongratz'
Cc: 'Eric Auger' , 'Shlomo Pongratz' , 'QEMU Developers' , 'Shannon Zhao' , ashoks@broadcom.com, 'Igor Mammedov'
> I think it would be less confusing to store the entire MPIDR
> here, and then mask it out if there are places that only
> want the affinity bits.
I thought about it when i developed this, but in my implementation =
affinity bits are assigned during CPU instantiation, while feature bits =
can be added later, during realize. I could tweak set_feature() to sync =
up MPIDR value but perhaps it isn't the best thing to do.
Additionally, currently we support only ARM_FEATURE_V7MP, which is =
32-bit only. I believe this would be a more complex modification which =
would touch more of 32-bit code.
So would it be acceptable to leave mpidr handling as it is?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia