Received: from eggs.gnu.org ([2001:4830:134:3::10]:47146) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dnQZJ-0000W9-1p for qemu-devel@nongnu.org; Thu, 31 Aug 2017 10:35:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dnQZE-0003pq-0f for qemu-devel@nongnu.org; Thu, 31 Aug 2017 10:35:41 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42879) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dnQZD-0003nv-RA for qemu-devel@nongnu.org; Thu, 31 Aug 2017 10:35:35 -0400 Date: Thu, 31 Aug 2017 16:35:13 +0200 From: Cornelia Huck Message-ID: <20170831163513.17c0a963.cohuck@redhat.com> In-Reply-To: <20170830170601.15855-7-david@redhat.com> References: <20170830170601.15855-1-david@redhat.com> <20170830170601.15855-7-david@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v1 06/11] target/s390x: cleanup cpu number/address handling List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Hildenbrand Cc: qemu-devel@nongnu.org, Richard Henderson , Aurelien Jarno , thuth@redhat.com, borntraeger@de.ibm.com, Alexander Graf On Wed, 30 Aug 2017 19:05:56 +0200 David Hildenbrand wrote: > Some time ago we discussed that using "id" as property name is not the > right thing to do, as it is a reserved property for other devices. > > Switch to the term "addr" instead, which matches the definition in the > PoP called "CPU address". There is no such thing as cpu number, so > rename env.cpu_num to env.cpu_addr. > > We can get rid of cpu->id now. Keep cpu->index and env->cpu_addr in sync. > cpu->index was already implicitly used by e.g. cpu_exists(), so keeping > both in sync seems to be the right thing to do. > > cpu->index will now no longer automatically get set via > cpu_exec_realizefn(). For now, we were lucky that both implicitly stayed > in sync. > > Our new cpu property "addr" can be a static property. Range checks can > be avoided by using the correct type and the "setting after realized" > check is done implicitly. > > AFAIK, s390x only supports cpu_add and not device_add for cpus. So we > should be able to safely rename that property (no the "id" property > could properly be used for device_add, which needs an artificial id for > identification purposes). I cannot parse the sentence in the brackets... > > Signed-off-by: David Hildenbrand > --- > hw/s390x/s390-virtio-ccw.c | 2 +- > target/s390x/cpu.c | 69 ++++++++++++---------------------------------- > target/s390x/cpu.h | 5 ++-- > target/s390x/cpu_models.c | 2 +- > target/s390x/excp_helper.c | 2 +- > target/s390x/helper.c | 4 +-- > target/s390x/misc_helper.c | 4 +-- > target/s390x/translate.c | 5 +--- > 8 files changed, 28 insertions(+), 65 deletions(-) ...the patch seems fine, though :)