qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, borntraeger@de.ibm.com, agraf@suse.de,
	pmorel@linux.vnet.ibm.com, zyimin@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH RFC 5/7] s390x/pci: fence off instructions for non-pci
Date: Fri, 7 Jul 2017 15:10:30 +0200	[thread overview]
Message-ID: <20170707151030.1352cecf@dhcp-192-215.str.redhat.com> (raw)
In-Reply-To: <8815f788-c1ba-d979-6c5d-2ab615b34d46@redhat.com>

On Fri, 7 Jul 2017 15:00:20 +0200
Thomas Huth <thuth@redhat.com> wrote:

> On 07.07.2017 14:21, Cornelia Huck wrote:
> > If a guest running on a non-pci build issues a pci instruction,
> > throw them an exception.
> > 
> > Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> > ---
> >  target/s390x/kvm.c | 24 ++++++++++++++++++++++++
> >  1 file changed, 24 insertions(+)
> > 
> > diff --git a/target/s390x/kvm.c b/target/s390x/kvm.c
> > index a3d00196f4..c5c7c27a21 100644
> > --- a/target/s390x/kvm.c
> > +++ b/target/s390x/kvm.c
> > @@ -1160,6 +1160,9 @@ static int kvm_clp_service_call(S390CPU *cpu, struct kvm_run *run)
> >  {
> >      uint8_t r2 = (run->s390_sieic.ipb & 0x000f0000) >> 16;
> >  
> > +#ifndef CONFIG_PCI
> > +    return -1;
> > +#endif
> >      return clp_service_call(cpu, r2);
> >  }
> >  
> > @@ -1168,6 +1171,9 @@ static int kvm_pcilg_service_call(S390CPU *cpu, struct kvm_run *run)
> >      uint8_t r1 = (run->s390_sieic.ipb & 0x00f00000) >> 20;
> >      uint8_t r2 = (run->s390_sieic.ipb & 0x000f0000) >> 16;
> >  
> > +#ifndef CONFIG_PCI
> > +    return -1;
> > +#endif
> >      return pcilg_service_call(cpu, r1, r2);
> >  }  
> 
> pcilg_service_call() seems to be defined in s390-pci-inst.c ... which
> you later remove from the !CONFIG_PCI builds... so I wonder why this
> still compiles ... I guess GCC is smart enough to optimize it away.

Yes, as the second return is not reachable anymore.

> Anyway, to be on the safe side (and to be able to compile with -O0), you
> should maybe rather do this instead:
> 
> #ifndef CONFIG_PCI
>     return -1;
> #else
>     return pcilg_service_call(cpu, r1, r2);
> #endif
> 
> ?

I'll try Christian's suggestion to use the cpu model first. However,
we'll need some ifdeffery somewhere... maybe we should introduce a
zpci-stub.c for the referenced functions.

  reply	other threads:[~2017-07-07 13:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-07 12:21 [Qemu-devel] [PATCH RFC 0/7] s390x: zPCI detangling Cornelia Huck
2017-07-07 12:21 ` [Qemu-devel] [PATCH RFC 1/7] kvm: remove hard dependency on pci Cornelia Huck
2017-07-07 13:11   ` Thomas Huth
2017-07-07 13:15     ` Cornelia Huck
2017-07-07 12:21 ` [Qemu-devel] [PATCH RFC 2/7] s390x: chsc nt2 events are pci-only Cornelia Huck
2017-07-07 13:01   ` Christian Borntraeger
2017-07-07 13:11     ` Cornelia Huck
2017-07-07 12:21 ` [Qemu-devel] [PATCH RFC 3/7] s390x/sclp: properly guard pci-specific functions Cornelia Huck
2017-07-07 12:21 ` [Qemu-devel] [PATCH RFC 4/7] s390x/ccw: create s390 phb conditionally Cornelia Huck
2017-07-07 12:21 ` [Qemu-devel] [PATCH RFC 5/7] s390x/pci: fence off instructions for non-pci Cornelia Huck
2017-07-07 12:55   ` Christian Borntraeger
2017-07-07 13:04     ` Cornelia Huck
2017-07-10 11:04       ` Cornelia Huck
2017-07-10 12:41         ` Christian Borntraeger
2017-07-10 12:54           ` Cornelia Huck
2017-07-07 13:00   ` Thomas Huth
2017-07-07 13:10     ` Cornelia Huck [this message]
2017-07-07 12:21 ` [Qemu-devel] [PATCH RFC 6/7] s390x/kvm: msi route fixup " Cornelia Huck
2017-07-07 12:21 ` [Qemu-devel] [PATCH RFC 7/7] s390x: refine pci dependencies 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=20170707151030.1352cecf@dhcp-192-215.str.redhat.com \
    --to=cohuck@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.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).