From: Christoph Hellwig <hch@infradead.org>
To: Sherry Sun <sherry.sun@nxp.com>
Cc: hch@infradead.org, sudeep.dutt@intel.com,
ashutosh.dixit@intel.com, arnd@arndb.de,
gregkh@linuxfoundation.org, kishon@ti.com,
lorenzo.pieralisi@arm.com, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, linux-imx@nxp.com
Subject: Re: [PATCH V3 4/4] misc: vop: mapping kernel memory to user space as noncached
Date: Fri, 23 Oct 2020 10:28:37 +0100 [thread overview]
Message-ID: <20201023092837.GC29066@infradead.org> (raw)
In-Reply-To: <20201022050638.29641-5-sherry.sun@nxp.com>
On Thu, Oct 22, 2020 at 01:06:38PM +0800, Sherry Sun wrote:
> Mapping kernel space memory to user space as noncached, since user space
> need check the updates of avail_idx and device page flags timely.
>
> Signed-off-by: Joakim Zhang <qiangqing.zhang@nxp.com>
> Signed-off-by: Sherry Sun <sherry.sun@nxp.com>
> ---
> drivers/misc/mic/vop/vop_vringh.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/misc/mic/vop/vop_vringh.c b/drivers/misc/mic/vop/vop_vringh.c
> index b5612183dcb8..b75c2b713a3b 100644
> --- a/drivers/misc/mic/vop/vop_vringh.c
> +++ b/drivers/misc/mic/vop/vop_vringh.c
> @@ -1058,7 +1058,7 @@ static int vop_mmap(struct file *f, struct vm_area_struct *vma)
> }
> err = remap_pfn_range(vma, vma->vm_start + offset,
> pa >> PAGE_SHIFT, size,
> - vma->vm_page_prot);
> + pgprot_noncached(vma->vm_page_prot));
Again, memory allocated using dma_alloc_coherent can only be mapped
using dma_mmap_coherent, which will use the right attributes for the
mapping, which often are cached.
prev parent reply other threads:[~2020-10-23 9:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 5:06 [PATCH V3 0/4] Change vring space from nomal memory to dma coherent memory Sherry Sun
2020-10-22 5:06 ` [PATCH V3 1/4] misc: vop: change the way of allocating vring and device page Sherry Sun
2020-10-22 7:58 ` kernel test robot
2020-10-22 7:58 ` kernel test robot
2020-10-23 9:25 ` Christoph Hellwig
2020-10-26 2:54 ` Sherry Sun
2020-10-22 5:06 ` [PATCH V3 2/4] misc: vop: do not allocate and reassign the used ring Sherry Sun
2020-10-22 8:53 ` kernel test robot
2020-10-22 8:53 ` kernel test robot
2020-10-23 9:26 ` Christoph Hellwig
2020-10-26 3:04 ` Sherry Sun
2020-10-27 6:28 ` gregkh
2020-10-27 7:05 ` Sherry Sun
2020-10-27 15:11 ` Vincent Whitchurch
2020-10-28 1:47 ` Sherry Sun
[not found] ` <93bd1c60ea4d910489a7592200856eaf8022ced0.camel@intel.com>
2020-10-28 6:29 ` Sherry Sun
[not found] ` <CAK8P3a1JRx32VfFcwFpK0i6F5MQMCK-yCKw8=d_R08Y3iQ7wLQ@mail.gmail.com>
2020-10-28 15:50 ` Arnd Bergmann
2020-10-29 2:42 ` Sherry Sun
2020-10-29 9:20 ` Arnd Bergmann
2020-10-29 10:07 ` Vincent Whitchurch
2020-10-29 10:34 ` gregkh
2020-10-29 11:53 ` Arnd Bergmann
2020-10-29 13:35 ` Dixit, Ashutosh
2020-10-29 13:54 ` Arnd Bergmann
2020-10-29 13:23 ` Dixit, Ashutosh
2020-10-28 9:14 ` Vincent Whitchurch
2020-10-22 5:06 ` [PATCH V3 3/4] misc: vop: simply return the saved dma address instead of virt_to_phys Sherry Sun
2020-10-22 5:06 ` [PATCH V3 4/4] misc: vop: mapping kernel memory to user space as noncached Sherry Sun
2020-10-23 9:28 ` Christoph Hellwig [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201023092837.GC29066@infradead.org \
--to=hch@infradead.org \
--cc=arnd@arndb.de \
--cc=ashutosh.dixit@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=sherry.sun@nxp.com \
--cc=sudeep.dutt@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.