From: Yi Liu <yi.l.liu@intel.com>
To: Jason Wang <jasowang@redhat.com>
Cc: CLEMENT MATHIEU--DRIF <clement.mathieu--drif@eviden.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"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>,
"mst@redhat.com" <mst@redhat.com>
Subject: Re: [PATCH v4 1/4] intel_iommu: fix FRCD construction macro
Date: Tue, 9 Jul 2024 14:12:26 +0800 [thread overview]
Message-ID: <ede5f232-78b6-4a2e-b61a-ff2b56bd2ca5@intel.com> (raw)
In-Reply-To: <CACGkMEvwBvjRQ5tpJLCHRfL6FRQHEGrT+FD2v1GpAmt5EGJzhQ@mail.gmail.com>
On 2024/7/9 10:51, Jason Wang wrote:
> On Mon, Jul 8, 2024 at 3:04 PM Yi Liu <yi.l.liu@intel.com> wrote:
>>
>> On 2024/7/5 19:01, CLEMENT MATHIEU--DRIF wrote:
>>> From: Clément Mathieu--Drif <clement.mathieu--drif@eviden.com>
>>>
>>> The constant must be unsigned, otherwise the two's complement
>>> overrides the other fields when a PASID is present.
>>>
>>> Fixes: 1b2b12376c8a ("intel-iommu: PASID support")
>>>
>>
>> The extra line behind the "Fixes tag" is not needed.
>>
>>> Signed-off-by: Clément Mathieu--Drif <clement.mathieu--drif@eviden.com>
>>> Reviewed-by: Yi Liu <yi.l.liu@intel.com>
>>> Reviewed-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
>>> ---
>>> hw/i386/intel_iommu_internal.h | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/hw/i386/intel_iommu_internal.h b/hw/i386/intel_iommu_internal.h
>>> index f8cf99bddf..cbc4030031 100644
>>> --- a/hw/i386/intel_iommu_internal.h
>>> +++ b/hw/i386/intel_iommu_internal.h
>>> @@ -267,7 +267,7 @@
>>> /* For the low 64-bit of 128-bit */
>>> #define VTD_FRCD_FI(val) ((val) & ~0xfffULL)
>>> #define VTD_FRCD_PV(val) (((val) & 0xffffULL) << 40)
>>> -#define VTD_FRCD_PP(val) (((val) & 0x1) << 31)
>>> +#define VTD_FRCD_PP(val) (((val) & 0x1ULL) << 31)
>>> #define VTD_FRCD_IR_IDX(val) (((val) & 0xffffULL) << 48)
>>>
>>> /* DMA Remapping Fault Conditions */
>>
>> It might be fine to squash patch 02 of this series into this one. @Jason?
>
> Not sure, we may need this for -stable. So having a standalone patch
> doesn't hurt.
I see. :)
--
Regards,
Yi Liu
next prev parent reply other threads:[~2024-07-09 6:08 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 [this message]
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 ` [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=ede5f232-78b6-4a2e-b61a-ff2b56bd2ca5@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.