From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
Richard Henderson <rth@twiddle.net>,
Alexander Graf <agraf@suse.de>, Thomas Huth <thuth@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] s390x/cpumodel: model PTFF subfunctions for Multiple-epoch facility
Date: Tue, 6 Feb 2018 18:19:07 +0100 [thread overview]
Message-ID: <20180206181907.577e9b3f.cohuck@redhat.com> (raw)
In-Reply-To: <ee01d23d-5bbc-9b57-d6a5-25ef8d792374@redhat.com>
On Mon, 5 Feb 2018 13:37:17 +0100
David Hildenbrand <david@redhat.com> wrote:
> On 05.02.2018 13:22, Cornelia Huck wrote:
> > On Mon, 5 Feb 2018 12:27:33 +0100
> > David Hildenbrand <david@redhat.com> wrote:
> >
> >> On 05.02.2018 12:22, Christian Borntraeger wrote:
> >>> Looks sane on a z14.
> >>> Tested-by: Christian Borntraeger <borntraeger@de.ibm.com>
> >>>
> >>>
> >>> On 02/05/2018 11:29 AM, David Hildenbrand wrote:
> >>>> --- a/target/s390x/kvm.c
> >>>> +++ b/target/s390x/kvm.c
> >>>> @@ -2221,6 +2221,14 @@ void kvm_s390_get_host_cpu_model(S390CPUModel *model, Error **errp)
> >>>> return;
> >>>> }
> >>>>
> >>>> + /* PTFF subfunctions might be indicated although kernel support missing */
> >>>> + if (!test_bit(S390_FEAT_MULTIPLE_EPOCH, model->features)) {
> >>>> + clear_bit(S390_FEAT_PTFF_QSIE, model->features);
> >>>> + clear_bit(S390_FEAT_PTFF_QTOUE, model->features);
> >>>> + clear_bit(S390_FEAT_PTFF_STOE, model->features);
> >>>> + clear_bit(S390_FEAT_PTFF_STOUE, model->features);
> >>>> + }
> >>>> +
> >>>> /* with cpu model support, CMM is only indicated if really available */
> >>>> if (kvm_s390_cmma_available()) {
> >>>> set_bit(S390_FEAT_CMM, model->features);
> >>>>
> >>>
> >>> Do you also want to add something to check_consistency ?
> >>>
> >>> Right now the following user error
> >>> -cpu z14,mepoch=off,mepochptff=on
> >>> is accepted.
> >>> On the other hand we also have no consistency checks for other subfunctions.
> >>>
> >>
> >> Thought about that, but that implies that a CPU model runable now, will
> >> not run without warnings. Especially if migrating. We could add such
> >> checks if we would push this into stable.
I'm currently wondering whether this change would actually be
applicable and useful for stable. Given the way stable is usually used,
probably not.
> >>
> >
> > So, adding this check for the z14 stuff would work iff pushed into
> > stable - but for the other subfunctions the ship has already sailed?
> >
>
> I don't know if we really have problems with other subfunctions. We
> could also add consistency checks there (the problem here is that we
> actually have to add missing subfunctions). So it is easier to check for
> consistency with already existing subfunctions.
Hm, so not really worth the hassle, just keep this as-is (and apply
this patch as-is)?
next prev parent reply other threads:[~2018-02-06 17:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 10:29 [Qemu-devel] [PATCH v2] s390x/cpumodel: model PTFF subfunctions for Multiple-epoch facility David Hildenbrand
2018-02-05 10:42 ` no-reply
2018-02-05 11:22 ` Christian Borntraeger
2018-02-05 11:27 ` David Hildenbrand
2018-02-05 12:22 ` Cornelia Huck
2018-02-05 12:37 ` David Hildenbrand
2018-02-06 17:19 ` Cornelia Huck [this message]
2018-02-06 17:22 ` David Hildenbrand
2018-02-06 18:00 ` Christian Borntraeger
2018-02-06 13:00 ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2018-02-06 18:58 ` [Qemu-devel] " 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=20180206181907.577e9b3f.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.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).