From: David Hildenbrand <david@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Cc: rth@twiddle.net, agraf@suse.de
Subject: Re: [Qemu-devel] [PATCH v2 2/2] s390x/cpumodel: allow zpci features in qemu model
Date: Thu, 1 Feb 2018 13:31:46 +0100 [thread overview]
Message-ID: <0542bcf4-fc37-cf4a-6bd1-4dafa3533772@redhat.com> (raw)
In-Reply-To: <20180131181742.2037-3-cohuck@redhat.com>
On 31.01.2018 19:17, Cornelia Huck wrote:
> AEN can be provided unconditionally, ZPCI should be turned on
> manually.
>
> With -cpu qemu,zpci=on, a 4.15 guest kernel can now successfully
> detect virtio-pci devices under tcg.
>
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
> target/s390x/cpu_models.c | 6 ++++++
> target/s390x/gen-features.c | 3 +++
> 2 files changed, 9 insertions(+)
>
> diff --git a/target/s390x/cpu_models.c b/target/s390x/cpu_models.c
> index 212a5f0697..250d931d7e 100644
> --- a/target/s390x/cpu_models.c
> +++ b/target/s390x/cpu_models.c
> @@ -23,6 +23,7 @@
> #include "qapi/qmp/qbool.h"
> #ifndef CONFIG_USER_ONLY
> #include "sysemu/arch_init.h"
> +#include "hw/pci/pci.h"
> #endif
>
> #define CPUDEF_INIT(_type, _gen, _ec_ga, _mha_pow, _hmfai, _name, _desc) \
> @@ -1271,6 +1272,11 @@ static void register_types(void)
>
> /* init all bitmaps from gnerated data initially */
> s390_init_feat_bitmap(qemu_max_cpu_feat_init, qemu_max_cpu_feat);
> +#ifndef CONFIG_USER_ONLY
> + if (!pci_available) {
> + clear_bit(S390_FEAT_ZPCI, qemu_max_cpu_feat);
> + }
> +#endif
> for (i = 0; i < ARRAY_SIZE(s390_cpu_defs); i++) {
> s390_init_feat_bitmap(s390_cpu_defs[i].base_init,
> s390_cpu_defs[i].base_feat);
> diff --git a/target/s390x/gen-features.c b/target/s390x/gen-features.c
> index 0570f597ec..c7083ed4a8 100644
> --- a/target/s390x/gen-features.c
> +++ b/target/s390x/gen-features.c
> @@ -574,6 +574,7 @@ static uint16_t qemu_LATEST[] = {
> S390_FEAT_INTERLOCKED_ACCESS_2,
> S390_FEAT_MSA_EXT_4,
> S390_FEAT_MSA_EXT_3,
> + S390_FEAT_ADAPTER_EVENT_NOTIFICATION,
Minor nit, according to the order in target/s390x/cpu_features_def.h,
this should go before FEAT_MSA_EXT_3 (yes, the order of EXT3/EXT4 is
messed up)
> };
>
> /* add all new definitions before this point */
> @@ -582,6 +583,8 @@ static uint16_t qemu_MAX[] = {
> S390_FEAT_STFLE_53,
> /* generates a dependency warning, leave it out for now */
> S390_FEAT_MSA_EXT_5,
> + /* only with CONFIG_PCI */
> + S390_FEAT_ZPCI,
> };
>
> /****** END FEATURE DEFS ******/
>
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2018-02-01 12:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 18:17 [Qemu-devel] [PATCH v2 0/2] s390x: support zpci in tcg Cornelia Huck
2018-01-31 18:17 ` [Qemu-devel] [PATCH v2 1/2] s390x/tcg: wire up pci instructions Cornelia Huck
2018-02-01 10:00 ` Pierre Morel
2018-02-01 14:23 ` Cornelia Huck
2018-02-01 12:42 ` David Hildenbrand
2018-02-01 12:48 ` Cornelia Huck
2018-02-01 12:59 ` David Hildenbrand
2018-02-01 16:05 ` Cornelia Huck
2018-02-01 14:47 ` Cornelia Huck
2018-01-31 18:17 ` [Qemu-devel] [PATCH v2 2/2] s390x/cpumodel: allow zpci features in qemu model Cornelia Huck
2018-02-01 12:31 ` David Hildenbrand [this message]
2018-02-01 14:04 ` 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=0542bcf4-fc37-cf4a-6bd1-4dafa3533772@redhat.com \
--to=david@redhat.com \
--cc=agraf@suse.de \
--cc=cohuck@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
/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).