From: David Hildenbrand <david@redhat.com>
To: lizhe.67@bytedance.com, alex.williamson@redhat.com,
akpm@linux-foundation.org, peterx@redhat.com, jgg@ziepe.ca
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 4/5] vfio/type1: introduce a new member has_rsvd for struct vfio_dma
Date: Fri, 4 Jul 2025 10:46:18 +0200 [thread overview]
Message-ID: <10a7ced9-33f2-47a0-b368-a6fecad6a842@redhat.com> (raw)
In-Reply-To: <20250704062602.33500-5-lizhe.67@bytedance.com>
On 04.07.25 08:26, 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 | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
> index b770eb1c4e07..13c5667d431c 100644
> --- a/drivers/vfio/vfio_iommu_type1.c
> +++ b/drivers/vfio/vfio_iommu_type1.c
> @@ -92,6 +92,7 @@ struct vfio_dma {
> bool iommu_mapped;
> bool lock_cap; /* capable(CAP_IPC_LOCK) */
> bool vaddr_invalid;
> + bool has_rsvd; /* has 1 or more rsvd pfns */
> struct task_struct *task;
> struct rb_root pfn_list; /* Ex-user pinned pfn list */
> unsigned long *bitmap;
> @@ -774,6 +775,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:
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-07-04 8:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 6:25 [PATCH v2 0/5] vfio/type1: optimize vfio_pin_pages_remote() and vfio_unpin_pages_remote() lizhe.67
2025-07-04 6:25 ` [PATCH v2 1/5] mm: introduce num_pages_contiguous() lizhe.67
2025-07-04 7:56 ` David Hildenbrand
2025-07-04 8:21 ` lizhe.67
2025-07-04 17:10 ` Jason Gunthorpe
2025-07-07 3:38 ` lizhe.67
2025-07-04 21:19 ` kernel test robot
2025-07-07 3:52 ` lizhe.67
2025-07-04 6:25 ` [PATCH v2 2/5] vfio/type1: optimize vfio_pin_pages_remote() lizhe.67
2025-07-04 8:41 ` David Hildenbrand
2025-07-04 6:26 ` [PATCH v2 3/5] vfio/type1: batch vfio_find_vpfn() in function vfio_unpin_pages_remote() lizhe.67
2025-07-04 6:26 ` [PATCH v2 4/5] vfio/type1: introduce a new member has_rsvd for struct vfio_dma lizhe.67
2025-07-04 8:46 ` David Hildenbrand [this message]
2025-07-04 6:26 ` [PATCH v2 5/5] vfio/type1: optimize vfio_unpin_pages_remote() lizhe.67
2025-07-04 8:47 ` David Hildenbrand
2025-07-04 17:11 ` Jason Gunthorpe
2025-07-07 3:44 ` 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=10a7ced9-33f2-47a0-b368-a6fecad6a842@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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