From: "Michael S. Tsirkin" <mst@redhat.com>
To: CLEMENT MATHIEU--DRIF <clement.mathieu--drif@eviden.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"zhenzhong.duan@intel.com" <zhenzhong.duan@intel.com>,
"kevin.tian@intel.com" <kevin.tian@intel.com>,
"yi.l.liu@intel.com" <yi.l.liu@intel.com>,
"joao.m.martins@oracle.com" <joao.m.martins@oracle.com>,
"peterx@redhat.com" <peterx@redhat.com>
Subject: Re: [PATCH v4 0/4] VT-d minor fixes
Date: Sat, 20 Jul 2024 14:44:15 -0400 [thread overview]
Message-ID: <20240720144357-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240705105937.1630829-1-clement.mathieu--drif@eviden.com>
On Fri, Jul 05, 2024 at 11:01:55AM +0000, CLEMENT MATHIEU--DRIF wrote:
> From: Clément Mathieu--Drif <clement.mathieu--drif@eviden.com>
>
> Various fixes for VT-d
>
> This series contains fixes that will be necessary
> when adding in-guest (fully emulated) SVM support.
Clément are you going to address Yi Liu's comments?
> v4
> - Move declarations of VTD_FRCD_PV and VTD_FRCD_PP
> - intel_iommu: make types match:
> - edit commit message to explain that we are not fixing a bug
> - intel_iommu: fix type of the mask field in VTDIOTLBPageInvInfo
> - edit commit message
>
> v3
> FRCD construction macro :
> - Longer sha1 for the 'Fixes' tag
> - Add '.' at the end of the sentence
>
> Make types match :
> - Split into 2 patches (one for the fix and one for type matching)
>
> Remove patch for wait descriptor handling (will be in the PRI series)
>
> v2
> Make commit author consistent
>
>
>
> Clément Mathieu--Drif (4):
> intel_iommu: fix FRCD construction macro
> intel_iommu: move VTD_FRCD_PV and VTD_FRCD_PP declarations
> intel_iommu: fix type of the mask field in VTDIOTLBPageInvInfo
> intel_iommu: make types match
>
> hw/i386/intel_iommu.c | 2 +-
> hw/i386/intel_iommu_internal.h | 6 +++---
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> --
> 2.45.2
next prev parent reply other threads:[~2024-07-20 18:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 11:01 [PATCH v4 0/4] VT-d minor fixes CLEMENT MATHIEU--DRIF
2024-07-05 11:01 ` [PATCH v4 1/4] intel_iommu: fix FRCD construction macro CLEMENT MATHIEU--DRIF
2024-07-08 7:07 ` Yi Liu
2024-07-09 2:51 ` Jason Wang
2024-07-09 6:12 ` Yi Liu
2024-07-05 11:01 ` [PATCH v4 2/4] intel_iommu: move VTD_FRCD_PV and VTD_FRCD_PP declarations CLEMENT MATHIEU--DRIF
2024-07-05 11:01 ` [PATCH v4 3/4] intel_iommu: fix type of the mask field in VTDIOTLBPageInvInfo CLEMENT MATHIEU--DRIF
2024-07-08 7:12 ` Yi Liu
2024-07-20 18:45 ` Michael S. Tsirkin
2024-07-20 19:08 ` Michael S. Tsirkin
2024-07-05 11:01 ` [PATCH v4 4/4] intel_iommu: make types match CLEMENT MATHIEU--DRIF
2024-07-08 7:20 ` Yi Liu
2024-07-20 18:46 ` Michael S. Tsirkin
2024-07-20 19:09 ` Michael S. Tsirkin
2024-07-20 18:44 ` Michael S. Tsirkin [this message]
2024-07-20 19:08 ` [PATCH v4 0/4] VT-d minor fixes Michael S. Tsirkin
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=20240720144357-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=clement.mathieu--drif@eviden.com \
--cc=jasowang@redhat.com \
--cc=joao.m.martins@oracle.com \
--cc=kevin.tian@intel.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yi.l.liu@intel.com \
--cc=zhenzhong.duan@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;
as well as URLs for NNTP newsgroup(s).