[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aMl1lCvuKQFfOhNb@google.com>
Date: Tue, 16 Sep 2025 14:35:00 +0000
From: Mostafa Saleh <smostafa@...gle.com>
To: Daniel Mentz <danielmentz@...gle.com>
Cc: linux-kernel@...r.kernel.org, kvmarm@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org, iommu@...ts.linux.dev,
maz@...nel.org, oliver.upton@...ux.dev, joey.gouly@....com,
suzuki.poulose@....com, yuzenghui@...wei.com,
catalin.marinas@....com, will@...nel.org, robin.murphy@....com,
jean-philippe@...aro.org, qperret@...gle.com, tabba@...gle.com,
jgg@...pe.ca, mark.rutland@....com, praan@...gle.com
Subject: Re: [PATCH v4 16/28] iommu/arm-smmu-v3-kvm: Create array for hyp
SMMUv3
On Tue, Sep 09, 2025 at 11:30:48AM -0700, Daniel Mentz wrote:
> On Tue, Aug 19, 2025 at 2:55 PM Mostafa Saleh <smostafa@...gle.com> wrote:
> >
> > + if (kvm_arm_smmu_array[i].mmio_size < SZ_128K) {
> > + pr_err("SMMUv3(%s) has unsupported size(0x%lx)\n", np->name,
> > + kvm_arm_smmu_array[i].mmio_size);
>
> Use format specifier %pOF to print device tree node.
> If mmio_size is a size_t type, use format specifier %zx.
> Align language of error message with kernel driver which prints "MMIO
> region too small (%pr)\n".
Thanks for catching that, I will fix it in v5.
> I'm wondering if we should use kvm_err instead of pr_err.
I am not sure, kvm_err seems to be used from core arch code only, but
I don't see why not.
Thanks,
Mostafa
Powered by blists - more mailing lists