[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZVFb4f8IRJeCFmYD@liuwe-devbox-debian-v2>
Date: Sun, 12 Nov 2023 23:12:33 +0000
From: Wei Liu <wei.liu@...nel.org>
To: Nischala Yelchuri <niyelchu@...ux.microsoft.com>
Cc: linux-kernel@...r.kernel.org, linux-hyperv@...r.kernel.org,
linux-fbdev@...r.kernel.org, kys@...rosoft.com,
haiyangz@...rosoft.com, wei.liu@...nel.org, decui@...rosoft.com,
tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
drawat.floss@...il.com, maarten.lankhorst@...ux.intel.com,
mripard@...nel.org, tzimmermann@...e.de, airlied@...il.com,
daniel@...ll.ch, dri-devel@...ts.freedesktop.org, deller@....de,
mhklinux@...look.com, mhkelley@...look.com,
singhabhinav9051571833@...il.com, niyelchu@...rosoft.com
Subject: Re: [PATCH] Replace ioremap_cache() with memremap()
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 to map normal memory as the returned pointer
> has the __iomem attribute.
Do you find any real world issues with the current code? How do you
discover these issues?
Thanks,
Wei.
Powered by blists - more mailing lists