From: Yi Liu <yi.l.liu@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
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>,
"joao.m.martins@oracle.com" <joao.m.martins@oracle.com>,
"peterx@redhat.com" <peterx@redhat.com>
Subject: Re: [PATCH v2 2/3] intel_iommu: make types match
Date: Fri, 5 Jul 2024 10:53:42 +0800 [thread overview]
Message-ID: <075d57d1-6ddf-4a78-a3af-aac585224075@intel.com> (raw)
In-Reply-To: <20240704180821-mutt-send-email-mst@kernel.org>
On 2024/7/5 06:13, Michael S. Tsirkin wrote:
> On Thu, Jul 04, 2024 at 03:12:48PM +0000, 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.
>>
>> VTDIOTLBPageInvInfo.mask is used in binary operations with addresses.
>
> this last sentence is a bit opaque. is there a bug ? E.g.
> can mask ever get so big it does not fit in u8?
yes, this looks to be a bug. It's initialized and used by below code.
The am is a u8. So it may make more sense to split this patch. One
is to make type match, another is to fix a bug.
info.mask = ~((1 << am) - 1);
uint64_t gfn = (info->addr >> VTD_PAGE_SHIFT_4K) & info->mask;
>> Signed-off-by: Clément Mathieu--Drif <clement.mathieu--drif@eviden.com>
>> ---
>> hw/i386/intel_iommu.c | 2 +-
>> hw/i386/intel_iommu_internal.h | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> 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);
>> diff --git a/hw/i386/intel_iommu_internal.h b/hw/i386/intel_iommu_internal.h
>> index cbc4030031..5fcbe2744f 100644
>> --- a/hw/i386/intel_iommu_internal.h
>> +++ b/hw/i386/intel_iommu_internal.h
>> @@ -436,7 +436,7 @@ struct VTDIOTLBPageInvInfo {
>> uint16_t domain_id;
>> uint32_t pasid;
>> uint64_t addr;
>> - uint8_t mask;
>> + uint64_t mask;
>> };
>> typedef struct VTDIOTLBPageInvInfo VTDIOTLBPageInvInfo;
>>
>> --
>> 2.45.2
>
--
Regards,
Yi Liu
next prev parent reply other threads:[~2024-07-05 2:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 15:12 [PATCH v2 0/3] VT-d minor fixes CLEMENT MATHIEU--DRIF
2024-07-04 15:12 ` [PATCH v2 1/3] intel_iommu: fix FRCD construction macro CLEMENT MATHIEU--DRIF
2024-07-05 3:08 ` Yi Liu
2024-07-04 15:12 ` [PATCH v2 2/3] intel_iommu: make types match CLEMENT MATHIEU--DRIF
2024-07-04 22:13 ` Michael S. Tsirkin
2024-07-05 2:53 ` Yi Liu [this message]
2024-07-04 15:12 ` [PATCH v2 3/3] intel_iommu: Bypass barrier wait descriptor CLEMENT MATHIEU--DRIF
2024-07-05 3:01 ` Yi Liu
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=075d57d1-6ddf-4a78-a3af-aac585224075@intel.com \
--to=yi.l.liu@intel.com \
--cc=clement.mathieu--drif@eviden.com \
--cc=jasowang@redhat.com \
--cc=joao.m.martins@oracle.com \
--cc=kevin.tian@intel.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).