From: Alex Williamson <alex.williamson@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 3/7] vfio/pci: Use vfio_device_unmap_mapping_range()
Date: Tue, 10 Aug 2021 13:59:32 -0600 [thread overview]
Message-ID: <20210810135932.6825833b.alex.williamson@redhat.com> (raw)
In-Reply-To: <YRLJ/wdiY/fnGj2d@t490s>
On Tue, 10 Aug 2021 14:48:31 -0400
Peter Xu <peterx@redhat.com> wrote:
> On Thu, Aug 05, 2021 at 11:07:35AM -0600, Alex Williamson wrote:
> > @@ -1690,7 +1554,7 @@ static int vfio_pci_mmap(struct vfio_device *core_vdev, struct vm_area_struct *v
> >
> > vma->vm_private_data = vdev;
> > vma->vm_page_prot = pgprot_noncached(vma->vm_page_prot);
> > - vma->vm_pgoff = (pci_resource_start(pdev, index) >> PAGE_SHIFT) + pgoff;
> > + vma->vm_page_prot = pgprot_decrypted(vma->vm_page_prot);
>
> This addition seems to be an accident. :) Thanks,
Nope, Jason noted on a previous version that io_remap_pfn_range() is
essentially:
remap_pfn_range(vma, addr, pfn, size, pgprot_decrypted(prot));
So since we switched to vmf_insert_pfn() I added this page protection
flag to the vma instead, then it gets removed later when we switch back
to io_remap_pfn_range(). Thanks,
Alex
next prev parent reply other threads:[~2021-08-10 19:59 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 17:06 [PATCH 0/7] vfio: device fd address space and vfio-pci mmap invalidation cleanup Alex Williamson
2021-08-05 17:07 ` [PATCH 1/7] vfio: Create vfio_fs_type with inode per device Alex Williamson
2021-08-10 8:43 ` Christoph Hellwig
2021-08-10 14:52 ` Alex Williamson
2021-08-10 14:57 ` Christoph Hellwig
2021-08-10 18:49 ` Peter Xu
2021-08-10 21:16 ` Alex Williamson
2021-08-10 22:18 ` Peter Xu
2021-08-05 17:07 ` [PATCH 2/7] vfio: Export unmap_mapping_range() wrapper Alex Williamson
2021-08-10 8:45 ` Christoph Hellwig
2021-08-10 18:56 ` Peter Xu
2021-08-05 17:07 ` [PATCH 3/7] vfio/pci: Use vfio_device_unmap_mapping_range() Alex Williamson
2021-08-06 1:04 ` Jason Gunthorpe
2021-08-06 20:17 ` Alex Williamson
2021-08-10 8:51 ` Christoph Hellwig
2021-08-10 11:57 ` Jason Gunthorpe
2021-08-10 12:55 ` Christoph Hellwig
2021-08-10 21:50 ` Alex Williamson
2021-08-11 11:57 ` Jason Gunthorpe
2021-08-10 8:53 ` Christoph Hellwig
2021-08-10 19:02 ` Peter Xu
2021-08-10 20:51 ` Alex Williamson
2021-08-10 18:48 ` Peter Xu
2021-08-10 19:59 ` Alex Williamson [this message]
2021-08-10 20:20 ` Peter Xu
2021-08-05 17:07 ` [PATCH 4/7] vfio,vfio-pci: Add vma to pfn callback Alex Williamson
2021-08-06 1:01 ` Jason Gunthorpe
2021-08-10 9:00 ` Christoph Hellwig
2021-08-10 9:00 ` Christoph Hellwig
2021-08-05 17:08 ` [PATCH 5/7] mm/interval_tree.c: Export vma interval tree iterators Alex Williamson
2021-08-05 17:08 ` [PATCH 6/7] vfio: Add vfio_device_io_remap_mapping_range() Alex Williamson
2021-08-10 9:04 ` Christoph Hellwig
2021-08-05 17:08 ` [PATCH 7/7] vfio/pci: Remove map-on-fault behavior Alex Williamson
2021-08-10 9:11 ` Christoph Hellwig
2021-08-10 15:04 ` Alex Williamson
2021-08-10 20:54 ` Peter Xu
2021-08-10 21:45 ` Alex Williamson
2021-08-10 22:27 ` Peter Xu
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=20210810135932.6825833b.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=jgg@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterx@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).