qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH RFC 1/2] s390x/tcg: wire up pci instructions


From: Cornelia Huck
Subject: Re: [Qemu-devel] [PATCH RFC 1/2] s390x/tcg: wire up pci instructions
Date: Wed, 31 Jan 2018 18:38:45 +0100

On Tue, 30 Jan 2018 14:00:12 +0100
David Hildenbrand <address@hidden> wrote:

> On 29.01.2018 17:52, Cornelia Huck wrote:
> > On s390x, pci support is implemented via a set of instructions
> > (no mmio). Unfortunately, none of them are documented in the
> > PoP; the code is based upon the existing implementation for KVM
> > and the Linux zpci driver.
> > 
> > Signed-off-by: Cornelia Huck <address@hidden>
> > ---
> >  target/s390x/helper.h      |   9 ++++
> >  target/s390x/insn-data.def |  13 +++++
> >  target/s390x/misc_helper.c | 123 
> > +++++++++++++++++++++++++++++++++++++++++++++
> >  target/s390x/translate.c   | 123 
> > +++++++++++++++++++++++++++++++++++++++++++++
> >  4 files changed, 268 insertions(+)
> > 

> > diff --git a/target/s390x/insn-data.def b/target/s390x/insn-data.def
> > index 11ee43dcbc..2ffc051072 100644
> > --- a/target/s390x/insn-data.def
> > +++ b/target/s390x/insn-data.def
> > @@ -1067,4 +1067,17 @@
> >      /* ??? Not listed in PoO ninth edition, but there's a linux driver that
> >         uses it: "A CHSC subchannel is usually present on LPAR only."  */
> >      C(0xb25f, CHSC,  RRE,     Z,   0, insn, 0, 0, chsc, 0)
> > +
> > +/* zPCI Instructions */
> > +    /* None of these instructions are documented in the PoP, so this is all
> > +       based upon target/s390x/kvm.c and Linux code and likely incomplete 
> > */
> > +    C(0xebd0, PCISTB, RSY_a, PCI, 0, 0, 0, 0, pcistb, 0)
> > +    C(0xebd1, SIC, RSY_a, PCI, 0, 0, 0, 0, sic, 0)
> > +    C(0xb9a0, CLP, RRF_c, PCI, 0, 0, 0, 0, clp, 0)
> > +    C(0xb9d0, PCISTG, RRE, PCI, 0, 0, 0, 0, pcistg, 0)
> > +    C(0xb9d2, PCILG, RRE, PCI, 0, 0, 0, 0, pcilg, 0)
> > +    C(0xb9d3, RPCIT, RRE, PCI, 0, 0, 0, 0, rpcit, 0)
> > +    C(0xe3d0, MPCIFC, RXY_a, PCI, 0, 0, 0, 0, mpcifc, 0)
> > +    C(0xe3d4, STPCIFC, RXY_a, PCI, 0, 0, 0, 0, stpcifc, 0)
> > +
> >  #endif /* CONFIG_USER_ONLY */

> b) we will handle !s390_has_feat(S390_FEAT_ZPCI) although available
> later just as other instructions via the "PCI" flag you attached to the
> instructions (Richard once posted a patch to do that).

> > @@ -5708,6 +5830,7 @@ enum DisasInsnEnum {
> >  #define FAC_MSA4        S390_FEAT_MSA_EXT_4 /* msa-extension-4 facility */
> >  #define FAC_MSA5        S390_FEAT_MSA_EXT_5 /* msa-extension-5 facility */
> >  #define FAC_ECT         S390_FEAT_EXTRACT_CPU_TIME
> > +#define FAC_PCI         S390_FEAT_ZPCI /* z/PCI facility */

Thinking again: We should probably not attach the PCI flag to SIC, it
is independent of it (although only in use for pci adapters right now).



reply via email to

[Prev in Thread] Current Thread [Next in Thread]