From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, ajones@ventanamicro.com,
yan.y.zhao@intel.com, kevin.tian@intel.com, peterx@redhat.com
Subject: Re: [PATCH] vfio/pci: Insert full vma on mmap'd MMIO fault
Date: Wed, 12 Jun 2024 09:17:12 -0300 [thread overview]
Message-ID: <20240612121712.GY19897@nvidia.com> (raw)
In-Reply-To: <20240611092333.6bb17d60.alex.williamson@redhat.com>
On Tue, Jun 11, 2024 at 09:23:33AM -0600, Alex Williamson wrote:
>
> Any support for this or should we just go with the v2 series[1] by
> itself for v6.10? Thanks,
I didn't think of a reason not to do this, but I don't know the fault
path especially well.
It sure would be nice to fault all the memory in one shot.
Jason
prev parent reply other threads:[~2024-06-12 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 3:52 [PATCH] vfio/pci: Insert full vma on mmap'd MMIO fault Alex Williamson
2024-06-11 15:23 ` Alex Williamson
2024-06-12 10:08 ` Yan Zhao
2024-06-12 12:17 ` Jason Gunthorpe [this message]
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=20240612121712.GY19897@nvidia.com \
--to=jgg@nvidia.com \
--cc=ajones@ventanamicro.com \
--cc=alex.williamson@redhat.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=yan.y.zhao@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.