qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 3/7] s390x/pci: create a header dedicated to PCI CLP
Date: Fri, 25 Sep 2020 17:03:00 +0200	[thread overview]
Message-ID: <20200925170300.1367e307.cohuck@redhat.com> (raw)
In-Reply-To: <9303d8c1-dd93-6e63-d90e-0303bd42677b@linux.ibm.com>

On Fri, 25 Sep 2020 10:10:12 -0400
Matthew Rosato <mjrosato@linux.ibm.com> wrote:

> On 9/25/20 5:17 AM, Cornelia Huck wrote:
> > On Sat, 19 Sep 2020 11:34:28 -0400
> > Matthew Rosato <mjrosato@linux.ibm.com> wrote:
> >   
> >> From: Pierre Morel <pmorel@linux.ibm.com>
> >>
> >> To have a clean separation between s390-pci-bus.h and s390-pci-inst.h
> >> headers we export the PCI CLP instructions in a dedicated header.
> >>
> >> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
> >> Signed-off-by: Matthew Rosato <mjrosato@linux.ibm.com>
> >> ---
> >>   hw/s390x/s390-pci-bus.h  |   1 +
> >>   hw/s390x/s390-pci-clp.h  | 211 +++++++++++++++++++++++++++++++++++++++++++++++
> >>   hw/s390x/s390-pci-inst.h | 196 -------------------------------------------
> >>   3 files changed, 212 insertions(+), 196 deletions(-)
> >>   create mode 100644 hw/s390x/s390-pci-clp.h  
> > 
> > Looks sane; but I wonder whether we should move the stuff under
> > include/hw/s390x/.
> >   
> 
> Probably.  I'd be fine with creating this file under include, but if 
> we're going to do that we should plan to move the other s390-pci* ones 
> too.  For this patchset, I can change this patch to put the new header 
> in include/hw/s390x, easy enough.
> 
> I'll plan to do a separate cleanup patchset to move s390-pci-bus.h and 
> s390-pci-inst.h.
> 
> How would you like me to handle s390-pci-vfio.h (this is a new file 
> added by both this patch set and 's390x/pci: Accomodate vfio DMA 
> limiting') --  It seems likely that the latter patch set will merge 
> first, so my thought would be to avoid a cleanup on this one and just 
> re-send 's390x/pci: Accomodate vfio DMA limiting' once the kernel part 
> hits mainline (it's currently in linux-next via Alex) with 
> s390-pci-vfio.h also created in include/hw/s390x (and I guess the 
> MAINTAINERS hit for it too). Sound OK?

Yes, I guess that would be best.




  reply	other threads:[~2020-09-25 15:09 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 [this message]
2020-09-19 15:34 ` [PATCH 4/7] s390x/pci: use a PCI Group structure Matthew Rosato
2020-09-25  9:41   ` Cornelia Huck
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=20200925170300.1367e307.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).