public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Niklas Schnelle <schnelle@linux.ibm.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Gerd Bayer <gbayer@linux.ibm.com>,
	Matthew Rosato <mjrosato@linux.ibm.com>,
	Jason Gunthorpe <jgg@ziepe.ca>
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org
Subject: Re: [PATCH v4 2/4] s390/pci: Add quirk support and set pdev-non_compliant_bars for ISM devices
Date: Wed, 26 Jun 2024 13:20:45 +0200	[thread overview]
Message-ID: <b22a641f84b3e3259777ff54576f3a2f1435785b.camel@linux.ibm.com> (raw)
In-Reply-To: <20240626-vfio_pci_mmap-v4-2-7f038870f022@linux.ibm.com>

On Wed, 2024-06-26 at 13:15 +0200, Niklas Schnelle wrote:
> On s390 there is a virtual PCI device called ISM which has a few
> pecularities. For one it claims to have a 256 TiB PCI BAR which leads to
> any attempt to ioremap() in its entirety failing. This is problematic
> since mapping the whole BAR is the default behavior of for example QEMU
> with VFIO_PCI_MMAP enabled.
> 
> Even if one tried to map this BAR only partially the mapping would not
> be usable on systems with MIO support enabled unless using the function
> handle based PCI instructions directly. This is because of another
> oddity in that this virtual PCI device does not support the newer memory
> I/O (MIO) PCI instructions and legacy PCI instructions are not
> accessible through writeq()/readq() or by user-space when MIO is in use.
> 
> Indicate that ISM's BAR is special and does not conform to PCI BAR
> expectations by setting pdev->non_compliant_bars such that drivers not
> specifically developed for ISM can easily ignore it. To this end add
> basic PCI quirks support modeled after x86's arch/x86/pci/fixup.c and
> move the ISM device's PCI ID to the common header to make it accessible.
> Also enable CONFIG_PCI_QUIRKS whenever CONFIG_PCI is enabled.
> 
> Signed-off-by: Niklas Schnelle <schnelle@linux.ibm.com>
> ---
> 


Fixed the '-' instead of '->' typo in the patch subject locally.
Chances are we get a v5 anyway.

Thanks,
Niklas

  reply	other threads:[~2024-06-26 11:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 11:15 [PATCH v4 0/4] vfio/pci: s390: Fix issues preventing VFIO_PCI_MMAP=y for s390 and enable it Niklas Schnelle
2024-06-26 11:15 ` [PATCH v4 1/4] s390/pci: Fix s390_mmio_read/write syscall page fault handling Niklas Schnelle
2024-06-26 11:15 ` [PATCH v4 2/4] s390/pci: Add quirk support and set pdev-non_compliant_bars for ISM devices Niklas Schnelle
2024-06-26 11:20   ` Niklas Schnelle [this message]
2024-06-27 11:12     ` Alexandra Winter
2024-06-26 11:15 ` [PATCH v4 3/4] vfio/pci: Disable mmap() non-compliant BARs Niklas Schnelle
2024-06-27 22:05   ` Alex Williamson
2024-06-28  8:49     ` Niklas Schnelle
2024-06-26 11:15 ` [PATCH v4 4/4] vfio/pci: Enable PCI resource mmap() on s390 and remove VFIO_PCI_MMAP Niklas Schnelle
2024-07-04 16:16   ` Alex Williamson
2024-07-11 10:20     ` Niklas Schnelle
2024-06-26 11:59 ` [PATCH v4 0/4] vfio/pci: s390: Fix issues preventing VFIO_PCI_MMAP=y for s390 and enable it Christoph Hellwig

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=b22a641f84b3e3259777ff54576f3a2f1435785b.camel@linux.ibm.com \
    --to=schnelle@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=gbayer@linux.ibm.com \
    --cc=gerald.schaefer@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=hch@lst.de \
    --cc=helgaas@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mjrosato@linux.ibm.com \
    --cc=svens@linux.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