From: Alex Williamson <alex.williamson@redhat.com>
To: lizhe.67@bytedance.com
Cc: jgg@ziepe.ca, david@redhat.com, peterx@redhat.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/3] vfio/type1: introduce a new member has_rsvd for struct vfio_dma
Date: Fri, 27 Jun 2025 15:40:03 -0600 [thread overview]
Message-ID: <20250627154003.6cbd5e53.alex.williamson@redhat.com> (raw)
In-Reply-To: <20250620032344.13382-3-lizhe.67@bytedance.com>
On Fri, 20 Jun 2025 11:23:43 +0800
lizhe.67@bytedance.com wrote:
> From: Li Zhe <lizhe.67@bytedance.com>
>
> Introduce a new member has_rsvd for struct vfio_dma. This member is
> used to indicate whether there are any reserved or invalid pfns in
> the region represented by this vfio_dma. If it is true, it indicates
> that there is at least one pfn in this region that is either reserved
> or invalid.
>
> Signed-off-by: Li Zhe <lizhe.67@bytedance.com>
> ---
> drivers/vfio/vfio_iommu_type1.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
> index e952bf8bdfab..8827e315e3d8 100644
> --- a/drivers/vfio/vfio_iommu_type1.c
> +++ b/drivers/vfio/vfio_iommu_type1.c
> @@ -93,6 +93,10 @@ struct vfio_dma {
> bool iommu_mapped;
> bool lock_cap; /* capable(CAP_IPC_LOCK) */
> bool vaddr_invalid;
> + /*
> + * Any reserved or invalid pfns within this range?
> + */
> + bool has_rsvd;
Nit, the topic isn't so complex to make a brief comment:
bool has_rsvd; /* has 1 or more rsvd pfns */
Thanks,
Alex
> struct task_struct *task;
> struct rb_root pfn_list; /* Ex-user pinned pfn list */
> unsigned long *bitmap;
> @@ -785,6 +789,7 @@ static long vfio_pin_pages_remote(struct vfio_dma *dma, unsigned long vaddr,
> }
>
> out:
> + dma->has_rsvd |= rsvd;
> ret = vfio_lock_acct(dma, lock_acct, false);
>
> unpin_out:
next prev parent reply other threads:[~2025-06-27 21:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 3:23 [PATCH v5 0/3] vfio/type1: optimize vfio_unpin_pages_remote() for large folio lizhe.67
2025-06-20 3:23 ` [PATCH v5 1/3] vfio/type1: batch vfio_find_vpfn() in function vfio_unpin_pages_remote() lizhe.67
2025-06-24 16:23 ` kernel test robot
2025-06-25 2:29 ` lizhe.67
2025-06-27 21:40 ` Alex Williamson
2025-06-30 2:45 ` lizhe.67
2025-06-20 3:23 ` [PATCH v5 2/3] vfio/type1: introduce a new member has_rsvd for struct vfio_dma lizhe.67
2025-06-27 21:40 ` Alex Williamson [this message]
2025-06-20 3:23 ` [PATCH v5 3/3] vfio/type1: optimize vfio_unpin_pages_remote() for large folio lizhe.67
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=20250627154003.6cbd5e53.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=david@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhe.67@bytedance.com \
--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).