public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Precific <precification@posteo.de>,
	Athul Krishna <athul.krishna.kr@protonmail.com>,
	Bjorn Helgaas <helgaas@kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Linux PCI <linux-pci@vger.kernel.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [bugzilla-daemon@kernel.org: [Bug 219619] New: vfio-pci: screen graphics artifacts after 6.12 kernel upgrade]
Date: Thu, 2 Jan 2025 11:38:32 -0700	[thread overview]
Message-ID: <20250102113832.4d5c101a.alex.williamson@redhat.com> (raw)
In-Reply-To: <20250102100402.33fa8435.alex.williamson@redhat.com>

On Thu, 2 Jan 2025 10:04:02 -0700
Alex Williamson <alex.williamson@redhat.com> wrote:

> On Thu, 2 Jan 2025 11:39:23 -0500
> Peter Xu <peterx@redhat.com> wrote:
> > OTOH, a pure question here is whether we should check pfn+pgoff instead of
> > pgoff alone.  I have no idea how firmware would allocate BAR resources,
> > especially on start address alignments.  I assume that needs to be somehow
> > relevant to the max size of the bar, probably the start address should
> > always be aligned to that max bar size?  If so, there should have no
> > functional difference checking either pfn+pgoff or pgoff.  It could be a
> > matter of readability in that case, saying that the limitation is about pfn
> > (of pgtable) rather than directly relevant to the offset of the bar.  
> 
> Yes, I'm working on the proper patch now that we have a root cause and
> I'm changing this to test alignment of pfn+pgoff.  The PCI BARs
> themselves are required to have natural alignment, but the vma mapping
> the BAR could be at an offset from the base of the BAR, which is
> accounted for in our local vma_to_pfn() function.  So I agree that
> pfn+pgoff is the more complete fix, which I'll post soon, and hope that
> Precific can re-verify the fix.  Thanks,

The proposed fix is now posted here:

https://lore.kernel.org/all/20250102183416.1841878-1-alex.williamson@redhat.com

Please reply there with Tested-by and Reviewed-by as available.  Thanks,

Alex


  reply	other threads:[~2025-01-02 18:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-22 22:36 [bugzilla-daemon@kernel.org: [Bug 219619] New: vfio-pci: screen graphics artifacts after 6.12 kernel upgrade] Bjorn Helgaas
2024-12-23  7:37 ` Athul Krishna
2024-12-23 16:59   ` Peter Xu
2024-12-23 18:15     ` Alex Williamson
2024-12-24 18:06       ` Athul Krishna
2024-12-30 21:03     ` Precific
2024-12-31  1:27       ` Alex Williamson
2024-12-31 15:44         ` Precific
2024-12-31 16:07           ` Alex Williamson
2025-01-01  3:10             ` Precific
2025-01-02 16:39             ` Peter Xu
2025-01-02 17:04               ` Alex Williamson
2025-01-02 18:38                 ` Alex Williamson [this message]
2025-02-25 17:59                   ` Bjorn Helgaas

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=20250102113832.4d5c101a.alex.williamson@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=athul.krishna.kr@protonmail.com \
    --cc=helgaas@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=peterx@redhat.com \
    --cc=precification@posteo.de \
    --cc=regressions@lists.linux.dev \
    /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