[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0ab42ae0-9323-9297-c2c8-1cfc1ebada08@gmail.com>
Date: Wed, 17 Nov 2021 21:32:13 +0800
From: Tianyu Lan <ltykernel@...il.com>
To: Christoph Hellwig <hch@....de>
Cc: dave.hansen@...ux.intel.com, luto@...nel.org, peterz@...radead.org,
tglx@...utronix.de, mingo@...hat.com, bp@...en8.de, x86@...nel.org,
hpa@...or.com, jgross@...e.com, sstabellini@...nel.org,
boris.ostrovsky@...cle.com, kys@...rosoft.com,
haiyangz@...rosoft.com, sthemmin@...rosoft.com, wei.liu@...nel.org,
decui@...rosoft.com, joro@...tes.org, will@...nel.org,
davem@...emloft.net, kuba@...nel.org, jejb@...ux.ibm.com,
martin.petersen@...cle.com, m.szyprowski@...sung.com,
robin.murphy@....com, xen-devel@...ts.xenproject.org,
michael.h.kelley@...rosoft.com,
Tianyu Lan <Tianyu.Lan@...rosoft.com>,
iommu@...ts.linux-foundation.org, linux-hyperv@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
netdev@...r.kernel.org, vkuznets@...hat.com, brijesh.singh@....com,
konrad.wilk@...cle.com, parri.andrea@...il.com,
thomas.lendacky@....com, dave.hansen@...el.com
Subject: Re: [PATCH 1/5] x86/Swiotlb: Add Swiotlb bounce buffer remap function
for HV IVM
Hi Christoph:
Thanks for your review.
On 11/17/2021 5:59 PM, Christoph Hellwig wrote:
> The subject is wrong, nothing x86-specific here. Please use
> "swiotlb: " as the prefix
OK. Will update. Thanks.
>
>> + * @vaddr: The vaddr of the swiotlb memory pool. The swiotlb
>> + * memory pool may be remapped in the memory encrypted case and store
>
> Please avoid the overly long line. >
>> + /*
>> + * With swiotlb_unencrypted_base setting, swiotlb bounce buffer will
>> + * be remapped in the swiotlb_update_mem_attributes() and return here
>> + * directly.
>> + */
>
> I'd word this as:
>
> /*
> * If swiotlb_unencrypted_base is set, the bounce buffer memory will
> * be remapped and cleared in swiotlb_update_mem_attributes.
> */
Thanks for suggestion. Will update. Thanks.
>> + ret = swiotlb_init_io_tlb_mem(mem, __pa(tlb), nslabs, false);
>> + if (ret) {
>> + memblock_free(mem->slots, alloc_size);
>> + return ret;
>> + }
>
> With the latest update swiotlb_init_io_tlb_mem will always return 0,
> so no need for the return value change or error handling here.
>
OK. Will revert the change.
Powered by blists - more mailing lists