From: Alex Williamson <alex.williamson@redhat.com>
To: Joao Martins <joao.m.martins@oracle.com>
Cc: kvm@vger.kernel.org, Cornelia Huck <cohuck@redhat.com>,
Avihai Horon <avihaih@nvidia.com>,
Yishai Hadas <yishaih@nvidia.com>
Subject: Re: [PATCH v1 0/2] vfio/iova_bitmap: bug fixes
Date: Thu, 10 Nov 2022 13:16:33 -0700 [thread overview]
Message-ID: <20221110131633.535bbe42.alex.williamson@redhat.com> (raw)
In-Reply-To: <20221025193114.58695-1-joao.m.martins@oracle.com>
On Tue, 25 Oct 2022 20:31:12 +0100
Joao Martins <joao.m.martins@oracle.com> wrote:
> Hey,
>
> This small series addresses one small improvement and one bug fix:
>
> 1) Avoid obscurity into how I use slab helpers yet I was
> never include it directly. And it wasn't detected thanks to a unrelated
> commit in v5.18 that lead linux/mm.h to indirectly include slab.h.
>
> 2) A bug reported by Avihai reported during migration testing where
> we weren't handling correctly PAGE_SIZE unaligned bitmaps, which lead
> to miss dirty marked correctly on some IOVAs.
>
> Comments appreciated
>
> Thanks,
> Joao
>
> Joao Martins (2):
> vfio/iova_bitmap: Explicitly include linux/slab.h
> vfio/iova_bitmap: Fix PAGE_SIZE unaligned bitmaps
>
> drivers/vfio/iova_bitmap.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
Applied to vfio next branch for v6.2. Thanks,
Alex
prev parent reply other threads:[~2022-11-10 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 19:31 [PATCH v1 0/2] vfio/iova_bitmap: bug fixes Joao Martins
2022-10-25 19:31 ` [PATCH v1 1/2] vfio/iova_bitmap: Explicitly include linux/slab.h Joao Martins
2022-10-25 19:31 ` [PATCH v1 2/2] vfio/iova_bitmap: Fix PAGE_SIZE unaligned bitmaps Joao Martins
2022-11-24 18:20 ` Jason Gunthorpe
2022-11-25 10:37 ` Joao Martins
2022-11-25 12:42 ` Jason Gunthorpe
2022-11-25 14:31 ` Joao Martins
2022-11-09 20:09 ` [PATCH v1 0/2] vfio/iova_bitmap: bug fixes Joao Martins
2022-11-10 20:16 ` Alex Williamson [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=20221110131633.535bbe42.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=avihaih@nvidia.com \
--cc=cohuck@redhat.com \
--cc=joao.m.martins@oracle.com \
--cc=kvm@vger.kernel.org \
--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