qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	Cornelia Huck <cohuck@redhat.com>,
	Collin Walling <walling@linux.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
	pasic@linux.ibm.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH 1/2] s390x/cpumodel: default enable mepoch for z14 and later
Date: Mon, 11 Feb 2019 09:55:25 +0100	[thread overview]
Message-ID: <ce43fc8a-b494-c5ad-d14a-3c3fc1badf34@redhat.com> (raw)
In-Reply-To: <4441a5a6-6c26-0e2c-8b95-40af98b2962c@de.ibm.com>

On 11.02.19 09:28, Christian Borntraeger wrote:
> 
> 
> On 11.02.2019 09:23, Cornelia Huck wrote:
>> On Fri,  8 Feb 2019 17:11:10 -0500
>> Collin Walling <walling@linux.ibm.com> wrote:
>>
>>> Latest systems and host kernels support mepoch, which is a
>>> feature that was meant to be supported for z14 GA1 from the
>>> get-go. Let's copy it to the z14 GA1 default CPU model.
>>
>> Do older kernels simply not support it, or was there something actively
>> missing? IOW, is it fine to turn this on with older kernels?
> 
> Older kernels will not provide the necessary implementation, so mepoch will not
> work with such older kernel. (So worst case would be that a new qemu+old kernel
> requires to add mepoch=off to -cpu z14)

Or use a compat machine.

> The idea of this patch is to update QEMU in accordance with newer kernels to use
> more features by default if people use -cpu z14.

Agreed, this was the original purpose of the default models. Can "break"
on old kernels, but the compat machines can help for these users, so it
does not really "break".

> 
> Now that I look a 2nd time: shall we also add 
> S390_FEAT_GROUP_MULTIPLE_EPOCH_PTFF ?

I think so.

> 
> 
>>
>> [It's probably all good, although I like to wait for David's ack for
>> any cpu model patches :)]

I'm fine with this :)

With S390_FEAT_GROUP_MULTIPLE_EPOCH_PTFF also added

Reviewed-by: David Hildenbrand <david@redhat.com>

>>
>>>
>>> Machines s390-ccw-virtio-3.1 and older will retain the old CPU
>>> models and will not provide this bit in the default model.
>>>
>>> Signed-off-by: Collin Walling <walling@linux.ibm.com>
>>> ---
>>>  hw/s390x/s390-virtio-ccw.c  | 1 +
>>>  target/s390x/gen-features.c | 1 +
>>>  2 files changed, 2 insertions(+)
>>>
>>> diff --git a/hw/s390x/s390-virtio-ccw.c b/hw/s390x/s390-virtio-ccw.c
>>> index fd9d0b0542..32c5027345 100644
>>> --- a/hw/s390x/s390-virtio-ccw.c
>>> +++ b/hw/s390x/s390-virtio-ccw.c
>>> @@ -757,6 +757,7 @@ DEFINE_CCW_MACHINE(4_0, "4.0", true);
>>>  static void ccw_machine_3_1_instance_options(MachineState *machine)
>>>  {
>>>      ccw_machine_4_0_instance_options(machine);
>>> +    s390_cpudef_featoff_greater(14, 1, S390_FEAT_MULTIPLE_EPOCH);
>>>  }
>>>  
>>>  static void ccw_machine_3_1_class_options(MachineClass *mc)
>>> diff --git a/target/s390x/gen-features.c b/target/s390x/gen-features.c
>>> index 70015eaaf5..d258d67dca 100644
>>> --- a/target/s390x/gen-features.c
>>> +++ b/target/s390x/gen-features.c
>>> @@ -550,6 +550,7 @@ static uint16_t default_GEN14_GA1[] = {
>>>      S390_FEAT_GROUP_MSA_EXT_6,
>>>      S390_FEAT_GROUP_MSA_EXT_7,
>>>      S390_FEAT_GROUP_MSA_EXT_8,
>>> +    S390_FEAT_MULTIPLE_EPOCH,
>>>  };
>>>  
>>>  /* QEMU (CPU model) features */
>>
> 


-- 

Thanks,

David / dhildenb

  reply	other threads:[~2019-02-11  8:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 22:11 [Qemu-devel] [PATCH 1/2] s390x/cpumodel: default enable mepoch for z14 and later Collin Walling
2019-02-08 22:11 ` [Qemu-devel] [PATCH 2/2] s390x/cpumodel: add z14 GA2 model Collin Walling
2019-02-11  8:19   ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2019-02-11  8:50   ` [Qemu-devel] " David Hildenbrand
2019-02-11  8:14 ` [Qemu-devel] [qemu-s390x] [PATCH 1/2] s390x/cpumodel: default enable mepoch for z14 and later Christian Borntraeger
2019-02-11  8:23 ` [Qemu-devel] " Cornelia Huck
2019-02-11  8:28   ` Christian Borntraeger
2019-02-11  8:55     ` David Hildenbrand [this message]
2019-02-11 10:37       ` Cornelia Huck

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=ce43fc8a-b494-c5ad-d14a-3c3fc1badf34@redhat.com \
    --to=david@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.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).