From: "Michael S. Tsirkin" <mst@redhat.com>
To: Yi Liu <yi.l.liu@intel.com>
Cc: CLEMENT MATHIEU--DRIF <clement.mathieu--drif@eviden.com>,
"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>,
"joao.m.martins@oracle.com" <joao.m.martins@oracle.com>,
"peterx@redhat.com" <peterx@redhat.com>
Subject: Re: [PATCH v4 4/4] intel_iommu: make types match
Date: Sat, 20 Jul 2024 15:09:05 -0400 [thread overview]
Message-ID: <20240720150853-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240720144539-mutt-send-email-mst@kernel.org>
On Sat, Jul 20, 2024 at 02:46:14PM -0400, Michael S. Tsirkin wrote:
> On Mon, Jul 08, 2024 at 03:20:45PM +0800, Yi Liu wrote:
> > On 2024/7/5 19:01, CLEMENT MATHIEU--DRIF wrote:
> > > From: Clément Mathieu--Drif <clement.mathieu--drif@eviden.com>
> > >
> > > The 'level' field in vtd_iotlb_key is an unsigned integer.
> > > We don't need to store level as an int in vtd_lookup_iotlb.
> > >
> > > This is not an issue by itself, but using unsigned here seems cleaner.
> >
> > a nit to the subject. s/"make types match"/"make type match"/
>
> Hmm not sure I agree.
> There are two variables, they have types. We make them match.
ignore pls this is on old version
>
> > > Signed-off-by: Clément Mathieu--Drif <clement.mathieu--drif@eviden.com>
> > > ---
> > > hw/i386/intel_iommu.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/hw/i386/intel_iommu.c b/hw/i386/intel_iommu.c
> > > index 37c21a0aec..be0cb39b5c 100644
> > > --- a/hw/i386/intel_iommu.c
> > > +++ b/hw/i386/intel_iommu.c
> > > @@ -358,7 +358,7 @@ static VTDIOTLBEntry *vtd_lookup_iotlb(IntelIOMMUState *s, uint16_t source_id,
> > > {
> > > struct vtd_iotlb_key key;
> > > VTDIOTLBEntry *entry;
> > > - int level;
> > > + unsigned level;
> > > for (level = VTD_SL_PT_LEVEL; level < VTD_SL_PML4_LEVEL; level++) {
> > > key.gfn = vtd_get_iotlb_gfn(addr, level);
> >
> > --
> > Regards,
> > Yi Liu
next prev parent reply other threads:[~2024-07-20 19:09 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 [this message]
2024-07-20 18:44 ` [PATCH v4 0/4] VT-d minor fixes Michael S. Tsirkin
2024-07-20 19:08 ` 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=20240720150853-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).