qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: qemu-devel@nongnu.org, agraf@suse.de, thuth@redhat.com,
	david@redhat.com, pmorel@linux.vnet.ibm.com,
	zyimin@linux.vnet.ibm.com, pasic@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH RFC v2 1/1] s390x/ccw: create s390 phb for compat reasons as well
Date: Mon, 18 Sep 2017 10:07:56 +0200	[thread overview]
Message-ID: <20170918100756.75eec02d.cohuck@redhat.com> (raw)
In-Reply-To: <396c3d9d-644a-c946-3099-aba94f0571e8@de.ibm.com>

On Mon, 18 Sep 2017 09:47:00 +0200
Christian Borntraeger <borntraeger@de.ibm.com> wrote:

> On 09/18/2017 09:33 AM, Christian Borntraeger wrote:
> > 
> > 
> > On 09/15/2017 06:39 PM, Cornelia Huck wrote:  
> >> d32bd032d8 ("s390x/ccw: create s390 phb conditionally") made
> >> registering the s390 pci host bridge conditional on presense
> >> of the zpci facility bit. Sadly, that breaks migration from
> >> machines that did not use the cpu model (2.7 and previous).
> >>
> >> Create the s390 phb for pre-cpu model machines as well.
> >>
> >> Fixes: d32bd032d8 ("s390x/ccw: create s390 phb conditionally")
> >> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> >> ---
> >>  hw/s390x/s390-virtio-ccw.c | 2 ++
> >>  target/s390x/cpu_models.c  | 3 +++
> >>  2 files changed, 5 insertions(+)
> >>
> >> diff --git a/hw/s390x/s390-virtio-ccw.c b/hw/s390x/s390-virtio-ccw.c
> >> index 0471407187..907abc7a32 100644
> >> --- a/hw/s390x/s390-virtio-ccw.c
> >> +++ b/hw/s390x/s390-virtio-ccw.c
> >> @@ -269,6 +269,8 @@ static void s390_create_virtio_net(BusState *bus, const char *name)
> >>      }
> >>  }
> >>
> >> +static S390CcwMachineClass *get_machine_class(void);
> >> +
> >>  static void ccw_init(MachineState *machine)
> >>  {
> >>      int ret;

This hunk is from the previous version and should not be in there...

> >> diff --git a/target/s390x/cpu_models.c b/target/s390x/cpu_models.c
> >> index c295e641e6..5169379db5 100644
> >> --- a/target/s390x/cpu_models.c
> >> +++ b/target/s390x/cpu_models.c
> >> @@ -196,6 +196,9 @@ bool s390_has_feat(S390Feat feat)
> >>              }
> >>          }
> >>  #endif
> >> +        if (feat == S390_FEAT_ZPCI) {
> >> +            return true;
> >> +        }  
> > 
> > Shouldnt that be depend on the machine being 2.7? I mean unless I misread 
> > the context of this patch, you hard enable the PCI facility bit for all 
> > machines and make all s390_has_feat(S390_FEAT_ZPCI) useless?
> >   
> 
> Sorry, I had to lookup again the original code. So this is inside !cpu->model. 
> Yes makes sense then.

Yes, this is hard to figure out from the context alone.

  reply	other threads:[~2017-09-18  8:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-15 16:39 [Qemu-devel] [PATCH RFC v2 0/1] s390x: pci compat handling Cornelia Huck
2017-09-15 16:39 ` [Qemu-devel] [PATCH RFC v2 1/1] s390x/ccw: create s390 phb for compat reasons as well Cornelia Huck
2017-09-18  7:33   ` Christian Borntraeger
2017-09-18  7:47     ` Christian Borntraeger
2017-09-18  8:07       ` Cornelia Huck [this message]
2017-09-18  8:35         ` Christian Borntraeger
2017-09-18  7:48     ` 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=20170918100756.75eec02d.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 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).