| commit | 1e70ba24a906211c26930f4f41a674fcb685f8ef | |
| author | David Hildenbrand <david@redhat.com> | |
| Thu, 28 Sep 2017 13:46:08 +0000 (28 15:46 +0200) | ||
| committer | Cornelia Huck <cohuck@redhat.com> | |
| Fri, 6 Oct 2017 08:53:02 +0000 (6 10:53 +0200) | ||
| tree | 6140d0c507a76fdc2897550fb4e7887cb5661bb4 | treesnapshot (tar.gz zip) |
| parent | c547a757f492cb037aec81965893046b7ef6d201 | commitdiff |
target/s390x: get rid of next_core_id
core_id is not needed by linux-user, as the core_id a.k.a. CPU address
is only accessible from kernel space.
Therefore, drop next_core_id and make cpu_index get autoassigned again
for linux-user.
While at it, shield core_id and cpuid completely from linux-user. cpuid
can also only be queried from kernel space.
Suggested-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20170928134609.16985-5-david@redhat.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
core_id is not needed by linux-user, as the core_id a.k.a. CPU address
is only accessible from kernel space.
Therefore, drop next_core_id and make cpu_index get autoassigned again
for linux-user.
While at it, shield core_id and cpuid completely from linux-user. cpuid
can also only be queried from kernel space.
Suggested-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20170928134609.16985-5-david@redhat.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
| target/s390x/cpu-qom.h | diffblobblamehistory | |
| target/s390x/cpu.c | diffblobblamehistory | |
| target/s390x/cpu.h | diffblobblamehistory | |
| target/s390x/cpu_models.c | diffblobblamehistory |