From: Kirti Wankhede <kwankhede@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Liu Yi L <yi.l.liu@intel.com>, <linux-kernel@vger.kernel.org>,
<kvm@vger.kernel.org>
Subject: Re: [PATCH] vfio/type1: Fix migration info capability ID
Date: Fri, 19 Jun 2020 18:29:24 +0530 [thread overview]
Message-ID: <8c4f9b33-faee-fbe1-3600-426f199952db@nvidia.com> (raw)
In-Reply-To: <159250751478.22544.8607332732745502185.stgit@gimli.home>
On 6/19/2020 12:42 AM, Alex Williamson wrote:
> ID 1 is already used by the IOVA range capability, use ID 2.
>
Ops.
Thanks for Fixing it.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
> Reported-by: Liu Yi L <yi.l.liu@intel.com>
> Cc: Kirti Wankhede <kwankhede@nvidia.com>
> Fixes: ad721705d09c ("vfio iommu: Add migration capability to report supported features")
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
> include/uapi/linux/vfio.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h
> index eca6692667a3..920470502329 100644
> --- a/include/uapi/linux/vfio.h
> +++ b/include/uapi/linux/vfio.h
> @@ -1030,7 +1030,7 @@ struct vfio_iommu_type1_info_cap_iova_range {
> * size in bytes that can be used by user applications when getting the dirty
> * bitmap.
> */
> -#define VFIO_IOMMU_TYPE1_INFO_CAP_MIGRATION 1
> +#define VFIO_IOMMU_TYPE1_INFO_CAP_MIGRATION 2
>
> struct vfio_iommu_type1_info_cap_migration {
> struct vfio_info_cap_header header;
>
prev parent reply other threads:[~2020-06-19 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 19:12 Alex Williamson
2020-06-19 12:59 ` Kirti Wankhede [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=8c4f9b33-faee-fbe1-3600-426f199952db@nvidia.com \
--to=kwankhede@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yi.l.liu@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 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®