From: "Cédric Le Goater" <clg@redhat.com>
To: Jason Gunthorpe <jgg@nvidia.com>,
Alex Williamson <alex.williamson@redhat.com>
Cc: Yan Zhao <yan.y.zhao@intel.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
kevin.tian@intel.com, yishaih@nvidia.com,
shameerali.kolothum.thodi@huawei.com
Subject: Re: [PATCH] vfio/pci: take mmap write lock for io_remap_pfn_range
Date: Thu, 11 May 2023 09:32:06 +0200 [thread overview]
Message-ID: <e7849fb1-e333-6210-6c92-b00ecb52ccd4@redhat.com> (raw)
In-Reply-To: <ZFwBYtjL1V0r5WW3@nvidia.com>
On 5/10/23 22:41, Jason Gunthorpe wrote:
> On Mon, May 08, 2023 at 02:57:15PM -0600, Alex Williamson wrote:
>
>> We already try to set the flags in advance, but there are some
>> architectural flags like VM_PAT that make that tricky. Cedric has been
>> looking at inserting individual pages with vmf_insert_pfn(), but that
>> incurs a lot more faults and therefore latency vs remapping the entire
>> vma on fault. I'm not convinced that we shouldn't just attempt to
>> remove the fault handler entirely, but I haven't tried it yet to know
>> what gotchas are down that path. Thanks,
OTOH I didn't see any noticeable slowdowns in the tests I did with
NICs, IGD and NVIDIA GPU pass-through. I lack devices with large
BARs though. If anyone has some time for it, here are commits :
https://github.com/legoater/linux/commits/vfio
First does a one page insert and fixes the lockdep issues we are
seeing with the recent series:
https://lore.kernel.org/all/20230126193752.297968-1-surenb@google.com/
Second adds some statistics. For the NVIDIA GPU, faults reach 800k.
Thanks,
C.
> I thought we did it like this because there were races otherwise with
> PTE insertion and zapping? I don't remember well anymore.
>
> I vaugely remember the address_space conversion might help remove the
> fault handler?
>
> Jason
>
next prev parent reply other threads:[~2023-05-11 7:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 12:58 Yan Zhao
2023-05-08 16:48 ` Jason Gunthorpe
2023-05-08 20:57 ` Alex Williamson
2023-05-10 20:41 ` Jason Gunthorpe
2023-05-11 6:56 ` Yan Zhao
2023-05-11 7:38 ` Cédric Le Goater
2023-05-11 7:32 ` Cédric Le Goater [this message]
2023-05-11 16:07 ` Alex Williamson
2023-05-11 17:47 ` Jason Gunthorpe
2023-05-12 8:02 ` Yan Zhao
2024-05-22 16:56 ` Andrew Jones
2024-05-22 17:50 ` Alex Williamson
2024-05-22 18:30 ` Jason Gunthorpe
2024-05-22 19:43 ` Alex Williamson
2024-05-22 21:21 ` 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=e7849fb1-e333-6210-6c92-b00ecb52ccd4@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=yan.y.zhao@intel.com \
--cc=yishaih@nvidia.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
all inboxes | Powered by JetHome®