From: Cornelia Huck <cohuck@redhat.com>
To: Matthew Rosato <mjrosato@linux.ibm.com>
Cc: thuth@redhat.com, kvm@vger.kernel.org, pmorel@linux.ibm.com,
david@redhat.com, schnelle@linux.ibm.com, qemu-s390x@nongnu.org,
qemu-devel@nongnu.org, pasic@linux.ibm.com,
borntraeger@de.ibm.com, alex.williamson@redhat.com,
mst@redhat.com, pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [PATCH 4/7] s390x/pci: use a PCI Group structure
Date: Fri, 25 Sep 2020 11:41:05 +0200 [thread overview]
Message-ID: <20200925114105.439c1c7d.cohuck@redhat.com> (raw)
In-Reply-To: <1600529672-10243-5-git-send-email-mjrosato@linux.ibm.com>
On Sat, 19 Sep 2020 11:34:29 -0400
Matthew Rosato <mjrosato@linux.ibm.com> wrote:
> From: Pierre Morel <pmorel@linux.ibm.com>
>
> We use a S390PCIGroup structure to hold the information related to a
> zPCI Function group.
>
> This allows us to be ready to support multiple groups and to retrieve
> the group information from the host.
>
> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
> Signed-off-by: Matthew Rosato <mjrosato@linux.ibm.com>
> ---
> hw/s390x/s390-pci-bus.c | 42 ++++++++++++++++++++++++++++++++++++++++++
> hw/s390x/s390-pci-bus.h | 10 ++++++++++
> hw/s390x/s390-pci-inst.c | 22 +++++++++++++---------
> 3 files changed, 65 insertions(+), 9 deletions(-)
>
> diff --git a/hw/s390x/s390-pci-bus.c b/hw/s390x/s390-pci-bus.c
> index 92146a2..3015d86 100644
> --- a/hw/s390x/s390-pci-bus.c
> +++ b/hw/s390x/s390-pci-bus.c
> @@ -737,6 +737,46 @@ static void s390_pci_iommu_free(S390pciState *s, PCIBus *bus, int32_t devfn)
> object_unref(OBJECT(iommu));
> }
>
> +static S390PCIGroup *s390_grp_create(int ug)
I think you made the identifiers a bit too compact :)
s390_group_create() is not that long, and I have no idea what the 'ug'
(ugh :) parameter is supposed to mean.
> +{
> + S390PCIGroup *grp;
group?
> + S390pciState *s = s390_get_phb();
> +
> + grp = g_new0(S390PCIGroup, 1);
> + grp->ug = ug;
> + QTAILQ_INSERT_TAIL(&s->zpci_grps, grp, link);
zpci_groups? I think you get the idea :)
> + return grp;
> +}
(...)
No objection to the patch in general.
next prev parent reply other threads:[~2020-09-25 9:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-19 15:34 [PATCH 0/7] Retrieve zPCI hardware information from VFIO Matthew Rosato
2020-09-19 15:34 ` [PATCH 1/7] update-linux-headers: Add vfio_zdev.h Matthew Rosato
2020-09-19 15:34 ` [PATCH 2/7] linux-headers: update against 5.9-rc5 Matthew Rosato
2020-09-19 15:34 ` [PATCH 3/7] s390x/pci: create a header dedicated to PCI CLP Matthew Rosato
2020-09-25 9:17 ` Cornelia Huck
2020-09-25 14:10 ` Matthew Rosato
2020-09-25 15:03 ` Cornelia Huck
2020-09-19 15:34 ` [PATCH 4/7] s390x/pci: use a PCI Group structure Matthew Rosato
2020-09-25 9:41 ` Cornelia Huck [this message]
2020-09-25 14:17 ` Matthew Rosato
2020-09-19 15:34 ` [PATCH 5/7] s390x/pci: clean up s390 PCI groups Matthew Rosato
2020-09-19 15:34 ` [PATCH 6/7] s390x/pci: use a PCI Function structure Matthew Rosato
2020-09-19 15:34 ` [PATCH 7/7] s390x/pci: get zPCI function info from host Matthew Rosato
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=20200925114105.439c1c7d.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=pmorel@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=schnelle@linux.ibm.com \
--cc=thuth@redhat.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).