Wei, this is one of the Hyper-V code improvement tasks that Michael Kelley
identified.
Using memremap() is the right thing to do here. Abhinav Singh (cc'ed) also
tried to fix this earlier as there are sparse warnings with ioremap_cache().
On Sun, Nov 12, 2023 at 11:12:33PM +, Wei Liu wrote:
>
On Wed, Nov 01, 2023 at 09:01:48AM -0700, Nischala Yelchuri wrote:
> Current Hyper-V code for CoCo VMs uses ioremap_cache() to map normal memory
> as decrypted.
> ioremap_cache() is ideally used to map I/O device memory when it has the
> characteristics
> of normal memory. It should not be used t
From: Nischala Yelchuri Sent: Wednesday,
November 1, 2023 9:02 AM
>
It's customary for the patch "Subject:" line to have a prefix indicating the
area of the code being modified. This patch touches on multiple Hyper-V
drivers, so there's not a clear choice for prefix. I would suggest using
"Dri
Current Hyper-V code for CoCo VMs uses ioremap_cache() to map normal memory as
decrypted.
ioremap_cache() is ideally used to map I/O device memory when it has the
characteristics
of normal memory. It should not be used to map normal memory as the returned
pointer
has the __iomem attribute.
Fix
