From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: qemu-devel@nongnu.org, borntraeger@de.ibm.com, agraf@suse.de,
thuth@redhat.com, pmorel@linux.vnet.ibm.com,
zyimin@linux.vnet.ibm.com, pasic@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH RFC 1/1] s390x/ccw: create s390 phb for compat reasons as well
Date: Fri, 15 Sep 2017 15:07:05 +0200 [thread overview]
Message-ID: <20170915150705.359a5356.cohuck@redhat.com> (raw)
In-Reply-To: <37791e7b-c096-3e88-4121-4f1739615367@redhat.com>
On Fri, 15 Sep 2017 13:57:40 +0200
David Hildenbrand <david@redhat.com> wrote:
> As an alternative, simply
>
> diff --git a/target/s390x/cpu_models.c b/target/s390x/cpu_models.c
> index 0f28ebd162..0f22efc3b6 100644
> --- a/target/s390x/cpu_models.c
> +++ b/target/s390x/cpu_models.c
> @@ -195,6 +195,8 @@ bool s390_has_feat(S390Feat feat)
> return true;
> }
> }
> + if (feat == S390_FEAT_ZPCI)
> + return true;
Move that out of the CONFIG_KVM #ifdef?
(Also, we still have the issue with pci support :/ - depend on
pci_available?)
> #endif
> return 0;
> }
>
>
> (this is also the way we handle other features without cpu model support
> -especially if cpu model support is disabled for older machines)
Now that you mention cpu models (which are disabled on old machines),
the failure starts to look plausible :)
next prev parent reply other threads:[~2017-09-15 13:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 10:14 [Qemu-devel] [PATCH RFC 0/1] s390x: pci compat handling Cornelia Huck
2017-09-15 10:14 ` [Qemu-devel] [PATCH RFC 1/1] s390x/ccw: create s390 phb for compat reasons as well Cornelia Huck
2017-09-15 11:57 ` David Hildenbrand
2017-09-15 13:07 ` Cornelia Huck [this message]
2017-09-15 13:09 ` David Hildenbrand
2017-09-15 13:22 ` Cornelia Huck
2017-09-15 13:37 ` David Hildenbrand
2017-09-15 14:16 ` Halil Pasic
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=20170915150705.359a5356.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pmorel@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=zyimin@linux.vnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.