From: Cornelia Huck <cohuck@redhat.com>
To: Niklas Schnelle <schnelle@linux.ibm.com>
Cc: thuth@redhat.com, Pierre Morel <pmorel@linux.ibm.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
david@redhat.com, mst@redhat.com, richard.henderson@linaro.org,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
pasic@linux.ibm.com, borntraeger@de.ibm.com,
alex.williamson@redhat.com, pbonzini@redhat.com
Subject: Re: [PATCH 0/8] s390x/pci: Fixing s390 vfio-pci ISM support
Date: Thu, 21 Jan 2021 18:50:36 +0100 [thread overview]
Message-ID: <20210121185036.41fde30c.cohuck@redhat.com> (raw)
In-Reply-To: <9522792d-6677-eed4-f480-4efaaf00dd51@linux.ibm.com>
On Thu, 21 Jan 2021 15:54:22 +0100
Niklas Schnelle <schnelle@linux.ibm.com> wrote:
> On 1/21/21 3:46 PM, Pierre Morel wrote:
> >
> >
> > On 1/21/21 2:37 PM, Niklas Schnelle wrote:
> >>
> >>
> >> On 1/21/21 1:30 PM, Pierre Morel wrote:
> >
> >>>>
> >>>> Just wanted to say that we've had a very similar discussion with
> >>>> Cornelia end of last year and came to the conclusion that explicitly
> >>>> matching the PFT is likely the safest bet:
> >>>> https://lkml.org/lkml/2020/12/22/479
> >>>
> >>> What I see there is a discussion on the relation between relaxed access and MIO without explaining to Connie that we have in the kernel the possibility to know if a device support MIO or not independently of it supports the relaxed access.
> >>>
> >>> The all point here is about taking decisions for the right reasons.
> >>>
> >>> We have the possibility to take the decision based on functionalities and not on a specific PCI function.
> >>
> >> Yes but that goes both ways the functionality of the region has to match
> >> that of the device and at least in it's current state the regions functionality
> >> matches only ISM in a way that is so specific that it is very unlikely to match anything
> >> else. For example it can't support a PCI device that requires non-MIO but
> >> also MSI-X. In its current form it doesn't even support PCI Store only PCI Store
> >> Block, we had that in an earlier version and it's trivial but then we get the MSI-X
> >> problem.
> >
> >
> > What does that change if we take one or the other solution considering the checking of MIO/MSIX/relax versus PFT?
>
>
> If it's !MIO && !MSIX && relax_align I'm fine with that check but
> then we should also add PCISTG to the region.
>
Just to double check: that would today cover only ISM (which doesn't
use PCISTG), correct?
/me getting a bit lost in this discussion :)
next prev parent reply other threads:[~2021-01-21 17:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 20:44 [PATCH 0/8] s390x/pci: Fixing s390 vfio-pci ISM support Matthew Rosato
2021-01-19 20:44 ` [PATCH 1/8] linux-headers: update against 5.11-rc4 Matthew Rosato
2021-01-19 20:44 ` [PATCH 2/8] s390x/pci: Keep track of the PCI Function type Matthew Rosato
2021-01-19 20:44 ` [PATCH 3/8] s390x/pci: MSI-X isn't strictly required for passthrough Matthew Rosato
2021-01-19 20:44 ` [PATCH 4/8] s390x/pci: Introduce the ZpciOps structure Matthew Rosato
2021-01-19 20:44 ` [PATCH 5/8] s390x/pci: Handle devices that support relaxed alignment Matthew Rosato
2021-01-19 20:44 ` [PATCH 6/8] s390x/pci: PCISTB via the vfio zPCI I/O region Matthew Rosato
2021-01-19 20:44 ` [PATCH 7/8] s390x/pci: PCILG " Matthew Rosato
2021-01-19 20:44 ` [PATCH 8/8] s390x/pci: Prevent ISM device passthrough on older host kernels Matthew Rosato
2021-01-20 9:12 ` [PATCH 0/8] s390x/pci: Fixing s390 vfio-pci ISM support Pierre Morel
2021-01-20 14:03 ` Matthew Rosato
2021-01-20 14:45 ` Pierre Morel
2021-01-20 15:59 ` Matthew Rosato
2021-01-20 19:18 ` Pierre Morel
2021-01-20 20:29 ` Matthew Rosato
2021-01-21 8:27 ` Pierre Morel
2021-01-21 9:58 ` Niklas Schnelle
2021-01-21 12:30 ` Pierre Morel
2021-01-21 13:37 ` Niklas Schnelle
2021-01-21 14:46 ` Pierre Morel
2021-01-21 14:54 ` Niklas Schnelle
2021-01-21 17:50 ` Cornelia Huck [this message]
2021-01-21 18:06 ` Matthew Rosato
2021-01-22 16:46 ` Cornelia Huck
2021-01-25 14:55 ` Matthew Rosato
2021-01-21 14:42 ` Matthew Rosato
2021-01-21 15:45 ` Pierre Morel
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=20210121185036.41fde30c.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--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=richard.henderson@linaro.org \
--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).