From: Matthew Rosato <mjrosato@linux.ibm.com>
To: Michael Tokarev <mjt@tls.msk.ru>, qemu-s390x@nongnu.org
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v2 2/2] s390x/pci: only limit DMA aperture if vfio DMA limit reported
Date: Mon, 13 Nov 2023 16:49:34 -0500 [thread overview]
Message-ID: <fa2bacd4-2d7d-06fa-e588-685697e03840@linux.ibm.com> (raw)
In-Reply-To: <6222c257-2732-490c-8f84-3582f501d548@tls.msk.ru>
On 11/13/23 4:24 PM, Michael Tokarev wrote:
> 10.11.2023 20:51, Matthew Rosato wrote:
>> If the host kernel lacks vfio DMA limit reporting, do not attempt
>> to shrink the guest DMA aperture.
>>
>> Fixes: df202e3ff3 ("s390x/pci: shrink DMA aperture to be bound by vfio DMA limit")
>> Signed-off-by: Matthew Rosato <mjrosato@linux.ibm.com>
>
> Is this stable-8.1 material?
>
> Thanks,
>
> /mjt
>
Yes, I believe it is (sorry, should have added CC stable)
If you have a host kernel that doesn't report the vfio DMA limit the resulting PCI device will be rendered unusable in the s390x guest due this bug.
Thanks,
Matt
next prev parent reply other threads:[~2023-11-13 21:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 17:51 [PATCH v2 0/2] s390x/pci: small set of fixes Matthew Rosato
2023-11-10 17:51 ` [PATCH v2 1/2] s390x/pci: bypass vfio DMA counting when using cdev Matthew Rosato
2023-11-10 17:51 ` [PATCH v2 2/2] s390x/pci: only limit DMA aperture if vfio DMA limit reported Matthew Rosato
2023-11-13 21:24 ` Michael Tokarev
2023-11-13 21:49 ` Matthew Rosato [this message]
2023-11-13 6:29 ` [PATCH v2 0/2] s390x/pci: small set of fixes Thomas Huth
2023-11-13 14:49 ` Eric Farman
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=fa2bacd4-2d7d-06fa-e588-685697e03840@linux.ibm.com \
--to=mjrosato@linux.ibm.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
/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).