* [PATCH] x86: fix movdir64b() sparse warning
@ 2021-01-06 20:40 Dave Jiang
2021-01-06 20:59 ` Dan Williams
0 siblings, 1 reply; 3+ messages in thread
From: Dave Jiang @ 2021-01-06 20:40 UTC (permalink / raw)
To: bp, x86
Cc: kernel test robot, Ben Widawsky, dan.j.williams, ben.widawsky,
tglx, mingo, hpa, linux-kernel
Add missing __iomem anotation to address sparse warning.
"sparse warnings: (new ones prefixed by >>)"
drivers/dma/idxd/submit.c: note: in included file (through include/linux/io.h, include/linux/pci.h):
>> arch/x86/include/asm/io.h:422:27: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *dst @@ got void [noderef] __iomem *dst @@
arch/x86/include/asm/io.h:422:27: sparse: expected void *dst
arch/x86/include/asm/io.h:422:27: sparse: got void [noderef] __iomem *dst
Fixes: 0888e1030d3e ("x86/asm: Carve out a generic movdir64b() helper for general usage")
Reported-by: kernel test robot <lkp@intel.com>
Reviewed-by: Ben Widawsky <ben.widawsky@intel.com>
Signed-off-by: Dave Jiang <dave.jiang@intel.com>
---
arch/x86/include/asm/special_insns.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/include/asm/special_insns.h b/arch/x86/include/asm/special_insns.h
index cc177b4431ae..4e234645f0c6 100644
--- a/arch/x86/include/asm/special_insns.h
+++ b/arch/x86/include/asm/special_insns.h
@@ -243,10 +243,10 @@ static inline void serialize(void)
}
/* The dst parameter must be 64-bytes aligned */
-static inline void movdir64b(void *dst, const void *src)
+static inline void movdir64b(void __iomem *dst, const void *src)
{
const struct { char _[64]; } *__src = src;
- struct { char _[64]; } *__dst = dst;
+ struct { char _[64]; } __iomem *__dst = dst;
/*
* MOVDIR64B %(rdx), rax.
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] x86: fix movdir64b() sparse warning
2021-01-06 20:40 [PATCH] x86: fix movdir64b() sparse warning Dave Jiang
@ 2021-01-06 20:59 ` Dan Williams
2021-01-06 21:04 ` Ben Widawsky
0 siblings, 1 reply; 3+ messages in thread
From: Dan Williams @ 2021-01-06 20:59 UTC (permalink / raw)
To: Dave Jiang
Cc: Borislav Petkov, X86 ML, kernel test robot, Ben Widawsky,
Thomas Gleixner, Ingo Molnar, H. Peter Anvin,
Linux Kernel Mailing List
On Wed, Jan 6, 2021 at 12:40 PM Dave Jiang <dave.jiang@intel.com> wrote:
>
> Add missing __iomem anotation to address sparse warning.
s/anotation/annotation/
>
> "sparse warnings: (new ones prefixed by >>)"
> drivers/dma/idxd/submit.c: note: in included file (through include/linux/io.h, include/linux/pci.h):
> >> arch/x86/include/asm/io.h:422:27: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *dst @@ got void [noderef] __iomem *dst @@
> arch/x86/include/asm/io.h:422:27: sparse: expected void *dst
> arch/x86/include/asm/io.h:422:27: sparse: got void [noderef] __iomem *dst
The sparse spew is somewhat interesting, but what would be more
helpful is explain the why. I.e. that existing and future users expect
to be passing an __iomem annotated pointer to this routine because...
<reasons go here>. Otherwise someone (reviewer / future git blame
user) might reasonably ask, "well, why is the driver passing an
__iomem annotated pointer in the first instance?".
To Ben's point you might also duplicate part of the comment from
movdir64b and say:
"Recall, from the comment in movdir64b @__dst must be supplied as an
lvalue because this tells the compiler what the object is (its size)
the instruction accesses. I.e., not the pointers but what they point
to, thus the deref'ing '*'."
With clarified changelog for both you can add:
Reviewed-by: Dan Williams <dan.j.williams@intel.com>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] x86: fix movdir64b() sparse warning
2021-01-06 20:59 ` Dan Williams
@ 2021-01-06 21:04 ` Ben Widawsky
0 siblings, 0 replies; 3+ messages in thread
From: Ben Widawsky @ 2021-01-06 21:04 UTC (permalink / raw)
To: Dan Williams
Cc: Dave Jiang, Borislav Petkov, X86 ML, kernel test robot,
Thomas Gleixner, Ingo Molnar, H. Peter Anvin,
Linux Kernel Mailing List
On 21-01-06 12:59:35, Dan Williams wrote:
> On Wed, Jan 6, 2021 at 12:40 PM Dave Jiang <dave.jiang@intel.com> wrote:
> >
> > Add missing __iomem anotation to address sparse warning.
>
> s/anotation/annotation/
>
> >
> > "sparse warnings: (new ones prefixed by >>)"
> > drivers/dma/idxd/submit.c: note: in included file (through include/linux/io.h, include/linux/pci.h):
> > >> arch/x86/include/asm/io.h:422:27: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *dst @@ got void [noderef] __iomem *dst @@
> > arch/x86/include/asm/io.h:422:27: sparse: expected void *dst
> > arch/x86/include/asm/io.h:422:27: sparse: got void [noderef] __iomem *dst
>
> The sparse spew is somewhat interesting, but what would be more
> helpful is explain the why. I.e. that existing and future users expect
> to be passing an __iomem annotated pointer to this routine because...
> <reasons go here>. Otherwise someone (reviewer / future git blame
> user) might reasonably ask, "well, why is the driver passing an
> __iomem annotated pointer in the first instance?".
>
> To Ben's point you might also duplicate part of the comment from
> movdir64b and say:
>
> "Recall, from the comment in movdir64b @__dst must be supplied as an
> lvalue because this tells the compiler what the object is (its size)
> the instruction accesses. I.e., not the pointers but what they point
> to, thus the deref'ing '*'."
Thanks for pasting this, I missed that. It still doesn't make sense to me why
the compiler needs to know this. I guess it makes sense to the rest of you.
>
> With clarified changelog for both you can add:
>
> Reviewed-by: Dan Williams <dan.j.williams@intel.com>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-01-06 21:04 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-06 20:40 [PATCH] x86: fix movdir64b() sparse warning Dave Jiang
2021-01-06 20:59 ` Dan Williams
2021-01-06 21:04 ` Ben Widawsky
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.