From: David Hildenbrand <david@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cohuck@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
qemu-s390x <qemu-s390x@nongnu.org>,
Halil Pasic <pasic@linux.ibm.com>,
Richard Henderson <rth@twiddle.net>,
Collin Walling <walling@linux.ibm.com>,
"Jason J . Herne" <jjherne@linux.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2 10/10] s390x/cpumodel: wire up 8561 and 8562 as gen15 machines
Date: Fri, 26 Apr 2019 14:05:30 +0200 [thread overview]
Message-ID: <93f0ecac-47cc-c791-9e32-ad5743489bf3@redhat.com> (raw)
In-Reply-To: <057d438c-2062-1aa7-887a-918f076911c5@de.ibm.com>
On 26.04.19 14:01, Christian Borntraeger wrote:
>
>
> On 26.04.19 13:52, David Hildenbrand wrote:
>> On 26.04.19 13:36, Christian Borntraeger wrote:
>>>
>>>
>>> On 26.04.19 13:32, David Hildenbrand wrote:
>>>> On 26.04.19 13:10, Christian Borntraeger wrote:
>>>>> 8561 and 8562 will be gen15 machines. There is no name yet, lets us use
>>>>> the cpu id as base name. Later on we can provide aliases with the proper
>>>>> name.
>>>>>
>>>>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>>>>> ---
>>>>> target/s390x/cpu_models.c | 2 ++
>>>>> 1 file changed, 2 insertions(+)
>>>>>
>>>>> diff --git a/target/s390x/cpu_models.c b/target/s390x/cpu_models.c
>>>>> index d683635eb5..dd6415103f 100644
>>>>> --- a/target/s390x/cpu_models.c
>>>>> +++ b/target/s390x/cpu_models.c
>>>>> @@ -83,6 +83,8 @@ static S390CPUDef s390_cpu_defs[] = {
>>>>> CPUDEF_INIT(0x3906, 14, 1, 47, 0x08000000U, "z14", "IBM z14 GA1"),
>>>>> CPUDEF_INIT(0x3906, 14, 2, 47, 0x08000000U, "z14.2", "IBM z14 GA2"),
>>>>> CPUDEF_INIT(0x3907, 14, 1, 47, 0x08000000U, "z14ZR1", "IBM z14 Model ZR1 GA1"),
>>>>> + CPUDEF_INIT(0x8561, 15, 1, 47, 0x08000000U, "8561", "IBM 8561 GA1"),
>>>>> + CPUDEF_INIT(0x8562, 15, 1, 47, 0x08000000U, "8562", "IBM 8562 GA1"),
>>>>> };
>>>>
>>>> Thinking out loud, I know that official names are not published yet.
>>>> Looking at the recent history (z13, z14), my educated guess would be
>>>> z15. I guess pretty much everybody would guess that.
>>>
>>> Not sure about trademark aspects - especially if this really becomes z15. The smaller
>>> machine has no real history (ZR1 vs. s vs BC). So I think I would rather have a correct
>>> number than a partially correct name.
>>
>> We could also use "gen15a" and "gen15b", still better to get than magic
>> numbers. (yeah well, they are not magic)
>>
>> If you want to stick with numbers, be aware that cpu numbers are not
>> injective, so at some point we will need e.g. "8561.2", just so you're
>> aware of the implications.
>
> I think whatever we have here is only used internally for expansion (host-model)
> and the user will use later the real name when available. (custom). So probably this
> does not matter for a long time. But I might be wrong.
> I tend to prefer gen15 over z15 but 856x has also its charm.
>
Another question would be, can we rename before the next QEMU release,
so it will never be officially part of QEMU? Then we don't need aliases
after all. Of course, distros have to take care of that as well, but
that shouldn't be upstream QEMUs business.
--
Thanks,
David / dhildenb
WARNING: multiple messages have this Message-ID (diff)
From: David Hildenbrand <david@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cohuck@redhat.com>
Cc: "Jason J . Herne" <jjherne@linux.ibm.com>,
Collin Walling <walling@linux.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
Halil Pasic <pasic@linux.ibm.com>,
qemu-s390x <qemu-s390x@nongnu.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v2 10/10] s390x/cpumodel: wire up 8561 and 8562 as gen15 machines
Date: Fri, 26 Apr 2019 14:05:30 +0200 [thread overview]
Message-ID: <93f0ecac-47cc-c791-9e32-ad5743489bf3@redhat.com> (raw)
Message-ID: <20190426120530.aWBDD6dPoCWgEgyO1NKLI-aJQkxSOxCh-g96lyDm4ss@z> (raw)
In-Reply-To: <057d438c-2062-1aa7-887a-918f076911c5@de.ibm.com>
On 26.04.19 14:01, Christian Borntraeger wrote:
>
>
> On 26.04.19 13:52, David Hildenbrand wrote:
>> On 26.04.19 13:36, Christian Borntraeger wrote:
>>>
>>>
>>> On 26.04.19 13:32, David Hildenbrand wrote:
>>>> On 26.04.19 13:10, Christian Borntraeger wrote:
>>>>> 8561 and 8562 will be gen15 machines. There is no name yet, lets us use
>>>>> the cpu id as base name. Later on we can provide aliases with the proper
>>>>> name.
>>>>>
>>>>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>>>>> ---
>>>>> target/s390x/cpu_models.c | 2 ++
>>>>> 1 file changed, 2 insertions(+)
>>>>>
>>>>> diff --git a/target/s390x/cpu_models.c b/target/s390x/cpu_models.c
>>>>> index d683635eb5..dd6415103f 100644
>>>>> --- a/target/s390x/cpu_models.c
>>>>> +++ b/target/s390x/cpu_models.c
>>>>> @@ -83,6 +83,8 @@ static S390CPUDef s390_cpu_defs[] = {
>>>>> CPUDEF_INIT(0x3906, 14, 1, 47, 0x08000000U, "z14", "IBM z14 GA1"),
>>>>> CPUDEF_INIT(0x3906, 14, 2, 47, 0x08000000U, "z14.2", "IBM z14 GA2"),
>>>>> CPUDEF_INIT(0x3907, 14, 1, 47, 0x08000000U, "z14ZR1", "IBM z14 Model ZR1 GA1"),
>>>>> + CPUDEF_INIT(0x8561, 15, 1, 47, 0x08000000U, "8561", "IBM 8561 GA1"),
>>>>> + CPUDEF_INIT(0x8562, 15, 1, 47, 0x08000000U, "8562", "IBM 8562 GA1"),
>>>>> };
>>>>
>>>> Thinking out loud, I know that official names are not published yet.
>>>> Looking at the recent history (z13, z14), my educated guess would be
>>>> z15. I guess pretty much everybody would guess that.
>>>
>>> Not sure about trademark aspects - especially if this really becomes z15. The smaller
>>> machine has no real history (ZR1 vs. s vs BC). So I think I would rather have a correct
>>> number than a partially correct name.
>>
>> We could also use "gen15a" and "gen15b", still better to get than magic
>> numbers. (yeah well, they are not magic)
>>
>> If you want to stick with numbers, be aware that cpu numbers are not
>> injective, so at some point we will need e.g. "8561.2", just so you're
>> aware of the implications.
>
> I think whatever we have here is only used internally for expansion (host-model)
> and the user will use later the real name when available. (custom). So probably this
> does not matter for a long time. But I might be wrong.
> I tend to prefer gen15 over z15 but 856x has also its charm.
>
Another question would be, can we rename before the next QEMU release,
so it will never be officially part of QEMU? Then we don't need aliases
after all. Of course, distros have to take care of that as well, but
that shouldn't be upstream QEMUs business.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-04-26 12:05 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 11:09 [Qemu-devel] [PATCH v2 00/10] s390x: new guest features Christian Borntraeger
2019-04-26 11:09 ` Christian Borntraeger
2019-04-26 11:09 ` [Qemu-devel] [PATCH v2 01/10] linux header sync Christian Borntraeger
2019-04-26 11:09 ` Christian Borntraeger
2019-04-26 11:09 ` [Qemu-devel] [PATCH v2 02/10] s390x/cpumodel: ignore csske for expansion Christian Borntraeger
2019-04-26 11:09 ` Christian Borntraeger
2019-04-26 11:15 ` David Hildenbrand
2019-04-26 11:15 ` David Hildenbrand
2019-04-26 11:09 ` [Qemu-devel] [PATCH v2 03/10] s390x/cpumodel: Miscellaneous-Instruction-Extensions Facility 3 Christian Borntraeger
2019-04-26 11:09 ` Christian Borntraeger
2019-04-26 11:09 ` [Qemu-devel] [PATCH v2 04/10] s390x/cpumodel: msa9 facility Christian Borntraeger
2019-04-26 11:09 ` Christian Borntraeger
2019-04-26 11:09 ` [Qemu-devel] [PATCH v2 05/10] s390x/cpumodel: vector enhancements Christian Borntraeger
2019-04-26 11:09 ` Christian Borntraeger
2019-04-26 11:09 ` [Qemu-devel] [PATCH v2 06/10] s390x/cpumodel: enhanced sort facility Christian Borntraeger
2019-04-26 11:09 ` Christian Borntraeger
2019-04-26 11:10 ` [Qemu-devel] [PATCH v2 07/10] s390x/cpumodel: add Deflate-conversion facility Christian Borntraeger
2019-04-26 11:10 ` Christian Borntraeger
2019-04-26 11:10 ` [Qemu-devel] [PATCH v2 08/10] s390x/cpumodel: add gen15 defintions Christian Borntraeger
2019-04-26 11:10 ` Christian Borntraeger
2019-04-26 11:10 ` [Qemu-devel] [PATCH v2 09/10] s390x/cpumodel: disable csske and bpb from gen15 cpu models onwards Christian Borntraeger
2019-04-26 11:10 ` Christian Borntraeger
2019-04-26 11:18 ` David Hildenbrand
2019-04-26 11:18 ` David Hildenbrand
2019-04-26 11:18 ` Christian Borntraeger
2019-04-26 11:18 ` Christian Borntraeger
2019-04-26 11:20 ` David Hildenbrand
2019-04-26 11:20 ` David Hildenbrand
2019-04-26 11:10 ` [Qemu-devel] [PATCH v2 10/10] s390x/cpumodel: wire up 8561 and 8562 as gen15 machines Christian Borntraeger
2019-04-26 11:10 ` Christian Borntraeger
2019-04-26 11:21 ` David Hildenbrand
2019-04-26 11:21 ` David Hildenbrand
2019-04-26 11:22 ` Christian Borntraeger
2019-04-26 11:22 ` Christian Borntraeger
2019-04-26 11:24 ` Christian Borntraeger
2019-04-26 11:24 ` Christian Borntraeger
2019-04-26 11:34 ` David Hildenbrand
2019-04-26 11:34 ` David Hildenbrand
2019-04-26 11:32 ` David Hildenbrand
2019-04-26 11:32 ` David Hildenbrand
2019-04-26 11:36 ` Christian Borntraeger
2019-04-26 11:36 ` Christian Borntraeger
2019-04-26 11:52 ` David Hildenbrand
2019-04-26 11:52 ` David Hildenbrand
2019-04-26 12:01 ` Christian Borntraeger
2019-04-26 12:01 ` Christian Borntraeger
2019-04-26 12:05 ` David Hildenbrand [this message]
2019-04-26 12:05 ` David Hildenbrand
2019-04-26 12:55 ` Cornelia Huck
2019-04-26 12:55 ` Cornelia Huck
2019-04-29 7:51 ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2019-04-29 7:51 ` Christian Borntraeger
2019-04-29 8:53 ` Cornelia Huck
2019-04-29 8:53 ` Cornelia Huck
2019-04-29 8:55 ` Christian Borntraeger
2019-04-29 8:55 ` Christian Borntraeger
2019-04-29 10:16 ` David Hildenbrand
2019-04-29 10:16 ` David Hildenbrand
2019-04-26 11:23 ` [Qemu-devel] [PATCH v2 00/10] s390x: new guest features no-reply
2019-04-26 11:23 ` no-reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=93f0ecac-47cc-c791-9e32-ad5743489bf3@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=jjherne@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=walling@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).