xen: dma-buf support for grant device
Subsystems (2)
v2 cover xen: dma-buf support for grant device
From: Oleksandr Andrushchenko <[email protected]>
This work is in response to my previous attempt to introduce Xen/DRM zero-copy driver [1] to enable Linux dma-buf API [2] for Xen based frontends/backends. There is also an existing hyper_dmabuf approach available [3] which, if reworked to utilize the proposed solution, can greatly benefit as well.
RFC for this series was published and discussed [9], comments addressed.
The original rationale behind this work was to enable zero-copying use-cases while working with Xen para-virtual display driver [4]:
when using Xen PV DRM frontend driver then on backend side one will need to do copying of display buffers' contents (filled by the frontend's user-space) into buffers allocated at the backend side. Taking into account the size of display buffers and frames per second it may result in unneeded huge data bus occupation and performance loss.
The helper driver [4] allows implementing zero-copying use-cases when using Xen para-virtualized frontend display driver by implementing a DRM/KMS helper driver running on backend's side.
It utilizes PRIME buffers API (implemented on top of Linux dma-buf) to share frontend's buffers with physical device drivers on backend's side:
- a dumb buffer created on backend's side can be shared with the Xen PV frontend driver, so it directly writes into backend's domain memory (into the buffer exported from DRM/KMS driver of a physical display device)
- a dumb buffer allocated by the frontend can be imported into physical device DRM/KMS driver, thus allowing to achieve no copying as well
Finally, it was discussed and decided ([1], [5]) that it is worth implementing such use-cases via extension of the existing Xen gntdev driver instead of introducing new DRM specific driver. Please note, that the support of dma-buf is Linux only, as dma-buf is a Linux only thing.
Now to the proposed solution. The changes to the existing Xen drivers in the Linux kernel fall into 2 categories:
1. DMA-able memory buffer allocation and increasing/decreasing memory reservation of the pages of such a buffer.
This is required if we are about to share dma-buf with the hardware that does require those to be allocated with dma_alloc_xxx API. (It is still possible to allocate a dma-buf from any system memory, e.g. system pages).
2. Extension of the gntdev driver to enable it to import/export dma-buf’s.
The first five patches are in preparation for Xen dma-buf support, but I consider those usable regardless of the dma-buf use-case, e.g. other frontend/backend kernel modules may also benefit from these for better code reuse:
0001-xen-grant-table-Export-gnttab_-alloc-free-_pages-as-.patch
0002-xen-grant-table-Make-set-clear-page-private-code-sha.patch
0003-xen-balloon-Share-common-memory-reservation-routines.patch
0004-xen-grant-table-Allow-allocating-buffers-suitable-fo.patch
0005-xen-gntdev-Allow-mappings-for-DMA-buffers.patchThe next three patches are Xen implementation of dma-buf as part of the grant device:
0006-xen-gntdev-Add-initial-support-for-dma-buf-UAPI.patch 0007-xen-gntdev-Implement-dma-buf-export-functionality.patch 0008-xen-gntdev-Implement-dma-buf-import-functionality.patch
The last patch makes it possible for in-kernel use of Xen dma-buf API:
0009-xen-gntdev-Expose-gntdev-s-dma-buf-API-for-in-kernel.patch
The corresponding libxengnttab changes are available at [6].
All the above was tested with display backend [7] and its accompanying helper library [8] on Renesas ARM64 based board.
Basic balloon tests on x86.
*To all the communities*: I would like to ask you to review the proposed solution and give feedback on it, so I can improve and send final patches for review (this is still work in progress, but enough to start discussing the implementation).
Thank you in advance,
Oleksandr Andrushchenko
[1] https://lists.freedesktop.org/archives/dri-devel/2018-April/173163.html
[2] https://elixir.bootlin.com/linux/v4.17-rc5/source/Documentation/driver-api/dma-buf.rst
[3] https://lists.xenproject.org/archives/html/xen-devel/2018-02/msg01202.html
[4] https://cgit.freedesktop.org/drm/drm-misc/tree/drivers/gpu/drm/xen
[5] https://patchwork.kernel.org/patch/10279681/
[6] https://github.com/andr2000/xen/tree/xen_dma_buf_v1
[7] https://github.com/andr2000/displ_be/tree/xen_dma_buf_v1
[8] https://github.com/andr2000/libxenbe/tree/xen_dma_buf_v1
[9] https://lkml.org/lkml/2018/5/17/215
Changes since v1:
*****************
- Define GNTDEV_DMA_FLAG_XXX starting from bit 0
- Rename mem_reservation.h to mem-reservation.h
- Remove usless comments
- Change licenses from GPLv2 OR MIT to GPLv2 only
- Make xenmem_reservation_va_mapping_{update|clear} inline
- Change EXPORT_SYMBOL to EXPORT_SYMBOL_GPL for new functions
- Make gnttab_dma_{alloc|free}_pages to request frames array
be allocated outside
- Fixe gnttab_dma_alloc_pages fail path (added xenmem_reservation_increase)
- Move most of dma-buf from gntdev.c to gntdev-dmabuf.c
- Add required dependencies to Kconfig
- Rework "#ifdef CONFIG_XEN_XXX" for if/else
- Export gnttab_{alloc|free}_pages as GPL symbols (patch 1)
Oleksandr Andrushchenko (9):
xen/grant-table: Export gnttab_{alloc|free}_pages as GPL xen/grant-table: Make set/clear page private code shared xen/balloon: Share common memory reservation routines xen/grant-table: Allow allocating buffers suitable for DMA xen/gntdev: Allow mappings for DMA buffers xen/gntdev: Add initial support for dma-buf UAPI xen/gntdev: Implement dma-buf export functionality xen/gntdev: Implement dma-buf import functionality xen/gntdev: Expose gntdev's dma-buf API for in-kernel use
drivers/xen/Kconfig | 23 ++ drivers/xen/Makefile | 2 + drivers/xen/balloon.c | 71 +--- drivers/xen/gntdev-dmabuf.c | 707 ++++++++++++++++++++++++++++++++++ drivers/xen/gntdev-dmabuf.h | 48 +++ drivers/xen/gntdev.c | 387 ++++++++++++++++++- drivers/xen/grant-table.c | 165 +++++++- drivers/xen/mem-reservation.c | 120 ++++++ include/uapi/xen/gntdev.h | 106 +++++ include/xen/grant_dev.h | 37 ++ include/xen/grant_table.h | 21 + include/xen/mem-reservation.h | 65 ++++ 12 files changed, 1647 insertions(+), 105 deletions(-) create mode 100644 drivers/xen/gntdev-dmabuf.c create mode 100644 drivers/xen/gntdev-dmabuf.h create mode 100644 drivers/xen/mem-reservation.c create mode 100644 include/xen/grant_dev.h create mode 100644 include/xen/mem-reservation.h
Signature · 6 lines
2.17.0 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH v2 1/9 xen/grant-table: Export gnttab_{alloc|free}_pages as GPL
From: Oleksandr Andrushchenko <[email protected]>
Only gnttab_{alloc|free}_pages are exported as EXPORT_SYMBOL while all the rest are exported as EXPORT_SYMBOL_GPL, thus effectively making it not possible for non-GPL driver modules to use grant table module. Export gnttab_{alloc|free}_pages as EXPORT_SYMBOL_GPL so all the exports are aligned.
--- drivers/xen/grant-table.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/xen/grant-table.c +2 -2
@@ -799,7 +799,7 @@ int gnttab_alloc_pages(int nr_pages, struct page **pages)return 0 ; } -EXPORT_SYMBOL (gnttab_alloc_pages); +EXPORT_SYMBOL_GPL (gnttab_alloc_pages);/** * gnttab_free_pages - free pages allocated by gnttab_alloc_pages()
@@ -820,7 +820,7 @@ void gnttab_free_pages(int nr_pages, struct page **pages) }free_xenballooned_pages (nr_pages, pages); } -EXPORT_SYMBOL (gnttab_free_pages); +EXPORT_SYMBOL_GPL (gnttab_free_pages);/* Handling of paged out grant targets (GNTST_eagain) */ #define MAX_DELAY 256
Signature · 6 lines
2.17.0 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 1/9] xen/grant-table: Export gnttab_{alloc|free}_pages as GPL
Quoted 9 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Only gnttab_{alloc|free}_pages are exported as
EXPORT_SYMBOLwhile all the rest are exported asEXPORT_SYMBOL_GPL, thus effectively making it not possible for non-GPL driver modules to use grant table module. Export gnttab_{alloc|free}_pages asEXPORT_SYMBOL_GPLso all the exports are aligned.Signed-off-by Oleksandr Andrushchenko <[email protected]>
Juergen
Re: [PATCH v2 1/9] xen/grant-table: Export gnttab_{alloc|free}_pages as GPL
In reply to Oleksandr AndrushchenkoQuoted 9 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Only gnttab_{alloc|free}_pages are exported as
EXPORT_SYMBOLwhile all the rest are exported asEXPORT_SYMBOL_GPL, thus effectively making it not possible for non-GPL driver modules to use grant table module. Export gnttab_{alloc|free}_pages asEXPORT_SYMBOL_GPLso all the exports are aligned.Signed-off-by Oleksandr Andrushchenko <[email protected]>
Juergen
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 1/9] xen/grant-table: Export gnttab_{alloc|free}_pages as GPL
In reply to Oleksandr AndrushchenkoQuoted 9 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Only gnttab_{alloc|free}_pages are exported as
EXPORT_SYMBOLwhile all the rest are exported asEXPORT_SYMBOL_GPL, thus effectively making it not possible for non-GPL driver modules to use grant table module. Export gnttab_{alloc|free}_pages asEXPORT_SYMBOL_GPLso all the exports are aligned.Signed-off-by Oleksandr Andrushchenko <[email protected]>
Pushed to xen/tip.git for-linus-4.18
Juergen
Re: [PATCH v2 1/9] xen/grant-table: Export gnttab_{alloc|free}_pages as GPL
In reply to Oleksandr AndrushchenkoQuoted 9 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Only gnttab_{alloc|free}_pages are exported as
EXPORT_SYMBOLwhile all the rest are exported asEXPORT_SYMBOL_GPL, thus effectively making it not possible for non-GPL driver modules to use grant table module. Export gnttab_{alloc|free}_pages asEXPORT_SYMBOL_GPLso all the exports are aligned.Signed-off-by Oleksandr Andrushchenko <[email protected]>
Pushed to xen/tip.git for-linus-4.18
Juergen
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v2 1/9 xen/grant-table: Export gnttab_{alloc|free}_pages as GPL
In reply to Oleksandr AndrushchenkoFrom: Oleksandr Andrushchenko <[email protected]>
Only gnttab_{alloc|free}_pages are exported as EXPORT_SYMBOL while all the rest are exported as EXPORT_SYMBOL_GPL, thus effectively making it not possible for non-GPL driver modules to use grant table module. Export gnttab_{alloc|free}_pages as EXPORT_SYMBOL_GPL so all the exports are aligned.
--- drivers/xen/grant-table.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/xen/grant-table.c +2 -2
@@ -799,7 +799,7 @@ int gnttab_alloc_pages(int nr_pages, struct page **pages)return 0 ; } -EXPORT_SYMBOL (gnttab_alloc_pages); +EXPORT_SYMBOL_GPL (gnttab_alloc_pages);/** * gnttab_free_pages - free pages allocated by gnttab_alloc_pages()
@@ -820,7 +820,7 @@ void gnttab_free_pages(int nr_pages, struct page **pages) }free_xenballooned_pages (nr_pages, pages); } -EXPORT_SYMBOL (gnttab_free_pages); +EXPORT_SYMBOL_GPL (gnttab_free_pages);/* Handling of paged out grant targets (GNTST_eagain) */ #define MAX_DELAY 256
Signature · 7 lines
2.17.0 _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v2 2/9 xen/grant-table: Make set/clear page private code shared
In reply to Oleksandr AndrushchenkoFrom: Oleksandr Andrushchenko <[email protected]>
Make set/clear page private code shared and accessible to other kernel modules which can re-use these instead of open-coding.
--- drivers/xen/grant-table.c | 54 +++++++++++++++++++++++++-------------- include/xen/grant_table.h | 3 +++ 2 files changed, 38 insertions(+), 19 deletions(-)
drivers/xen/grant-table.c +35 -19
@@ -769,29 +769,18 @@ void gnttab_free_auto_xlat_frames(void) }EXPORT_SYMBOL_GPL (gnttab_free_auto_xlat_frames); -/** -* gnttab_alloc_pages - alloc pages suitable for grant mapping into -* @nr_pages: number of pages to alloc -* @pages: returns the pages -*/ -int gnttab_alloc_pages (int nr_pages,struct page **pages) +int gnttab_pages_set_private (int nr_pages,struct page **pages) {int i; -int ret; - - ret =alloc_xenballooned_pages (nr_pages, pages); -if (ret <0 ) -return ret;for (i =0 ; i < nr_pages; i++) {#if BITS_PER_LONG <64 struct xen_page_foreign *foreign; foreign =kzalloc (sizeof (*foreign),GFP_KERNEL ); -if (!foreign) { -gnttab_free_pages (nr_pages, pages); +if (!foreign)return -ENOMEM ; - } +set_page_private (pages[i], (unsigned long )foreign);#endif SetPagePrivate (pages[i]);
@@ -799,14 +788,30 @@ int gnttab_alloc_pages(int nr_pages, struct page **pages)return 0 ; } -EXPORT_SYMBOL_GPL (gnttab_alloc_pages); +EXPORT_SYMBOL_GPL (gnttab_pages_set_private);/** -* gnttab_free_pages - free pages allocated by gnttab_alloc_pages() -* @nr_pages; number of pages to free -* @pages: the pages +* gnttab_alloc_pages - alloc pages suitable for grant mapping into +* @nr_pages: number of pages to alloc +* @pages: returns the pages */ -void gnttab_free_pages (int nr_pages,struct page **pages) +int gnttab_alloc_pages (int nr_pages,struct page **pages) +{ +int ret; + + ret =alloc_xenballooned_pages (nr_pages, pages); +if (ret <0 ) +return ret; + + ret =gnttab_pages_set_private (nr_pages, pages); +if (ret <0 ) +gnttab_free_pages (nr_pages, pages); + +return ret; +} +EXPORT_SYMBOL_GPL (gnttab_alloc_pages); + +void gnttab_pages_clear_private (int nr_pages,struct page **pages) {int i;
@@ -818,6 +823,17 @@ void gnttab_free_pages(int nr_pages, struct page **pages)ClearPagePrivate (pages[i]); } } +} +EXPORT_SYMBOL_GPL (gnttab_pages_clear_private); + +/** +* gnttab_free_pages - free pages allocated by gnttab_alloc_pages() +* @nr_pages; number of pages to free +* @pages: the pages +*/ +void gnttab_free_pages (int nr_pages,struct page **pages) +{ +gnttab_pages_clear_private (nr_pages, pages);free_xenballooned_pages (nr_pages, pages); }EXPORT_SYMBOL_GPL (gnttab_free_pages);
include/xen/grant_table.h +3 -0
@@ -198,6 +198,9 @@ void gnttab_free_auto_xlat_frames(void);int gnttab_alloc_pages (int nr_pages,struct page **pages);void gnttab_free_pages (int nr_pages,struct page **pages); +int gnttab_pages_set_private (int nr_pages,struct page **pages); +void gnttab_pages_clear_private (int nr_pages,struct page **pages); +int gnttab_map_refs (struct gnttab_map_grant_ref *map_ops,struct gnttab_map_grant_ref *kmap_ops,struct page **pages,unsigned int count);
Signature · 6 lines
2.17.0 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 2/9] xen/grant-table: Make set/clear page private code shared
Boris, I dropped your r-b for this patch as I changed
EXPORT_SYMBOL to EXPORT_SYMBOL_GPL as Juergen requested
Quoted 107 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Make set/clear page private code shared and accessible to other kernel modules which can re-use these instead of open-coding.
Signed-off-by Oleksandr Andrushchenko <[email protected]>--- drivers/xen/grant-table.c | 54 +++++++++++++++++++++++++-------------- include/xen/grant_table.h | 3 +++ 2 files changed, 38 insertions(+), 19 deletions(-)drivers/xen/grant-table.c +35
-19@@ -769,29 +769,18 @@ void gnttab_free_auto_xlat_frames(void) }EXPORT_SYMBOL_GPL (gnttab_free_auto_xlat_frames); -/** -* gnttab_alloc_pages - alloc pages suitable for grant mapping into -* @nr_pages: number of pages to alloc -* @pages: returns the pages -*/ -int gnttab_alloc_pages (int nr_pages,struct page **pages) +int gnttab_pages_set_private (int nr_pages,struct page **pages) {int i; -int ret; - - ret =alloc_xenballooned_pages (nr_pages, pages); -if (ret <0 ) -return ret;for (i =0 ; i < nr_pages; i++) {#if BITS_PER_LONG <64 struct xen_page_foreign *foreign; foreign =kzalloc (sizeof (*foreign),GFP_KERNEL ); -if (!foreign) { -gnttab_free_pages (nr_pages, pages); +if (!foreign)return -ENOMEM ; - } +set_page_private (pages[i], (unsigned long )foreign);#endif SetPagePrivate (pages[i]);@@ -799,14 +788,30 @@ int gnttab_alloc_pages(int nr_pages, struct page **pages)return 0 ; } -EXPORT_SYMBOL_GPL (gnttab_alloc_pages); +EXPORT_SYMBOL_GPL (gnttab_pages_set_private);/** -* gnttab_free_pages - free pages allocated by gnttab_alloc_pages() -* @nr_pages; number of pages to free -* @pages: the pages +* gnttab_alloc_pages - alloc pages suitable for grant mapping into +* @nr_pages: number of pages to alloc +* @pages: returns the pages */ -void gnttab_free_pages (int nr_pages,struct page **pages) +int gnttab_alloc_pages (int nr_pages,struct page **pages) +{ +int ret; + + ret =alloc_xenballooned_pages (nr_pages, pages); +if (ret <0 ) +return ret; + + ret =gnttab_pages_set_private (nr_pages, pages); +if (ret <0 ) +gnttab_free_pages (nr_pages, pages); + +return ret; +} +EXPORT_SYMBOL_GPL (gnttab_alloc_pages); + +void gnttab_pages_clear_private (int nr_pages,struct page **pages) {int i;@@ -818,6 +823,17 @@ void gnttab_free_pages(int nr_pages, struct page **pages)ClearPagePrivate (pages[i]); } } +} +EXPORT_SYMBOL_GPL (gnttab_pages_clear_private); + +/** +* gnttab_free_pages - free pages allocated by gnttab_alloc_pages() +* @nr_pages; number of pages to free +* @pages: the pages +*/ +void gnttab_free_pages (int nr_pages,struct page **pages) +{ +gnttab_pages_clear_private (nr_pages, pages);free_xenballooned_pages (nr_pages, pages); }EXPORT_SYMBOL_GPL (gnttab_free_pages);include/xen/grant_table.h +0
-0
include/xen/grant_table.h void gnttab_free_auto_xlat_frames(void); · line 206
Quoted 9 lines
include/xen/grant_table.h +3
-0@@ -198,6 +198,9 @@ void gnttab_free_auto_xlat_frames(void);int gnttab_alloc_pages (int nr_pages,struct page **pages);void gnttab_free_pages (int nr_pages,struct page **pages); +int gnttab_pages_set_private (int nr_pages,struct page **pages); +void gnttab_pages_clear_private (int nr_pages,struct page **pages); +int gnttab_map_refs (struct gnttab_map_grant_ref *map_ops,struct gnttab_map_grant_ref *kmap_ops,struct page **pages,unsigned int count);
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 2/9] xen/grant-table: Make set/clear page private code shared
In reply to Oleksandr AndrushchenkoBoris, I dropped your r-b for this patch as I changed
EXPORT_SYMBOL to EXPORT_SYMBOL_GPL as Juergen requested
Quoted 107 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Make set/clear page private code shared and accessible to other kernel modules which can re-use these instead of open-coding.
Signed-off-by Oleksandr Andrushchenko <[email protected]>--- drivers/xen/grant-table.c | 54 +++++++++++++++++++++++++-------------- include/xen/grant_table.h | 3 +++ 2 files changed, 38 insertions(+), 19 deletions(-)drivers/xen/grant-table.c +35
-19@@ -769,29 +769,18 @@ void gnttab_free_auto_xlat_frames(void) }EXPORT_SYMBOL_GPL (gnttab_free_auto_xlat_frames); -/** -* gnttab_alloc_pages - alloc pages suitable for grant mapping into -* @nr_pages: number of pages to alloc -* @pages: returns the pages -*/ -int gnttab_alloc_pages (int nr_pages,struct page **pages) +int gnttab_pages_set_private (int nr_pages,struct page **pages) {int i; -int ret; - - ret =alloc_xenballooned_pages (nr_pages, pages); -if (ret <0 ) -return ret;for (i =0 ; i < nr_pages; i++) {#if BITS_PER_LONG <64 struct xen_page_foreign *foreign; foreign =kzalloc (sizeof (*foreign),GFP_KERNEL ); -if (!foreign) { -gnttab_free_pages (nr_pages, pages); +if (!foreign)return -ENOMEM ; - } +set_page_private (pages[i], (unsigned long )foreign);#endif SetPagePrivate (pages[i]);@@ -799,14 +788,30 @@ int gnttab_alloc_pages(int nr_pages, struct page **pages)return 0 ; } -EXPORT_SYMBOL_GPL (gnttab_alloc_pages); +EXPORT_SYMBOL_GPL (gnttab_pages_set_private);/** -* gnttab_free_pages - free pages allocated by gnttab_alloc_pages() -* @nr_pages; number of pages to free -* @pages: the pages +* gnttab_alloc_pages - alloc pages suitable for grant mapping into +* @nr_pages: number of pages to alloc +* @pages: returns the pages */ -void gnttab_free_pages (int nr_pages,struct page **pages) +int gnttab_alloc_pages (int nr_pages,struct page **pages) +{ +int ret; + + ret =alloc_xenballooned_pages (nr_pages, pages); +if (ret <0 ) +return ret; + + ret =gnttab_pages_set_private (nr_pages, pages); +if (ret <0 ) +gnttab_free_pages (nr_pages, pages); + +return ret; +} +EXPORT_SYMBOL_GPL (gnttab_alloc_pages); + +void gnttab_pages_clear_private (int nr_pages,struct page **pages) {int i;@@ -818,6 +823,17 @@ void gnttab_free_pages(int nr_pages, struct page **pages)ClearPagePrivate (pages[i]); } } +} +EXPORT_SYMBOL_GPL (gnttab_pages_clear_private); + +/** +* gnttab_free_pages - free pages allocated by gnttab_alloc_pages() +* @nr_pages; number of pages to free +* @pages: the pages +*/ +void gnttab_free_pages (int nr_pages,struct page **pages) +{ +gnttab_pages_clear_private (nr_pages, pages);free_xenballooned_pages (nr_pages, pages); }EXPORT_SYMBOL_GPL (gnttab_free_pages);include/xen/grant_table.h +0
-0
include/xen/grant_table.h void gnttab_free_auto_xlat_frames(void); · line 206
Quoted 9 lines
include/xen/grant_table.h +3
-0@@ -198,6 +198,9 @@ void gnttab_free_auto_xlat_frames(void);int gnttab_alloc_pages (int nr_pages,struct page **pages);void gnttab_free_pages (int nr_pages,struct page **pages); +int gnttab_pages_set_private (int nr_pages,struct page **pages); +void gnttab_pages_clear_private (int nr_pages,struct page **pages); +int gnttab_map_refs (struct gnttab_map_grant_ref *map_ops,struct gnttab_map_grant_ref *kmap_ops,struct page **pages,unsigned int count);
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 2/9] xen/grant-table: Make set/clear page private code shared
In reply to Oleksandr AndrushchenkoQuoted 6 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Make set/clear page private code shared and accessible to other kernel modules which can re-use these instead of open-coding.
Signed-off-by Oleksandr Andrushchenko <[email protected]>
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 2/9] xen/grant-table: Make set/clear page private code shared
In reply to Oleksandr AndrushchenkoQuoted 6 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Make set/clear page private code shared and accessible to other kernel modules which can re-use these instead of open-coding.
Signed-off-by Oleksandr Andrushchenko <[email protected]>
PATCH v2 2/9 xen/grant-table: Make set/clear page private code shared
In reply to Oleksandr AndrushchenkoFrom: Oleksandr Andrushchenko <[email protected]>
Make set/clear page private code shared and accessible to other kernel modules which can re-use these instead of open-coding.
--- drivers/xen/grant-table.c | 54 +++++++++++++++++++++++++-------------- include/xen/grant_table.h | 3 +++ 2 files changed, 38 insertions(+), 19 deletions(-)
drivers/xen/grant-table.c +35 -19
@@ -769,29 +769,18 @@ void gnttab_free_auto_xlat_frames(void) }EXPORT_SYMBOL_GPL (gnttab_free_auto_xlat_frames); -/** -* gnttab_alloc_pages - alloc pages suitable for grant mapping into -* @nr_pages: number of pages to alloc -* @pages: returns the pages -*/ -int gnttab_alloc_pages (int nr_pages,struct page **pages) +int gnttab_pages_set_private (int nr_pages,struct page **pages) {int i; -int ret; - - ret =alloc_xenballooned_pages (nr_pages, pages); -if (ret <0 ) -return ret;for (i =0 ; i < nr_pages; i++) {#if BITS_PER_LONG <64 struct xen_page_foreign *foreign; foreign =kzalloc (sizeof (*foreign),GFP_KERNEL ); -if (!foreign) { -gnttab_free_pages (nr_pages, pages); +if (!foreign)return -ENOMEM ; - } +set_page_private (pages[i], (unsigned long )foreign);#endif SetPagePrivate (pages[i]);
@@ -799,14 +788,30 @@ int gnttab_alloc_pages(int nr_pages, struct page **pages)return 0 ; } -EXPORT_SYMBOL_GPL (gnttab_alloc_pages); +EXPORT_SYMBOL_GPL (gnttab_pages_set_private);/** -* gnttab_free_pages - free pages allocated by gnttab_alloc_pages() -* @nr_pages; number of pages to free -* @pages: the pages +* gnttab_alloc_pages - alloc pages suitable for grant mapping into +* @nr_pages: number of pages to alloc +* @pages: returns the pages */ -void gnttab_free_pages (int nr_pages,struct page **pages) +int gnttab_alloc_pages (int nr_pages,struct page **pages) +{ +int ret; + + ret =alloc_xenballooned_pages (nr_pages, pages); +if (ret <0 ) +return ret; + + ret =gnttab_pages_set_private (nr_pages, pages); +if (ret <0 ) +gnttab_free_pages (nr_pages, pages); + +return ret; +} +EXPORT_SYMBOL_GPL (gnttab_alloc_pages); + +void gnttab_pages_clear_private (int nr_pages,struct page **pages) {int i;
@@ -818,6 +823,17 @@ void gnttab_free_pages(int nr_pages, struct page **pages)ClearPagePrivate (pages[i]); } } +} +EXPORT_SYMBOL_GPL (gnttab_pages_clear_private); + +/** +* gnttab_free_pages - free pages allocated by gnttab_alloc_pages() +* @nr_pages; number of pages to free +* @pages: the pages +*/ +void gnttab_free_pages (int nr_pages,struct page **pages) +{ +gnttab_pages_clear_private (nr_pages, pages);free_xenballooned_pages (nr_pages, pages); }EXPORT_SYMBOL_GPL (gnttab_free_pages);
include/xen/grant_table.h +3 -0
@@ -198,6 +198,9 @@ void gnttab_free_auto_xlat_frames(void);int gnttab_alloc_pages (int nr_pages,struct page **pages);void gnttab_free_pages (int nr_pages,struct page **pages); +int gnttab_pages_set_private (int nr_pages,struct page **pages); +void gnttab_pages_clear_private (int nr_pages,struct page **pages); +int gnttab_map_refs (struct gnttab_map_grant_ref *map_ops,struct gnttab_map_grant_ref *kmap_ops,struct page **pages,unsigned int count);
Signature · 7 lines
2.17.0 _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v2 3/9 xen/balloon: Share common memory reservation routines
In reply to Oleksandr AndrushchenkoFrom: Oleksandr Andrushchenko <[email protected]>
Memory {increase|decrease}_reservation and VA mappings update/reset code used in balloon driver can be made common, so other drivers can also re-use the same functionality without open-coding. Create a dedicated file for the shared code and export corresponding symbols for other kernel modules.
--- drivers/xen/Makefile | 1 + drivers/xen/balloon.c | 71 ++------------------ drivers/xen/mem-reservation.c | 120 ++++++++++++++++++++++++++++++++++ include/xen/mem-reservation.h | 65 ++++++++++++++++++ 4 files changed, 192 insertions(+), 65 deletions(-) create mode 100644 drivers/xen/mem-reservation.c create mode 100644 include/xen/mem-reservation.h
drivers/xen/Makefile +1 -0
@@ -2,6 +2,7 @@ obj-$(CONFIG_HOTPLUG_CPU) += cpu_hotplug.o obj-$(CONFIG_X86) += fallback.o obj-y += grant-table.o features.o balloon.o manage.o preempt.o time.o +obj-y += mem-reservation.o obj-y += events/ obj-y += xenbus/
drivers/xen/balloon.c +6 -65
126 lines not on this page · raw message
drivers/xen/mem-reservation.c new file +120 -0
120 lines not on this page · raw message
include/xen/mem-reservation.h new file +65 -0
65 lines not on this page · raw message
Signature · 6 lines
2.17.0 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 3/9] xen/balloon: Share common memory reservation routines
Quoted 27 lines · Oleksandr Andrushchenko
include/xen/mem-reservation.h new file +21
-0@@ -0,0 +1,65 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +/* +* Xen memory reservation utilities. +* +* Copyright (c) 2003, B Dragovic +* Copyright (c) 2003-2004, M Williamson, K Fraser +* Copyright (c) 2005 Dan M. Smith, IBM Corporation +* Copyright (c) 2010 Daniel Kiper +* Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. +*/ + +#ifndef _XENMEM_RESERVATION_H +#define _XENMEM_RESERVATION_H + +#include <linux/kernel.h> +#include <linux/slab.h> + +#include <asm/xen/hypercall.h> +#include <asm/tlb.h> +
include/xen/mem-reservation.h line 31
Quoted 10 lines
include/xen/mem-reservation.h new file +10
-0+#include <xen/interface/memory.h> +#include <xen/page.h> + +#ifdef CONFIG_XEN_SCRUB_PAGES +void xenmem_reservation_scrub_page (struct page *page); +#else +static inline void xenmem_reservation_scrub_page (struct page *page) +{ +} +#endif
Given that this is a wrapper around a single call I'd prefer
inline void xenmem_reservation_scrub_page(struct page *page) {
#ifdef CONFIG_XEN_SCRUB_PAGES clear_highpage(page);
#endif
}
-boris
Re: [PATCH v2 3/9] xen/balloon: Share common memory reservation routines
Quoted 41 lines · Boris Ostrovsky
Quoted 27 lines · Oleksandr Andrushchenko
include/xen/mem-reservation.h new file +21
-0@@ -0,0 +1,65 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +/* +* Xen memory reservation utilities. +* +* Copyright (c) 2003, B Dragovic +* Copyright (c) 2003-2004, M Williamson, K Fraser +* Copyright (c) 2005 Dan M. Smith, IBM Corporation +* Copyright (c) 2010 Daniel Kiper +* Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. +*/ + +#ifndef _XENMEM_RESERVATION_H +#define _XENMEM_RESERVATION_H + +#include <linux/kernel.h> +#include <linux/slab.h> + +#include <asm/xen/hypercall.h> +#include <asm/tlb.h> +include/xen/mem-reservation.h line 31
Quoted 10 lines
include/xen/mem-reservation.h new file +10
-0+#include <xen/interface/memory.h> +#include <xen/page.h> + +#ifdef CONFIG_XEN_SCRUB_PAGES +void xenmem_reservation_scrub_page (struct page *page); +#else +static inline void xenmem_reservation_scrub_page (struct page *page) +{ +} +#endif Given that this is a wrapper around a single call I'd prefer
Quoted 7 lines
inline void
xenmem_reservation_scrub_page(struct page *page){
#ifdefCONFIG_XEN_SCRUB_PAGES
clear_highpage(page);
#endif
}
Ok, will change
Quoted 4 lines
-boris
Thank you,
Oleksandr
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 3/9] xen/balloon: Share common memory reservation routines
In reply to Boris OstrovskyQuoted 41 lines · Boris Ostrovsky
Quoted 27 lines · Oleksandr Andrushchenko
include/xen/mem-reservation.h new file +21
-0@@ -0,0 +1,65 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +/* +* Xen memory reservation utilities. +* +* Copyright (c) 2003, B Dragovic +* Copyright (c) 2003-2004, M Williamson, K Fraser +* Copyright (c) 2005 Dan M. Smith, IBM Corporation +* Copyright (c) 2010 Daniel Kiper +* Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. +*/ + +#ifndef _XENMEM_RESERVATION_H +#define _XENMEM_RESERVATION_H + +#include <linux/kernel.h> +#include <linux/slab.h> + +#include <asm/xen/hypercall.h> +#include <asm/tlb.h> +include/xen/mem-reservation.h line 31
Quoted 10 lines
include/xen/mem-reservation.h new file +10
-0+#include <xen/interface/memory.h> +#include <xen/page.h> + +#ifdef CONFIG_XEN_SCRUB_PAGES +void xenmem_reservation_scrub_page (struct page *page); +#else +static inline void xenmem_reservation_scrub_page (struct page *page) +{ +} +#endif Given that this is a wrapper around a single call I'd prefer
Quoted 7 lines
inline void
xenmem_reservation_scrub_page(struct page *page){
#ifdefCONFIG_XEN_SCRUB_PAGES
clear_highpage(page);
#endif
}
Ok, will change
Quoted 4 lines
-boris
Thank you,
Oleksandr
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 3/9] xen/balloon: Share common memory reservation routines
In reply to Boris OstrovskyQuoted 41 lines · Boris Ostrovsky
Quoted 27 lines · Oleksandr Andrushchenko
include/xen/mem-reservation.h new file +21
-0@@ -0,0 +1,65 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +/* +* Xen memory reservation utilities. +* +* Copyright (c) 2003, B Dragovic +* Copyright (c) 2003-2004, M Williamson, K Fraser +* Copyright (c) 2005 Dan M. Smith, IBM Corporation +* Copyright (c) 2010 Daniel Kiper +* Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. +*/ + +#ifndef _XENMEM_RESERVATION_H +#define _XENMEM_RESERVATION_H + +#include <linux/kernel.h> +#include <linux/slab.h> + +#include <asm/xen/hypercall.h> +#include <asm/tlb.h> +include/xen/mem-reservation.h line 31
Quoted 10 lines
include/xen/mem-reservation.h new file +10
-0+#include <xen/interface/memory.h> +#include <xen/page.h> + +#ifdef CONFIG_XEN_SCRUB_PAGES +void xenmem_reservation_scrub_page (struct page *page); +#else +static inline void xenmem_reservation_scrub_page (struct page *page) +{ +} +#endif Given that this is a wrapper around a single call I'd prefer
Quoted 6 lines
inline void
xenmem_reservation_scrub_page(struct page *page){
#ifdefCONFIG_XEN_SCRUB_PAGES
clear_highpage(page);
#endif
}
Unfortunately this can't be done because of EXPORT_SYMBOL_GPL(xenmem_reservation_scrub_page); which is obviously cannot be used for static inline functions. So, I'll keep it as is.
Quoted 5 lines
-boris
Thank you,
Oleksandr
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 3/9] xen/balloon: Share common memory reservation routines
Quoted 49 lines · Oleksandr Andrushchenko
Quoted 42 lines · Boris Ostrovsky
Quoted 28 lines · Oleksandr Andrushchenko
include/xen/mem-reservation.h new file +21
-0@@ -0,0 +1,65 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +/* +* Xen memory reservation utilities. +* +* Copyright (c) 2003, B Dragovic +* Copyright (c) 2003-2004, M Williamson, K Fraser +* Copyright (c) 2005 Dan M. Smith, IBM Corporation +* Copyright (c) 2010 Daniel Kiper +* Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. +*/ + +#ifndef _XENMEM_RESERVATION_H +#define _XENMEM_RESERVATION_H + +#include <linux/kernel.h> +#include <linux/slab.h> + +#include <asm/xen/hypercall.h> +#include <asm/tlb.h> +include/xen/mem-reservation.h line 31
Quoted 10 lines
include/xen/mem-reservation.h new file +10
-0+#include <xen/interface/memory.h> +#include <xen/page.h> + +#ifdef CONFIG_XEN_SCRUB_PAGES +void xenmem_reservation_scrub_page (struct page *page); +#else +static inline void xenmem_reservation_scrub_page (struct page *page) +{ +} +#endif Given that this is a wrapper around a single call I'd prefer
Quoted 6 lines
inline void
xenmem_reservation_scrub_page(struct page *page){
#ifdefCONFIG_XEN_SCRUB_PAGESclear_highpage(page);
#endif
}
Quoted 3 lines
Unfortunately this can't be done because of
EXPORT_SYMBOL_GPL(xenmem_reservation_scrub_page); which is obviously cannot be used for static inline functions.
Why do you need to export it? It's an inline defined in the header file. Just like clear_highpage().
-boris
Quoted 8 lines
So, I'll keep it as is.
Quoted 5 lines
-boris
Thank you,
Oleksandr
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 3/9] xen/balloon: Share common memory reservation routines
In reply to Oleksandr AndrushchenkoQuoted 49 lines · Oleksandr Andrushchenko
Quoted 42 lines · Boris Ostrovsky
Quoted 28 lines · Oleksandr Andrushchenko
include/xen/mem-reservation.h new file +21
-0@@ -0,0 +1,65 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +/* +* Xen memory reservation utilities. +* +* Copyright (c) 2003, B Dragovic +* Copyright (c) 2003-2004, M Williamson, K Fraser +* Copyright (c) 2005 Dan M. Smith, IBM Corporation +* Copyright (c) 2010 Daniel Kiper +* Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. +*/ + +#ifndef _XENMEM_RESERVATION_H +#define _XENMEM_RESERVATION_H + +#include <linux/kernel.h> +#include <linux/slab.h> + +#include <asm/xen/hypercall.h> +#include <asm/tlb.h> +include/xen/mem-reservation.h line 31
Quoted 10 lines
include/xen/mem-reservation.h new file +10
-0+#include <xen/interface/memory.h> +#include <xen/page.h> + +#ifdef CONFIG_XEN_SCRUB_PAGES +void xenmem_reservation_scrub_page (struct page *page); +#else +static inline void xenmem_reservation_scrub_page (struct page *page) +{ +} +#endif Given that this is a wrapper around a single call I'd prefer
Quoted 6 lines
inline void
xenmem_reservation_scrub_page(struct page *page){
#ifdefCONFIG_XEN_SCRUB_PAGESclear_highpage(page);
#endif
}
Quoted 3 lines
Unfortunately this can't be done because of
EXPORT_SYMBOL_GPL(xenmem_reservation_scrub_page); which is obviously cannot be used for static inline functions.
Why do you need to export it? It's an inline defined in the header file. Just like clear_highpage().
-boris
Quoted 8 lines
So, I'll keep it as is.
Quoted 5 lines
-boris
Thank you,
Oleksandr
Re: [PATCH v2 3/9] xen/balloon: Share common memory reservation routines
Quoted 49 lines · Boris Ostrovsky
Quoted 48 lines · Oleksandr Andrushchenko
Quoted 47 lines · Boris Ostrovsky
Quoted 28 lines · Oleksandr Andrushchenko
include/xen/mem-reservation.h new file +21
-0@@ -0,0 +1,65 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +/* +* Xen memory reservation utilities. +* +* Copyright (c) 2003, B Dragovic +* Copyright (c) 2003-2004, M Williamson, K Fraser +* Copyright (c) 2005 Dan M. Smith, IBM Corporation +* Copyright (c) 2010 Daniel Kiper +* Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. +*/ + +#ifndef _XENMEM_RESERVATION_H +#define _XENMEM_RESERVATION_H + +#include <linux/kernel.h> +#include <linux/slab.h> + +#include <asm/xen/hypercall.h> +#include <asm/tlb.h> +include/xen/mem-reservation.h line 31
Quoted 10 lines
include/xen/mem-reservation.h new file +10
-0+#include <xen/interface/memory.h> +#include <xen/page.h> + +#ifdef CONFIG_XEN_SCRUB_PAGES +void xenmem_reservation_scrub_page (struct page *page); +#else +static inline void xenmem_reservation_scrub_page (struct page *page) +{ +} +#endif Given that this is a wrapper around a single call I'd prefer
inline void
xenmem_reservation_scrub_page(struct page *page){
#ifdefCONFIG_XEN_SCRUB_PAGES
clear_highpage(page);
#endif
}
Quoted 7 lines
Quoted 3 lines
Unfortunately this can't be done because of
EXPORT_SYMBOL_GPL(xenmem_reservation_scrub_page); which is obviously cannot be used for static inline functions.Why do you need to export it? It's an inline defined in the header file. Just like
clear_highpage().
You are perfectly right, will change as you suggest
Quoted 2 lines
-boris
Thank you,
Oleksandr
Quoted 7 lines
Quoted 7 lines
So, I'll keep it as is.
Quoted 4 lines
-boris
Thank you,
Oleksandr
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 3/9] xen/balloon: Share common memory reservation routines
In reply to Boris OstrovskyQuoted 49 lines · Boris Ostrovsky
Quoted 48 lines · Oleksandr Andrushchenko
Quoted 47 lines · Boris Ostrovsky
Quoted 28 lines · Oleksandr Andrushchenko
include/xen/mem-reservation.h new file +21
-0@@ -0,0 +1,65 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +/* +* Xen memory reservation utilities. +* +* Copyright (c) 2003, B Dragovic +* Copyright (c) 2003-2004, M Williamson, K Fraser +* Copyright (c) 2005 Dan M. Smith, IBM Corporation +* Copyright (c) 2010 Daniel Kiper +* Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. +*/ + +#ifndef _XENMEM_RESERVATION_H +#define _XENMEM_RESERVATION_H + +#include <linux/kernel.h> +#include <linux/slab.h> + +#include <asm/xen/hypercall.h> +#include <asm/tlb.h> +include/xen/mem-reservation.h line 31
Quoted 10 lines
include/xen/mem-reservation.h new file +10
-0+#include <xen/interface/memory.h> +#include <xen/page.h> + +#ifdef CONFIG_XEN_SCRUB_PAGES +void xenmem_reservation_scrub_page (struct page *page); +#else +static inline void xenmem_reservation_scrub_page (struct page *page) +{ +} +#endif Given that this is a wrapper around a single call I'd prefer
inline void
xenmem_reservation_scrub_page(struct page *page){
#ifdefCONFIG_XEN_SCRUB_PAGES
clear_highpage(page);
#endif
}
Quoted 7 lines
Quoted 3 lines
Unfortunately this can't be done because of
EXPORT_SYMBOL_GPL(xenmem_reservation_scrub_page); which is obviously cannot be used for static inline functions.Why do you need to export it? It's an inline defined in the header file. Just like
clear_highpage().
You are perfectly right, will change as you suggest
Quoted 2 lines
-boris
Thank you,
Oleksandr
Quoted 7 lines
Quoted 7 lines
So, I'll keep it as is.
Quoted 4 lines
-boris
Thank you,
Oleksandr
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 3/9] xen/balloon: Share common memory reservation routines
In reply to Boris OstrovskyQuoted 41 lines · Boris Ostrovsky
Quoted 27 lines · Oleksandr Andrushchenko
include/xen/mem-reservation.h new file +21
-0@@ -0,0 +1,65 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +/* +* Xen memory reservation utilities. +* +* Copyright (c) 2003, B Dragovic +* Copyright (c) 2003-2004, M Williamson, K Fraser +* Copyright (c) 2005 Dan M. Smith, IBM Corporation +* Copyright (c) 2010 Daniel Kiper +* Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. +*/ + +#ifndef _XENMEM_RESERVATION_H +#define _XENMEM_RESERVATION_H + +#include <linux/kernel.h> +#include <linux/slab.h> + +#include <asm/xen/hypercall.h> +#include <asm/tlb.h> +include/xen/mem-reservation.h line 31
Quoted 10 lines
include/xen/mem-reservation.h new file +10
-0+#include <xen/interface/memory.h> +#include <xen/page.h> + +#ifdef CONFIG_XEN_SCRUB_PAGES +void xenmem_reservation_scrub_page (struct page *page); +#else +static inline void xenmem_reservation_scrub_page (struct page *page) +{ +} +#endif Given that this is a wrapper around a single call I'd prefer
Quoted 6 lines
inline void
xenmem_reservation_scrub_page(struct page *page){
#ifdefCONFIG_XEN_SCRUB_PAGES
clear_highpage(page);
#endif
}
Unfortunately this can't be done because of EXPORT_SYMBOL_GPL(xenmem_reservation_scrub_page); which is obviously cannot be used for static inline functions. So, I'll keep it as is.
Quoted 5 lines
-boris
Thank you,
Oleksandr
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 3/9] xen/balloon: Share common memory reservation routines
In reply to Oleksandr AndrushchenkoQuoted 27 lines · Oleksandr Andrushchenko
include/xen/mem-reservation.h new file +21
-0@@ -0,0 +1,65 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +/* +* Xen memory reservation utilities. +* +* Copyright (c) 2003, B Dragovic +* Copyright (c) 2003-2004, M Williamson, K Fraser +* Copyright (c) 2005 Dan M. Smith, IBM Corporation +* Copyright (c) 2010 Daniel Kiper +* Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. +*/ + +#ifndef _XENMEM_RESERVATION_H +#define _XENMEM_RESERVATION_H + +#include <linux/kernel.h> +#include <linux/slab.h> + +#include <asm/xen/hypercall.h> +#include <asm/tlb.h> +
include/xen/mem-reservation.h line 31
Quoted 10 lines
include/xen/mem-reservation.h new file +10
-0+#include <xen/interface/memory.h> +#include <xen/page.h> + +#ifdef CONFIG_XEN_SCRUB_PAGES +void xenmem_reservation_scrub_page (struct page *page); +#else +static inline void xenmem_reservation_scrub_page (struct page *page) +{ +} +#endif
Given that this is a wrapper around a single call I'd prefer
inline void xenmem_reservation_scrub_page(struct page *page) {
#ifdef CONFIG_XEN_SCRUB_PAGES clear_highpage(page);
#endif
}
-boris
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v2 3/9 xen/balloon: Share common memory reservation routines
In reply to Oleksandr AndrushchenkoFrom: Oleksandr Andrushchenko <[email protected]>
Memory {increase|decrease}_reservation and VA mappings update/reset code used in balloon driver can be made common, so other drivers can also re-use the same functionality without open-coding. Create a dedicated file for the shared code and export corresponding symbols for other kernel modules.
--- drivers/xen/Makefile | 1 + drivers/xen/balloon.c | 71 ++------------------ drivers/xen/mem-reservation.c | 120 ++++++++++++++++++++++++++++++++++ include/xen/mem-reservation.h | 65 ++++++++++++++++++ 4 files changed, 192 insertions(+), 65 deletions(-) create mode 100644 drivers/xen/mem-reservation.c create mode 100644 include/xen/mem-reservation.h
drivers/xen/Makefile +1 -0
@@ -2,6 +2,7 @@ obj-$(CONFIG_HOTPLUG_CPU) += cpu_hotplug.o obj-$(CONFIG_X86) += fallback.o obj-y += grant-table.o features.o balloon.o manage.o preempt.o time.o +obj-y += mem-reservation.o obj-y += events/ obj-y += xenbus/
drivers/xen/balloon.c +6 -65
126 lines not on this page · raw message
drivers/xen/mem-reservation.c new file +120 -0
120 lines not on this page · raw message
include/xen/mem-reservation.h new file +65 -0
65 lines not on this page · raw message
Signature · 7 lines
2.17.0 _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v2 4/9 xen/grant-table: Allow allocating buffers suitable for DMA
In reply to Oleksandr AndrushchenkoFrom: Oleksandr Andrushchenko <[email protected]>
Extend grant table module API to allow allocating buffers that can be used for DMA operations and mapping foreign grant references on top of those.
The resulting buffer is similar to the one allocated by the balloon driver in terms that proper memory reservation is made ({increase|decrease}_reservation and VA mappings updated if needed). This is useful for sharing foreign buffers with HW drivers which cannot work with scattered buffers provided by the balloon driver, but require DMAable memory instead.
--- drivers/xen/Kconfig | 13 +++++ drivers/xen/grant-table.c | 109 ++++++++++++++++++++++++++++++++++++++ include/xen/grant_table.h | 18 +++++++ 3 files changed, 140 insertions(+)
drivers/xen/Kconfig +13 -0
@@ -161,6 +161,19 @@ config XEN_GRANT_DEV_ALLOC to other domains. This can be used to implement frontend drivers or as part of an inter-domain shared memory channel. +config XEN_GRANT_DMA_ALLOC + bool "Allow allocating DMA capable buffers with grant reference module" + depends on XEN && HAS_DMA + help + Extends grant table module API to allow allocating DMA capable + buffers and mapping foreign grant references on top of it. + The resulting buffer is similar to one allocated by the balloon + driver in terms that proper memory reservation is made + ({increase|decrease}_reservation and VA mappings updated if needed). + This is useful for sharing foreign buffers with HW drivers which + cannot work with scattered buffers provided by the balloon driver, + but require DMAable memory instead. + config SWIOTLB_XEN def_bool y select SWIOTLB
drivers/xen/grant-table.c +109 -0
133 lines not on this page · raw message
include/xen/grant_table.h +18 -0
@@ -198,6 +198,24 @@ void gnttab_free_auto_xlat_frames(void);int gnttab_alloc_pages (int nr_pages,struct page **pages);void gnttab_free_pages (int nr_pages,struct page **pages); +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +struct gnttab_dma_alloc_args { +/* Device for which DMA memory will be/was allocated. */ +struct device *dev; +/* If set then DMA buffer is coherent and write-combine otherwise. */ +bool coherent; + +int nr_pages; +struct page **pages; +xen_pfn_t *frames; +void *vaddr; +dma_addr_t dev_bus_addr; +}; + +int gnttab_dma_alloc_pages (struct gnttab_dma_alloc_args *args); +int gnttab_dma_free_pages (struct gnttab_dma_alloc_args *args); +#endif +int gnttab_pages_set_private (int nr_pages,struct page **pages);void gnttab_pages_clear_private (int nr_pages,struct page **pages);
Signature · 6 lines
2.17.0 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 4/9] xen/grant-table: Allow allocating buffers suitable for DMA
Quoted 123 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Extend grant table module API to allow allocating buffers that can be used for DMA operations and mapping foreign grant references on top of those.
The resulting buffer is similar to the one allocated by the balloon driver in terms that proper memory reservation is made ({increase|decrease}_reservation and VA mappings updated if needed). This is useful for sharing foreign buffers with HW drivers which cannot work with scattered buffers provided by the balloon driver, but require DMAable memory instead.Signed-off-by Oleksandr Andrushchenko <[email protected]>--- drivers/xen/Kconfig | 13 +++++ drivers/xen/grant-table.c | 109 ++++++++++++++++++++++++++++++++++++++ include/xen/grant_table.h | 18 +++++++ 3 files changed, 140 insertions(+)drivers/xen/Kconfig +13
-0@@ -161,6 +161,19 @@ config XEN_GRANT_DEV_ALLOC to other domains. This can be used to implement frontend drivers or as part of an inter-domain shared memory channel. +config XEN_GRANT_DMA_ALLOC + bool "Allow allocating DMA capable buffers with grant reference module" + depends on XEN && HAS_DMA + help + Extends grant table module API to allow allocating DMA capable + buffers and mapping foreign grant references on top of it. + The resulting buffer is similar to one allocated by the balloon + driver in terms that proper memory reservation is made + ({increase|decrease}_reservation and VA mappings updated if needed). + This is useful for sharing foreign buffers with HW drivers which + cannot work with scattered buffers provided by the balloon driver, + but require DMAable memory instead. + config SWIOTLB_XEN def_bool y select SWIOTLBdrivers/xen/grant-table.c +58
-0@@ -45,6 +45,9 @@#include <linux/workqueue.h> #include <linux/ratelimit.h> #include <linux/moduleparam.h> +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +#include <linux/dma-mapping.h> +#endif #include <xen/xen.h> #include <xen/interface/xen.h> @@ -57,6 +60,7 @@#ifdef CONFIG_X86 #include <asm/xen/cpuid.h> #endif +#include <xen/mem-reservation.h> #include <asm/xen/hypercall.h> #include <asm/xen/interface.h> @@ -811,6 +815,73 @@ int gnttab_alloc_pages(int nr_pages, struct page **pages) }EXPORT_SYMBOL_GPL (gnttab_alloc_pages); +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +/** +* gnttab_dma_alloc_pages - alloc DMAable pages suitable for grant mapping into +* @args: arguments to the function +*/ +int gnttab_dma_alloc_pages (struct gnttab_dma_alloc_args *args) +{ +unsigned long pfn, start_pfn; +size_t size; +int i, ret; + + size = args->nr_pages <<PAGE_SHIFT ; +if (args->coherent) + args->vaddr =dma_alloc_coherent (args->dev, size, + &args->dev_bus_addr, +GFP_KERNEL | __GFP_NOWARN); +else + args->vaddr =dma_alloc_wc (args->dev, size, + &args->dev_bus_addr, +GFP_KERNEL | __GFP_NOWARN); +if (!args->vaddr) { +pr_err ("Failed to allocate DMA buffer of size %zu\n" , size); +return -ENOMEM ; + } + + start_pfn =__phys_to_pfn (args->dev_bus_addr); +for (pfn = start_pfn, i =0 ; pfn < start_pfn + args->nr_pages; + pfn++, i++) { +struct page *page =pfn_to_page (pfn); + + args->pages[i] = page; + args->frames[i] =xen_page_to_gfn (page); +xenmem_reservation_scrub_page (page); + } + +xenmem_reservation_va_mapping_reset (args->nr_pages, args->pages); + + ret =xenmem_reservation_decrease (args->nr_pages, args->frames); +if (ret != args->nr_pages) { +pr_err ("Failed to decrease reservation for DMA buffer\n" ); + ret = -EFAULT ; + goto fail_free_dma; + } + + ret =gnttab_pages_set_private (args->nr_pages, args->pages); +if (ret <0 ) + goto fail_clear_private; + +return 0 ; + +fail_clear_private: +gnttab_pages_clear_private (args->nr_pages, args->pages); +fail_free_dma: +xenmem_reservation_increase (args->nr_pages, args->frames);
drivers/xen/grant-table.c int gnttab_alloc_pages(int nr_pages, struct page **pages) · line 881
Quoted 10 lines
drivers/xen/grant-table.c +10
-0+xenmem_reservation_va_mapping_update (args->nr_pages, args->pages, + args->frames); +if (args->coherent) +dma_free_coherent (args->dev, size, + args->vaddr, args->dev_bus_addr); +else +dma_free_wc (args->dev, size, + args->vaddr, args->dev_bus_addr); +return ret; +}
Would it be possible to call gnttab_dma_free_pages() here?
drivers/xen/grant-table.c void gnttab_free_pages(int nr_pages, struct page **pages) · line 912
Quoted 11 lines
drivers/xen/grant-table.c +4
-0+EXPORT_SYMBOL_GPL (gnttab_dma_alloc_pages); +#endif +void gnttab_pages_clear_private (int nr_pages,struct page **pages) {int i;@@ -838,6 +909,44 @@ void gnttab_free_pages(int nr_pages, struct page **pages) }EXPORT_SYMBOL_GPL (gnttab_free_pages); +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC
I'd move this after (or before) gnttab_dma_alloc_page() to keep both inside a single ifdef block.
-boris
Quoted 59 lines
drivers/xen/grant-table.c +37
-0+/** +* gnttab_dma_free_pages - free DMAable pages +* @args: arguments to the function +*/ +int gnttab_dma_free_pages (struct gnttab_dma_alloc_args *args) +{ +size_t size; +int i, ret; + +gnttab_pages_clear_private (args->nr_pages, args->pages); + +for (i =0 ; i < args->nr_pages; i++) + args->frames[i] =page_to_xen_pfn (args->pages[i]); + + ret =xenmem_reservation_increase (args->nr_pages, args->frames); +if (ret != args->nr_pages) { +pr_err ("Failed to decrease reservation for DMA buffer\n" ); + ret = -EFAULT ; + }else { + ret =0 ; + } + +xenmem_reservation_va_mapping_update (args->nr_pages, args->pages, + args->frames); + + size = args->nr_pages <<PAGE_SHIFT ; +if (args->coherent) +dma_free_coherent (args->dev, size, + args->vaddr, args->dev_bus_addr); +else +dma_free_wc (args->dev, size, + args->vaddr, args->dev_bus_addr); +return ret; +} +EXPORT_SYMBOL_GPL (gnttab_dma_free_pages); +#endif +/* Handling of paged out grant targets (GNTST_eagain) */ #define MAX_DELAY 256 static inline voidinclude/xen/grant_table.h +11
-0@@ -198,6 +198,24 @@ void gnttab_free_auto_xlat_frames(void);int gnttab_alloc_pages (int nr_pages,struct page **pages);void gnttab_free_pages (int nr_pages,struct page **pages); +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +struct gnttab_dma_alloc_args { + /* Device for which DMA memory will be/was allocated. */ + struct device *dev; + /* If set then DMA buffer is coherent and write-combine otherwise. */ + bool coherent; + + int nr_pages; + struct page **pages; + xen_pfn_t *frames; + void *vaddr;
include/xen/grant_table.h void gnttab_free_auto_xlat_frames(void); · line 221
Quoted 10 lines
include/xen/grant_table.h +7
-0+ dma_addr_t dev_bus_addr; +}; + +int gnttab_dma_alloc_pages (struct gnttab_dma_alloc_args *args); +int gnttab_dma_free_pages (struct gnttab_dma_alloc_args *args); +#endif +int gnttab_pages_set_private (int nr_pages,struct page **pages);void gnttab_pages_clear_private (int nr_pages,struct page **pages);
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 4/9] xen/grant-table: Allow allocating buffers suitable for DMA
In reply to Oleksandr AndrushchenkoQuoted 123 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Extend grant table module API to allow allocating buffers that can be used for DMA operations and mapping foreign grant references on top of those.
The resulting buffer is similar to the one allocated by the balloon driver in terms that proper memory reservation is made ({increase|decrease}_reservation and VA mappings updated if needed). This is useful for sharing foreign buffers with HW drivers which cannot work with scattered buffers provided by the balloon driver, but require DMAable memory instead.Signed-off-by Oleksandr Andrushchenko <[email protected]>--- drivers/xen/Kconfig | 13 +++++ drivers/xen/grant-table.c | 109 ++++++++++++++++++++++++++++++++++++++ include/xen/grant_table.h | 18 +++++++ 3 files changed, 140 insertions(+)drivers/xen/Kconfig +13
-0@@ -161,6 +161,19 @@ config XEN_GRANT_DEV_ALLOC to other domains. This can be used to implement frontend drivers or as part of an inter-domain shared memory channel. +config XEN_GRANT_DMA_ALLOC + bool "Allow allocating DMA capable buffers with grant reference module" + depends on XEN && HAS_DMA + help + Extends grant table module API to allow allocating DMA capable + buffers and mapping foreign grant references on top of it. + The resulting buffer is similar to one allocated by the balloon + driver in terms that proper memory reservation is made + ({increase|decrease}_reservation and VA mappings updated if needed). + This is useful for sharing foreign buffers with HW drivers which + cannot work with scattered buffers provided by the balloon driver, + but require DMAable memory instead. + config SWIOTLB_XEN def_bool y select SWIOTLBdrivers/xen/grant-table.c +58
-0@@ -45,6 +45,9 @@#include <linux/workqueue.h> #include <linux/ratelimit.h> #include <linux/moduleparam.h> +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +#include <linux/dma-mapping.h> +#endif #include <xen/xen.h> #include <xen/interface/xen.h> @@ -57,6 +60,7 @@#ifdef CONFIG_X86 #include <asm/xen/cpuid.h> #endif +#include <xen/mem-reservation.h> #include <asm/xen/hypercall.h> #include <asm/xen/interface.h> @@ -811,6 +815,73 @@ int gnttab_alloc_pages(int nr_pages, struct page **pages) }EXPORT_SYMBOL_GPL (gnttab_alloc_pages); +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +/** +* gnttab_dma_alloc_pages - alloc DMAable pages suitable for grant mapping into +* @args: arguments to the function +*/ +int gnttab_dma_alloc_pages (struct gnttab_dma_alloc_args *args) +{ +unsigned long pfn, start_pfn; +size_t size; +int i, ret; + + size = args->nr_pages <<PAGE_SHIFT ; +if (args->coherent) + args->vaddr =dma_alloc_coherent (args->dev, size, + &args->dev_bus_addr, +GFP_KERNEL | __GFP_NOWARN); +else + args->vaddr =dma_alloc_wc (args->dev, size, + &args->dev_bus_addr, +GFP_KERNEL | __GFP_NOWARN); +if (!args->vaddr) { +pr_err ("Failed to allocate DMA buffer of size %zu\n" , size); +return -ENOMEM ; + } + + start_pfn =__phys_to_pfn (args->dev_bus_addr); +for (pfn = start_pfn, i =0 ; pfn < start_pfn + args->nr_pages; + pfn++, i++) { +struct page *page =pfn_to_page (pfn); + + args->pages[i] = page; + args->frames[i] =xen_page_to_gfn (page); +xenmem_reservation_scrub_page (page); + } + +xenmem_reservation_va_mapping_reset (args->nr_pages, args->pages); + + ret =xenmem_reservation_decrease (args->nr_pages, args->frames); +if (ret != args->nr_pages) { +pr_err ("Failed to decrease reservation for DMA buffer\n" ); + ret = -EFAULT ; + goto fail_free_dma; + } + + ret =gnttab_pages_set_private (args->nr_pages, args->pages); +if (ret <0 ) + goto fail_clear_private; + +return 0 ; + +fail_clear_private: +gnttab_pages_clear_private (args->nr_pages, args->pages); +fail_free_dma: +xenmem_reservation_increase (args->nr_pages, args->frames);
drivers/xen/grant-table.c int gnttab_alloc_pages(int nr_pages, struct page **pages) · line 881
Quoted 10 lines
drivers/xen/grant-table.c +10
-0+xenmem_reservation_va_mapping_update (args->nr_pages, args->pages, + args->frames); +if (args->coherent) +dma_free_coherent (args->dev, size, + args->vaddr, args->dev_bus_addr); +else +dma_free_wc (args->dev, size, + args->vaddr, args->dev_bus_addr); +return ret; +}
Would it be possible to call gnttab_dma_free_pages() here?
drivers/xen/grant-table.c void gnttab_free_pages(int nr_pages, struct page **pages) · line 912
Quoted 11 lines
drivers/xen/grant-table.c +4
-0+EXPORT_SYMBOL_GPL (gnttab_dma_alloc_pages); +#endif +void gnttab_pages_clear_private (int nr_pages,struct page **pages) {int i;@@ -838,6 +909,44 @@ void gnttab_free_pages(int nr_pages, struct page **pages) }EXPORT_SYMBOL_GPL (gnttab_free_pages); +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC
I'd move this after (or before) gnttab_dma_alloc_page() to keep both inside a single ifdef block.
-boris
Quoted 69 lines
drivers/xen/grant-table.c +37
-0+/** +* gnttab_dma_free_pages - free DMAable pages +* @args: arguments to the function +*/ +int gnttab_dma_free_pages (struct gnttab_dma_alloc_args *args) +{ +size_t size; +int i, ret; + +gnttab_pages_clear_private (args->nr_pages, args->pages); + +for (i =0 ; i < args->nr_pages; i++) + args->frames[i] =page_to_xen_pfn (args->pages[i]); + + ret =xenmem_reservation_increase (args->nr_pages, args->frames); +if (ret != args->nr_pages) { +pr_err ("Failed to decrease reservation for DMA buffer\n" ); + ret = -EFAULT ; + }else { + ret =0 ; + } + +xenmem_reservation_va_mapping_update (args->nr_pages, args->pages, + args->frames); + + size = args->nr_pages <<PAGE_SHIFT ; +if (args->coherent) +dma_free_coherent (args->dev, size, + args->vaddr, args->dev_bus_addr); +else +dma_free_wc (args->dev, size, + args->vaddr, args->dev_bus_addr); +return ret; +} +EXPORT_SYMBOL_GPL (gnttab_dma_free_pages); +#endif +/* Handling of paged out grant targets (GNTST_eagain) */ #define MAX_DELAY 256 static inline voidinclude/xen/grant_table.h +18
-0@@ -198,6 +198,24 @@ void gnttab_free_auto_xlat_frames(void);int gnttab_alloc_pages (int nr_pages,struct page **pages);void gnttab_free_pages (int nr_pages,struct page **pages); +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +struct gnttab_dma_alloc_args { +/* Device for which DMA memory will be/was allocated. */ +struct device *dev; +/* If set then DMA buffer is coherent and write-combine otherwise. */ +bool coherent; + +int nr_pages; +struct page **pages; +xen_pfn_t *frames; +void *vaddr; +dma_addr_t dev_bus_addr; +}; + +int gnttab_dma_alloc_pages (struct gnttab_dma_alloc_args *args); +int gnttab_dma_free_pages (struct gnttab_dma_alloc_args *args); +#endif +int gnttab_pages_set_private (int nr_pages,struct page **pages);void gnttab_pages_clear_private (int nr_pages,struct page **pages);
Re: [PATCH v2 4/9] xen/grant-table: Allow allocating buffers suitable for DMA
Quoted 128 lines · Boris Ostrovsky
Quoted 127 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Extend grant table module API to allow allocating buffers that can be used for DMA operations and mapping foreign grant references on top of those.
The resulting buffer is similar to the one allocated by the balloon driver in terms that proper memory reservation is made ({increase|decrease}_reservation and VA mappings updated if needed). This is useful for sharing foreign buffers with HW drivers which cannot work with scattered buffers provided by the balloon driver, but require DMAable memory instead.Signed-off-by Oleksandr Andrushchenko <[email protected]>--- drivers/xen/Kconfig | 13 +++++ drivers/xen/grant-table.c | 109 ++++++++++++++++++++++++++++++++++++++ include/xen/grant_table.h | 18 +++++++ 3 files changed, 140 insertions(+)drivers/xen/Kconfig +13
-0@@ -161,6 +161,19 @@ config XEN_GRANT_DEV_ALLOC to other domains. This can be used to implement frontend drivers or as part of an inter-domain shared memory channel. +config XEN_GRANT_DMA_ALLOC + bool "Allow allocating DMA capable buffers with grant reference module" + depends on XEN && HAS_DMA + help + Extends grant table module API to allow allocating DMA capable + buffers and mapping foreign grant references on top of it. + The resulting buffer is similar to one allocated by the balloon + driver in terms that proper memory reservation is made + ({increase|decrease}_reservation and VA mappings updated if needed). + This is useful for sharing foreign buffers with HW drivers which + cannot work with scattered buffers provided by the balloon driver, + but require DMAable memory instead. + config SWIOTLB_XEN def_bool y select SWIOTLBdrivers/xen/grant-table.c +62
-0@@ -45,6 +45,9 @@#include <linux/workqueue.h> #include <linux/ratelimit.h> #include <linux/moduleparam.h> +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +#include <linux/dma-mapping.h> +#endif #include <xen/xen.h> #include <xen/interface/xen.h> @@ -57,6 +60,7 @@#ifdef CONFIG_X86 #include <asm/xen/cpuid.h> #endif +#include <xen/mem-reservation.h> #include <asm/xen/hypercall.h> #include <asm/xen/interface.h> @@ -811,6 +815,73 @@ int gnttab_alloc_pages(int nr_pages, struct page **pages) }EXPORT_SYMBOL_GPL (gnttab_alloc_pages); +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +/** +* gnttab_dma_alloc_pages - alloc DMAable pages suitable for grant mapping into +* @args: arguments to the function +*/ +int gnttab_dma_alloc_pages (struct gnttab_dma_alloc_args *args) +{ +unsigned long pfn, start_pfn; +size_t size; +int i, ret; + + size = args->nr_pages <<PAGE_SHIFT ; +if (args->coherent) + args->vaddr =dma_alloc_coherent (args->dev, size, + &args->dev_bus_addr, +GFP_KERNEL | __GFP_NOWARN); +else + args->vaddr =dma_alloc_wc (args->dev, size, + &args->dev_bus_addr, +GFP_KERNEL | __GFP_NOWARN); +if (!args->vaddr) { +pr_err ("Failed to allocate DMA buffer of size %zu\n" , size); +return -ENOMEM ; + } + + start_pfn =__phys_to_pfn (args->dev_bus_addr); +for (pfn = start_pfn, i =0 ; pfn < start_pfn + args->nr_pages; + pfn++, i++) { +struct page *page =pfn_to_page (pfn); + + args->pages[i] = page; + args->frames[i] =xen_page_to_gfn (page); +xenmem_reservation_scrub_page (page); + } + +xenmem_reservation_va_mapping_reset (args->nr_pages, args->pages); + + ret =xenmem_reservation_decrease (args->nr_pages, args->frames); +if (ret != args->nr_pages) { +pr_err ("Failed to decrease reservation for DMA buffer\n" ); + ret = -EFAULT ; + goto fail_free_dma; + } + + ret =gnttab_pages_set_private (args->nr_pages, args->pages); +if (ret <0 ) + goto fail_clear_private; + +return 0 ; + +fail_clear_private: +gnttab_pages_clear_private (args->nr_pages, args->pages); +fail_free_dma: +xenmem_reservation_increase (args->nr_pages, args->frames); +xenmem_reservation_va_mapping_update (args->nr_pages, args->pages, + args->frames); +if (args->coherent) + dma_free_coherent(args->dev, size,
Quoted 8 lines
drivers/xen/grant-table.c int gnttab_alloc_pages(int nr_pages, struct page **pages) · line 881
Quoted 6 lines
drivers/xen/grant-table.c +6
-0+ args->vaddr, args->dev_bus_addr); + else + dma_free_wc(args->dev, size, + args->vaddr, args->dev_bus_addr); +return ret; +}Would it be possible to call
gnttab_dma_free_pages()here?
As we moved frames array outside - yes, I'll call gnttab_dma_free_pages on failure then.
Quoted 11 lines
Quoted 11 lines
drivers/xen/grant-table.c +3
-0+EXPORT_SYMBOL_GPL (gnttab_dma_alloc_pages); +#endif +void gnttab_pages_clear_private (int nr_pages,struct page **pages) {int i;@@ -838,6 +909,44 @@ void gnttab_free_pages(int nr_pages, struct page **pages) }EXPORT_SYMBOL_GPL (gnttab_free_pages);
Quoted 3 lines
drivers/xen/grant-table.c void gnttab_free_pages(int nr_pages, struct page **pages) · line 912
Quoted 1 line
drivers/xen/grant-table.c +1
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC I'd move this after (or before)
gnttab_dma_alloc_page()to keep both inside a single ifdef block.
Ok, will also move and regroup functions to be implemented close to each other:
gnttab_dma_{alloc|free}_pages gnttab_{alloc|free}_pages gnttab_pages_{set|clear}_private
Quoted 64 lines
-boris
Quoted 61 lines
drivers/xen/grant-table.c +37
-0+/** +* gnttab_dma_free_pages - free DMAable pages +* @args: arguments to the function +*/ +int gnttab_dma_free_pages (struct gnttab_dma_alloc_args *args) +{ +size_t size; +int i, ret; + +gnttab_pages_clear_private (args->nr_pages, args->pages); + +for (i =0 ; i < args->nr_pages; i++) + args->frames[i] =page_to_xen_pfn (args->pages[i]); + + ret =xenmem_reservation_increase (args->nr_pages, args->frames); +if (ret != args->nr_pages) { +pr_err ("Failed to decrease reservation for DMA buffer\n" ); + ret = -EFAULT ; + }else { + ret =0 ; + } + +xenmem_reservation_va_mapping_update (args->nr_pages, args->pages, + args->frames); + + size = args->nr_pages <<PAGE_SHIFT ; +if (args->coherent) +dma_free_coherent (args->dev, size, + args->vaddr, args->dev_bus_addr); +else +dma_free_wc (args->dev, size, + args->vaddr, args->dev_bus_addr); +return ret; +} +EXPORT_SYMBOL_GPL (gnttab_dma_free_pages); +#endif +/* Handling of paged out grant targets (GNTST_eagain) */ #define MAX_DELAY 256 static inline voidinclude/xen/grant_table.h +13
-0@@ -198,6 +198,24 @@ void gnttab_free_auto_xlat_frames(void);int gnttab_alloc_pages (int nr_pages,struct page **pages);void gnttab_free_pages (int nr_pages,struct page **pages); +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +struct gnttab_dma_alloc_args { +/* Device for which DMA memory will be/was allocated. */ +struct device *dev; +/* If set then DMA buffer is coherent and write-combine otherwise. */ +bool coherent; + +int nr_pages; +struct page **pages; +xen_pfn_t *frames; +void *vaddr; +dma_addr_t dev_bus_addr; +};
Quoted 8 lines
include/xen/grant_table.h void gnttab_free_auto_xlat_frames(void); · line 221
Quoted 8 lines
include/xen/grant_table.h +5
-0+ +int gnttab_dma_alloc_pages (struct gnttab_dma_alloc_args *args); +int gnttab_dma_free_pages (struct gnttab_dma_alloc_args *args); +#endif +int gnttab_pages_set_private (int nr_pages,struct page **pages);void gnttab_pages_clear_private (int nr_pages,struct page **pages);
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 4/9] xen/grant-table: Allow allocating buffers suitable for DMA
In reply to Boris OstrovskyQuoted 128 lines · Boris Ostrovsky
Quoted 127 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Extend grant table module API to allow allocating buffers that can be used for DMA operations and mapping foreign grant references on top of those.
The resulting buffer is similar to the one allocated by the balloon driver in terms that proper memory reservation is made ({increase|decrease}_reservation and VA mappings updated if needed). This is useful for sharing foreign buffers with HW drivers which cannot work with scattered buffers provided by the balloon driver, but require DMAable memory instead.Signed-off-by Oleksandr Andrushchenko <[email protected]>--- drivers/xen/Kconfig | 13 +++++ drivers/xen/grant-table.c | 109 ++++++++++++++++++++++++++++++++++++++ include/xen/grant_table.h | 18 +++++++ 3 files changed, 140 insertions(+)drivers/xen/Kconfig +13
-0@@ -161,6 +161,19 @@ config XEN_GRANT_DEV_ALLOC to other domains. This can be used to implement frontend drivers or as part of an inter-domain shared memory channel. +config XEN_GRANT_DMA_ALLOC + bool "Allow allocating DMA capable buffers with grant reference module" + depends on XEN && HAS_DMA + help + Extends grant table module API to allow allocating DMA capable + buffers and mapping foreign grant references on top of it. + The resulting buffer is similar to one allocated by the balloon + driver in terms that proper memory reservation is made + ({increase|decrease}_reservation and VA mappings updated if needed). + This is useful for sharing foreign buffers with HW drivers which + cannot work with scattered buffers provided by the balloon driver, + but require DMAable memory instead. + config SWIOTLB_XEN def_bool y select SWIOTLBdrivers/xen/grant-table.c +62
-0@@ -45,6 +45,9 @@#include <linux/workqueue.h> #include <linux/ratelimit.h> #include <linux/moduleparam.h> +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +#include <linux/dma-mapping.h> +#endif #include <xen/xen.h> #include <xen/interface/xen.h> @@ -57,6 +60,7 @@#ifdef CONFIG_X86 #include <asm/xen/cpuid.h> #endif +#include <xen/mem-reservation.h> #include <asm/xen/hypercall.h> #include <asm/xen/interface.h> @@ -811,6 +815,73 @@ int gnttab_alloc_pages(int nr_pages, struct page **pages) }EXPORT_SYMBOL_GPL (gnttab_alloc_pages); +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +/** +* gnttab_dma_alloc_pages - alloc DMAable pages suitable for grant mapping into +* @args: arguments to the function +*/ +int gnttab_dma_alloc_pages (struct gnttab_dma_alloc_args *args) +{ +unsigned long pfn, start_pfn; +size_t size; +int i, ret; + + size = args->nr_pages <<PAGE_SHIFT ; +if (args->coherent) + args->vaddr =dma_alloc_coherent (args->dev, size, + &args->dev_bus_addr, +GFP_KERNEL | __GFP_NOWARN); +else + args->vaddr =dma_alloc_wc (args->dev, size, + &args->dev_bus_addr, +GFP_KERNEL | __GFP_NOWARN); +if (!args->vaddr) { +pr_err ("Failed to allocate DMA buffer of size %zu\n" , size); +return -ENOMEM ; + } + + start_pfn =__phys_to_pfn (args->dev_bus_addr); +for (pfn = start_pfn, i =0 ; pfn < start_pfn + args->nr_pages; + pfn++, i++) { +struct page *page =pfn_to_page (pfn); + + args->pages[i] = page; + args->frames[i] =xen_page_to_gfn (page); +xenmem_reservation_scrub_page (page); + } + +xenmem_reservation_va_mapping_reset (args->nr_pages, args->pages); + + ret =xenmem_reservation_decrease (args->nr_pages, args->frames); +if (ret != args->nr_pages) { +pr_err ("Failed to decrease reservation for DMA buffer\n" ); + ret = -EFAULT ; + goto fail_free_dma; + } + + ret =gnttab_pages_set_private (args->nr_pages, args->pages); +if (ret <0 ) + goto fail_clear_private; + +return 0 ; + +fail_clear_private: +gnttab_pages_clear_private (args->nr_pages, args->pages); +fail_free_dma: +xenmem_reservation_increase (args->nr_pages, args->frames); +xenmem_reservation_va_mapping_update (args->nr_pages, args->pages, + args->frames); +if (args->coherent) + dma_free_coherent(args->dev, size,
Quoted 8 lines
drivers/xen/grant-table.c int gnttab_alloc_pages(int nr_pages, struct page **pages) · line 881
Quoted 6 lines
drivers/xen/grant-table.c +6
-0+ args->vaddr, args->dev_bus_addr); + else + dma_free_wc(args->dev, size, + args->vaddr, args->dev_bus_addr); +return ret; +}Would it be possible to call
gnttab_dma_free_pages()here?
As we moved frames array outside - yes, I'll call gnttab_dma_free_pages on failure then.
Quoted 11 lines
Quoted 11 lines
drivers/xen/grant-table.c +3
-0+EXPORT_SYMBOL_GPL (gnttab_dma_alloc_pages); +#endif +void gnttab_pages_clear_private (int nr_pages,struct page **pages) {int i;@@ -838,6 +909,44 @@ void gnttab_free_pages(int nr_pages, struct page **pages) }EXPORT_SYMBOL_GPL (gnttab_free_pages);
Quoted 3 lines
drivers/xen/grant-table.c void gnttab_free_pages(int nr_pages, struct page **pages) · line 912
Quoted 1 line
drivers/xen/grant-table.c +1
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC I'd move this after (or before)
gnttab_dma_alloc_page()to keep both inside a single ifdef block.
Ok, will also move and regroup functions to be implemented close to each other:
gnttab_dma_{alloc|free}_pages gnttab_{alloc|free}_pages gnttab_pages_{set|clear}_private
Quoted 64 lines
-boris
Quoted 61 lines
drivers/xen/grant-table.c +37
-0+/** +* gnttab_dma_free_pages - free DMAable pages +* @args: arguments to the function +*/ +int gnttab_dma_free_pages (struct gnttab_dma_alloc_args *args) +{ +size_t size; +int i, ret; + +gnttab_pages_clear_private (args->nr_pages, args->pages); + +for (i =0 ; i < args->nr_pages; i++) + args->frames[i] =page_to_xen_pfn (args->pages[i]); + + ret =xenmem_reservation_increase (args->nr_pages, args->frames); +if (ret != args->nr_pages) { +pr_err ("Failed to decrease reservation for DMA buffer\n" ); + ret = -EFAULT ; + }else { + ret =0 ; + } + +xenmem_reservation_va_mapping_update (args->nr_pages, args->pages, + args->frames); + + size = args->nr_pages <<PAGE_SHIFT ; +if (args->coherent) +dma_free_coherent (args->dev, size, + args->vaddr, args->dev_bus_addr); +else +dma_free_wc (args->dev, size, + args->vaddr, args->dev_bus_addr); +return ret; +} +EXPORT_SYMBOL_GPL (gnttab_dma_free_pages); +#endif +/* Handling of paged out grant targets (GNTST_eagain) */ #define MAX_DELAY 256 static inline voidinclude/xen/grant_table.h +13
-0@@ -198,6 +198,24 @@ void gnttab_free_auto_xlat_frames(void);int gnttab_alloc_pages (int nr_pages,struct page **pages);void gnttab_free_pages (int nr_pages,struct page **pages); +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +struct gnttab_dma_alloc_args { +/* Device for which DMA memory will be/was allocated. */ +struct device *dev; +/* If set then DMA buffer is coherent and write-combine otherwise. */ +bool coherent; + +int nr_pages; +struct page **pages; +xen_pfn_t *frames; +void *vaddr; +dma_addr_t dev_bus_addr; +};
Quoted 8 lines
include/xen/grant_table.h void gnttab_free_auto_xlat_frames(void); · line 221
Quoted 8 lines
include/xen/grant_table.h +5
-0+ +int gnttab_dma_alloc_pages (struct gnttab_dma_alloc_args *args); +int gnttab_dma_free_pages (struct gnttab_dma_alloc_args *args); +#endif +int gnttab_pages_set_private (int nr_pages,struct page **pages);void gnttab_pages_clear_private (int nr_pages,struct page **pages);
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v2 4/9 xen/grant-table: Allow allocating buffers suitable for DMA
In reply to Oleksandr AndrushchenkoFrom: Oleksandr Andrushchenko <[email protected]>
Extend grant table module API to allow allocating buffers that can be used for DMA operations and mapping foreign grant references on top of those.
The resulting buffer is similar to the one allocated by the balloon driver in terms that proper memory reservation is made ({increase|decrease}_reservation and VA mappings updated if needed). This is useful for sharing foreign buffers with HW drivers which cannot work with scattered buffers provided by the balloon driver, but require DMAable memory instead.
--- drivers/xen/Kconfig | 13 +++++ drivers/xen/grant-table.c | 109 ++++++++++++++++++++++++++++++++++++++ include/xen/grant_table.h | 18 +++++++ 3 files changed, 140 insertions(+)
drivers/xen/Kconfig +13 -0
@@ -161,6 +161,19 @@ config XEN_GRANT_DEV_ALLOC to other domains. This can be used to implement frontend drivers or as part of an inter-domain shared memory channel. +config XEN_GRANT_DMA_ALLOC + bool "Allow allocating DMA capable buffers with grant reference module" + depends on XEN && HAS_DMA + help + Extends grant table module API to allow allocating DMA capable + buffers and mapping foreign grant references on top of it. + The resulting buffer is similar to one allocated by the balloon + driver in terms that proper memory reservation is made + ({increase|decrease}_reservation and VA mappings updated if needed). + This is useful for sharing foreign buffers with HW drivers which + cannot work with scattered buffers provided by the balloon driver, + but require DMAable memory instead. + config SWIOTLB_XEN def_bool y select SWIOTLB
drivers/xen/grant-table.c +109 -0
133 lines not on this page · raw message
include/xen/grant_table.h +18 -0
@@ -198,6 +198,24 @@ void gnttab_free_auto_xlat_frames(void);int gnttab_alloc_pages (int nr_pages,struct page **pages);void gnttab_free_pages (int nr_pages,struct page **pages); +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +struct gnttab_dma_alloc_args { +/* Device for which DMA memory will be/was allocated. */ +struct device *dev; +/* If set then DMA buffer is coherent and write-combine otherwise. */ +bool coherent; + +int nr_pages; +struct page **pages; +xen_pfn_t *frames; +void *vaddr; +dma_addr_t dev_bus_addr; +}; + +int gnttab_dma_alloc_pages (struct gnttab_dma_alloc_args *args); +int gnttab_dma_free_pages (struct gnttab_dma_alloc_args *args); +#endif +int gnttab_pages_set_private (int nr_pages,struct page **pages);void gnttab_pages_clear_private (int nr_pages,struct page **pages);
Signature · 7 lines
2.17.0 _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v2 5/9 xen/gntdev: Allow mappings for DMA buffers
In reply to Oleksandr AndrushchenkoFrom: Oleksandr Andrushchenko <[email protected]>
Allow mappings for DMA backed buffers if grant table module supports such: this extends grant device to not only map buffers made of balloon pages, but also from buffers allocated with dma_alloc_xxx.
--- drivers/xen/gntdev.c | 99 ++++++++++++++++++++++++++++++++++++++- include/uapi/xen/gntdev.h | 15 ++++++ 2 files changed, 112 insertions(+), 2 deletions(-)
drivers/xen/gntdev.c +97 -2
@@ -37,6 +37,9 @@#include <linux/slab.h> #include <linux/highmem.h> #include <linux/refcount.h> +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +#include <linux/of_device.h> +#endif #include <xen/xen.h> #include <xen/grant_table.h>
@@ -72,6 +75,11 @@ struct gntdev_priv {struct mutex lock;struct mm_struct *mm;struct mmu_notifier mn; + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +/* Device for which DMA memory is allocated. */ +struct device *dma_dev; +#endif };struct unmap_notify {
@@ -96,10 +104,27 @@ struct grant_map {struct gnttab_unmap_grant_ref *kunmap_ops;struct page **pages;unsigned long pages_vm_start; + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +/* +* If dmabuf_vaddr is not NULL then this mapping is backed by DMA +* capable memory. +*/ + +struct device *dma_dev; +/* Flags used to create this DMA buffer: GNTDEV_DMA_FLAG_XXX. */ +int dma_flags; +void *dma_vaddr; +dma_addr_t dma_bus_addr; +/* This is required for gnttab_dma_{alloc|free}_pages. */ +xen_pfn_t *frames; +#endif };static int unmap_grant_pages (struct grant_map *map,int offset,int pages); +static struct miscdevice gntdev_miscdev; +/* ------------------------------------------------------------------ */ static void gntdev_print_maps(struct gntdev_priv *priv,
@@ -121,8 +146,27 @@ static void gntdev_free_map(struct grant_map *map)if (map ==NULL )return ; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +if (map->dma_vaddr) { +struct gnttab_dma_alloc_args args; + + args.dev = map->dma_dev; + args.coherent = map->dma_flags &GNTDEV_DMA_FLAG_COHERENT ; + args.nr_pages = map->count; + args.pages = map->pages; + args.frames = map->frames; + args.vaddr = map->dma_vaddr; + args.dev_bus_addr = map->dma_bus_addr; + +gnttab_dma_free_pages (&args); + } else +#endif if (map->pages)gnttab_free_pages (map->count, map->pages); + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +kfree (map->frames); +#endif kfree (map->pages);kfree (map->grants);kfree (map->map_ops);
@@ -132,7 +176,8 @@ static void gntdev_free_map(struct grant_map *map)kfree (map); } -static struct grant_map *gntdev_alloc_map (struct gntdev_priv *priv,int count) +static struct grant_map *gntdev_alloc_map (struct gntdev_priv *priv,int count, +int dma_flags) {struct grant_map *add;int i;
@@ -155,6 +200,37 @@ static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) NULL == add->pages) goto err; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + add->dma_flags = dma_flags; + +/* +* Check if this mapping is requested to be backed +* by a DMA buffer. +*/ +if (dma_flags & (GNTDEV_DMA_FLAG_WC |GNTDEV_DMA_FLAG_COHERENT )) { +struct gnttab_dma_alloc_args args; + + add->frames =kcalloc (count,sizeof (add->frames[0 ]), +GFP_KERNEL ); +if (!add->frames) + goto err; + +/* Remember the device, so we can free DMA memory. */ + add->dma_dev = priv->dma_dev; + + args.dev = priv->dma_dev; + args.coherent = dma_flags &GNTDEV_DMA_FLAG_COHERENT ; + args.nr_pages = count; + args.pages = add->pages; + args.frames = add->frames; + +if (gnttab_dma_alloc_pages (&args)) + goto err; + + add->dma_vaddr = args.vaddr; + add->dma_bus_addr = args.dev_bus_addr; + } else +#endif if (gnttab_alloc_pages (count, add->pages)) goto err;
@@ -325,6 +401,14 @@ static int map_grant_pages(struct grant_map *map) map->unmap_ops[i].handle = map->map_ops[i].handle;if (use_ptemod) map->kunmap_ops[i].handle = map->kmap_ops[i].handle; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { +unsigned long mfn; + + mfn =__pfn_to_mfn (page_to_pfn (map->pages[i])); + map->unmap_ops[i].dev_bus_addr =__pfn_to_phys (mfn); + } +#endif }return err; }
@@ -548,6 +632,17 @@ static int gntdev_open(struct inode *inode, struct file *flip) } flip->private_data = priv; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + priv->dma_dev = gntdev_miscdev.this_device; + +/* +* The device is not spawn from a device tree, so arch_setup_dma_ops +* is not called, thus leaving the device with dummy DMA ops. +* Fix this call of_dma_configure() with a NULL node to set +* default DMA ops. +*/ +of_dma_configure (priv->dma_dev,NULL ); +#endif pr_debug ("priv %p\n" , priv);return 0 ;
@@ -589,7 +684,7 @@ static long gntdev_ioctl_map_grant_ref(struct gntdev_priv *priv,return -EINVAL ; err = -ENOMEM ; - map =gntdev_alloc_map (priv, op.count); + map =gntdev_alloc_map (priv, op.count,0 /* This is not a dma-buf. */ );if (!map)return err;
include/uapi/xen/gntdev.h +15 -0
@@ -200,4 +200,19 @@ struct ioctl_gntdev_grant_copy {/* Send an interrupt on the indicated event channel */ #define UNMAP_NOTIFY_SEND_EVENT 0x2 +/* +* Flags to be used while requesting memory mapping's backing storage +* to be allocated with DMA API. +*/ + +/* +* The buffer is backed with memory allocated with dma_alloc_wc. +*/ +#define GNTDEV_DMA_FLAG_WC (1 << 0) + +/* +* The buffer is backed with memory allocated with dma_alloc_coherent. +*/ +#define GNTDEV_DMA_FLAG_COHERENT (1 << 1) +#endif /* __LINUX_PUBLIC_GNTDEV_H__ */
Signature · 6 lines
2.17.0 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
Quoted 46 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Allow mappings for DMA backed buffers if grant table module supports such: this extends grant device to not only map buffers made of balloon pages, but also from buffers allocated with
dma_alloc_xxx.Signed-off-by Oleksandr Andrushchenko <[email protected]>--- drivers/xen/gntdev.c | 99 ++++++++++++++++++++++++++++++++++++++- include/uapi/xen/gntdev.h | 15 ++++++ 2 files changed, 112 insertions(+), 2 deletions(-)drivers/xen/gntdev.c +11
-0@@ -37,6 +37,9 @@#include <linux/slab.h> #include <linux/highmem.h> #include <linux/refcount.h> +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +#include <linux/of_device.h> +#endif #include <xen/xen.h> #include <xen/grant_table.h> @@ -72,6 +75,11 @@ struct gntdev_priv {struct mutex lock;struct mm_struct *mm;struct mmu_notifier mn; + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +/* Device for which DMA memory is allocated. */ +struct device *dma_dev; +#endif };struct unmap_notify {@@ -96,10 +104,27 @@ struct grant_map {struct gnttab_unmap_grant_ref *kunmap_ops;struct page **pages;unsigned long pages_vm_start; + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +/*
drivers/xen/gntdev.c struct grant_map { · line 119
Quoted 10 lines
drivers/xen/gntdev.c +10
-0+* If dmabuf_vaddr is not NULL then this mapping is backed by DMA +* capable memory. +*/ + +struct device *dma_dev; +/* Flags used to create this DMA buffer: GNTDEV_DMA_FLAG_XXX. */ +int dma_flags; +void *dma_vaddr; +dma_addr_t dma_bus_addr; +/* This is required for gnttab_dma_{alloc|free}_pages. */
How about
/* Needed to avoid allocation in gnttab_dma_free_pages(). */
Quoted 26 lines
drivers/xen/gntdev.c +15
-0+xen_pfn_t *frames; +#endif };static int unmap_grant_pages (struct grant_map *map,int offset,int pages); +static struct miscdevice gntdev_miscdev; +/* ------------------------------------------------------------------ */ static void gntdev_print_maps(struct gntdev_priv *priv,@@ -121,8 +146,27 @@ static void gntdev_free_map(struct grant_map *map)if (map ==NULL )return ; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +if (map->dma_vaddr) { +struct gnttab_dma_alloc_args args; + + args.dev = map->dma_dev; + args.coherent = map->dma_flags &GNTDEV_DMA_FLAG_COHERENT ; + args.nr_pages = map->count; + args.pages = map->pages; + args.frames = map->frames; + args.vaddr = map->dma_vaddr; + args.dev_bus_addr = map->dma_bus_addr;
drivers/xen/gntdev.c static void gntdev_free_map(struct grant_map *map) · line 169
Quoted 10 lines
drivers/xen/gntdev.c +8
-0+ +gnttab_dma_free_pages (&args); + } else +#endif if (map->pages)gnttab_free_pages (map->count, map->pages); + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +kfree (map->frames); +#endif
Can this be done under if (map->dma_vaddr) ? In other words, is it possible for dma_vaddr to be NULL and still have unallocated frames pointer?
Quoted 52 lines
drivers/xen/gntdev.c +33
-1kfree (map->pages);kfree (map->grants);kfree (map->map_ops);@@ -132,7 +176,8 @@ static void gntdev_free_map(struct grant_map *map)kfree (map); } -static struct grant_map *gntdev_alloc_map (struct gntdev_priv *priv,int count) +static struct grant_map *gntdev_alloc_map (struct gntdev_priv *priv,int count, +int dma_flags) {struct grant_map *add;int i;@@ -155,6 +200,37 @@ static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) NULL == add->pages) goto err; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + add->dma_flags = dma_flags; + +/* +* Check if this mapping is requested to be backed +* by a DMA buffer. +*/ +if (dma_flags & (GNTDEV_DMA_FLAG_WC |GNTDEV_DMA_FLAG_COHERENT )) { +struct gnttab_dma_alloc_args args; + + add->frames =kcalloc (count,sizeof (add->frames[0 ]), +GFP_KERNEL ); +if (!add->frames) + goto err; + +/* Remember the device, so we can free DMA memory. */ + add->dma_dev = priv->dma_dev; + + args.dev = priv->dma_dev; + args.coherent = dma_flags &GNTDEV_DMA_FLAG_COHERENT ; + args.nr_pages = count; + args.pages = add->pages; + args.frames = add->frames; + +if (gnttab_dma_alloc_pages (&args)) + goto err; + + add->dma_vaddr = args.vaddr; + add->dma_bus_addr = args.dev_bus_addr; + } else +#endif if (gnttab_alloc_pages (count, add->pages)) goto err;
drivers/xen/gntdev.c static int map_grant_pages(struct grant_map *map) · line 408
Quoted 8 lines
drivers/xen/gntdev.c +5
-0@@ -325,6 +401,14 @@ static int map_grant_pages(struct grant_map *map) map->unmap_ops[i].handle = map->map_ops[i].handle;if (use_ptemod) map->kunmap_ops[i].handle = map->kmap_ops[i].handle; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { +unsigned long mfn; + + mfn =__pfn_to_mfn (page_to_pfn (map->pages[i]));
Not pfn_to_mfn()?
-boris
Quoted 47 lines
drivers/xen/gntdev.c +15
-1+ map->unmap_ops[i].dev_bus_addr = __pfn_to_phys(mfn); + } +#endif }return err; }@@ -548,6 +632,17 @@ static int gntdev_open(struct inode *inode, struct file *flip) } flip->private_data = priv; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + priv->dma_dev = gntdev_miscdev.this_device; + +/* +* The device is not spawn from a device tree, so arch_setup_dma_ops +* is not called, thus leaving the device with dummy DMA ops. +* Fix this call of_dma_configure() with a NULL node to set +* default DMA ops. +*/ +of_dma_configure (priv->dma_dev,NULL ); +#endif pr_debug ("priv %p\n" , priv);return 0 ;@@ -589,7 +684,7 @@ static long gntdev_ioctl_map_grant_ref(struct gntdev_priv *priv,return -EINVAL ; err = -ENOMEM ; - map =gntdev_alloc_map (priv, op.count); + map =gntdev_alloc_map (priv, op.count,0 /* This is not a dma-buf. */ );if (!map)return err;include/uapi/xen/gntdev.h +6
-0@@ -200,4 +200,19 @@ struct ioctl_gntdev_grant_copy {/* Send an interrupt on the indicated event channel */ #define UNMAP_NOTIFY_SEND_EVENT 0x2 +/* +* Flags to be used while requesting memory mapping's backing storage +* to be allocated with DMA API. +*/ + +/*
include/uapi/xen/gntdev.h struct ioctl_gntdev_grant_copy { · line 218
Quoted 10 lines
include/uapi/xen/gntdev.h +9
-0+* The buffer is backed with memory allocated with dma_alloc_wc. +*/ +#define GNTDEV_DMA_FLAG_WC (1 << 0) + +/* +* The buffer is backed with memory allocated with dma_alloc_coherent. +*/ +#define GNTDEV_DMA_FLAG_COHERENT (1 << 1) +#endif /* __LINUX_PUBLIC_GNTDEV_H__ */
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
In reply to Oleksandr AndrushchenkoQuoted 46 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Allow mappings for DMA backed buffers if grant table module supports such: this extends grant device to not only map buffers made of balloon pages, but also from buffers allocated with
dma_alloc_xxx.Signed-off-by Oleksandr Andrushchenko <[email protected]>--- drivers/xen/gntdev.c | 99 ++++++++++++++++++++++++++++++++++++++- include/uapi/xen/gntdev.h | 15 ++++++ 2 files changed, 112 insertions(+), 2 deletions(-)drivers/xen/gntdev.c +11
-0@@ -37,6 +37,9 @@#include <linux/slab.h> #include <linux/highmem.h> #include <linux/refcount.h> +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +#include <linux/of_device.h> +#endif #include <xen/xen.h> #include <xen/grant_table.h> @@ -72,6 +75,11 @@ struct gntdev_priv {struct mutex lock;struct mm_struct *mm;struct mmu_notifier mn; + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +/* Device for which DMA memory is allocated. */ +struct device *dma_dev; +#endif };struct unmap_notify {@@ -96,10 +104,27 @@ struct grant_map {struct gnttab_unmap_grant_ref *kunmap_ops;struct page **pages;unsigned long pages_vm_start; + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +/*
drivers/xen/gntdev.c struct grant_map { · line 119
Quoted 10 lines
drivers/xen/gntdev.c +10
-0+* If dmabuf_vaddr is not NULL then this mapping is backed by DMA +* capable memory. +*/ + +struct device *dma_dev; +/* Flags used to create this DMA buffer: GNTDEV_DMA_FLAG_XXX. */ +int dma_flags; +void *dma_vaddr; +dma_addr_t dma_bus_addr; +/* This is required for gnttab_dma_{alloc|free}_pages. */
How about
/* Needed to avoid allocation in gnttab_dma_free_pages(). */
Quoted 26 lines
drivers/xen/gntdev.c +15
-0+xen_pfn_t *frames; +#endif };static int unmap_grant_pages (struct grant_map *map,int offset,int pages); +static struct miscdevice gntdev_miscdev; +/* ------------------------------------------------------------------ */ static void gntdev_print_maps(struct gntdev_priv *priv,@@ -121,8 +146,27 @@ static void gntdev_free_map(struct grant_map *map)if (map ==NULL )return ; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +if (map->dma_vaddr) { +struct gnttab_dma_alloc_args args; + + args.dev = map->dma_dev; + args.coherent = map->dma_flags &GNTDEV_DMA_FLAG_COHERENT ; + args.nr_pages = map->count; + args.pages = map->pages; + args.frames = map->frames; + args.vaddr = map->dma_vaddr; + args.dev_bus_addr = map->dma_bus_addr;
drivers/xen/gntdev.c static void gntdev_free_map(struct grant_map *map) · line 169
Quoted 10 lines
drivers/xen/gntdev.c +8
-0+ +gnttab_dma_free_pages (&args); + } else +#endif if (map->pages)gnttab_free_pages (map->count, map->pages); + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +kfree (map->frames); +#endif
Can this be done under if (map->dma_vaddr) ? In other words, is it possible for dma_vaddr to be NULL and still have unallocated frames pointer?
Quoted 52 lines
drivers/xen/gntdev.c +33
-1kfree (map->pages);kfree (map->grants);kfree (map->map_ops);@@ -132,7 +176,8 @@ static void gntdev_free_map(struct grant_map *map)kfree (map); } -static struct grant_map *gntdev_alloc_map (struct gntdev_priv *priv,int count) +static struct grant_map *gntdev_alloc_map (struct gntdev_priv *priv,int count, +int dma_flags) {struct grant_map *add;int i;@@ -155,6 +200,37 @@ static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) NULL == add->pages) goto err; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + add->dma_flags = dma_flags; + +/* +* Check if this mapping is requested to be backed +* by a DMA buffer. +*/ +if (dma_flags & (GNTDEV_DMA_FLAG_WC |GNTDEV_DMA_FLAG_COHERENT )) { +struct gnttab_dma_alloc_args args; + + add->frames =kcalloc (count,sizeof (add->frames[0 ]), +GFP_KERNEL ); +if (!add->frames) + goto err; + +/* Remember the device, so we can free DMA memory. */ + add->dma_dev = priv->dma_dev; + + args.dev = priv->dma_dev; + args.coherent = dma_flags &GNTDEV_DMA_FLAG_COHERENT ; + args.nr_pages = count; + args.pages = add->pages; + args.frames = add->frames; + +if (gnttab_dma_alloc_pages (&args)) + goto err; + + add->dma_vaddr = args.vaddr; + add->dma_bus_addr = args.dev_bus_addr; + } else +#endif if (gnttab_alloc_pages (count, add->pages)) goto err;
drivers/xen/gntdev.c static int map_grant_pages(struct grant_map *map) · line 408
Quoted 8 lines
drivers/xen/gntdev.c +5
-0@@ -325,6 +401,14 @@ static int map_grant_pages(struct grant_map *map) map->unmap_ops[i].handle = map->map_ops[i].handle;if (use_ptemod) map->kunmap_ops[i].handle = map->kmap_ops[i].handle; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { +unsigned long mfn; + + mfn =__pfn_to_mfn (page_to_pfn (map->pages[i]));
Not pfn_to_mfn()?
-boris
Quoted 57 lines
drivers/xen/gntdev.c +15
-1+ map->unmap_ops[i].dev_bus_addr = __pfn_to_phys(mfn); + } +#endif }return err; }@@ -548,6 +632,17 @@ static int gntdev_open(struct inode *inode, struct file *flip) } flip->private_data = priv; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + priv->dma_dev = gntdev_miscdev.this_device; + +/* +* The device is not spawn from a device tree, so arch_setup_dma_ops +* is not called, thus leaving the device with dummy DMA ops. +* Fix this call of_dma_configure() with a NULL node to set +* default DMA ops. +*/ +of_dma_configure (priv->dma_dev,NULL ); +#endif pr_debug ("priv %p\n" , priv);return 0 ;@@ -589,7 +684,7 @@ static long gntdev_ioctl_map_grant_ref(struct gntdev_priv *priv,return -EINVAL ; err = -ENOMEM ; - map =gntdev_alloc_map (priv, op.count); + map =gntdev_alloc_map (priv, op.count,0 /* This is not a dma-buf. */ );if (!map)return err;include/uapi/xen/gntdev.h +15
-0@@ -200,4 +200,19 @@ struct ioctl_gntdev_grant_copy {/* Send an interrupt on the indicated event channel */ #define UNMAP_NOTIFY_SEND_EVENT 0x2 +/* +* Flags to be used while requesting memory mapping's backing storage +* to be allocated with DMA API. +*/ + +/* +* The buffer is backed with memory allocated with dma_alloc_wc. +*/ +#define GNTDEV_DMA_FLAG_WC (1 << 0) + +/* +* The buffer is backed with memory allocated with dma_alloc_coherent. +*/ +#define GNTDEV_DMA_FLAG_COHERENT (1 << 1) +#endif /* __LINUX_PUBLIC_GNTDEV_H__ */
Re: [Xen-devel] [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
Quoted 59 lines · Boris Ostrovsky
Quoted 46 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Allow mappings for DMA backed buffers if grant table module supports such: this extends grant device to not only map buffers made of balloon pages, but also from buffers allocated with
dma_alloc_xxx.Signed-off-by Oleksandr Andrushchenko <[email protected]>--- drivers/xen/gntdev.c | 99 ++++++++++++++++++++++++++++++++++++++- include/uapi/xen/gntdev.h | 15 ++++++ 2 files changed, 112 insertions(+), 2 deletions(-)drivers/xen/gntdev.c +11
-0@@ -37,6 +37,9 @@#include <linux/slab.h> #include <linux/highmem.h> #include <linux/refcount.h> +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +#include <linux/of_device.h> +#endif #include <xen/xen.h> #include <xen/grant_table.h> @@ -72,6 +75,11 @@ struct gntdev_priv {struct mutex lock;struct mm_struct *mm;struct mmu_notifier mn; + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +/* Device for which DMA memory is allocated. */ +struct device *dma_dev; +#endif };struct unmap_notify {@@ -96,10 +104,27 @@ struct grant_map {struct gnttab_unmap_grant_ref *kunmap_ops;struct page **pages;unsigned long pages_vm_start; + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +/* drivers/xen/gntdev.c struct grant_map { · line 119
Quoted 10 lines
drivers/xen/gntdev.c +10
-0+* If dmabuf_vaddr is not NULL then this mapping is backed by DMA +* capable memory. +*/ + +struct device *dma_dev; +/* Flags used to create this DMA buffer: GNTDEV_DMA_FLAG_XXX. */ +int dma_flags; +void *dma_vaddr; +dma_addr_t dma_bus_addr; +/* This is required for gnttab_dma_{alloc|free}_pages. */ How about
Quoted 2 lines
/* Needed to avoid allocation in
gnttab_dma_free_pages(). */
Ok
Quoted 39 lines
Quoted 26 lines
drivers/xen/gntdev.c +15
-0+xen_pfn_t *frames; +#endif };static int unmap_grant_pages (struct grant_map *map,int offset,int pages); +static struct miscdevice gntdev_miscdev; +/* ------------------------------------------------------------------ */ static void gntdev_print_maps(struct gntdev_priv *priv,@@ -121,8 +146,27 @@ static void gntdev_free_map(struct grant_map *map)if (map ==NULL )return ; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +if (map->dma_vaddr) { +struct gnttab_dma_alloc_args args; + + args.dev = map->dma_dev; + args.coherent = map->dma_flags &GNTDEV_DMA_FLAG_COHERENT ; + args.nr_pages = map->count; + args.pages = map->pages; + args.frames = map->frames; + args.vaddr = map->dma_vaddr; + args.dev_bus_addr = map->dma_bus_addr;drivers/xen/gntdev.c static void gntdev_free_map(struct grant_map *map) · line 169
Quoted 10 lines
drivers/xen/gntdev.c +8
-0+ +gnttab_dma_free_pages (&args); + } else +#endif if (map->pages)gnttab_free_pages (map->count, map->pages); + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +kfree (map->frames); +#endif Can this be done under if (
map->dma_vaddr) ?
Quoted 2 lines
In other words, is it
possible fordma_vaddrto be NULL and still have unallocated frames pointer?
It is possible to have vaddr == NULL and frames != NULL as we allocate frames outside of gnttab_dma_alloc_pages which may fail. Calling kfree on NULL pointer is safe, so I see no reason to change this code.
Quoted 52 lines
Quoted 52 lines
drivers/xen/gntdev.c +33
-1kfree (map->pages);kfree (map->grants);kfree (map->map_ops);@@ -132,7 +176,8 @@ static void gntdev_free_map(struct grant_map *map)kfree (map); } -static struct grant_map *gntdev_alloc_map (struct gntdev_priv *priv,int count) +static struct grant_map *gntdev_alloc_map (struct gntdev_priv *priv,int count, +int dma_flags) {struct grant_map *add;int i;@@ -155,6 +200,37 @@ static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) NULL == add->pages) goto err; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + add->dma_flags = dma_flags; + +/* +* Check if this mapping is requested to be backed +* by a DMA buffer. +*/ +if (dma_flags & (GNTDEV_DMA_FLAG_WC |GNTDEV_DMA_FLAG_COHERENT )) { +struct gnttab_dma_alloc_args args; + + add->frames =kcalloc (count,sizeof (add->frames[0 ]), +GFP_KERNEL ); +if (!add->frames) + goto err; + +/* Remember the device, so we can free DMA memory. */ + add->dma_dev = priv->dma_dev; + + args.dev = priv->dma_dev; + args.coherent = dma_flags &GNTDEV_DMA_FLAG_COHERENT ; + args.nr_pages = count; + args.pages = add->pages; + args.frames = add->frames; + +if (gnttab_dma_alloc_pages (&args)) + goto err; + + add->dma_vaddr = args.vaddr; + add->dma_bus_addr = args.dev_bus_addr; + } else +#endif if (gnttab_alloc_pages (count, add->pages)) goto err;
Quoted 11 lines
drivers/xen/gntdev.c static int map_grant_pages(struct grant_map *map) · line 408
Quoted 9 lines
drivers/xen/gntdev.c +5
-0@@ -325,6 +401,14 @@ static int map_grant_pages(struct grant_map *map) map->unmap_ops[i].handle = map->map_ops[i].handle;if (use_ptemod) map->kunmap_ops[i].handle = map->kmap_ops[i].handle; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { +unsigned long mfn; + + mfn =__pfn_to_mfn (page_to_pfn (map->pages[i]));Not
pfn_to_mfn()?
I'd love to, but pfn_to_mfn is only defined for x86, not ARM: [1] and [2] Thus,
drivers/xen/gntdev.c:408:10: error: implicit declaration of function ‘pfn_to_mfn’ [-Werror=implicit-function-declaration] mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
So, I'll keep __pfn_to_mfn
Quoted 3 lines
-boris
Thank you,
Oleksandr
Quoted 54 lines
Quoted 54 lines
drivers/xen/gntdev.c +15
-1+ map->unmap_ops[i].dev_bus_addr = __pfn_to_phys(mfn); + } +#endif }return err; }@@ -548,6 +632,17 @@ static int gntdev_open(struct inode *inode, struct file *flip) } flip->private_data = priv; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + priv->dma_dev = gntdev_miscdev.this_device; + +/* +* The device is not spawn from a device tree, so arch_setup_dma_ops +* is not called, thus leaving the device with dummy DMA ops. +* Fix this call of_dma_configure() with a NULL node to set +* default DMA ops. +*/ +of_dma_configure (priv->dma_dev,NULL ); +#endif pr_debug ("priv %p\n" , priv);return 0 ;@@ -589,7 +684,7 @@ static long gntdev_ioctl_map_grant_ref(struct gntdev_priv *priv,return -EINVAL ; err = -ENOMEM ; - map =gntdev_alloc_map (priv, op.count); + map =gntdev_alloc_map (priv, op.count,0 /* This is not a dma-buf. */ );if (!map)return err;include/uapi/xen/gntdev.h +13
-0@@ -200,4 +200,19 @@ struct ioctl_gntdev_grant_copy {/* Send an interrupt on the indicated event channel */ #define UNMAP_NOTIFY_SEND_EVENT 0x2 +/* +* Flags to be used while requesting memory mapping's backing storage +* to be allocated with DMA API. +*/ + +/* +* The buffer is backed with memory allocated with dma_alloc_wc. +*/ +#define GNTDEV_DMA_FLAG_WC (1 << 0) + +/* +* The buffer is backed with memory allocated with dma_alloc_coherent. +*/
Quoted 8 lines
include/uapi/xen/gntdev.h struct ioctl_gntdev_grant_copy { · line 218
Quoted 3 lines
include/uapi/xen/gntdev.h +2
-0+#define GNTDEV_DMA_FLAG_COHERENT (1 << 1) +#endif /* __LINUX_PUBLIC_GNTDEV_H__ */ _______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
[1] https://elixir.bootlin.com/linux/v4.17/ident/pfn_to_mfn
[2] https://elixir.bootlin.com/linux/v4.17/ident/__pfn_to_mfn
_______________________________________________
dri-devel mailing list [email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
Quoted 28 lines · Oleksandr Andrushchenko
Quoted 27 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev.c +0
-0@@ -121,8 +146,27 @@ static void gntdev_free_map(struct grant_map *map) if (map == NULL) return;+#ifdef
CONFIG_XEN_GRANT_DMA_ALLOC
+ if (map->dma_vaddr) {
+ structgnttab_dma_alloc_argsargs;drivers/xen/gntdev.c +12
-0+ + args.dev = map->dma_dev; + args.coherent = map->dma_flags & GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages = map->count; + args.pages = map->pages; + args.frames = map->frames; + args.vaddr = map->dma_vaddr; + args.dev_bus_addr = map->dma_bus_addr; + + gnttab_dma_free_pages(&args); + } else +#endif if (
map->pages)gnttab_free_pages(map->count, map->pages);drivers/xen/gntdev.c +4
-0+ +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + kfree(map->frames); +#endif
Quoted 8 lines
Quoted 5 lines
Can this be done under if (
map->dma_vaddr) ?In other words, is it
possible fordma_vaddrto be NULL and still have unallocated frames pointer?It is possible to have vaddr == NULL and frames != NULL as we allocate frames outside of
gnttab_dma_alloc_pageswhich may fail. Calling kfree on NULL pointer is safe,
I am not questioning safety of the code, I would like avoid another ifdef.
Quoted 66 lines
so
I see no reason to change this code.Quoted 56 lines
Quoted 56 lines
kfree(map->pages);
kfree(map->grants);
kfree(map->map_ops);drivers/xen/gntdev.c +0
-0@@ -132,7 +176,8 @@ static void gntdev_free_map(struct grant_map *map) kfree(map); }-static struct
grant_map*gntdev_alloc_map(structgntdev_priv*priv, int count)
+static structgrant_map*gntdev_alloc_map(structgntdev_priv*priv, int count,
+ intdma_flags)
{
structgrant_map*add;
int i;drivers/xen/gntdev.c +0
-0@@ -155,6 +200,37 @@ static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) NULL == add->pages) goto err;+#ifdef
CONFIG_XEN_GRANT_DMA_ALLOC
+add->dma_flags=dma_flags;drivers/xen/gntdev.c +29
-0+ + /* + * Check if this mapping is requested to be backed + * by a DMA buffer. + */ + if (dma_flags & (GNTDEV_DMA_FLAG_WC | GNTDEV_DMA_FLAG_COHERENT)) { + struct gnttab_dma_alloc_args args; + + add->frames = kcalloc(count, sizeof(add->frames[0]), + GFP_KERNEL); + if (!add->frames) + goto err; + + /* Remember the device, so we can free DMA memory. */ + add->dma_dev = priv->dma_dev; + + args.dev = priv->dma_dev; + args.coherent = dma_flags & GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages = count; + args.pages = add->pages; + args.frames = add->frames; + + if (gnttab_dma_alloc_pages(&args)) + goto err; + + add->dma_vaddr = args.vaddr; + add->dma_bus_addr = args.dev_bus_addr; + } else +#endif if (
gnttab_alloc_pages(count, add->pages))
goto err;
@@ -325,6 +401,14 @@ static intmap_grant_pages(struct grant_map *map)
map->unmap_ops[i].handle = map->map_ops[i].handle; if (use_ptemod)Quoted 8 lines
drivers/xen/gntdev.c static int map_grant_pages(struct grant_map *map) · line 408
Quoted 6 lines
map->kunmap_ops[i].handle = map->kmap_ops[i].handle;
drivers/xen/gntdev.c +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?
Quoted 8 lines
I'd love to, but
pfn_to_mfnis only defined for x86, not ARM: [1] and [2] Thus,
drivers/xen/gntdev.c:408:10: error: implicit declaration of function ‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfn
How will this work on non-PV x86?
-boris
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
In reply to Oleksandr AndrushchenkoQuoted 28 lines · Oleksandr Andrushchenko
Quoted 27 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev.c +0
-0@@ -121,8 +146,27 @@ static void gntdev_free_map(struct grant_map *map) if (map == NULL) return;+#ifdef
CONFIG_XEN_GRANT_DMA_ALLOC
+ if (map->dma_vaddr) {
+ structgnttab_dma_alloc_argsargs;drivers/xen/gntdev.c +12
-0+ + args.dev = map->dma_dev; + args.coherent = map->dma_flags & GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages = map->count; + args.pages = map->pages; + args.frames = map->frames; + args.vaddr = map->dma_vaddr; + args.dev_bus_addr = map->dma_bus_addr; + + gnttab_dma_free_pages(&args); + } else +#endif if (
map->pages)gnttab_free_pages(map->count, map->pages);drivers/xen/gntdev.c +4
-0+ +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + kfree(map->frames); +#endif
Quoted 8 lines
Quoted 5 lines
Can this be done under if (
map->dma_vaddr) ?In other words, is it
possible fordma_vaddrto be NULL and still have unallocated frames pointer?It is possible to have vaddr == NULL and frames != NULL as we allocate frames outside of
gnttab_dma_alloc_pageswhich may fail. Calling kfree on NULL pointer is safe,
I am not questioning safety of the code, I would like avoid another ifdef.
Quoted 66 lines
so
I see no reason to change this code.Quoted 56 lines
Quoted 56 lines
kfree(map->pages);
kfree(map->grants);
kfree(map->map_ops);drivers/xen/gntdev.c +0
-0@@ -132,7 +176,8 @@ static void gntdev_free_map(struct grant_map *map) kfree(map); }-static struct
grant_map*gntdev_alloc_map(structgntdev_priv*priv, int count)
+static structgrant_map*gntdev_alloc_map(structgntdev_priv*priv, int count,
+ intdma_flags)
{
structgrant_map*add;
int i;drivers/xen/gntdev.c +0
-0@@ -155,6 +200,37 @@ static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) NULL == add->pages) goto err;+#ifdef
CONFIG_XEN_GRANT_DMA_ALLOC
+add->dma_flags=dma_flags;drivers/xen/gntdev.c +29
-0+ + /* + * Check if this mapping is requested to be backed + * by a DMA buffer. + */ + if (dma_flags & (GNTDEV_DMA_FLAG_WC | GNTDEV_DMA_FLAG_COHERENT)) { + struct gnttab_dma_alloc_args args; + + add->frames = kcalloc(count, sizeof(add->frames[0]), + GFP_KERNEL); + if (!add->frames) + goto err; + + /* Remember the device, so we can free DMA memory. */ + add->dma_dev = priv->dma_dev; + + args.dev = priv->dma_dev; + args.coherent = dma_flags & GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages = count; + args.pages = add->pages; + args.frames = add->frames; + + if (gnttab_dma_alloc_pages(&args)) + goto err; + + add->dma_vaddr = args.vaddr; + add->dma_bus_addr = args.dev_bus_addr; + } else +#endif if (
gnttab_alloc_pages(count, add->pages))
goto err;
@@ -325,6 +401,14 @@ static intmap_grant_pages(struct grant_map *map)
map->unmap_ops[i].handle = map->map_ops[i].handle; if (use_ptemod)Quoted 8 lines
drivers/xen/gntdev.c static int map_grant_pages(struct grant_map *map) · line 408
Quoted 6 lines
map->kunmap_ops[i].handle = map->kmap_ops[i].handle;
drivers/xen/gntdev.c +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?
Quoted 8 lines
I'd love to, but
pfn_to_mfnis only defined for x86, not ARM: [1] and [2] Thus,
drivers/xen/gntdev.c:408:10: error: implicit declaration of function ‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfn
How will this work on non-PV x86?
-boris
Re: [Xen-devel] [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
Quoted 7 lines · Boris Ostrovsky
Quoted 6 lines · Oleksandr Andrushchenko
drivers/xen/gntdev.c static void gntdev_free_map(struct grant_map *map) · line 148
Quoted 5 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev.c +0
-0@@ -121,8 +146,27 @@ static void gntdev_free_map(struct grant_map *map) if (map == NULL) return; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC
*Option 1: kfree(map->frames);*
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
drivers/xen/gntdev.c +4
-0+ if (map->dma_vaddr) { + struct gnttab_dma_alloc_args args; + + args.dev = map->dma_dev;
Quoted 8 lines
Quoted 8 lines
drivers/xen/gntdev.c static void gntdev_free_map(struct grant_map *map) · line 161
Quoted 8 lines
drivers/xen/gntdev.c +8
-0+ args.coherent = map->dma_flags & GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages = map->count; + args.pages = map->pages; + args.frames = map->frames; + args.vaddr = map->dma_vaddr; + args.dev_bus_addr = map->dma_bus_addr; + + gnttab_dma_free_pages(&args);
*Option 2: kfree(map->frames);*
Quoted 17 lines
Quoted 9 lines
Quoted 9 lines
drivers/xen/gntdev.c +6
-0+ } else +#endif if (map->pages) gnttab_free_pages(map->count, map->pages); + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + kfree(map->frames); +#endif Quoted 7 lines
Quoted 4 lines
Can this be done under if (
map->dma_vaddr) ?
In other words, is it
possible fordma_vaddrto be NULL and still have unallocated frames pointer?It is possible to have vaddr == NULL and frames != NULL as we allocate frames outside of
gnttab_dma_alloc_pageswhich may fail. Calling kfree on NULL pointer is safe,
Quoted 1 line
I am not questioning safety of the code, I would like avoid another ifdef.
Ah, I now understand, so you are asking if we can have that kfree(map->frames); in the place *Option 2* I marked above. Unfortunately no: map->frames is allocated before we try to allocate DMA memory, e.g. before dma_vaddr is set:
[...]
add->frames = kcalloc(count, sizeof(add->frames[0]), GFP_KERNEL);
if (!add->frames)
goto err;
[...]
if (gnttab_dma_alloc_pages(&args))
goto err;
add->dma_vaddr = args.vaddr;
[...]
err:
gntdev_free_map(add);
So, it is possible to enter gntdev_free_map with
frames != NULL and dma_vaddr == NULL. Option 1 above cannot be used as map->frames is needed for gnttab_dma_free_pages(&args); and Option 2 cannot be used as frames != NULL and dma_vaddr == NULL. Thus, I think that unfortunately we need that #ifdef. Option 3 below can also be considered, but that seems to be not good as we free resources in different places which looks inconsistent.
Sorry if I'm still missing your point.
Quoted 38 lines
Quoted 38 lines
so
I see no reason to change this code.Quoted 35 lines
Quoted 35 lines
kfree(map->pages);
kfree(map->grants);
kfree(map->map_ops);drivers/xen/gntdev.c +18
-0@@ -132,7 +176,8 @@ static void gntdev_free_map(struct grant_map *map) kfree(map); } -static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) +static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv,int count, + int dma_flags) { struct grant_map *add; int i;@@ -155,6 +200,37 @@ static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) NULL == add->pages) goto err; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + add->dma_flags = dma_flags; + + /* + * Check if this mapping is requested to be backed + * by a DMA buffer. + */ + if (dma_flags & (GNTDEV_DMA_FLAG_WC | GNTDEV_DMA_FLAG_COHERENT)) { + struct gnttab_dma_alloc_args args; + + add->frames = kcalloc(count, sizeof(add->frames[0]), + GFP_KERNEL); + if (!add->frames) + goto err; + + /* Remember the device, so we can free DMA memory. */ + add->dma_dev = priv->dma_dev;
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
drivers/xen/gntdev.c static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) · line 227
Quoted 8 lines
drivers/xen/gntdev.c +8
-0+ + args.dev = priv->dma_dev; + args.coherent = dma_flags & GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages = count; + args.pages = add->pages; + args.frames = add->frames; + + if (gnttab_dma_alloc_pages(&args))
*Option 3: kfree(map->frames);*
Quoted 22 lines
Quoted 22 lines
Quoted 11 lines
Quoted 11 lines
drivers/xen/gntdev.c +6
-0+ goto err; + + add->dma_vaddr = args.vaddr; + add->dma_bus_addr = args.dev_bus_addr; + } else +#endif if (gnttab_alloc_pages(count, add->pages)) goto err; @@ -325,6 +401,14 @@ static int map_grant_pages(struct grant_map*map)
map->unmap_ops[i].handle = map->map_ops[i].handle;Quoted 8 lines
drivers/xen/gntdev.c static int map_grant_pages(struct grant_map *map) · line 408
Quoted 7 lines
if (
use_ptemod)
map->kunmap_ops[i].handle = map->kmap_ops[i].handle;drivers/xen/gntdev.c +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM: [1] and [2] Thus,
Quoted 7 lines
Quoted 5 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function ‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdef CONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endif
Quoted 3 lines
-boris
Thank you,
Oleksandr
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
(Stefano, question for you at the end)
Quoted 61 lines · Oleksandr Andrushchenko
Quoted 8 lines · Boris Ostrovsky
Quoted 7 lines · Oleksandr Andrushchenko
Quoted 6 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev.c +0
-0@@ -121,8 +146,27 @@ static void gntdev_free_map(struct grant_map *map) if (map == NULL) return;+#ifdef
CONFIG_XEN_GRANT_DMA_ALLOC*Option 1: kfree(map->frames);*
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
+ if (
map->dma_vaddr) {
+ structgnttab_dma_alloc_argsargs;
+
+ args.dev =map->dma_dev;Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
+ args.coherent =
map->dma_flags&GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages =map->count;
+ args.pages =map->pages;
+ args.frames =map->frames;
+ args.vaddr =map->dma_vaddr;
+ args.dev_bus_addr =map->dma_bus_addr;
+
+gnttab_dma_free_pages(&args);*Option 2: kfree(map->frames);*
Quoted 17 lines
Quoted 9 lines
Quoted 9 lines
+ } else
+#endif
if (map->pages)gnttab_free_pages(map->count, map->pages);drivers/xen/gntdev.c +4
-0+ +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + kfree(map->frames); +#endif Quoted 7 lines
Quoted 4 lines
Can this be done under if (
map->dma_vaddr) ?
In other words, is it
possible fordma_vaddrto be NULL and still have unallocated frames pointer?It is possible to have vaddr == NULL and frames != NULL as we allocate frames outside of
gnttab_dma_alloc_pageswhich may fail. Calling kfree on NULL pointer is safe,Quoted 2 lines
I am not questioning safety of the code, I would like avoid another ifdef.
Ah, I now understand, so you are asking if we can have that
kfree(map->frames); in the place *Option 2* I marked above. Unfortunately no:map->framesis allocated before we try to allocate DMA memory, e.g. beforedma_vaddris set:
[...]
add->frames=kcalloc(count, sizeof(add->frames[0]), GFP_KERNEL);
if (!add->frames)
goto err;[...]
if (gnttab_dma_alloc_pages(&args))
goto err;
add->dma_vaddr= args.vaddr;
[...]
err:
gntdev_free_map(add);
Quoted 7 lines
So, it is possible to enter
gntdev_free_mapwith
frames != NULL anddma_vaddr== NULL. Option 1 above cannot be used asmap->framesis needed forgnttab_dma_free_pages(&args); and Option 2 cannot be used as frames != NULL anddma_vaddr== NULL. Thus, I think that unfortunately we need that #ifdef. Option 3 below can also be considered, but that seems to be not good as we free resources in different places which looks inconsistent.
I was only thinking of option 2. But if it is possible to have frames != NULL and dma_vaddr == NULL then perhaps we indeed will have to live with the extra ifdef.
Quoted 80 lines
Sorry if I'm still missing your point.
Quoted 40 lines
Quoted 40 lines
so
I see no reason to change this code.Quoted 37 lines
Quoted 37 lines
kfree(map->pages);
kfree(map->grants);
kfree(map->map_ops);drivers/xen/gntdev.c +0
-0@@ -132,7 +176,8 @@ static void gntdev_free_map(struct grant_map *map) kfree(map); }-static struct
grant_map*gntdev_alloc_map(structgntdev_priv*priv, int count)
+static structgrant_map*gntdev_alloc_map(structgntdev_priv*priv, int count,
+ intdma_flags)
{
structgrant_map*add;
int i;drivers/xen/gntdev.c +0
-0@@ -155,6 +200,37 @@ static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) NULL == add->pages) goto err;+#ifdef
CONFIG_XEN_GRANT_DMA_ALLOC
+add->dma_flags=dma_flags;
+
+ /*
+ * Check if this mapping is requested to be backed + * by a DMA buffer.
+ */
+ if (dma_flags& (GNTDEV_DMA_FLAG_WC|GNTDEV_DMA_FLAG_COHERENT)) {
+ structgnttab_dma_alloc_argsargs;drivers/xen/gntdev.c +8
-0+ + add->frames = kcalloc(count, sizeof(add->frames[0]), + GFP_KERNEL); + if (!add->frames) + goto err; + + /* Remember the device, so we can free DMA memory. */ + add->dma_dev = priv->dma_dev;Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
drivers/xen/gntdev.c static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) · line 227
Quoted 8 lines
drivers/xen/gntdev.c +8
-0+ + args.dev = priv->dma_dev; + args.coherent = dma_flags & GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages = count; + args.pages = add->pages; + args.frames = add->frames; + + if (gnttab_dma_alloc_pages(&args))*Option 3: kfree(map->frames);*
Quoted 29 lines
Quoted 28 lines
Quoted 11 lines
Quoted 11 lines
+ goto err;
drivers/xen/gntdev.c +5
-0+ + add->dma_vaddr = args.vaddr; + add->dma_bus_addr = args.dev_bus_addr; + } else +#endif if (
gnttab_alloc_pages(count, add->pages))
goto err;
@@ -325,6 +401,14 @@ static intmap_grant_pages(struct grant_map *map)
map->unmap_ops[i].handle = map->map_ops[i].handle;Quoted 8 lines
drivers/xen/gntdev.c static int map_grant_pages(struct grant_map *map) · line 408
Quoted 7 lines
if (
use_ptemod)
map->kunmap_ops[i].handle = map->kmap_ops[i].handle;drivers/xen/gntdev.c +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM: [1] and [2]
Thus,
drivers/xen/gntdev.c:408:10: error: implicit declaration of function ‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfn
Quoted 8 lines
Quoted 1 line
How will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endif
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
-boris
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
In reply to Oleksandr Andrushchenko(Stefano, question for you at the end)
Quoted 61 lines · Oleksandr Andrushchenko
Quoted 8 lines · Boris Ostrovsky
Quoted 7 lines · Oleksandr Andrushchenko
Quoted 6 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev.c +0
-0@@ -121,8 +146,27 @@ static void gntdev_free_map(struct grant_map *map) if (map == NULL) return;+#ifdef
CONFIG_XEN_GRANT_DMA_ALLOC*Option 1: kfree(map->frames);*
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
+ if (
map->dma_vaddr) {
+ structgnttab_dma_alloc_argsargs;
+
+ args.dev =map->dma_dev;Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
+ args.coherent =
map->dma_flags&GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages =map->count;
+ args.pages =map->pages;
+ args.frames =map->frames;
+ args.vaddr =map->dma_vaddr;
+ args.dev_bus_addr =map->dma_bus_addr;
+
+gnttab_dma_free_pages(&args);*Option 2: kfree(map->frames);*
Quoted 17 lines
Quoted 9 lines
Quoted 9 lines
+ } else
+#endif
if (map->pages)gnttab_free_pages(map->count, map->pages);drivers/xen/gntdev.c +4
-0+ +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + kfree(map->frames); +#endif Quoted 7 lines
Quoted 4 lines
Can this be done under if (
map->dma_vaddr) ?
In other words, is it
possible fordma_vaddrto be NULL and still have unallocated frames pointer?It is possible to have vaddr == NULL and frames != NULL as we allocate frames outside of
gnttab_dma_alloc_pageswhich may fail. Calling kfree on NULL pointer is safe,Quoted 2 lines
I am not questioning safety of the code, I would like avoid another ifdef.
Ah, I now understand, so you are asking if we can have that
kfree(map->frames); in the place *Option 2* I marked above. Unfortunately no:map->framesis allocated before we try to allocate DMA memory, e.g. beforedma_vaddris set:
[...]
add->frames=kcalloc(count, sizeof(add->frames[0]), GFP_KERNEL);
if (!add->frames)
goto err;[...]
if (gnttab_dma_alloc_pages(&args))
goto err;
add->dma_vaddr= args.vaddr;
[...]
err:
gntdev_free_map(add);
Quoted 7 lines
So, it is possible to enter
gntdev_free_mapwith
frames != NULL anddma_vaddr== NULL. Option 1 above cannot be used asmap->framesis needed forgnttab_dma_free_pages(&args); and Option 2 cannot be used as frames != NULL anddma_vaddr== NULL. Thus, I think that unfortunately we need that #ifdef. Option 3 below can also be considered, but that seems to be not good as we free resources in different places which looks inconsistent.
I was only thinking of option 2. But if it is possible to have frames != NULL and dma_vaddr == NULL then perhaps we indeed will have to live with the extra ifdef.
Quoted 80 lines
Sorry if I'm still missing your point.
Quoted 40 lines
Quoted 40 lines
so
I see no reason to change this code.Quoted 37 lines
Quoted 37 lines
kfree(map->pages);
kfree(map->grants);
kfree(map->map_ops);drivers/xen/gntdev.c +0
-0@@ -132,7 +176,8 @@ static void gntdev_free_map(struct grant_map *map) kfree(map); }-static struct
grant_map*gntdev_alloc_map(structgntdev_priv*priv, int count)
+static structgrant_map*gntdev_alloc_map(structgntdev_priv*priv, int count,
+ intdma_flags)
{
structgrant_map*add;
int i;drivers/xen/gntdev.c +0
-0@@ -155,6 +200,37 @@ static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) NULL == add->pages) goto err;+#ifdef
CONFIG_XEN_GRANT_DMA_ALLOC
+add->dma_flags=dma_flags;
+
+ /*
+ * Check if this mapping is requested to be backed + * by a DMA buffer.
+ */
+ if (dma_flags& (GNTDEV_DMA_FLAG_WC|GNTDEV_DMA_FLAG_COHERENT)) {
+ structgnttab_dma_alloc_argsargs;drivers/xen/gntdev.c +8
-0+ + add->frames = kcalloc(count, sizeof(add->frames[0]), + GFP_KERNEL); + if (!add->frames) + goto err; + + /* Remember the device, so we can free DMA memory. */ + add->dma_dev = priv->dma_dev;Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
drivers/xen/gntdev.c static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) · line 227
Quoted 8 lines
drivers/xen/gntdev.c +8
-0+ + args.dev = priv->dma_dev; + args.coherent = dma_flags & GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages = count; + args.pages = add->pages; + args.frames = add->frames; + + if (gnttab_dma_alloc_pages(&args))*Option 3: kfree(map->frames);*
Quoted 29 lines
Quoted 28 lines
Quoted 11 lines
Quoted 11 lines
+ goto err;
drivers/xen/gntdev.c +5
-0+ + add->dma_vaddr = args.vaddr; + add->dma_bus_addr = args.dev_bus_addr; + } else +#endif if (
gnttab_alloc_pages(count, add->pages))
goto err;
@@ -325,6 +401,14 @@ static intmap_grant_pages(struct grant_map *map)
map->unmap_ops[i].handle = map->map_ops[i].handle;Quoted 8 lines
drivers/xen/gntdev.c static int map_grant_pages(struct grant_map *map) · line 408
Quoted 7 lines
if (
use_ptemod)
map->kunmap_ops[i].handle = map->kmap_ops[i].handle;drivers/xen/gntdev.c +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM: [1] and [2]
Thus,
drivers/xen/gntdev.c:408:10: error: implicit declaration of function ‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfn
Quoted 8 lines
Quoted 1 line
How will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endif
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
-boris
Re: [Xen-devel] [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
Quoted 71 lines · Boris Ostrovsky
(Stefano, question for you at the end)
Quoted 60 lines · Oleksandr Andrushchenko
Quoted 8 lines · Boris Ostrovsky
Quoted 7 lines · Oleksandr Andrushchenko
drivers/xen/gntdev.c static void gntdev_free_map(struct grant_map · line 149
Quoted 6 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev.c +0
-0@@ -121,8 +146,27 @@ static void gntdev_free_map(struct grant_map *map) if (map == NULL) return; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC*Option 1: kfree(map->frames);*
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
drivers/xen/gntdev.c +4
-0+ if (map->dma_vaddr) { + struct gnttab_dma_alloc_args args; + + args.dev = map->dma_dev;Quoted 8 lines
Quoted 8 lines
drivers/xen/gntdev.c static void gntdev_free_map(struct grant_map *map) · line 161
Quoted 8 lines
drivers/xen/gntdev.c +8
-0+ args.coherent = map->dma_flags & GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages = map->count; + args.pages = map->pages; + args.frames = map->frames; + args.vaddr = map->dma_vaddr; + args.dev_bus_addr = map->dma_bus_addr; + + gnttab_dma_free_pages(&args);*Option 2: kfree(map->frames);*
Quoted 16 lines
Quoted 9 lines
Quoted 9 lines
drivers/xen/gntdev.c +6
-0+ } else +#endif if (map->pages) gnttab_free_pages(map->count, map->pages); + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + kfree(map->frames); +#endif Quoted 7 lines
Quoted 4 lines
Can this be done under if (
map->dma_vaddr) ?
In other words, is it
possible fordma_vaddrto be NULL and still have unallocated frames pointer?It is possible to have vaddr == NULL and frames != NULL as we allocate frames outside of
gnttab_dma_alloc_pageswhich may fail. Calling kfree on NULL pointer is safe,Quoted 2 lines
I am not questioning safety of the code, I would like avoid another ifdef.
Ah, I now understand, so you are asking if we can have that
kfree(map->frames); in the place *Option 2* I marked above. Unfortunately no:map->framesis allocated before we try to allocate DMA memory, e.g. beforedma_vaddris set:
[...]
add->frames=kcalloc(count, sizeof(add->frames[0]), GFP_KERNEL);
if (!add->frames)
goto err;[...]
if (gnttab_dma_alloc_pages(&args))
goto err;
add->dma_vaddr= args.vaddr;
[...]
err:
gntdev_free_map(add);Quoted 7 lines
So, it is possible to enter
gntdev_free_mapwith
frames != NULL anddma_vaddr== NULL. Option 1 above cannot be used asmap->framesis needed forgnttab_dma_free_pages(&args); and Option 2 cannot be used as frames != NULL anddma_vaddr== NULL. Thus, I think that unfortunately we need that #ifdef. Option 3 below can also be considered, but that seems to be not good as we free resources in different places which looks inconsistent.
Quoted 3 lines
I was only thinking of option 2. But if it is possible to have frames != NULL and
dma_vaddr== NULL then perhaps we indeed will have to live with the extra ifdef.
ok
Quoted 86 lines
Quoted 77 lines
Sorry if I'm still missing your point.
Quoted 39 lines
Quoted 39 lines
so
I see no reason to change this code.Quoted 37 lines
Quoted 37 lines
kfree(map->pages);
kfree(map->grants);
kfree(map->map_ops);drivers/xen/gntdev.c +18
-0@@ -132,7 +176,8 @@ static void gntdev_free_map(struct grant_map *map) kfree(map); } -static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) +static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv,int count, + int dma_flags) { struct grant_map *add; int i;@@ -155,6 +200,37 @@ static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) NULL == add->pages) goto err; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + add->dma_flags = dma_flags; + + /* + * Check if this mapping is requested to be backed + * by a DMA buffer. + */ + if (dma_flags & (GNTDEV_DMA_FLAG_WC |GNTDEV_DMA_FLAG_COHERENT )) { + struct gnttab_dma_alloc_args args; + + add->frames = kcalloc(count, sizeof(add->frames[0]), + GFP_KERNEL); + if (!add->frames) + goto err; + + /* Remember the device, so we can free DMA memory. */ + add->dma_dev = priv->dma_dev;Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
drivers/xen/gntdev.c static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) · line 227
Quoted 8 lines
drivers/xen/gntdev.c +8
-0+ + args.dev = priv->dma_dev; + args.coherent = dma_flags & GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages = count; + args.pages = add->pages; + args.frames = add->frames; + + if (gnttab_dma_alloc_pages(&args))*Option 3: kfree(map->frames);*
Quoted 27 lines
Quoted 27 lines
Quoted 11 lines
Quoted 11 lines
drivers/xen/gntdev.c +6
-0+ goto err; + + add->dma_vaddr = args.vaddr; + add->dma_bus_addr = args.dev_bus_addr; + } else +#endif if (gnttab_alloc_pages(count, add->pages)) goto err; @@ -325,6 +401,14 @@ static int map_grant_pages(struct grant_map*map)
map->unmap_ops[i].handle = map->map_ops[i].handle;Quoted 8 lines
drivers/xen/gntdev.c static int map_grant_pages(struct grant_map *map) · line 408
Quoted 7 lines
if (
use_ptemod)
map->kunmap_ops[i].handle = map->kmap_ops[i].handle;drivers/xen/gntdev.c +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM: [1] and [2]
Thus,
drivers/xen/gntdev.c:408:10: error: implicit declaration of function ‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));Quoted 9 lines
Quoted 2 lines
Quoted 1 line
So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endif
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap __pfn_to_mfn with static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}
Quoted 3 lines
-boris
Thank you,
Oleksandr
Stefano Stabellini
maintainerRe: [Xen-devel] [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
Quoted 165 lines · Oleksandr Andrushchenko
Quoted 71 lines · Boris Ostrovsky
(Stefano, question for you at the end)
Quoted 60 lines · Oleksandr Andrushchenko
Quoted 8 lines · Boris Ostrovsky
Quoted 7 lines · Oleksandr Andrushchenko
Review static void gntdev_free_map(struct grant_map · line 149
Quoted 6 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
(quoted diff) +0
-0@@ -121,8 +146,27 @@ static void gntdev_free_map(struct grant_map *map) if (map == NULL) return; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC*Option 1: kfree(map->frames);*
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
(quoted diff) +4
-0+ if (map->dma_vaddr) { + struct gnttab_dma_alloc_args args; + + args.dev = map->dma_dev;Quoted 8 lines
Quoted 8 lines
Review static void gntdev_free_map(struct grant_map · line 161
Quoted 8 lines
(quoted diff) +8
-0+ args.coherent = map->dma_flags & GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages = map->count; + args.pages = map->pages; + args.frames = map->frames; + args.vaddr = map->dma_vaddr; + args.dev_bus_addr = map->dma_bus_addr; + + gnttab_dma_free_pages(&args);*Option 2: kfree(map->frames);*
Quoted 16 lines
Quoted 9 lines
Quoted 9 lines
(quoted diff) +6
-0+ } else +#endif if (map->pages) gnttab_free_pages(map->count, map->pages); + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + kfree(map->frames); +#endifQuoted 7 lines
Quoted 4 lines
Can this be done under if (
map->dma_vaddr) ?
In other words, is it
possible fordma_vaddrto be NULL and still have unallocated frames pointer?It is possible to have vaddr == NULL and frames != NULL as we allocate frames outside of
gnttab_dma_alloc_pageswhich may fail. Calling kfree on NULL pointer is safe,Quoted 2 lines
I am not questioning safety of the code, I would like avoid another ifdef.
Ah, I now understand, so you are asking if we can have that
kfree(map->frames); in the place *Option 2* I marked above. Unfortunately no:map->framesis allocated before we try to allocate DMA memory, e.g. beforedma_vaddris set:
[...]
add->frames=kcalloc(count, sizeof(add->frames[0]), GFP_KERNEL);
if (!add->frames)
goto err;[...]
if (gnttab_dma_alloc_pages(&args))
goto err;
add->dma_vaddr= args.vaddr;
[...]
err:
gntdev_free_map(add);Quoted 7 lines
So, it is possible to enter
gntdev_free_mapwith
frames != NULL anddma_vaddr== NULL. Option 1 above cannot be used asmap->framesis needed forgnttab_dma_free_pages(&args); and Option 2 cannot be used as frames != NULL anddma_vaddr== NULL. Thus, I think that unfortunately we need that #ifdef. Option 3 below can also be considered, but that seems to be not good as we free resources in different places which looks inconsistent.Quoted 3 lines
I was only thinking of option 2. But if it is possible to have frames != NULL and
dma_vaddr== NULL then perhaps we indeed will have to live with the extra ifdef.ok
Quoted 89 lines
Quoted 89 lines
Sorry if I'm still missing your point.
Quoted 40 lines
Quoted 40 lines
so
I see no reason to change this code.Quoted 38 lines
Quoted 38 lines
kfree(map->pages);
kfree(map->grants);
kfree(map->map_ops);(quoted diff) +18
-0@@ -132,7 +176,8 @@ static void gntdev_free_map(struct grant_map *map) kfree(map); } -static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) +static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count, + int dma_flags) { struct grant_map *add; int i;@@ -155,6 +200,37 @@ static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) NULL == add->pages) goto err; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + add->dma_flags = dma_flags; + + /* + * Check if this mapping is requested to be backed + * by a DMA buffer. + */ + if (dma_flags & (GNTDEV_DMA_FLAG_WC | GNTDEV_DMA_FLAG_COHERENT)) { + struct gnttab_dma_alloc_args args; + + add->frames = kcalloc(count, sizeof(add->frames[0]), + GFP_KERNEL); + if (!add->frames) + goto err; + + /* Remember the device, so we can free DMA memory. */ + add->dma_dev = priv->dma_dev;Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Review static struct grant_map · line 228
Quoted 8 lines
(quoted diff) +8
-0+ + args.dev = priv->dma_dev; + args.coherent = dma_flags & GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages = count; + args.pages = add->pages; + args.frames = add->frames; + + if (gnttab_dma_alloc_pages(&args))*Option 3: kfree(map->frames);*
Quoted 25 lines
Quoted 25 lines
Quoted 13 lines
Quoted 13 lines
(quoted diff) +6
-0+ goto err; + + add->dma_vaddr = args.vaddr; + add->dma_bus_addr = args.dev_bus_addr; + } else +#endif if (gnttab_alloc_pages(count, add->pages)) goto err; @@ -325,6 +401,14 @@ static int map_grant_pages(struct
grant_map
*map)
map->unmap_ops[i].handle = map->map_ops[i].handle; if (use_ptemod)Quoted 8 lines
Review
Quoted 7 lines
map->kunmap_ops[i].handle =
map->kmap_ops[i].handle;(quoted diff) +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM: [1] and [2]
Thus,Quoted 6 lines
Quoted 5 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function ‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endif
Quoted 8 lines
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap
__pfn_to_mfnwith static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}
A Xen on ARM guest doesn't actually know the mfns behind its own pseudo-physical pages. This is why we stopped using pfn_to_mfn and started using pfn_to_bfn instead, which will generally return "pfn", unless the page is a foreign grant. See include/xen/arm/page.h. pfn_to_bfn was also introduced on x86. For example, see the usage of pfn_to_bfn in drivers/xen/swiotlb-xen.c. Otherwise, if you don't care about other mapped grants, you can just use pfn_to_gfn, that always returns pfn.
Also, for your information, we support different page granularities in Linux as a Xen guest, see the comment at include/xen/arm/page.h:
/*
* The pseudo-physical frame (pfn) used in all the helpers is always based
* on Xen page granularity (i.e 4KB).
*
* A Linux page may be split across multiple non-contiguous Xen page so we
* have to keep track with frame based on 4KB page granularity. *
* PV drivers should never make a direct usage of those helpers (particularly
* pfn_to_gfn and gfn_to_pfn).
*/
A Linux page could be 64K, but a Xen page is always 4K. A granted page is also 4K. We have helpers to take into account the offsets to map multiple Xen grants in a single Linux page, see for example drivers/xen/grant-table.c:gnttab_foreach_grant. Most PV drivers have been converted to be able to work with 64K pages correctly, but if I remember correctly gntdev.c is the only remaining driver that doesn't support 64K pages yet, so you don't have to deal with it if you don't want to.
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
Quoted 40 lines · Stefano Stabellini
Quoted 31 lines
Quoted 31 lines
Quoted 31 lines
Quoted 18 lines
Quoted 18 lines
Quoted 14 lines
Review
Quoted 13 lines
@@ -325,6 +401,14 @@ static int map_grant_pages(struct
grant_map
*map)
map->unmap_ops[i].handle = map->map_ops[i].handle; if (use_ptemod) map->kunmap_ops[i].handle =
map->kmap_ops[i].handle;(quoted diff) +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM: [1] and [2]
Thus,Quoted 6 lines
Quoted 5 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function ‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endifQuoted 8 lines
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap
__pfn_to_mfnwith static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}
Quoted 8 lines
A Xen on ARM guest doesn't actually know the mfns behind its own pseudo-physical pages. This is why we stopped using
pfn_to_mfnand started usingpfn_to_bfninstead, which will generally return "pfn", unless the page is a foreign grant. Seeinclude/xen/arm/page.h.pfn_to_bfnwas also introduced on x86. For example, see the usage ofpfn_to_bfnindrivers/xen/swiotlb-xen.c. Otherwise, if you don't care about other mapped grants, you can just usepfn_to_gfn, that always returns pfn.
I think then this code needs to use pfn_to_bfn().
Quoted 15 lines
Also, for your information, we support different page granularities in Linux as a Xen guest, see the comment at
include/xen/arm/page.h:/*
* The pseudo-physical frame (pfn) used in all the helpers is always based
* on Xen page granularity (i.e 4KB).
*
* A Linux page may be split across multiple non-contiguous Xen page so we
* have to keep track with frame based on 4KB page granularity. *
* PV drivers should never make a direct usage of those helpers (particularly
*pfn_to_gfnandgfn_to_pfn).
*/
Quoted 8 lines
A Linux page could be 64K, but a Xen page is always 4K. A granted page is also 4K. We have helpers to take into account the offsets to map multiple Xen grants in a single Linux page, see for example drivers/xen/grant-table.c:gnttab_foreach_grant. Most PV drivers have been converted to be able to work with 64K pages correctly, but if I remember correctly
gntdev.cis the only remaining driver that doesn't support 64K pages yet, so you don't have to deal with it if you don't want to.
I believe somewhere in this series there is a test for PAGE_SIZE vs. XEN_PAGE_SIZE. Right, Oleksandr?
Thanks for the explanation.
-boris
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
In reply to Stefano StabelliniQuoted 40 lines · Stefano Stabellini
Quoted 31 lines
Quoted 31 lines
Quoted 31 lines
Quoted 18 lines
Quoted 18 lines
Quoted 14 lines
Review
Quoted 13 lines
@@ -325,6 +401,14 @@ static int map_grant_pages(struct
grant_map
*map)
map->unmap_ops[i].handle = map->map_ops[i].handle; if (use_ptemod) map->kunmap_ops[i].handle =
map->kmap_ops[i].handle;(quoted diff) +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM: [1] and [2]
Thus,Quoted 6 lines
Quoted 5 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function ‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endifQuoted 8 lines
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap
__pfn_to_mfnwith static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}
Quoted 8 lines
A Xen on ARM guest doesn't actually know the mfns behind its own pseudo-physical pages. This is why we stopped using
pfn_to_mfnand started usingpfn_to_bfninstead, which will generally return "pfn", unless the page is a foreign grant. Seeinclude/xen/arm/page.h.pfn_to_bfnwas also introduced on x86. For example, see the usage ofpfn_to_bfnindrivers/xen/swiotlb-xen.c. Otherwise, if you don't care about other mapped grants, you can just usepfn_to_gfn, that always returns pfn.
I think then this code needs to use pfn_to_bfn().
Quoted 15 lines
Also, for your information, we support different page granularities in Linux as a Xen guest, see the comment at
include/xen/arm/page.h:/*
* The pseudo-physical frame (pfn) used in all the helpers is always based
* on Xen page granularity (i.e 4KB).
*
* A Linux page may be split across multiple non-contiguous Xen page so we
* have to keep track with frame based on 4KB page granularity. *
* PV drivers should never make a direct usage of those helpers (particularly
*pfn_to_gfnandgfn_to_pfn).
*/
Quoted 8 lines
A Linux page could be 64K, but a Xen page is always 4K. A granted page is also 4K. We have helpers to take into account the offsets to map multiple Xen grants in a single Linux page, see for example drivers/xen/grant-table.c:gnttab_foreach_grant. Most PV drivers have been converted to be able to work with 64K pages correctly, but if I remember correctly
gntdev.cis the only remaining driver that doesn't support 64K pages yet, so you don't have to deal with it if you don't want to.
I believe somewhere in this series there is a test for PAGE_SIZE vs. XEN_PAGE_SIZE. Right, Oleksandr?
Thanks for the explanation.
-boris
Re: [Xen-devel] [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
Quoted 48 lines · Boris Ostrovsky
Quoted 38 lines · Stefano Stabellini
Quoted 30 lines
Quoted 30 lines
Quoted 30 lines
Quoted 17 lines
Quoted 17 lines
Quoted 5 lines
Quoted 5 lines
@@ -325,6 +401,14 @@ static int map_grant_pages(struct
grant_map
*map)
map->unmap_ops[i].handle = map->map_ops[i].handle; if (use_ptemod)Quoted 8 lines
Review
Quoted 7 lines
map->kunmap_ops[i].handle =
map->kmap_ops[i].handle;(quoted diff) +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM: [1] and [2]
Thus,Quoted 6 lines
Quoted 5 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function ‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endifQuoted 8 lines
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap
__pfn_to_mfnwith static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}Quoted 8 lines
A Xen on ARM guest doesn't actually know the mfns behind its own pseudo-physical pages. This is why we stopped using
pfn_to_mfnand started usingpfn_to_bfninstead, which will generally return "pfn", unless the page is a foreign grant. Seeinclude/xen/arm/page.h.pfn_to_bfnwas also introduced on x86. For example, see the usage ofpfn_to_bfnindrivers/xen/swiotlb-xen.c. Otherwise, if you don't care about other mapped grants, you can just usepfn_to_gfn, that always returns pfn.
Quoted 1 line
I think then this code needs to use
pfn_to_bfn().
Ok
Quoted 25 lines
Quoted 16 lines
Also, for your information, we support different page granularities in Linux as a Xen guest, see the comment at
include/xen/arm/page.h:/*
* The pseudo-physical frame (pfn) used in all the helpers is always based
* on Xen page granularity (i.e 4KB).
*
* A Linux page may be split across multiple non-contiguous Xen page so we
* have to keep track with frame based on 4KB page granularity. *
* PV drivers should never make a direct usage of those helpers (particularly
*pfn_to_gfnandgfn_to_pfn).
*/Quoted 8 lines
A Linux page could be 64K, but a Xen page is always 4K. A granted page is also 4K. We have helpers to take into account the offsets to map multiple Xen grants in a single Linux page, see for example drivers/xen/grant-table.c:gnttab_foreach_grant. Most PV drivers have been converted to be able to work with 64K pages correctly, but if I remember correctly
gntdev.cis the only remaining driver that doesn't support 64K pages yet, so you don't have to deal with it if you don't want to.
Quoted 2 lines
I believe somewhere in this series there is a test for
PAGE_SIZEvs.XEN_PAGE_SIZE. Right, Oleksandr?
Not in gntdev. You might have seen this in xen-drmfront/xen-sndfront, but I didn't touch gntdev for that. Do you want me to add yet another patch in the series to check for that?
Quoted 3 lines
Thanks for the explanation.
-boris
Thank you,
Oleksandr
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Stefano Stabellini
maintainerRe: [Xen-devel] [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
Quoted 82 lines · Oleksandr Andrushchenko
Quoted 51 lines · Boris Ostrovsky
Quoted 41 lines · Stefano Stabellini
Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
Quoted 19 lines
Quoted 19 lines
Quoted 6 lines
Quoted 6 lines
@@ -325,6 +401,14 @@ static int map_grant_pages(struct
grant_map
*map)
map->unmap_ops[i].handle =
map->map_ops[i].handle;
if (use_ptemod)Quoted 8 lines
Review
Quoted 7 lines
map->kunmap_ops[i].handle =
map->kmap_ops[i].handle;(quoted diff) +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM:
[1]
and [2]
Thus,Quoted 7 lines
Quoted 6 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function
‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endifQuoted 8 lines
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap
__pfn_to_mfnwith static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}Quoted 8 lines
A Xen on ARM guest doesn't actually know the mfns behind its own pseudo-physical pages. This is why we stopped using
pfn_to_mfnand started usingpfn_to_bfninstead, which will generally return "pfn", unless the page is a foreign grant. Seeinclude/xen/arm/page.h.pfn_to_bfnwas also introduced on x86. For example, see the usage ofpfn_to_bfnindrivers/xen/swiotlb-xen.c. Otherwise, if you don't care about other mapped grants, you can just usepfn_to_gfn, that always returns pfn.Quoted 1 line
I think then this code needs to use
pfn_to_bfn().Ok
Quoted 28 lines
Quoted 27 lines
Also, for your information, we support different page granularities in Linux as a Xen guest, see the comment at
include/xen/arm/page.h:/*
* The pseudo-physical frame (pfn) used in all the helpers is always
based
* on Xen page granularity (i.e 4KB).
*
* A Linux page may be split across multiple non-contiguous Xen page so
we
* have to keep track with frame based on 4KB page granularity. *
* PV drivers should never make a direct usage of those helpers
(particularly
*pfn_to_gfnandgfn_to_pfn).
*/A Linux page could be 64K, but a Xen page is always 4K. A granted page is also 4K. We have helpers to take into account the offsets to map multiple Xen grants in a single Linux page, see for example drivers/xen/grant-table.c:gnttab_foreach_grant. Most PV drivers have been converted to be able to work with 64K pages correctly, but if I remember correctly
gntdev.cis the only remaining driver that doesn't support 64K pages yet, so you don't have to deal with it if you don't want to.
Quoted 5 lines
Quoted 2 lines
I believe somewhere in this series there is a test for
PAGE_SIZEvs.XEN_PAGE_SIZE. Right, Oleksandr?Not in gntdev. You might have seen this in xen-drmfront/xen-sndfront, but I didn't touch gntdev for that. Do you want me to add yet another patch in the series to check for that?
gntdev.c is already not capable of handling PAGE_SIZE != XEN_PAGE_SIZE, so you are not going to break anything that is not already broken :-) If your new gntdev.c code relies on PAGE_SIZE == XEN_PAGE_SIZE, it might be good to add an in-code comment about it, just to make it easier to fix the whole of gntdev.c in the future.
Quoted 1 line
Quoted 1 line
Thanks for the explanation.
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Xen-devel] [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
Quoted 82 lines · Stefano Stabellini
Quoted 81 lines · Oleksandr Andrushchenko
Quoted 50 lines · Boris Ostrovsky
Quoted 41 lines · Stefano Stabellini
Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
Quoted 19 lines
Quoted 19 lines
Quoted 6 lines
Quoted 6 lines
@@ -325,6 +401,14 @@ static int map_grant_pages(struct
grant_map
*map)
map->unmap_ops[i].handle =
map->map_ops[i].handle;
if (use_ptemod)Quoted 8 lines
Review
Quoted 7 lines
map->kunmap_ops[i].handle =map->kmap_ops[i].handle;
(quoted diff) +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM:
[1]
and [2]
Thus,Quoted 7 lines
Quoted 6 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function
‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endifQuoted 8 lines
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap
__pfn_to_mfnwith static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}Quoted 8 lines
A Xen on ARM guest doesn't actually know the mfns behind its own pseudo-physical pages. This is why we stopped using
pfn_to_mfnand started usingpfn_to_bfninstead, which will generally return "pfn", unless the page is a foreign grant. Seeinclude/xen/arm/page.h.pfn_to_bfnwas also introduced on x86. For example, see the usage ofpfn_to_bfnindrivers/xen/swiotlb-xen.c. Otherwise, if you don't care about other mapped grants, you can just usepfn_to_gfn, that always returns pfn.Quoted 1 line
I think then this code needs to use
pfn_to_bfn().Ok
Quoted 28 lines
Quoted 18 lines
Also, for your information, we support different page granularities in Linux as a Xen guest, see the comment at
include/xen/arm/page.h:/*
* The pseudo-physical frame (pfn) used in all the helpers is always
based
* on Xen page granularity (i.e 4KB).
*
* A Linux page may be split across multiple non-contiguous Xen page so
we
* have to keep track with frame based on 4KB page granularity. *
* PV drivers should never make a direct usage of those helpers
(particularly
*pfn_to_gfnandgfn_to_pfn).
*/Quoted 8 lines
A Linux page could be 64K, but a Xen page is always 4K. A granted page is also 4K. We have helpers to take into account the offsets to map multiple Xen grants in a single Linux page, see for example drivers/xen/grant-table.c:gnttab_foreach_grant. Most PV drivers have been converted to be able to work with 64K pages correctly, but if I remember correctly
gntdev.cis the only remaining driver that doesn't support 64K pages yet, so you don't have to deal with it if you don't want to.I believe somewhere in this series there is a test for
PAGE_SIZEvs.XEN_PAGE_SIZE. Right, Oleksandr?
Quoted 9 lines
Quoted 3 lines
Not in gntdev. You might have seen this in xen-drmfront/xen-sndfront, but I didn't touch gntdev for that. Do you want me to add yet another patch in the series to check for that?
gntdev.cis already not capable of handlingPAGE_SIZE!=XEN_PAGE_SIZE, so you are not going to break anything that is not already broken :-) If your newgntdev.ccode relies onPAGE_SIZE==XEN_PAGE_SIZE, it might be good to add an in-code comment about it, just to make it easier to fix the whole ofgntdev.cin the future.
Yes, I just mean I can add something like [1] as a separate patch to the series, so we are on the safe side here
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Thanks for the explanation.
[1] https://cgit.freedesktop.org/drm/drm-misc/tree/drivers/gpu/drm/xen/xen_drm_front.c#n813
Re: [Xen-devel] [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
Hi,
Quoted 86 lines · Oleksandr Andrushchenko
Quoted 85 lines · Stefano Stabellini
Quoted 84 lines · Oleksandr Andrushchenko
Quoted 50 lines · Boris Ostrovsky
Quoted 41 lines · Stefano Stabellini
Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
Quoted 19 lines
Quoted 19 lines
Quoted 6 lines
Quoted 6 lines
@@ -325,6 +401,14 @@ static int map_grant_pages(struct
grant_map
*map)
map->unmap_ops[i].handle = map->map_ops[i].handle;
if (use_ptemod)Quoted 8 lines
Review
Quoted 7 lines
map->kunmap_ops[i].handle =
map->kmap_ops[i].handle;(quoted diff) +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM:
[1]
and [2]
Thus,Quoted 7 lines
Quoted 6 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function
‘pfn_to_mfn’ [-Werror=implicit-function-declaration] mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endifQuoted 8 lines
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap
__pfn_to_mfnwith static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}Quoted 8 lines
A Xen on ARM guest doesn't actually know the mfns behind its own pseudo-physical pages. This is why we stopped using
pfn_to_mfnand started usingpfn_to_bfninstead, which will generally return "pfn", unless the page is a foreign grant. Seeinclude/xen/arm/page.h.pfn_to_bfnwas also introduced on x86. For example, see the usage ofpfn_to_bfnindrivers/xen/swiotlb-xen.c. Otherwise, if you don't care about other mapped grants, you can just usepfn_to_gfn, that always returns pfn.Quoted 1 line
I think then this code needs to use
pfn_to_bfn().Ok
Quoted 26 lines
Quoted 18 lines
Also, for your information, we support different page granularities in Linux as a Xen guest, see the comment at
include/xen/arm/page.h:/*
* The pseudo-physical frame (pfn) used in all the helpers is always based
* on Xen page granularity (i.e 4KB).
*
* A Linux page may be split across multiple non-contiguous Xen page so we
* have to keep track with frame based on 4KB page granularity. *
* PV drivers should never make a direct usage of those helpers (particularly
*pfn_to_gfnandgfn_to_pfn).
*/Quoted 8 lines
A Linux page could be 64K, but a Xen page is always 4K. A granted page is also 4K. We have helpers to take into account the offsets to map multiple Xen grants in a single Linux page, see for example drivers/xen/grant-table.c:gnttab_foreach_grant. Most PV drivers have been converted to be able to work with 64K pages correctly, but if I remember correctly
gntdev.cis the only remaining driver that doesn't support 64K pages yet, so you don't have to deal with it if you don't want to.Quoted 2 lines
I believe somewhere in this series there is a test for
PAGE_SIZEvs.XEN_PAGE_SIZE. Right, Oleksandr?Not in gntdev. You might have seen this in xen-drmfront/xen-sndfront, but I didn't touch gntdev for that. Do you want me to add yet another patch in the series to check for that?
Quoted 8 lines
Quoted 6 lines
gntdev.cis already not capable of handlingPAGE_SIZE!=XEN_PAGE_SIZE, so you are not going to break anything that is not already broken :-) If your newgntdev.ccode relies onPAGE_SIZE==XEN_PAGE_SIZE, it might be good to add an in-code comment about it, just to make it easier to fix the whole ofgntdev.cin the future.Yes, I just mean I can add something like [1] as a separate patch to the series, so we are on the safe side here
See my comment on Stefano's e-mail. I believe gntdev is able to handle PAGE_SIZE != XEN_PAGE_SIZE. So I would rather keep the behavior we have today for such case.
Cheers,
Signature · 1 line
Julien Grall
Re: [Xen-devel] [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
Quoted 95 lines · Julien Grall
Hi,
Quoted 92 lines · Oleksandr Andrushchenko
Quoted 91 lines · Stefano Stabellini
Quoted 79 lines · Oleksandr Andrushchenko
Quoted 50 lines · Boris Ostrovsky
Quoted 41 lines · Stefano Stabellini
Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
Quoted 19 lines
Quoted 19 lines
Quoted 6 lines
Quoted 6 lines
@@ -325,6 +401,14 @@ static int map_grant_pages(struct
grant_map
*map)
map->unmap_ops[i].handle =
map->map_ops[i].handle;
if (use_ptemod)Quoted 8 lines
Quoted 7 lines
map->kunmap_ops[i].handle =
map->kmap_ops[i].handle;
+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC
+ else if (map->dma_vaddr) {
+ unsigned long mfn;
+
+ mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM:
[1]
and [2]
Thus,Quoted 7 lines
Quoted 6 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function
‘pfn_to_mfn’ [-Werror=implicit-function-declaration] mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endifQuoted 8 lines
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap
__pfn_to_mfnwith static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}Quoted 8 lines
A Xen on ARM guest doesn't actually know the mfns behind its own pseudo-physical pages. This is why we stopped using
pfn_to_mfnand started usingpfn_to_bfninstead, which will generally return "pfn", unless the page is a foreign grant. Seeinclude/xen/arm/page.h.pfn_to_bfnwas also introduced on x86. For example, see the usage ofpfn_to_bfnindrivers/xen/swiotlb-xen.c. Otherwise, if you don't care about other mapped grants, you can just usepfn_to_gfn, that always returns pfn.Quoted 1 line
I think then this code needs to use
pfn_to_bfn().Ok
Quoted 26 lines
Quoted 26 lines
Also, for your information, we support different page granularities in Linux as a Xen guest, see the comment at
include/xen/arm/page.h:/*
* The pseudo-physical frame (pfn) used in all the helpers is always based
* on Xen page granularity (i.e 4KB).
*
* A Linux page may be split across multiple non-contiguous Xen page so we
* have to keep track with frame based on 4KB page granularity. *
* PV drivers should never make a direct usage of those helpers (particularly
*pfn_to_gfnandgfn_to_pfn).
*/A Linux page could be 64K, but a Xen page is always 4K. A granted page is also 4K. We have helpers to take into account the offsets to map multiple Xen grants in a single Linux page, see for example drivers/xen/grant-table.c:gnttab_foreach_grant. Most PV drivers have been converted to be able to work with 64K pages correctly, but if I remember correctly
gntdev.cis the only remaining driver that doesn't support 64K pages yet, so you don't have to deal with it if you don't want to.Quoted 5 lines
Quoted 2 lines
I believe somewhere in this series there is a test for
PAGE_SIZEvs.XEN_PAGE_SIZE. Right, Oleksandr?Not in gntdev. You might have seen this in xen-drmfront/xen-sndfront, but I didn't touch gntdev for that. Do you want me to add yet another patch in the series to check for that?
gntdev.cis already not capable of handlingPAGE_SIZE!=XEN_PAGE_SIZE, so you are not going to break anything that is not already broken :-) If your newgntdev.ccode relies onPAGE_SIZE==XEN_PAGE_SIZE, it might be good to add an in-code comment about it, just to make it easier to fix the whole ofgntdev.cin the future.
Quoted 5 lines
Quoted 2 lines
Yes, I just mean I can add something like [1] as a separate patch to the series, so we are on the safe side here
See my comment on Stefano's e-mail. I believe gntdev is able to handle
PAGE_SIZE!=XEN_PAGE_SIZE. So I would rather keep the behavior we have today for such case.
Sure, with a note that we waste most of a 64KiB page ;)
Quoted 2 lines
Cheers,
Re: [Xen-devel] [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
Hi,
Quoted 96 lines · Oleksandr Andrushchenko
Quoted 95 lines · Julien Grall
Hi,
Quoted 92 lines · Oleksandr Andrushchenko
Quoted 91 lines · Stefano Stabellini
Quoted 79 lines · Oleksandr Andrushchenko
Quoted 50 lines · Boris Ostrovsky
Quoted 41 lines · Stefano Stabellini
Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
Quoted 19 lines
Quoted 19 lines
Quoted 14 lines
@@ -325,6 +401,14 @@ static int map_grant_pages(struct
grant_map
*map)
map->unmap_ops[i].handle =
map->map_ops[i].handle;
if (use_ptemod)
map->kunmap_ops[i].handle =
map->kmap_ops[i].handle;
+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC
+ else if (map->dma_vaddr) {
+ unsigned long mfn;
+
+ mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
Not pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM:
[1]
and [2]
Thus,Quoted 7 lines
Quoted 6 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function
‘pfn_to_mfn’ [-Werror=implicit-function-declaration] mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endifQuoted 8 lines
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap
__pfn_to_mfnwith static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}Quoted 8 lines
A Xen on ARM guest doesn't actually know the mfns behind its own pseudo-physical pages. This is why we stopped using
pfn_to_mfnand started usingpfn_to_bfninstead, which will generally return "pfn", unless the page is a foreign grant. Seeinclude/xen/arm/page.h.pfn_to_bfnwas also introduced on x86. For example, see the usage ofpfn_to_bfnindrivers/xen/swiotlb-xen.c. Otherwise, if you don't care about other mapped grants, you can just usepfn_to_gfn, that always returns pfn.Quoted 1 line
I think then this code needs to use
pfn_to_bfn().Ok
Quoted 26 lines
Quoted 26 lines
Also, for your information, we support different page granularities in Linux as a Xen guest, see the comment at
include/xen/arm/page.h:/*
* The pseudo-physical frame (pfn) used in all the helpers is always based
* on Xen page granularity (i.e 4KB).
*
* A Linux page may be split across multiple non-contiguous Xen page so we
* have to keep track with frame based on 4KB page granularity. *
* PV drivers should never make a direct usage of those helpers (particularly
*pfn_to_gfnandgfn_to_pfn).
*/A Linux page could be 64K, but a Xen page is always 4K. A granted page is also 4K. We have helpers to take into account the offsets to map multiple Xen grants in a single Linux page, see for example drivers/xen/grant-table.c:gnttab_foreach_grant. Most PV drivers have been converted to be able to work with 64K pages correctly, but if I remember correctly
gntdev.cis the only remaining driver that doesn't support 64K pages yet, so you don't have to deal with it if you don't want to.Quoted 5 lines
Quoted 2 lines
I believe somewhere in this series there is a test for
PAGE_SIZEvs.XEN_PAGE_SIZE. Right, Oleksandr?Not in gntdev. You might have seen this in xen-drmfront/xen-sndfront, but I didn't touch gntdev for that. Do you want me to add yet another patch in the series to check for that?
gntdev.cis already not capable of handlingPAGE_SIZE!=XEN_PAGE_SIZE, so you are not going to break anything that is not already broken :-) If your newgntdev.ccode relies onPAGE_SIZE==XEN_PAGE_SIZE, it might be good to add an in-code comment about it, just to make it easier to fix the whole ofgntdev.cin the future.
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines
Yes, I just mean I can add something like [1] as a separate patch to the series, so we are on the safe side here
See my comment on Stefano's e-mail. I believe gntdev is able to handle
PAGE_SIZE!=XEN_PAGE_SIZE. So I would rather keep the behavior we have today for such case.Sure, with a note that we waste most of a 64KiB page ;)
That's the second definition of "64KB page" ;). In the case of grants, it is actually quite hard to merge them in a single page. So quite a few places still allocate 64KB but only map the first 4KB.
You would need to rework most the grant framework (not only gntdev) to avoid that waste. Patches are welcomed.
Cheers,
Signature · 1 line
Julien Grall
Re: [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
In reply to Oleksandr AndrushchenkoHi,
Quoted 96 lines · Oleksandr Andrushchenko
Quoted 95 lines · Julien Grall
Hi,
Quoted 92 lines · Oleksandr Andrushchenko
Quoted 91 lines · Stefano Stabellini
Quoted 79 lines · Oleksandr Andrushchenko
Quoted 50 lines · Boris Ostrovsky
Quoted 41 lines · Stefano Stabellini
Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
Quoted 19 lines
Quoted 19 lines
Quoted 14 lines
@@ -325,6 +401,14 @@ static int map_grant_pages(struct
grant_map
*map)
map->unmap_ops[i].handle =
map->map_ops[i].handle;
if (use_ptemod)
map->kunmap_ops[i].handle =
map->kmap_ops[i].handle;
+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC
+ else if (map->dma_vaddr) {
+ unsigned long mfn;
+
+ mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
Not pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM:
[1]
and [2]
Thus,Quoted 7 lines
Quoted 6 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function
‘pfn_to_mfn’ [-Werror=implicit-function-declaration] mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endifQuoted 8 lines
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap
__pfn_to_mfnwith static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}Quoted 8 lines
A Xen on ARM guest doesn't actually know the mfns behind its own pseudo-physical pages. This is why we stopped using
pfn_to_mfnand started usingpfn_to_bfninstead, which will generally return "pfn", unless the page is a foreign grant. Seeinclude/xen/arm/page.h.pfn_to_bfnwas also introduced on x86. For example, see the usage ofpfn_to_bfnindrivers/xen/swiotlb-xen.c. Otherwise, if you don't care about other mapped grants, you can just usepfn_to_gfn, that always returns pfn.Quoted 1 line
I think then this code needs to use
pfn_to_bfn().Ok
Quoted 26 lines
Quoted 26 lines
Also, for your information, we support different page granularities in Linux as a Xen guest, see the comment at
include/xen/arm/page.h:/*
* The pseudo-physical frame (pfn) used in all the helpers is always based
* on Xen page granularity (i.e 4KB).
*
* A Linux page may be split across multiple non-contiguous Xen page so we
* have to keep track with frame based on 4KB page granularity. *
* PV drivers should never make a direct usage of those helpers (particularly
*pfn_to_gfnandgfn_to_pfn).
*/A Linux page could be 64K, but a Xen page is always 4K. A granted page is also 4K. We have helpers to take into account the offsets to map multiple Xen grants in a single Linux page, see for example drivers/xen/grant-table.c:gnttab_foreach_grant. Most PV drivers have been converted to be able to work with 64K pages correctly, but if I remember correctly
gntdev.cis the only remaining driver that doesn't support 64K pages yet, so you don't have to deal with it if you don't want to.Quoted 5 lines
Quoted 2 lines
I believe somewhere in this series there is a test for
PAGE_SIZEvs.XEN_PAGE_SIZE. Right, Oleksandr?Not in gntdev. You might have seen this in xen-drmfront/xen-sndfront, but I didn't touch gntdev for that. Do you want me to add yet another patch in the series to check for that?
gntdev.cis already not capable of handlingPAGE_SIZE!=XEN_PAGE_SIZE, so you are not going to break anything that is not already broken :-) If your newgntdev.ccode relies onPAGE_SIZE==XEN_PAGE_SIZE, it might be good to add an in-code comment about it, just to make it easier to fix the whole ofgntdev.cin the future.
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines
Yes, I just mean I can add something like [1] as a separate patch to the series, so we are on the safe side here
See my comment on Stefano's e-mail. I believe gntdev is able to handle
PAGE_SIZE!=XEN_PAGE_SIZE. So I would rather keep the behavior we have today for such case.Sure, with a note that we waste most of a 64KiB page ;)
That's the second definition of "64KB page" ;). In the case of grants, it is actually quite hard to merge them in a single page. So quite a few places still allocate 64KB but only map the first 4KB.
You would need to rework most the grant framework (not only gntdev) to avoid that waste. Patches are welcomed.
Cheers,
Signature · 6 lines
Julien Grall _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
In reply to Julien GrallQuoted 95 lines · Julien Grall
Hi,
Quoted 92 lines · Oleksandr Andrushchenko
Quoted 91 lines · Stefano Stabellini
Quoted 79 lines · Oleksandr Andrushchenko
Quoted 50 lines · Boris Ostrovsky
Quoted 41 lines · Stefano Stabellini
Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
Quoted 19 lines
Quoted 19 lines
Quoted 6 lines
Quoted 6 lines
@@ -325,6 +401,14 @@ static int map_grant_pages(struct
grant_map
*map)
map->unmap_ops[i].handle =
map->map_ops[i].handle;
if (use_ptemod)Quoted 8 lines
Quoted 7 lines
map->kunmap_ops[i].handle =
map->kmap_ops[i].handle;
+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC
+ else if (map->dma_vaddr) {
+ unsigned long mfn;
+
+ mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM:
[1]
and [2]
Thus,Quoted 7 lines
Quoted 6 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function
‘pfn_to_mfn’ [-Werror=implicit-function-declaration] mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endifQuoted 8 lines
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap
__pfn_to_mfnwith static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}Quoted 8 lines
A Xen on ARM guest doesn't actually know the mfns behind its own pseudo-physical pages. This is why we stopped using
pfn_to_mfnand started usingpfn_to_bfninstead, which will generally return "pfn", unless the page is a foreign grant. Seeinclude/xen/arm/page.h.pfn_to_bfnwas also introduced on x86. For example, see the usage ofpfn_to_bfnindrivers/xen/swiotlb-xen.c. Otherwise, if you don't care about other mapped grants, you can just usepfn_to_gfn, that always returns pfn.Quoted 1 line
I think then this code needs to use
pfn_to_bfn().Ok
Quoted 26 lines
Quoted 26 lines
Also, for your information, we support different page granularities in Linux as a Xen guest, see the comment at
include/xen/arm/page.h:/*
* The pseudo-physical frame (pfn) used in all the helpers is always based
* on Xen page granularity (i.e 4KB).
*
* A Linux page may be split across multiple non-contiguous Xen page so we
* have to keep track with frame based on 4KB page granularity. *
* PV drivers should never make a direct usage of those helpers (particularly
*pfn_to_gfnandgfn_to_pfn).
*/A Linux page could be 64K, but a Xen page is always 4K. A granted page is also 4K. We have helpers to take into account the offsets to map multiple Xen grants in a single Linux page, see for example drivers/xen/grant-table.c:gnttab_foreach_grant. Most PV drivers have been converted to be able to work with 64K pages correctly, but if I remember correctly
gntdev.cis the only remaining driver that doesn't support 64K pages yet, so you don't have to deal with it if you don't want to.Quoted 5 lines
Quoted 2 lines
I believe somewhere in this series there is a test for
PAGE_SIZEvs.XEN_PAGE_SIZE. Right, Oleksandr?Not in gntdev. You might have seen this in xen-drmfront/xen-sndfront, but I didn't touch gntdev for that. Do you want me to add yet another patch in the series to check for that?
gntdev.cis already not capable of handlingPAGE_SIZE!=XEN_PAGE_SIZE, so you are not going to break anything that is not already broken :-) If your newgntdev.ccode relies onPAGE_SIZE==XEN_PAGE_SIZE, it might be good to add an in-code comment about it, just to make it easier to fix the whole ofgntdev.cin the future.
Quoted 5 lines
Quoted 2 lines
Yes, I just mean I can add something like [1] as a separate patch to the series, so we are on the safe side here
See my comment on Stefano's e-mail. I believe gntdev is able to handle
PAGE_SIZE!=XEN_PAGE_SIZE. So I would rather keep the behavior we have today for such case.
Sure, with a note that we waste most of a 64KiB page ;)
Quoted 2 lines
Cheers,
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
In reply to Oleksandr AndrushchenkoHi,
Quoted 86 lines · Oleksandr Andrushchenko
Quoted 85 lines · Stefano Stabellini
Quoted 84 lines · Oleksandr Andrushchenko
Quoted 50 lines · Boris Ostrovsky
Quoted 41 lines · Stefano Stabellini
Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
Quoted 19 lines
Quoted 19 lines
Quoted 6 lines
Quoted 6 lines
@@ -325,6 +401,14 @@ static int map_grant_pages(struct
grant_map
*map)
map->unmap_ops[i].handle = map->map_ops[i].handle;
if (use_ptemod)Quoted 8 lines
Review
Quoted 7 lines
map->kunmap_ops[i].handle =
map->kmap_ops[i].handle;(quoted diff) +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM:
[1]
and [2]
Thus,Quoted 7 lines
Quoted 6 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function
‘pfn_to_mfn’ [-Werror=implicit-function-declaration] mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endifQuoted 8 lines
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap
__pfn_to_mfnwith static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}Quoted 8 lines
A Xen on ARM guest doesn't actually know the mfns behind its own pseudo-physical pages. This is why we stopped using
pfn_to_mfnand started usingpfn_to_bfninstead, which will generally return "pfn", unless the page is a foreign grant. Seeinclude/xen/arm/page.h.pfn_to_bfnwas also introduced on x86. For example, see the usage ofpfn_to_bfnindrivers/xen/swiotlb-xen.c. Otherwise, if you don't care about other mapped grants, you can just usepfn_to_gfn, that always returns pfn.Quoted 1 line
I think then this code needs to use
pfn_to_bfn().Ok
Quoted 26 lines
Quoted 18 lines
Also, for your information, we support different page granularities in Linux as a Xen guest, see the comment at
include/xen/arm/page.h:/*
* The pseudo-physical frame (pfn) used in all the helpers is always based
* on Xen page granularity (i.e 4KB).
*
* A Linux page may be split across multiple non-contiguous Xen page so we
* have to keep track with frame based on 4KB page granularity. *
* PV drivers should never make a direct usage of those helpers (particularly
*pfn_to_gfnandgfn_to_pfn).
*/Quoted 8 lines
A Linux page could be 64K, but a Xen page is always 4K. A granted page is also 4K. We have helpers to take into account the offsets to map multiple Xen grants in a single Linux page, see for example drivers/xen/grant-table.c:gnttab_foreach_grant. Most PV drivers have been converted to be able to work with 64K pages correctly, but if I remember correctly
gntdev.cis the only remaining driver that doesn't support 64K pages yet, so you don't have to deal with it if you don't want to.Quoted 2 lines
I believe somewhere in this series there is a test for
PAGE_SIZEvs.XEN_PAGE_SIZE. Right, Oleksandr?Not in gntdev. You might have seen this in xen-drmfront/xen-sndfront, but I didn't touch gntdev for that. Do you want me to add yet another patch in the series to check for that?
Quoted 8 lines
Quoted 6 lines
gntdev.cis already not capable of handlingPAGE_SIZE!=XEN_PAGE_SIZE, so you are not going to break anything that is not already broken :-) If your newgntdev.ccode relies onPAGE_SIZE==XEN_PAGE_SIZE, it might be good to add an in-code comment about it, just to make it easier to fix the whole ofgntdev.cin the future.Yes, I just mean I can add something like [1] as a separate patch to the series, so we are on the safe side here
See my comment on Stefano's e-mail. I believe gntdev is able to handle PAGE_SIZE != XEN_PAGE_SIZE. So I would rather keep the behavior we have today for such case.
Cheers,
Signature · 6 lines
Julien Grall _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
In reply to Stefano StabelliniQuoted 82 lines · Stefano Stabellini
Quoted 81 lines · Oleksandr Andrushchenko
Quoted 50 lines · Boris Ostrovsky
Quoted 41 lines · Stefano Stabellini
Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
Quoted 19 lines
Quoted 19 lines
Quoted 6 lines
Quoted 6 lines
@@ -325,6 +401,14 @@ static int map_grant_pages(struct
grant_map
*map)
map->unmap_ops[i].handle =
map->map_ops[i].handle;
if (use_ptemod)Quoted 8 lines
Review
Quoted 7 lines
map->kunmap_ops[i].handle =map->kmap_ops[i].handle;
(quoted diff) +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM:
[1]
and [2]
Thus,Quoted 7 lines
Quoted 6 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function
‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endifQuoted 8 lines
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap
__pfn_to_mfnwith static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}Quoted 8 lines
A Xen on ARM guest doesn't actually know the mfns behind its own pseudo-physical pages. This is why we stopped using
pfn_to_mfnand started usingpfn_to_bfninstead, which will generally return "pfn", unless the page is a foreign grant. Seeinclude/xen/arm/page.h.pfn_to_bfnwas also introduced on x86. For example, see the usage ofpfn_to_bfnindrivers/xen/swiotlb-xen.c. Otherwise, if you don't care about other mapped grants, you can just usepfn_to_gfn, that always returns pfn.Quoted 1 line
I think then this code needs to use
pfn_to_bfn().Ok
Quoted 28 lines
Quoted 18 lines
Also, for your information, we support different page granularities in Linux as a Xen guest, see the comment at
include/xen/arm/page.h:/*
* The pseudo-physical frame (pfn) used in all the helpers is always
based
* on Xen page granularity (i.e 4KB).
*
* A Linux page may be split across multiple non-contiguous Xen page so
we
* have to keep track with frame based on 4KB page granularity. *
* PV drivers should never make a direct usage of those helpers
(particularly
*pfn_to_gfnandgfn_to_pfn).
*/Quoted 8 lines
A Linux page could be 64K, but a Xen page is always 4K. A granted page is also 4K. We have helpers to take into account the offsets to map multiple Xen grants in a single Linux page, see for example drivers/xen/grant-table.c:gnttab_foreach_grant. Most PV drivers have been converted to be able to work with 64K pages correctly, but if I remember correctly
gntdev.cis the only remaining driver that doesn't support 64K pages yet, so you don't have to deal with it if you don't want to.I believe somewhere in this series there is a test for
PAGE_SIZEvs.XEN_PAGE_SIZE. Right, Oleksandr?
Quoted 9 lines
Quoted 3 lines
Not in gntdev. You might have seen this in xen-drmfront/xen-sndfront, but I didn't touch gntdev for that. Do you want me to add yet another patch in the series to check for that?
gntdev.cis already not capable of handlingPAGE_SIZE!=XEN_PAGE_SIZE, so you are not going to break anything that is not already broken :-) If your newgntdev.ccode relies onPAGE_SIZE==XEN_PAGE_SIZE, it might be good to add an in-code comment about it, just to make it easier to fix the whole ofgntdev.cin the future.
Yes, I just mean I can add something like [1] as a separate patch to the series, so we are on the safe side here
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Thanks for the explanation.
[1] https://cgit.freedesktop.org/drm/drm-misc/tree/drivers/gpu/drm/xen/xen_drm_front.c#n813
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
In reply to Stefano StabelliniHi Stefano,
Quoted 89 lines · Stefano Stabellini
Quoted 82 lines · Oleksandr Andrushchenko
Quoted 51 lines · Boris Ostrovsky
Quoted 41 lines · Stefano Stabellini
Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
Quoted 19 lines
Quoted 19 lines
Quoted 6 lines
Quoted 6 lines
@@ -325,6 +401,14 @@ static int map_grant_pages(struct
grant_map
*map)
map->unmap_ops[i].handle =
map->map_ops[i].handle;
if (use_ptemod)Quoted 8 lines
Review
Quoted 7 lines
map->kunmap_ops[i].handle =map->kmap_ops[i].handle;
(quoted diff) +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM:
[1]
and [2]
Thus,Quoted 7 lines
Quoted 6 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function
‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endifQuoted 8 lines
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap
__pfn_to_mfnwith static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}Quoted 8 lines
A Xen on ARM guest doesn't actually know the mfns behind its own pseudo-physical pages. This is why we stopped using
pfn_to_mfnand started usingpfn_to_bfninstead, which will generally return "pfn", unless the page is a foreign grant. Seeinclude/xen/arm/page.h.pfn_to_bfnwas also introduced on x86. For example, see the usage ofpfn_to_bfnindrivers/xen/swiotlb-xen.c. Otherwise, if you don't care about other mapped grants, you can just usepfn_to_gfn, that always returns pfn.Quoted 1 line
I think then this code needs to use
pfn_to_bfn().Ok
Quoted 28 lines
Quoted 27 lines
Also, for your information, we support different page granularities in Linux as a Xen guest, see the comment at
include/xen/arm/page.h:/*
* The pseudo-physical frame (pfn) used in all the helpers is always
based
* on Xen page granularity (i.e 4KB).
*
* A Linux page may be split across multiple non-contiguous Xen page so
we
* have to keep track with frame based on 4KB page granularity. *
* PV drivers should never make a direct usage of those helpers
(particularly
*pfn_to_gfnandgfn_to_pfn).
*/A Linux page could be 64K, but a Xen page is always 4K. A granted page is also 4K. We have helpers to take into account the offsets to map multiple Xen grants in a single Linux page, see for example drivers/xen/grant-table.c:gnttab_foreach_grant. Most PV drivers have been converted to be able to work with 64K pages correctly, but if I remember correctly
gntdev.cis the only remaining driver that doesn't support 64K pages yet, so you don't have to deal with it if you don't want to.Quoted 5 lines
Quoted 2 lines
I believe somewhere in this series there is a test for
PAGE_SIZEvs.XEN_PAGE_SIZE. Right, Oleksandr?Not in gntdev. You might have seen this in xen-drmfront/xen-sndfront, but I didn't touch gntdev for that. Do you want me to add yet another patch in the series to check for that?
Quoted 5 lines
gntdev.cis already not capable of handlingPAGE_SIZE!=XEN_PAGE_SIZE, so you are not going to break anything that is not already broken :-) If your newgntdev.ccode relies onPAGE_SIZE==XEN_PAGE_SIZE, it might be good to add an in-code comment about it, just to make it easier to fix the whole ofgntdev.cin the future.
Well, I think gntdev is capable of handling PAGE_SIZE != XEN_PAGE_SIZE.
Let's imagine Linux is built with 64K pages. gntdev will map each grant at a 64K alignment. Although, I am not sure if patches for QEMU ever make it upstream (I think it is in Centos).
Cheers,
Signature · 1 line
Julien Grall
Re: [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
In reply to Stefano StabelliniHi Stefano,
Quoted 89 lines · Stefano Stabellini
Quoted 82 lines · Oleksandr Andrushchenko
Quoted 51 lines · Boris Ostrovsky
Quoted 41 lines · Stefano Stabellini
Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
Quoted 19 lines
Quoted 19 lines
Quoted 6 lines
Quoted 6 lines
@@ -325,6 +401,14 @@ static int map_grant_pages(struct
grant_map
*map)
map->unmap_ops[i].handle =
map->map_ops[i].handle;
if (use_ptemod)Quoted 8 lines
Review
Quoted 7 lines
map->kunmap_ops[i].handle =map->kmap_ops[i].handle;
(quoted diff) +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM:
[1]
and [2]
Thus,Quoted 7 lines
Quoted 6 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function
‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endifQuoted 8 lines
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap
__pfn_to_mfnwith static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}Quoted 8 lines
A Xen on ARM guest doesn't actually know the mfns behind its own pseudo-physical pages. This is why we stopped using
pfn_to_mfnand started usingpfn_to_bfninstead, which will generally return "pfn", unless the page is a foreign grant. Seeinclude/xen/arm/page.h.pfn_to_bfnwas also introduced on x86. For example, see the usage ofpfn_to_bfnindrivers/xen/swiotlb-xen.c. Otherwise, if you don't care about other mapped grants, you can just usepfn_to_gfn, that always returns pfn.Quoted 1 line
I think then this code needs to use
pfn_to_bfn().Ok
Quoted 28 lines
Quoted 27 lines
Also, for your information, we support different page granularities in Linux as a Xen guest, see the comment at
include/xen/arm/page.h:/*
* The pseudo-physical frame (pfn) used in all the helpers is always
based
* on Xen page granularity (i.e 4KB).
*
* A Linux page may be split across multiple non-contiguous Xen page so
we
* have to keep track with frame based on 4KB page granularity. *
* PV drivers should never make a direct usage of those helpers
(particularly
*pfn_to_gfnandgfn_to_pfn).
*/A Linux page could be 64K, but a Xen page is always 4K. A granted page is also 4K. We have helpers to take into account the offsets to map multiple Xen grants in a single Linux page, see for example drivers/xen/grant-table.c:gnttab_foreach_grant. Most PV drivers have been converted to be able to work with 64K pages correctly, but if I remember correctly
gntdev.cis the only remaining driver that doesn't support 64K pages yet, so you don't have to deal with it if you don't want to.Quoted 5 lines
Quoted 2 lines
I believe somewhere in this series there is a test for
PAGE_SIZEvs.XEN_PAGE_SIZE. Right, Oleksandr?Not in gntdev. You might have seen this in xen-drmfront/xen-sndfront, but I didn't touch gntdev for that. Do you want me to add yet another patch in the series to check for that?
Quoted 5 lines
gntdev.cis already not capable of handlingPAGE_SIZE!=XEN_PAGE_SIZE, so you are not going to break anything that is not already broken :-) If your newgntdev.ccode relies onPAGE_SIZE==XEN_PAGE_SIZE, it might be good to add an in-code comment about it, just to make it easier to fix the whole ofgntdev.cin the future.
Well, I think gntdev is capable of handling PAGE_SIZE != XEN_PAGE_SIZE.
Let's imagine Linux is built with 64K pages. gntdev will map each grant at a 64K alignment. Although, I am not sure if patches for QEMU ever make it upstream (I think it is in Centos).
Cheers,
Signature · 6 lines
Julien Grall _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
Stefano Stabellini
maintainerRe: [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
In reply to Oleksandr AndrushchenkoQuoted 82 lines · Oleksandr Andrushchenko
Quoted 51 lines · Boris Ostrovsky
Quoted 41 lines · Stefano Stabellini
Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
Quoted 19 lines
Quoted 19 lines
Quoted 6 lines
Quoted 6 lines
@@ -325,6 +401,14 @@ static int map_grant_pages(struct
grant_map
*map)
map->unmap_ops[i].handle =
map->map_ops[i].handle;
if (use_ptemod)Quoted 8 lines
Review
Quoted 7 lines
map->kunmap_ops[i].handle =
map->kmap_ops[i].handle;(quoted diff) +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM:
[1]
and [2]
Thus,Quoted 7 lines
Quoted 6 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function
‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endifQuoted 8 lines
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap
__pfn_to_mfnwith static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}Quoted 8 lines
A Xen on ARM guest doesn't actually know the mfns behind its own pseudo-physical pages. This is why we stopped using
pfn_to_mfnand started usingpfn_to_bfninstead, which will generally return "pfn", unless the page is a foreign grant. Seeinclude/xen/arm/page.h.pfn_to_bfnwas also introduced on x86. For example, see the usage ofpfn_to_bfnindrivers/xen/swiotlb-xen.c. Otherwise, if you don't care about other mapped grants, you can just usepfn_to_gfn, that always returns pfn.Quoted 1 line
I think then this code needs to use
pfn_to_bfn().Ok
Quoted 28 lines
Quoted 27 lines
Also, for your information, we support different page granularities in Linux as a Xen guest, see the comment at
include/xen/arm/page.h:/*
* The pseudo-physical frame (pfn) used in all the helpers is always
based
* on Xen page granularity (i.e 4KB).
*
* A Linux page may be split across multiple non-contiguous Xen page so
we
* have to keep track with frame based on 4KB page granularity. *
* PV drivers should never make a direct usage of those helpers
(particularly
*pfn_to_gfnandgfn_to_pfn).
*/A Linux page could be 64K, but a Xen page is always 4K. A granted page is also 4K. We have helpers to take into account the offsets to map multiple Xen grants in a single Linux page, see for example drivers/xen/grant-table.c:gnttab_foreach_grant. Most PV drivers have been converted to be able to work with 64K pages correctly, but if I remember correctly
gntdev.cis the only remaining driver that doesn't support 64K pages yet, so you don't have to deal with it if you don't want to.
Quoted 5 lines
Quoted 2 lines
I believe somewhere in this series there is a test for
PAGE_SIZEvs.XEN_PAGE_SIZE. Right, Oleksandr?Not in gntdev. You might have seen this in xen-drmfront/xen-sndfront, but I didn't touch gntdev for that. Do you want me to add yet another patch in the series to check for that?
gntdev.c is already not capable of handling PAGE_SIZE != XEN_PAGE_SIZE, so you are not going to break anything that is not already broken :-) If your new gntdev.c code relies on PAGE_SIZE == XEN_PAGE_SIZE, it might be good to add an in-code comment about it, just to make it easier to fix the whole of gntdev.c in the future.
Quoted 1 line
Quoted 1 line
Thanks for the explanation.
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
In reply to Boris OstrovskyQuoted 48 lines · Boris Ostrovsky
Quoted 38 lines · Stefano Stabellini
Quoted 30 lines
Quoted 30 lines
Quoted 30 lines
Quoted 17 lines
Quoted 17 lines
Quoted 5 lines
Quoted 5 lines
@@ -325,6 +401,14 @@ static int map_grant_pages(struct
grant_map
*map)
map->unmap_ops[i].handle = map->map_ops[i].handle; if (use_ptemod)Quoted 8 lines
Review
Quoted 7 lines
map->kunmap_ops[i].handle =
map->kmap_ops[i].handle;(quoted diff) +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM: [1] and [2]
Thus,Quoted 6 lines
Quoted 5 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function ‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endifQuoted 8 lines
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap
__pfn_to_mfnwith static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}Quoted 8 lines
A Xen on ARM guest doesn't actually know the mfns behind its own pseudo-physical pages. This is why we stopped using
pfn_to_mfnand started usingpfn_to_bfninstead, which will generally return "pfn", unless the page is a foreign grant. Seeinclude/xen/arm/page.h.pfn_to_bfnwas also introduced on x86. For example, see the usage ofpfn_to_bfnindrivers/xen/swiotlb-xen.c. Otherwise, if you don't care about other mapped grants, you can just usepfn_to_gfn, that always returns pfn.
Quoted 1 line
I think then this code needs to use
pfn_to_bfn().
Ok
Quoted 25 lines
Quoted 16 lines
Also, for your information, we support different page granularities in Linux as a Xen guest, see the comment at
include/xen/arm/page.h:/*
* The pseudo-physical frame (pfn) used in all the helpers is always based
* on Xen page granularity (i.e 4KB).
*
* A Linux page may be split across multiple non-contiguous Xen page so we
* have to keep track with frame based on 4KB page granularity. *
* PV drivers should never make a direct usage of those helpers (particularly
*pfn_to_gfnandgfn_to_pfn).
*/Quoted 8 lines
A Linux page could be 64K, but a Xen page is always 4K. A granted page is also 4K. We have helpers to take into account the offsets to map multiple Xen grants in a single Linux page, see for example drivers/xen/grant-table.c:gnttab_foreach_grant. Most PV drivers have been converted to be able to work with 64K pages correctly, but if I remember correctly
gntdev.cis the only remaining driver that doesn't support 64K pages yet, so you don't have to deal with it if you don't want to.
Quoted 2 lines
I believe somewhere in this series there is a test for
PAGE_SIZEvs.XEN_PAGE_SIZE. Right, Oleksandr?
Not in gntdev. You might have seen this in xen-drmfront/xen-sndfront, but I didn't touch gntdev for that. Do you want me to add yet another patch in the series to check for that?
Quoted 3 lines
Thanks for the explanation.
-boris
Thank you,
Oleksandr
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Stefano Stabellini
maintainerRe: [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
In reply to Oleksandr AndrushchenkoQuoted 165 lines · Oleksandr Andrushchenko
Quoted 71 lines · Boris Ostrovsky
(Stefano, question for you at the end)
Quoted 60 lines · Oleksandr Andrushchenko
Quoted 8 lines · Boris Ostrovsky
Quoted 7 lines · Oleksandr Andrushchenko
Review static void gntdev_free_map(struct grant_map · line 149
Quoted 6 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
(quoted diff) +0
-0@@ -121,8 +146,27 @@ static void gntdev_free_map(struct grant_map *map) if (map == NULL) return; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC*Option 1: kfree(map->frames);*
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
(quoted diff) +4
-0+ if (map->dma_vaddr) { + struct gnttab_dma_alloc_args args; + + args.dev = map->dma_dev;Quoted 8 lines
Quoted 8 lines
Review static void gntdev_free_map(struct grant_map · line 161
Quoted 8 lines
(quoted diff) +8
-0+ args.coherent = map->dma_flags & GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages = map->count; + args.pages = map->pages; + args.frames = map->frames; + args.vaddr = map->dma_vaddr; + args.dev_bus_addr = map->dma_bus_addr; + + gnttab_dma_free_pages(&args);*Option 2: kfree(map->frames);*
Quoted 16 lines
Quoted 9 lines
Quoted 9 lines
(quoted diff) +6
-0+ } else +#endif if (map->pages) gnttab_free_pages(map->count, map->pages); + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + kfree(map->frames); +#endifQuoted 7 lines
Quoted 4 lines
Can this be done under if (
map->dma_vaddr) ?
In other words, is it
possible fordma_vaddrto be NULL and still have unallocated frames pointer?It is possible to have vaddr == NULL and frames != NULL as we allocate frames outside of
gnttab_dma_alloc_pageswhich may fail. Calling kfree on NULL pointer is safe,Quoted 2 lines
I am not questioning safety of the code, I would like avoid another ifdef.
Ah, I now understand, so you are asking if we can have that
kfree(map->frames); in the place *Option 2* I marked above. Unfortunately no:map->framesis allocated before we try to allocate DMA memory, e.g. beforedma_vaddris set:
[...]
add->frames=kcalloc(count, sizeof(add->frames[0]), GFP_KERNEL);
if (!add->frames)
goto err;[...]
if (gnttab_dma_alloc_pages(&args))
goto err;
add->dma_vaddr= args.vaddr;
[...]
err:
gntdev_free_map(add);Quoted 7 lines
So, it is possible to enter
gntdev_free_mapwith
frames != NULL anddma_vaddr== NULL. Option 1 above cannot be used asmap->framesis needed forgnttab_dma_free_pages(&args); and Option 2 cannot be used as frames != NULL anddma_vaddr== NULL. Thus, I think that unfortunately we need that #ifdef. Option 3 below can also be considered, but that seems to be not good as we free resources in different places which looks inconsistent.Quoted 3 lines
I was only thinking of option 2. But if it is possible to have frames != NULL and
dma_vaddr== NULL then perhaps we indeed will have to live with the extra ifdef.ok
Quoted 89 lines
Quoted 89 lines
Sorry if I'm still missing your point.
Quoted 40 lines
Quoted 40 lines
so
I see no reason to change this code.Quoted 38 lines
Quoted 38 lines
kfree(map->pages);
kfree(map->grants);
kfree(map->map_ops);(quoted diff) +18
-0@@ -132,7 +176,8 @@ static void gntdev_free_map(struct grant_map *map) kfree(map); } -static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) +static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count, + int dma_flags) { struct grant_map *add; int i;@@ -155,6 +200,37 @@ static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) NULL == add->pages) goto err; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + add->dma_flags = dma_flags; + + /* + * Check if this mapping is requested to be backed + * by a DMA buffer. + */ + if (dma_flags & (GNTDEV_DMA_FLAG_WC | GNTDEV_DMA_FLAG_COHERENT)) { + struct gnttab_dma_alloc_args args; + + add->frames = kcalloc(count, sizeof(add->frames[0]), + GFP_KERNEL); + if (!add->frames) + goto err; + + /* Remember the device, so we can free DMA memory. */ + add->dma_dev = priv->dma_dev;Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Review static struct grant_map · line 228
Quoted 8 lines
(quoted diff) +8
-0+ + args.dev = priv->dma_dev; + args.coherent = dma_flags & GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages = count; + args.pages = add->pages; + args.frames = add->frames; + + if (gnttab_dma_alloc_pages(&args))*Option 3: kfree(map->frames);*
Quoted 25 lines
Quoted 25 lines
Quoted 13 lines
Quoted 13 lines
(quoted diff) +6
-0+ goto err; + + add->dma_vaddr = args.vaddr; + add->dma_bus_addr = args.dev_bus_addr; + } else +#endif if (gnttab_alloc_pages(count, add->pages)) goto err; @@ -325,6 +401,14 @@ static int map_grant_pages(struct
grant_map
*map)
map->unmap_ops[i].handle = map->map_ops[i].handle; if (use_ptemod)Quoted 8 lines
Review
Quoted 7 lines
map->kunmap_ops[i].handle =
map->kmap_ops[i].handle;(quoted diff) +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM: [1] and [2]
Thus,Quoted 6 lines
Quoted 5 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function ‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endif
Quoted 8 lines
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap
__pfn_to_mfnwith static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}
A Xen on ARM guest doesn't actually know the mfns behind its own pseudo-physical pages. This is why we stopped using pfn_to_mfn and started using pfn_to_bfn instead, which will generally return "pfn", unless the page is a foreign grant. See include/xen/arm/page.h. pfn_to_bfn was also introduced on x86. For example, see the usage of pfn_to_bfn in drivers/xen/swiotlb-xen.c. Otherwise, if you don't care about other mapped grants, you can just use pfn_to_gfn, that always returns pfn.
Also, for your information, we support different page granularities in Linux as a Xen guest, see the comment at include/xen/arm/page.h:
/*
* The pseudo-physical frame (pfn) used in all the helpers is always based
* on Xen page granularity (i.e 4KB).
*
* A Linux page may be split across multiple non-contiguous Xen page so we
* have to keep track with frame based on 4KB page granularity. *
* PV drivers should never make a direct usage of those helpers (particularly
* pfn_to_gfn and gfn_to_pfn).
*/
A Linux page could be 64K, but a Xen page is always 4K. A granted page is also 4K. We have helpers to take into account the offsets to map multiple Xen grants in a single Linux page, see for example drivers/xen/grant-table.c:gnttab_foreach_grant. Most PV drivers have been converted to be able to work with 64K pages correctly, but if I remember correctly gntdev.c is the only remaining driver that doesn't support 64K pages yet, so you don't have to deal with it if you don't want to.
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
In reply to Boris OstrovskyQuoted 71 lines · Boris Ostrovsky
(Stefano, question for you at the end)
Quoted 60 lines · Oleksandr Andrushchenko
Quoted 8 lines · Boris Ostrovsky
Quoted 7 lines · Oleksandr Andrushchenko
drivers/xen/gntdev.c static void gntdev_free_map(struct grant_map · line 149
Quoted 6 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev.c +0
-0@@ -121,8 +146,27 @@ static void gntdev_free_map(struct grant_map *map) if (map == NULL) return; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC*Option 1: kfree(map->frames);*
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
drivers/xen/gntdev.c +4
-0+ if (map->dma_vaddr) { + struct gnttab_dma_alloc_args args; + + args.dev = map->dma_dev;Quoted 8 lines
Quoted 8 lines
drivers/xen/gntdev.c static void gntdev_free_map(struct grant_map *map) · line 161
Quoted 8 lines
drivers/xen/gntdev.c +8
-0+ args.coherent = map->dma_flags & GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages = map->count; + args.pages = map->pages; + args.frames = map->frames; + args.vaddr = map->dma_vaddr; + args.dev_bus_addr = map->dma_bus_addr; + + gnttab_dma_free_pages(&args);*Option 2: kfree(map->frames);*
Quoted 16 lines
Quoted 9 lines
Quoted 9 lines
drivers/xen/gntdev.c +6
-0+ } else +#endif if (map->pages) gnttab_free_pages(map->count, map->pages); + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + kfree(map->frames); +#endif Quoted 7 lines
Quoted 4 lines
Can this be done under if (
map->dma_vaddr) ?
In other words, is it
possible fordma_vaddrto be NULL and still have unallocated frames pointer?It is possible to have vaddr == NULL and frames != NULL as we allocate frames outside of
gnttab_dma_alloc_pageswhich may fail. Calling kfree on NULL pointer is safe,Quoted 2 lines
I am not questioning safety of the code, I would like avoid another ifdef.
Ah, I now understand, so you are asking if we can have that
kfree(map->frames); in the place *Option 2* I marked above. Unfortunately no:map->framesis allocated before we try to allocate DMA memory, e.g. beforedma_vaddris set:
[...]
add->frames=kcalloc(count, sizeof(add->frames[0]), GFP_KERNEL);
if (!add->frames)
goto err;[...]
if (gnttab_dma_alloc_pages(&args))
goto err;
add->dma_vaddr= args.vaddr;
[...]
err:
gntdev_free_map(add);Quoted 7 lines
So, it is possible to enter
gntdev_free_mapwith
frames != NULL anddma_vaddr== NULL. Option 1 above cannot be used asmap->framesis needed forgnttab_dma_free_pages(&args); and Option 2 cannot be used as frames != NULL anddma_vaddr== NULL. Thus, I think that unfortunately we need that #ifdef. Option 3 below can also be considered, but that seems to be not good as we free resources in different places which looks inconsistent.
Quoted 3 lines
I was only thinking of option 2. But if it is possible to have frames != NULL and
dma_vaddr== NULL then perhaps we indeed will have to live with the extra ifdef.
ok
Quoted 86 lines
Quoted 77 lines
Sorry if I'm still missing your point.
Quoted 39 lines
Quoted 39 lines
so
I see no reason to change this code.Quoted 37 lines
Quoted 37 lines
kfree(map->pages);
kfree(map->grants);
kfree(map->map_ops);drivers/xen/gntdev.c +18
-0@@ -132,7 +176,8 @@ static void gntdev_free_map(struct grant_map *map) kfree(map); } -static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) +static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv,int count, + int dma_flags) { struct grant_map *add; int i;@@ -155,6 +200,37 @@ static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) NULL == add->pages) goto err; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + add->dma_flags = dma_flags; + + /* + * Check if this mapping is requested to be backed + * by a DMA buffer. + */ + if (dma_flags & (GNTDEV_DMA_FLAG_WC |GNTDEV_DMA_FLAG_COHERENT )) { + struct gnttab_dma_alloc_args args; + + add->frames = kcalloc(count, sizeof(add->frames[0]), + GFP_KERNEL); + if (!add->frames) + goto err; + + /* Remember the device, so we can free DMA memory. */ + add->dma_dev = priv->dma_dev;Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
drivers/xen/gntdev.c static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) · line 227
Quoted 8 lines
drivers/xen/gntdev.c +8
-0+ + args.dev = priv->dma_dev; + args.coherent = dma_flags & GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages = count; + args.pages = add->pages; + args.frames = add->frames; + + if (gnttab_dma_alloc_pages(&args))*Option 3: kfree(map->frames);*
Quoted 27 lines
Quoted 27 lines
Quoted 11 lines
Quoted 11 lines
drivers/xen/gntdev.c +6
-0+ goto err; + + add->dma_vaddr = args.vaddr; + add->dma_bus_addr = args.dev_bus_addr; + } else +#endif if (gnttab_alloc_pages(count, add->pages)) goto err; @@ -325,6 +401,14 @@ static int map_grant_pages(struct grant_map*map)
map->unmap_ops[i].handle = map->map_ops[i].handle;Quoted 8 lines
drivers/xen/gntdev.c static int map_grant_pages(struct grant_map *map) · line 408
Quoted 7 lines
if (
use_ptemod)
map->kunmap_ops[i].handle = map->kmap_ops[i].handle;drivers/xen/gntdev.c +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM: [1] and [2]
Thus,
drivers/xen/gntdev.c:408:10: error: implicit declaration of function ‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));Quoted 9 lines
Quoted 2 lines
Quoted 1 line
So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdefCONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endif
Quoted 2 lines
I'd rather fix it in ARM code. Stefano, why does ARM uses the underscored version?
Do you want me to add one more patch for ARM to wrap __pfn_to_mfn with static inline for ARM? e.g.
static inline ...pfn_to_mfn(...)
{
__pfn_to_mfn();
}
Quoted 3 lines
-boris
Thank you,
Oleksandr
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
In reply to Boris OstrovskyQuoted 7 lines · Boris Ostrovsky
Quoted 6 lines · Oleksandr Andrushchenko
drivers/xen/gntdev.c static void gntdev_free_map(struct grant_map *map) · line 148
Quoted 5 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev.c +0
-0@@ -121,8 +146,27 @@ static void gntdev_free_map(struct grant_map *map) if (map == NULL) return; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC
*Option 1: kfree(map->frames);*
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
drivers/xen/gntdev.c +4
-0+ if (map->dma_vaddr) { + struct gnttab_dma_alloc_args args; + + args.dev = map->dma_dev;
Quoted 8 lines
Quoted 8 lines
drivers/xen/gntdev.c static void gntdev_free_map(struct grant_map *map) · line 161
Quoted 8 lines
drivers/xen/gntdev.c +8
-0+ args.coherent = map->dma_flags & GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages = map->count; + args.pages = map->pages; + args.frames = map->frames; + args.vaddr = map->dma_vaddr; + args.dev_bus_addr = map->dma_bus_addr; + + gnttab_dma_free_pages(&args);
*Option 2: kfree(map->frames);*
Quoted 17 lines
Quoted 9 lines
Quoted 9 lines
drivers/xen/gntdev.c +6
-0+ } else +#endif if (map->pages) gnttab_free_pages(map->count, map->pages); + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + kfree(map->frames); +#endif Quoted 7 lines
Quoted 4 lines
Can this be done under if (
map->dma_vaddr) ?
In other words, is it
possible fordma_vaddrto be NULL and still have unallocated frames pointer?It is possible to have vaddr == NULL and frames != NULL as we allocate frames outside of
gnttab_dma_alloc_pageswhich may fail. Calling kfree on NULL pointer is safe,
Quoted 1 line
I am not questioning safety of the code, I would like avoid another ifdef.
Ah, I now understand, so you are asking if we can have that kfree(map->frames); in the place *Option 2* I marked above. Unfortunately no: map->frames is allocated before we try to allocate DMA memory, e.g. before dma_vaddr is set:
[...]
add->frames = kcalloc(count, sizeof(add->frames[0]), GFP_KERNEL);
if (!add->frames)
goto err;
[...]
if (gnttab_dma_alloc_pages(&args))
goto err;
add->dma_vaddr = args.vaddr;
[...]
err:
gntdev_free_map(add);
So, it is possible to enter gntdev_free_map with
frames != NULL and dma_vaddr == NULL. Option 1 above cannot be used as map->frames is needed for gnttab_dma_free_pages(&args); and Option 2 cannot be used as frames != NULL and dma_vaddr == NULL. Thus, I think that unfortunately we need that #ifdef. Option 3 below can also be considered, but that seems to be not good as we free resources in different places which looks inconsistent.
Sorry if I'm still missing your point.
Quoted 38 lines
Quoted 38 lines
so
I see no reason to change this code.Quoted 35 lines
Quoted 35 lines
kfree(map->pages);
kfree(map->grants);
kfree(map->map_ops);drivers/xen/gntdev.c +18
-0@@ -132,7 +176,8 @@ static void gntdev_free_map(struct grant_map *map) kfree(map); } -static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) +static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv,int count, + int dma_flags) { struct grant_map *add; int i;@@ -155,6 +200,37 @@ static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) NULL == add->pages) goto err; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + add->dma_flags = dma_flags; + + /* + * Check if this mapping is requested to be backed + * by a DMA buffer. + */ + if (dma_flags & (GNTDEV_DMA_FLAG_WC | GNTDEV_DMA_FLAG_COHERENT)) { + struct gnttab_dma_alloc_args args; + + add->frames = kcalloc(count, sizeof(add->frames[0]), + GFP_KERNEL); + if (!add->frames) + goto err; + + /* Remember the device, so we can free DMA memory. */ + add->dma_dev = priv->dma_dev;
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
drivers/xen/gntdev.c static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) · line 227
Quoted 8 lines
drivers/xen/gntdev.c +8
-0+ + args.dev = priv->dma_dev; + args.coherent = dma_flags & GNTDEV_DMA_FLAG_COHERENT; + args.nr_pages = count; + args.pages = add->pages; + args.frames = add->frames; + + if (gnttab_dma_alloc_pages(&args))
*Option 3: kfree(map->frames);*
Quoted 22 lines
Quoted 22 lines
Quoted 11 lines
Quoted 11 lines
drivers/xen/gntdev.c +6
-0+ goto err; + + add->dma_vaddr = args.vaddr; + add->dma_bus_addr = args.dev_bus_addr; + } else +#endif if (gnttab_alloc_pages(count, add->pages)) goto err; @@ -325,6 +401,14 @@ static int map_grant_pages(struct grant_map*map)
map->unmap_ops[i].handle = map->map_ops[i].handle;Quoted 8 lines
drivers/xen/gntdev.c static int map_grant_pages(struct grant_map *map) · line 408
Quoted 7 lines
if (
use_ptemod)
map->kunmap_ops[i].handle = map->kmap_ops[i].handle;drivers/xen/gntdev.c +5
-0+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { + unsigned long mfn; + + mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));Not
pfn_to_mfn()?I'd love to, but
pfn_to_mfnis only defined for x86, not ARM: [1] and [2] Thus,
Quoted 7 lines
Quoted 5 lines
drivers/xen/gntdev.c:408:10: error: implicit declaration of function ‘pfn_to_mfn’ [-Werror=implicit-function-declaration]
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));So, I'll keep
__pfn_to_mfnHow will this work on non-PV x86?
So, you mean I need:
#ifdef CONFIG_X86
mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
#else
mfn = __pfn_to_mfn(page_to_pfn(map->pages[i]));
#endif
Quoted 3 lines
-boris
Thank you,
Oleksandr
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 5/9] xen/gntdev: Allow mappings for DMA buffers
In reply to Boris OstrovskyQuoted 59 lines · Boris Ostrovsky
Quoted 46 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Allow mappings for DMA backed buffers if grant table module supports such: this extends grant device to not only map buffers made of balloon pages, but also from buffers allocated with
dma_alloc_xxx.Signed-off-by Oleksandr Andrushchenko <[email protected]>--- drivers/xen/gntdev.c | 99 ++++++++++++++++++++++++++++++++++++++- include/uapi/xen/gntdev.h | 15 ++++++ 2 files changed, 112 insertions(+), 2 deletions(-)drivers/xen/gntdev.c +11
-0@@ -37,6 +37,9 @@#include <linux/slab.h> #include <linux/highmem.h> #include <linux/refcount.h> +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +#include <linux/of_device.h> +#endif #include <xen/xen.h> #include <xen/grant_table.h> @@ -72,6 +75,11 @@ struct gntdev_priv {struct mutex lock;struct mm_struct *mm;struct mmu_notifier mn; + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +/* Device for which DMA memory is allocated. */ +struct device *dma_dev; +#endif };struct unmap_notify {@@ -96,10 +104,27 @@ struct grant_map {struct gnttab_unmap_grant_ref *kunmap_ops;struct page **pages;unsigned long pages_vm_start; + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +/* drivers/xen/gntdev.c struct grant_map { · line 119
Quoted 10 lines
drivers/xen/gntdev.c +10
-0+* If dmabuf_vaddr is not NULL then this mapping is backed by DMA +* capable memory. +*/ + +struct device *dma_dev; +/* Flags used to create this DMA buffer: GNTDEV_DMA_FLAG_XXX. */ +int dma_flags; +void *dma_vaddr; +dma_addr_t dma_bus_addr; +/* This is required for gnttab_dma_{alloc|free}_pages. */ How about
Quoted 2 lines
/* Needed to avoid allocation in
gnttab_dma_free_pages(). */
Ok
Quoted 39 lines
Quoted 26 lines
drivers/xen/gntdev.c +15
-0+xen_pfn_t *frames; +#endif };static int unmap_grant_pages (struct grant_map *map,int offset,int pages); +static struct miscdevice gntdev_miscdev; +/* ------------------------------------------------------------------ */ static void gntdev_print_maps(struct gntdev_priv *priv,@@ -121,8 +146,27 @@ static void gntdev_free_map(struct grant_map *map)if (map ==NULL )return ; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +if (map->dma_vaddr) { +struct gnttab_dma_alloc_args args; + + args.dev = map->dma_dev; + args.coherent = map->dma_flags &GNTDEV_DMA_FLAG_COHERENT ; + args.nr_pages = map->count; + args.pages = map->pages; + args.frames = map->frames; + args.vaddr = map->dma_vaddr; + args.dev_bus_addr = map->dma_bus_addr;drivers/xen/gntdev.c static void gntdev_free_map(struct grant_map *map) · line 169
Quoted 10 lines
drivers/xen/gntdev.c +8
-0+ +gnttab_dma_free_pages (&args); + } else +#endif if (map->pages)gnttab_free_pages (map->count, map->pages); + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +kfree (map->frames); +#endif Can this be done under if (
map->dma_vaddr) ?
Quoted 2 lines
In other words, is it
possible fordma_vaddrto be NULL and still have unallocated frames pointer?
It is possible to have vaddr == NULL and frames != NULL as we allocate frames outside of gnttab_dma_alloc_pages which may fail. Calling kfree on NULL pointer is safe, so I see no reason to change this code.
Quoted 52 lines
Quoted 52 lines
drivers/xen/gntdev.c +33
-1kfree (map->pages);kfree (map->grants);kfree (map->map_ops);@@ -132,7 +176,8 @@ static void gntdev_free_map(struct grant_map *map)kfree (map); } -static struct grant_map *gntdev_alloc_map (struct gntdev_priv *priv,int count) +static struct grant_map *gntdev_alloc_map (struct gntdev_priv *priv,int count, +int dma_flags) {struct grant_map *add;int i;@@ -155,6 +200,37 @@ static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) NULL == add->pages) goto err; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + add->dma_flags = dma_flags; + +/* +* Check if this mapping is requested to be backed +* by a DMA buffer. +*/ +if (dma_flags & (GNTDEV_DMA_FLAG_WC |GNTDEV_DMA_FLAG_COHERENT )) { +struct gnttab_dma_alloc_args args; + + add->frames =kcalloc (count,sizeof (add->frames[0 ]), +GFP_KERNEL ); +if (!add->frames) + goto err; + +/* Remember the device, so we can free DMA memory. */ + add->dma_dev = priv->dma_dev; + + args.dev = priv->dma_dev; + args.coherent = dma_flags &GNTDEV_DMA_FLAG_COHERENT ; + args.nr_pages = count; + args.pages = add->pages; + args.frames = add->frames; + +if (gnttab_dma_alloc_pages (&args)) + goto err; + + add->dma_vaddr = args.vaddr; + add->dma_bus_addr = args.dev_bus_addr; + } else +#endif if (gnttab_alloc_pages (count, add->pages)) goto err;
Quoted 11 lines
drivers/xen/gntdev.c static int map_grant_pages(struct grant_map *map) · line 408
Quoted 9 lines
drivers/xen/gntdev.c +5
-0@@ -325,6 +401,14 @@ static int map_grant_pages(struct grant_map *map) map->unmap_ops[i].handle = map->map_ops[i].handle;if (use_ptemod) map->kunmap_ops[i].handle = map->kmap_ops[i].handle; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { +unsigned long mfn; + + mfn =__pfn_to_mfn (page_to_pfn (map->pages[i]));Not
pfn_to_mfn()?
I'd love to, but pfn_to_mfn is only defined for x86, not ARM: [1] and [2] Thus,
drivers/xen/gntdev.c:408:10: error: implicit declaration of function ‘pfn_to_mfn’ [-Werror=implicit-function-declaration] mfn = pfn_to_mfn(page_to_pfn(map->pages[i]));
So, I'll keep __pfn_to_mfn
Quoted 3 lines
-boris
Thank you,
Oleksandr
Quoted 54 lines
Quoted 54 lines
drivers/xen/gntdev.c +15
-1+ map->unmap_ops[i].dev_bus_addr = __pfn_to_phys(mfn); + } +#endif }return err; }@@ -548,6 +632,17 @@ static int gntdev_open(struct inode *inode, struct file *flip) } flip->private_data = priv; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + priv->dma_dev = gntdev_miscdev.this_device; + +/* +* The device is not spawn from a device tree, so arch_setup_dma_ops +* is not called, thus leaving the device with dummy DMA ops. +* Fix this call of_dma_configure() with a NULL node to set +* default DMA ops. +*/ +of_dma_configure (priv->dma_dev,NULL ); +#endif pr_debug ("priv %p\n" , priv);return 0 ;@@ -589,7 +684,7 @@ static long gntdev_ioctl_map_grant_ref(struct gntdev_priv *priv,return -EINVAL ; err = -ENOMEM ; - map =gntdev_alloc_map (priv, op.count); + map =gntdev_alloc_map (priv, op.count,0 /* This is not a dma-buf. */ );if (!map)return err;include/uapi/xen/gntdev.h +13
-0@@ -200,4 +200,19 @@ struct ioctl_gntdev_grant_copy {/* Send an interrupt on the indicated event channel */ #define UNMAP_NOTIFY_SEND_EVENT 0x2 +/* +* Flags to be used while requesting memory mapping's backing storage +* to be allocated with DMA API. +*/ + +/* +* The buffer is backed with memory allocated with dma_alloc_wc. +*/ +#define GNTDEV_DMA_FLAG_WC (1 << 0) + +/* +* The buffer is backed with memory allocated with dma_alloc_coherent. +*/
Quoted 8 lines
include/uapi/xen/gntdev.h struct ioctl_gntdev_grant_copy { · line 218
Quoted 3 lines
include/uapi/xen/gntdev.h +2
-0+#define GNTDEV_DMA_FLAG_COHERENT (1 << 1) +#endif /* __LINUX_PUBLIC_GNTDEV_H__ */ _______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
[1] https://elixir.bootlin.com/linux/v4.17/ident/pfn_to_mfn
[2] https://elixir.bootlin.com/linux/v4.17/ident/__pfn_to_mfn
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v2 5/9 xen/gntdev: Allow mappings for DMA buffers
In reply to Oleksandr AndrushchenkoFrom: Oleksandr Andrushchenko <[email protected]>
Allow mappings for DMA backed buffers if grant table module supports such: this extends grant device to not only map buffers made of balloon pages, but also from buffers allocated with dma_alloc_xxx.
--- drivers/xen/gntdev.c | 99 ++++++++++++++++++++++++++++++++++++++- include/uapi/xen/gntdev.h | 15 ++++++ 2 files changed, 112 insertions(+), 2 deletions(-)
drivers/xen/gntdev.c +97 -2
@@ -37,6 +37,9 @@#include <linux/slab.h> #include <linux/highmem.h> #include <linux/refcount.h> +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +#include <linux/of_device.h> +#endif #include <xen/xen.h> #include <xen/grant_table.h>
@@ -72,6 +75,11 @@ struct gntdev_priv {struct mutex lock;struct mm_struct *mm;struct mmu_notifier mn; + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +/* Device for which DMA memory is allocated. */ +struct device *dma_dev; +#endif };struct unmap_notify {
@@ -96,10 +104,27 @@ struct grant_map {struct gnttab_unmap_grant_ref *kunmap_ops;struct page **pages;unsigned long pages_vm_start; + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +/* +* If dmabuf_vaddr is not NULL then this mapping is backed by DMA +* capable memory. +*/ + +struct device *dma_dev; +/* Flags used to create this DMA buffer: GNTDEV_DMA_FLAG_XXX. */ +int dma_flags; +void *dma_vaddr; +dma_addr_t dma_bus_addr; +/* This is required for gnttab_dma_{alloc|free}_pages. */ +xen_pfn_t *frames; +#endif };static int unmap_grant_pages (struct grant_map *map,int offset,int pages); +static struct miscdevice gntdev_miscdev; +/* ------------------------------------------------------------------ */ static void gntdev_print_maps(struct gntdev_priv *priv,
@@ -121,8 +146,27 @@ static void gntdev_free_map(struct grant_map *map)if (map ==NULL )return ; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +if (map->dma_vaddr) { +struct gnttab_dma_alloc_args args; + + args.dev = map->dma_dev; + args.coherent = map->dma_flags &GNTDEV_DMA_FLAG_COHERENT ; + args.nr_pages = map->count; + args.pages = map->pages; + args.frames = map->frames; + args.vaddr = map->dma_vaddr; + args.dev_bus_addr = map->dma_bus_addr; + +gnttab_dma_free_pages (&args); + } else +#endif if (map->pages)gnttab_free_pages (map->count, map->pages); + +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC +kfree (map->frames); +#endif kfree (map->pages);kfree (map->grants);kfree (map->map_ops);
@@ -132,7 +176,8 @@ static void gntdev_free_map(struct grant_map *map)kfree (map); } -static struct grant_map *gntdev_alloc_map (struct gntdev_priv *priv,int count) +static struct grant_map *gntdev_alloc_map (struct gntdev_priv *priv,int count, +int dma_flags) {struct grant_map *add;int i;
@@ -155,6 +200,37 @@ static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count) NULL == add->pages) goto err; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + add->dma_flags = dma_flags; + +/* +* Check if this mapping is requested to be backed +* by a DMA buffer. +*/ +if (dma_flags & (GNTDEV_DMA_FLAG_WC |GNTDEV_DMA_FLAG_COHERENT )) { +struct gnttab_dma_alloc_args args; + + add->frames =kcalloc (count,sizeof (add->frames[0 ]), +GFP_KERNEL ); +if (!add->frames) + goto err; + +/* Remember the device, so we can free DMA memory. */ + add->dma_dev = priv->dma_dev; + + args.dev = priv->dma_dev; + args.coherent = dma_flags &GNTDEV_DMA_FLAG_COHERENT ; + args.nr_pages = count; + args.pages = add->pages; + args.frames = add->frames; + +if (gnttab_dma_alloc_pages (&args)) + goto err; + + add->dma_vaddr = args.vaddr; + add->dma_bus_addr = args.dev_bus_addr; + } else +#endif if (gnttab_alloc_pages (count, add->pages)) goto err;
@@ -325,6 +401,14 @@ static int map_grant_pages(struct grant_map *map) map->unmap_ops[i].handle = map->map_ops[i].handle;if (use_ptemod) map->kunmap_ops[i].handle = map->kmap_ops[i].handle; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + else if (map->dma_vaddr) { +unsigned long mfn; + + mfn =__pfn_to_mfn (page_to_pfn (map->pages[i])); + map->unmap_ops[i].dev_bus_addr =__pfn_to_phys (mfn); + } +#endif }return err; }
@@ -548,6 +632,17 @@ static int gntdev_open(struct inode *inode, struct file *flip) } flip->private_data = priv; +#ifdef CONFIG_XEN_GRANT_DMA_ALLOC + priv->dma_dev = gntdev_miscdev.this_device; + +/* +* The device is not spawn from a device tree, so arch_setup_dma_ops +* is not called, thus leaving the device with dummy DMA ops. +* Fix this call of_dma_configure() with a NULL node to set +* default DMA ops. +*/ +of_dma_configure (priv->dma_dev,NULL ); +#endif pr_debug ("priv %p\n" , priv);return 0 ;
@@ -589,7 +684,7 @@ static long gntdev_ioctl_map_grant_ref(struct gntdev_priv *priv,return -EINVAL ; err = -ENOMEM ; - map =gntdev_alloc_map (priv, op.count); + map =gntdev_alloc_map (priv, op.count,0 /* This is not a dma-buf. */ );if (!map)return err;
include/uapi/xen/gntdev.h +15 -0
@@ -200,4 +200,19 @@ struct ioctl_gntdev_grant_copy {/* Send an interrupt on the indicated event channel */ #define UNMAP_NOTIFY_SEND_EVENT 0x2 +/* +* Flags to be used while requesting memory mapping's backing storage +* to be allocated with DMA API. +*/ + +/* +* The buffer is backed with memory allocated with dma_alloc_wc. +*/ +#define GNTDEV_DMA_FLAG_WC (1 << 0) + +/* +* The buffer is backed with memory allocated with dma_alloc_coherent. +*/ +#define GNTDEV_DMA_FLAG_COHERENT (1 << 1) +#endif /* __LINUX_PUBLIC_GNTDEV_H__ */
Signature · 7 lines
2.17.0 _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v2 6/9 xen/gntdev: Add initial support for dma-buf UAPI
In reply to Oleksandr AndrushchenkoFrom: Oleksandr Andrushchenko <[email protected]>
Add UAPI and IOCTLs for dma-buf grant device driver extension:
the extension allows userspace processes and kernel modules to use Xen backed dma-buf implementation. With this extension grant references to the pages of an imported dma-buf can be exported for other domain use and grant references coming from a foreign domain can be converted into a local dma-buf for local export. Implement basic initialization and stubs for Xen DMA buffers' support.
--- drivers/xen/Kconfig | 10 +++ drivers/xen/Makefile | 1 + drivers/xen/gntdev-dmabuf.c | 75 +++++++++++++++++++ drivers/xen/gntdev-dmabuf.h | 41 +++++++++++ drivers/xen/gntdev.c | 142 ++++++++++++++++++++++++++++++++++++ include/uapi/xen/gntdev.h | 91 +++++++++++++++++++++++ 6 files changed, 360 insertions(+) create mode 100644 drivers/xen/gntdev-dmabuf.c create mode 100644 drivers/xen/gntdev-dmabuf.h
drivers/xen/Kconfig +10 -0
@@ -152,6 +152,16 @@ config XEN_GNTDEV help Allows userspace processes to use grants. +config XEN_GNTDEV_DMABUF + bool "Add support for dma-buf grant access device driver extension" + depends on XEN_GNTDEV && XEN_GRANT_DMA_ALLOC && DMA_SHARED_BUFFER + help + Allows userspace processes and kernel modules to use Xen backed + dma-buf implementation. With this extension grant references to + the pages of an imported dma-buf can be exported for other domain + use and grant references coming from a foreign domain can be + converted into a local dma-buf for local export. + config XEN_GRANT_DEV_ALLOC tristate "User-space grant reference allocator driver" depends on XEN
drivers/xen/Makefile +1 -0
@@ -41,5 +41,6 @@ obj-$(CONFIG_XEN_PVCALLS_BACKEND) += pvcalls-back.o obj-$(CONFIG_XEN_PVCALLS_FRONTEND) += pvcalls-front.o xen-evtchn-y := evtchn.o xen-gntdev-y := gntdev.o +xen-gntdev-$(CONFIG_XEN_GNTDEV_DMABUF) += gntdev-dmabuf.o xen-gntalloc-y := gntalloc.o xen-privcmd-y := privcmd.o
drivers/xen/gntdev-dmabuf.c new file +75 -0
75 lines not on this page · raw message
drivers/xen/gntdev-dmabuf.h new file +41 -0
41 lines not on this page · raw message
drivers/xen/gntdev.c +142 -0
186 lines not on this page · raw message
include/uapi/xen/gntdev.h +91 -0
101 lines not on this page · raw message
Signature · 1 line
2.17.0
Re: [PATCH v2 6/9] xen/gntdev: Add initial support for dma-buf UAPI
Quoted 10 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Add UAPI and IOCTLs for dma-buf grant device driver extension:
the extension allows userspace processes and kernel modules to use Xen backed dma-buf implementation. With this extension grant references to the pages of an imported dma-buf can be exported for other domain use and grant references coming from a foreign domain can be converted into a local dma-buf for local export. Implement basic initialization and stubs for Xen DMA buffers' support.
It would be very helpful if people advocating for this interface reviewed it as well.
Quoted 18 lines
Signed-off-by Oleksandr Andrushchenko <[email protected]>--- drivers/xen/Kconfig | 10 +++ drivers/xen/Makefile | 1 + drivers/xen/gntdev-dmabuf.c | 75 +++++++++++++++++++ drivers/xen/gntdev-dmabuf.h | 41 +++++++++++ drivers/xen/gntdev.c | 142 ++++++++++++++++++++++++++++++++++++ include/uapi/xen/gntdev.h | 91 +++++++++++++++++++++++ 6 files changed, 360 insertions(+) create mode 100644 drivers/xen/gntdev-dmabuf.c create mode 100644 drivers/xen/gntdev-dmabuf.hdrivers/xen/Kconfig +0
-0
drivers/xen/Kconfig config XEN_GNTDEV · line 157
Quoted 6 lines
drivers/xen/Kconfig +3
-0@@ -152,6 +152,16 @@ config XEN_GNTDEV help Allows userspace processes to use grants. +config XEN_GNTDEV_DMABUF + bool "Add support for dma-buf grant access device driver extension" + depends on XEN_GNTDEV && XEN_GRANT_DMA_ALLOC && DMA_SHARED_BUFFER
Is there a reason to have XEN_GRANT_DMA_ALLOC without XEN_GNTDEV_DMABUF?
Quoted 40 lines
drivers/xen/Kconfig +7
-0+ help + Allows userspace processes and kernel modules to use Xen backed + dma-buf implementation. With this extension grant references to + the pages of an imported dma-buf can be exported for other domain + use and grant references coming from a foreign domain can be + converted into a local dma-buf for local export. + config XEN_GRANT_DEV_ALLOC tristate "User-space grant reference allocator driver" depends on XENdrivers/xen/Makefile +1
-0@@ -41,5 +41,6 @@ obj-$(CONFIG_XEN_PVCALLS_BACKEND) += pvcalls-back.o obj-$(CONFIG_XEN_PVCALLS_FRONTEND) += pvcalls-front.o xen-evtchn-y := evtchn.o xen-gntdev-y := gntdev.o +xen-gntdev-$(CONFIG_XEN_GNTDEV_DMABUF) += gntdev-dmabuf.o xen-gntalloc-y := gntalloc.o xen-privcmd-y := privcmd.odrivers/xen/gntdev-dmabuf.c new file +13
-0@@ -0,0 +1,75 @@ +// SPDX-License-Identifier: GPL-2.0 + +/* +* Xen dma-buf functionality for gntdev. +* +* Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. +*/ + +#include <linux/slab.h> + +#include "gntdev-dmabuf.h" + +struct gntdev_dmabuf_priv {
drivers/xen/gntdev-dmabuf.c line 23
Quoted 10 lines
drivers/xen/gntdev-dmabuf.c new file +10
-0+int dummy; +}; + +/* ------------------------------------------------------------------ */ +/* DMA buffer export support. */ +/* ------------------------------------------------------------------ */ + +/* ------------------------------------------------------------------ */ +/* Implementation of wait for exported DMA buffer to be released. */ +/* ------------------------------------------------------------------ */
Why this comment style?
Quoted 70 lines
drivers/xen/gntdev-dmabuf.c new file +52
-0+ +int gntdev_dmabuf_exp_wait_released (struct gntdev_dmabuf_priv *priv,int fd, +int wait_to_ms) +{ +return -EINVAL ; +} + +/* ------------------------------------------------------------------ */ +/* DMA buffer export support. */ +/* ------------------------------------------------------------------ */ + +int gntdev_dmabuf_exp_from_pages (struct gntdev_dmabuf_export_args *args) +{ +return -EINVAL ; +} + +/* ------------------------------------------------------------------ */ +/* DMA buffer import support. */ +/* ------------------------------------------------------------------ */ + +struct gntdev_dmabuf * +gntdev_dmabuf_imp_to_refs (struct gntdev_dmabuf_priv *priv,struct device *dev, +int fd,int count,int domid) +{ +return ERR_PTR (-ENOMEM ); +} + +u32 *gntdev_dmabuf_imp_get_refs (struct gntdev_dmabuf *gntdev_dmabuf) +{ +return NULL ; +} + +int gntdev_dmabuf_imp_release (struct gntdev_dmabuf_priv *priv,u32 fd) +{ +return -EINVAL ; +} + +struct gntdev_dmabuf_priv *gntdev_dmabuf_init (void ) +{ +struct gntdev_dmabuf_priv *priv; + + priv =kzalloc (sizeof (*priv),GFP_KERNEL ); +if (!priv) +return ERR_PTR (-ENOMEM ); + +return priv; +} + +void gntdev_dmabuf_fini (struct gntdev_dmabuf_priv *priv) +{ +kfree (priv); +}drivers/xen/gntdev-dmabuf.h new file +12
-0@@ -0,0 +1,41 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +/* +* Xen dma-buf functionality for gntdev. +* +* Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. +*/ + +#ifndef _GNTDEV_DMABUF_H +#define _GNTDEV_DMABUF_H + +#include <linux/kernel.h>
drivers/xen/gntdev-dmabuf.h line 22
Quoted 10 lines
drivers/xen/gntdev-dmabuf.h new file +10
-0+#include <linux/errno.h> +#include <linux/types.h> + +struct gntdev_dmabuf_priv ; +struct gntdev_dmabuf ; +struct device ; + +struct gntdev_dmabuf_export_args { +int dummy; +};
Please define the full structure (at least what you have in the next patch) here.
Quoted 23 lines
drivers/xen/gntdev-dmabuf.h new file +19
-0+ +struct gntdev_dmabuf_priv *gntdev_dmabuf_init (void ); + +void gntdev_dmabuf_fini (struct gntdev_dmabuf_priv *priv); + +int gntdev_dmabuf_exp_from_pages (struct gntdev_dmabuf_export_args *args); + +int gntdev_dmabuf_exp_wait_released (struct gntdev_dmabuf_priv *priv,int fd, +int wait_to_ms); + +struct gntdev_dmabuf * +gntdev_dmabuf_imp_to_refs (struct gntdev_dmabuf_priv *priv,struct device *dev, +int fd,int count,int domid); + +u32 *gntdev_dmabuf_imp_get_refs (struct gntdev_dmabuf *gntdev_dmabuf); + +int gntdev_dmabuf_imp_release (struct gntdev_dmabuf_priv *priv,u32 fd); + +#endif drivers/xen/gntdev.c +0
-0
...
Quoted 2 lines
+#ifdef
CONFIG_XEN_GNTDEV_DMABUF
This code belongs in gntdev-dmabuf.c.
drivers/xen/gntdev.c static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) · line 1069
Quoted 8 lines
drivers/xen/gntdev.c +8
-0+/* ------------------------------------------------------------------ */ +/* DMA buffer export support. */ +/* ------------------------------------------------------------------ */ + +int gntdev_dmabuf_exp_from_refs (struct gntdev_priv *priv,int flags, +int count,u32 domid,u32 *refs,u32 *fd) +{ +/* XXX: this will need to work with gntdev's map, so leave it here. */
This doesn't help understanding what's going on (at least to me) and is removed in the next patch. So no need for this comment.
-boris
Quoted 3 lines
drivers/xen/gntdev.c +3
-0+ *fd =-1 ; +return -EINVAL ; +}
Re: [PATCH v2 6/9] xen/gntdev: Add initial support for dma-buf UAPI
Quoted 12 lines · Boris Ostrovsky
Quoted 10 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Add UAPI and IOCTLs for dma-buf grant device driver extension:
the extension allows userspace processes and kernel modules to use Xen backed dma-buf implementation. With this extension grant references to the pages of an imported dma-buf can be exported for other domain use and grant references coming from a foreign domain can be converted into a local dma-buf for local export. Implement basic initialization and stubs for Xen DMA buffers' support.
Quoted 2 lines
It would be very helpful if people advocating for this interface reviewed it as well.
I would also love to see their comments here ;)
Quoted 21 lines
Quoted 21 lines
Signed-off-by Oleksandr Andrushchenko <[email protected]>--- drivers/xen/Kconfig | 10 +++ drivers/xen/Makefile | 1 + drivers/xen/gntdev-dmabuf.c | 75 +++++++++++++++++++ drivers/xen/gntdev-dmabuf.h | 41 +++++++++++ drivers/xen/gntdev.c | 142 ++++++++++++++++++++++++++++++++++++ include/uapi/xen/gntdev.h | 91 +++++++++++++++++++++++ 6 files changed, 360 insertions(+)create mode 100644
drivers/xen/gntdev-dmabuf.c
create mode 100644drivers/xen/gntdev-dmabuf.hdrivers/xen/Kconfig +0
-0@@ -152,6 +152,16 @@ config XEN_GNTDEV help Allows userspace processes to use grants.
Quoted 5 lines
drivers/xen/Kconfig config XEN_GNTDEV · line 157
Quoted 3 lines
drivers/xen/Kconfig +3
-0+config XEN_GNTDEV_DMABUF + bool "Add support for dma-buf grant access device driver extension" + depends on XEN_GNTDEV && XEN_GRANT_DMA_ALLOC && DMA_SHARED_BUFFERIs there a reason to have
XEN_GRANT_DMA_ALLOCwithoutXEN_GNTDEV_DMABUF?
One can use grant-table's DMA API without using dma-buf at all, e.g. dma-buf is sort of functionality on top of DMA allocated memory. We have a use-case for a driver domain (guest domain in fact) backed with IOMMU and still requiring allocations created as contiguous/DMA memory, so those buffers can be passed around to drivers expecting DMA-only buffers.
So, IMO this is a valid use-case "to have XEN_GRANT_DMA_ALLOC without XEN_GNTDEV_DMABUF"
Quoted 44 lines
Quoted 44 lines
drivers/xen/Kconfig +7
-0+ help + Allows userspace processes and kernel modules to use Xen backed + dma-buf implementation. With this extension grant references to + the pages of an imported dma-buf can be exported for other domain + use and grant references coming from a foreign domain can be + converted into a local dma-buf for local export. + config XEN_GRANT_DEV_ALLOC tristate "User-space grant reference allocator driver" depends on XENdrivers/xen/Makefile +1
-0@@ -41,5 +41,6 @@ obj-$(CONFIG_XEN_PVCALLS_BACKEND) += pvcalls-back.o obj-$(CONFIG_XEN_PVCALLS_FRONTEND) += pvcalls-front.o xen-evtchn-y := evtchn.o xen-gntdev-y := gntdev.o +xen-gntdev-$(CONFIG_XEN_GNTDEV_DMABUF) += gntdev-dmabuf.o xen-gntalloc-y := gntalloc.o xen-privcmd-y := privcmd.odrivers/xen/gntdev-dmabuf.c new file +16
-0@@ -0,0 +1,75 @@ +// SPDX-License-Identifier: GPL-2.0 + +/* +* Xen dma-buf functionality for gntdev. +* +* Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. +*/ + +#include <linux/slab.h> + +#include "gntdev-dmabuf.h" + +struct gntdev_dmabuf_priv { +int dummy; +}; +
Quoted 8 lines
drivers/xen/gntdev-dmabuf.c line 23
Quoted 7 lines
drivers/xen/gntdev-dmabuf.c new file +7
-0+/* ------------------------------------------------------------------ */ +/* DMA buffer export support. */ +/* ------------------------------------------------------------------ */ + +/* ------------------------------------------------------------------ */ +/* Implementation of wait for exported DMA buffer to be released. */ +/* ------------------------------------------------------------------ */ Why this comment style?
Just a copy-paste from gntdev, will change to usual /*..*/
Quoted 76 lines
Quoted 76 lines
drivers/xen/gntdev-dmabuf.c new file +52
-0+ +int gntdev_dmabuf_exp_wait_released (struct gntdev_dmabuf_priv *priv,int fd, +int wait_to_ms) +{ +return -EINVAL ; +} + +/* ------------------------------------------------------------------ */ +/* DMA buffer export support. */ +/* ------------------------------------------------------------------ */ + +int gntdev_dmabuf_exp_from_pages (struct gntdev_dmabuf_export_args *args) +{ +return -EINVAL ; +} + +/* ------------------------------------------------------------------ */ +/* DMA buffer import support. */ +/* ------------------------------------------------------------------ */ + +struct gntdev_dmabuf * +gntdev_dmabuf_imp_to_refs (struct gntdev_dmabuf_priv *priv,struct device *dev, +int fd,int count,int domid) +{ +return ERR_PTR (-ENOMEM ); +} + +u32 *gntdev_dmabuf_imp_get_refs (struct gntdev_dmabuf *gntdev_dmabuf) +{ +return NULL ; +} + +int gntdev_dmabuf_imp_release (struct gntdev_dmabuf_priv *priv,u32 fd) +{ +return -EINVAL ; +} + +struct gntdev_dmabuf_priv *gntdev_dmabuf_init (void ) +{ +struct gntdev_dmabuf_priv *priv; + + priv =kzalloc (sizeof (*priv),GFP_KERNEL ); +if (!priv) +return ERR_PTR (-ENOMEM ); + +return priv; +} + +void gntdev_dmabuf_fini (struct gntdev_dmabuf_priv *priv) +{ +kfree (priv); +}drivers/xen/gntdev-dmabuf.h new file +17
-0@@ -0,0 +1,41 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +/* +* Xen dma-buf functionality for gntdev. +* +* Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. +*/ + +#ifndef _GNTDEV_DMABUF_H +#define _GNTDEV_DMABUF_H + +#include <linux/kernel.h> +#include <linux/errno.h> +#include <linux/types.h> + +struct gntdev_dmabuf_priv ; +struct gntdev_dmabuf ;
Quoted 8 lines
drivers/xen/gntdev-dmabuf.h line 22
Quoted 5 lines
drivers/xen/gntdev-dmabuf.h new file +5
-0+struct device ; + +struct gntdev_dmabuf_export_args { +int dummy; +};Please define the full structure (at least what you have in the next patch) here.
Ok, will define what I have in the next patch, but won't initialize anything until the next patch. Will this work for you?
Quoted 27 lines
Quoted 24 lines
drivers/xen/gntdev-dmabuf.h new file +19
-0+ +struct gntdev_dmabuf_priv *gntdev_dmabuf_init (void ); + +void gntdev_dmabuf_fini (struct gntdev_dmabuf_priv *priv); + +int gntdev_dmabuf_exp_from_pages (struct gntdev_dmabuf_export_args *args); + +int gntdev_dmabuf_exp_wait_released (struct gntdev_dmabuf_priv *priv,int fd, +int wait_to_ms); + +struct gntdev_dmabuf * +gntdev_dmabuf_imp_to_refs (struct gntdev_dmabuf_priv *priv,struct device *dev, +int fd,int count,int domid); + +u32 *gntdev_dmabuf_imp_get_refs (struct gntdev_dmabuf *gntdev_dmabuf); + +int gntdev_dmabuf_imp_release (struct gntdev_dmabuf_priv *priv,u32 fd); + +#endif drivers/xen/gntdev.c +0
-0...
Quoted 1 line
Quoted 2 lines
Quoted 1 line
+#ifdef
CONFIG_XEN_GNTDEV_DMABUFThis code belongs in
gntdev-dmabuf.c.
The reason I have this code here is that it is heavily tied to gntdev's internal functionality, e.g. map/unmap. I do not want to extend gntdev's API, so gntdev-dmabuf can access these. What is more dma-buf doesn't need to know about maps done by gntdev as there is no use of that information in gntdev-dmabuf. So, it seems more naturally to have dma-buf's related map/unmap code where it is: in gntdev.
Quoted 11 lines
drivers/xen/gntdev.c static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) · line 1069
Quoted 9 lines
drivers/xen/gntdev.c +8
-0+/* ------------------------------------------------------------------ */ +/* DMA buffer export support. */ +/* ------------------------------------------------------------------ */ + +int gntdev_dmabuf_exp_from_refs (struct gntdev_priv *priv,int flags, +int count,u32 domid,u32 *refs,u32 *fd) +{ +/* XXX: this will need to work with gntdev's map, so leave it here. */ This doesn't help understanding what's going on (at least to me) and is removed in the next patch. So no need for this comment.
Will remove the comment
Quoted 6 lines
-boris
drivers/xen/gntdev.c static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) · line 1072
Quoted 3 lines
drivers/xen/gntdev.c +3
-0+ *fd =-1 ; +return -EINVAL ; +}
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 6/9] xen/gntdev: Add initial support for dma-buf UAPI
Quoted 11 lines · Oleksandr Andrushchenko
Quoted 8 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev-dmabuf.h new file +3
-0+struct gntdev_dmabuf_export_args { + int dummy; +};Please define the full structure (at least what you have in the next patch) here.
Ok, will define what I have in the next patch, but won't initialize anything until the next patch. Will this work for you?
Sure, I just didn't see the need for the dummy argument that you remove later.
Quoted 8 lines
Quoted 8 lines
Quoted 5 lines
drivers/xen/gntdev.c +0
-0...
Quoted 1 line
+#ifdef
CONFIG_XEN_GNTDEV_DMABUF
Quoted 8 lines
Quoted 1 line
This code belongs in
gntdev-dmabuf.c.The reason I have this code here is that it is heavily tied to gntdev's internal functionality, e.g. map/unmap. I do not want to extend gntdev's API, so gntdev-dmabuf can access these. What is more dma-buf doesn't need to know about maps done by gntdev as there is no use of that information in gntdev-dmabuf. So, it seems more naturally to have dma-buf's related map/unmap code where it is: in gntdev.
Sorry, I don't follow. Why would this require extending the API? It's just moving routines to a different file that is linked to the same module.
Since this is under CONFIG_XEN_GNTDEV_DMABUF then why shouldn't it be in gntdev-dmabuf.c? In my view that's the file where all dma-related "stuff" lives.
-boris
-boris
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 6/9] xen/gntdev: Add initial support for dma-buf UAPI
In reply to Oleksandr AndrushchenkoQuoted 11 lines · Oleksandr Andrushchenko
Quoted 8 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev-dmabuf.h new file +3
-0+struct gntdev_dmabuf_export_args { + int dummy; +};Please define the full structure (at least what you have in the next patch) here.
Ok, will define what I have in the next patch, but won't initialize anything until the next patch. Will this work for you?
Sure, I just didn't see the need for the dummy argument that you remove later.
Quoted 8 lines
Quoted 8 lines
Quoted 5 lines
drivers/xen/gntdev.c +0
-0...
Quoted 1 line
+#ifdef
CONFIG_XEN_GNTDEV_DMABUF
Quoted 8 lines
Quoted 1 line
This code belongs in
gntdev-dmabuf.c.The reason I have this code here is that it is heavily tied to gntdev's internal functionality, e.g. map/unmap. I do not want to extend gntdev's API, so gntdev-dmabuf can access these. What is more dma-buf doesn't need to know about maps done by gntdev as there is no use of that information in gntdev-dmabuf. So, it seems more naturally to have dma-buf's related map/unmap code where it is: in gntdev.
Sorry, I don't follow. Why would this require extending the API? It's just moving routines to a different file that is linked to the same module.
Since this is under CONFIG_XEN_GNTDEV_DMABUF then why shouldn't it be in gntdev-dmabuf.c? In my view that's the file where all dma-related "stuff" lives.
-boris
-boris
Re: [PATCH v2 6/9] xen/gntdev: Add initial support for dma-buf UAPI
Quoted 7 lines · Boris Ostrovsky
Quoted 6 lines · Oleksandr Andrushchenko
Quoted 5 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev-dmabuf.h new file +3
-0+struct gntdev_dmabuf_export_args { + int dummy; +};
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Please define the full structure (at least what you have in the next patch) here.
Ok, will define what I have in the next patch, but won't initialize anything until the next patch. Will this work for you?
Sure, I just didn't see the need for the dummy argument that you remove later.
Ok
Quoted 15 lines
Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
drivers/xen/gntdev.c +0
-0...
Quoted 1 line
+#ifdef
CONFIG_XEN_GNTDEV_DMABUFQuoted 8 lines
Quoted 1 line
This code belongs in
gntdev-dmabuf.c.The reason I have this code here is that it is heavily tied to gntdev's internal functionality, e.g. map/unmap. I do not want to extend gntdev's API, so gntdev-dmabuf can access these. What is more dma-buf doesn't need to know about maps done by gntdev as there is no use of that information in gntdev-dmabuf. So, it seems more naturally to have dma-buf's related map/unmap code where it is: in gntdev.
Quoted 2 lines
Sorry, I don't follow. Why would this require extending the API? It's just moving routines to a different file that is linked to the same module.
I do understand your intention here and tried to avoid dma-buf related code in gntdev.c as much as possible. So, let me explain my decision in more detail.
There are 2 use-cases we have: dma-buf import and export.
While importing a dma-buf all the dma-buf related functionality can easily be kept inside gntdev-dmabuf.c w/o any issue as all we need from gntdev.c is dev, dma_buf_fd, count and domid for that.
But in case of dma-buf export we need to:
1. struct grant_map *map = gntdev_alloc_map(priv, count, dmabuf_flags);
2. gntdev_add_map(priv, map);
3. Set map->flags
4. ret = map_grant_pages(map);
5. And only now we are all set to export the new dma-buf from *map->pages*
So, until 5) we use private gtndev.c's API not exported to outside world:
a. struct grant_map
b. static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count, int dma_flags)
c. static void gntdev_add_map(struct gntdev_priv *priv, struct grant_map *add) d. static int map_grant_pages(struct grant_map *map)
Thus, all the above cannot be accessed from gntdev-dmabuf.c
This is why I say that gntdev.c's API will need to be extended to provide the above a-d if we want all dma-buf export code to leave in gntdev-dmabuf.c. But that doesn't seem good to me and what is more a-d are really gntdev.c's functionality, not dma-buf's which only needs pages and doesn't really care from where those come.
That was the reason I partitioned export into 2 chunks: gntdev + gntdev-dmabuf.
You might also ask why importing side does Xen related things (granting references+) in gntdev-dmabuf, not gntdev so it is consistent with the dma-buf exporter? This is because importer uses grant-table's API which seems to be not natural for gntdev.c, so it can leave in gntdev-dmabuf.c which has a use-case for that, while gntdev remains the same.
Quoted 3 lines
Since this is under
CONFIG_XEN_GNTDEV_DMABUFthen why shouldn't it be ingntdev-dmabuf.c? In my view that's the file where all dma-related "stuff" lives.
Agree, but IMO grant_map stuff for dma-buf importer is right in its place in gntdev.c and all the rest of dma-buf specifics live in gntdev-dmabuf.c as they should
Review
Quoted 6 lines
(quoted diff) +0
-2-boris -boris
Thank you,
Oleksandr
PATCH v2 6/9 xen/gntdev: Add initial support for dma-buf UAPI
Quoted 48 lines · Oleksandr Andrushchenko
Quoted 17 lines · Boris Ostrovsky
Quoted 8 lines · Oleksandr Andrushchenko
Quoted 7 lines · Boris Ostrovsky
Quoted 4 lines
drivers/xen/gntdev.c +0
-0...
Quoted 1 line
+#ifdef
CONFIG_XEN_GNTDEV_DMABUFQuoted 8 lines
Quoted 1 line
This code belongs in
gntdev-dmabuf.c.The reason I have this code here is that it is heavily tied to gntdev's internal functionality, e.g. map/unmap. I do not want to extend gntdev's API, so gntdev-dmabuf can access these. What is more dma-buf doesn't need to know about maps done by gntdev as there is no use of that information in gntdev-dmabuf. So, it seems more naturally to have dma-buf's related map/unmap code where it is: in gntdev.
Quoted 3 lines
Sorry, I don't follow. Why would this require extending the API? It's just moving routines to a different file that is linked to the same module.
I do understand your intention here and tried to avoid dma-buf related code in
gntdev.cas much as possible. So, let me explain my decision in more detail.There are 2 use-cases we have: dma-buf import and export.
While importing a dma-buf all the dma-buf related functionality can easily be kept inside
gntdev-dmabuf.cw/o any issue as all we need fromgntdev.cis dev,dma_buf_fd, count and domid for that.But in case of dma-buf export we need to:
1. structgrant_map*map =gntdev_alloc_map(priv, count, dmabuf_flags);
2.gntdev_add_map(priv, map);
3. Setmap->flags
4. ret =map_grant_pages(map);
5. And only now we are all set to export the new dma-buf from *map->pages*So, until 5) we use private gtndev.c's API not exported to outside world:
a. structgrant_map
b. static structgrant_map*gntdev_alloc_map(structgntdev_priv*priv, int count,
intdma_flags)
c. static voidgntdev_add_map(struct gntdev_priv *priv, struct grant_map *add)
d. static intmap_grant_pages(struct grant_map *map)
Quoted 4 lines
Thus, all the above cannot be accessed from
gntdev-dmabuf.cThis is why I say that gntdev.c's API will need to be extended to provide the above
a-d if we want all dma-buf export code to leave ingntdev-dmabuf.c.
I still don't understand why you feel this would be extending the API. These routines and the struct can be declared in local header file and this header file will not be visible to anyone but gntdev.c and gntdev-dmabuf.c. You can, for example, put this into gntdev-dmabuf.h (and then rename it to something else, like gntdev-common.h).
Quoted 8 lines
But that doesn't seem good to me and what is more a-d are really gntdev.c's
functionality, not dma-buf's which only needs pages and doesn't really care from
where those come.
That was the reason I partitioned export into 2 chunks: gntdev + gntdev-dmabuf.
Quoted 9 lines
You might also ask why importing side does Xen related things (granting references+)
in gntdev-dmabuf, not gntdev so it is consistent with the dma-buf exporter?
This is because importer uses grant-table's API which seems to be not natural forgntdev.c,
so it can leave ingntdev-dmabuf.cwhich has a use-case for that, while gntdev
remains the same.
Yet another reason why this code should be moved: importing and exporting functionalities logically belong together. The fat that they are implemented using different methods is not relevant IMO.
If you have code which is under ifdef CONFIG_GNTDEV_DMABUF and you have file called gntdev-dmabuf.c it sort of implies that this code should live in that file (unless that code is intertwined with other code, which is not the case here).
-boris
Quoted 8 lines
Quoted 3 lines
Since this is under
CONFIG_XEN_GNTDEV_DMABUFthen why shouldn't it be ingntdev-dmabuf.c? In my view that's the file where all dma-related "stuff" lives.Agree, but IMO
grant_mapstuff for dma-buf importer is right in its place ingntdev.c
and all the rest of dma-buf specifics live ingntdev-dmabuf.cas they shouldQuoted 1 line
Quoted 7 lines
Review
Quoted 5 lines
(quoted diff) +0
-2-boris -borisThank you,
Oleksandr
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v2 6/9 xen/gntdev: Add initial support for dma-buf UAPI
In reply to Oleksandr AndrushchenkoQuoted 48 lines · Oleksandr Andrushchenko
Quoted 17 lines · Boris Ostrovsky
Quoted 8 lines · Oleksandr Andrushchenko
Quoted 7 lines · Boris Ostrovsky
Quoted 4 lines
drivers/xen/gntdev.c +0
-0...
Quoted 1 line
+#ifdef
CONFIG_XEN_GNTDEV_DMABUFQuoted 8 lines
Quoted 1 line
This code belongs in
gntdev-dmabuf.c.The reason I have this code here is that it is heavily tied to gntdev's internal functionality, e.g. map/unmap. I do not want to extend gntdev's API, so gntdev-dmabuf can access these. What is more dma-buf doesn't need to know about maps done by gntdev as there is no use of that information in gntdev-dmabuf. So, it seems more naturally to have dma-buf's related map/unmap code where it is: in gntdev.
Quoted 3 lines
Sorry, I don't follow. Why would this require extending the API? It's just moving routines to a different file that is linked to the same module.
I do understand your intention here and tried to avoid dma-buf related code in
gntdev.cas much as possible. So, let me explain my decision in more detail.There are 2 use-cases we have: dma-buf import and export.
While importing a dma-buf all the dma-buf related functionality can easily be kept inside
gntdev-dmabuf.cw/o any issue as all we need fromgntdev.cis dev,dma_buf_fd, count and domid for that.But in case of dma-buf export we need to:
1. structgrant_map*map =gntdev_alloc_map(priv, count, dmabuf_flags);
2.gntdev_add_map(priv, map);
3. Setmap->flags
4. ret =map_grant_pages(map);
5. And only now we are all set to export the new dma-buf from *map->pages*So, until 5) we use private gtndev.c's API not exported to outside world:
a. structgrant_map
b. static structgrant_map*gntdev_alloc_map(structgntdev_priv*priv, int count,
intdma_flags)
c. static voidgntdev_add_map(struct gntdev_priv *priv, struct grant_map *add)
d. static intmap_grant_pages(struct grant_map *map)
Quoted 4 lines
Thus, all the above cannot be accessed from
gntdev-dmabuf.cThis is why I say that gntdev.c's API will need to be extended to provide the above
a-d if we want all dma-buf export code to leave ingntdev-dmabuf.c.
I still don't understand why you feel this would be extending the API. These routines and the struct can be declared in local header file and this header file will not be visible to anyone but gntdev.c and gntdev-dmabuf.c. You can, for example, put this into gntdev-dmabuf.h (and then rename it to something else, like gntdev-common.h).
Quoted 8 lines
But that doesn't seem good to me and what is more a-d are really gntdev.c's
functionality, not dma-buf's which only needs pages and doesn't really care from
where those come.
That was the reason I partitioned export into 2 chunks: gntdev + gntdev-dmabuf.
Quoted 9 lines
You might also ask why importing side does Xen related things (granting references+)
in gntdev-dmabuf, not gntdev so it is consistent with the dma-buf exporter?
This is because importer uses grant-table's API which seems to be not natural forgntdev.c,
so it can leave ingntdev-dmabuf.cwhich has a use-case for that, while gntdev
remains the same.
Yet another reason why this code should be moved: importing and exporting functionalities logically belong together. The fat that they are implemented using different methods is not relevant IMO.
If you have code which is under ifdef CONFIG_GNTDEV_DMABUF and you have file called gntdev-dmabuf.c it sort of implies that this code should live in that file (unless that code is intertwined with other code, which is not the case here).
-boris
Quoted 15 lines
Quoted 3 lines
Since this is under
CONFIG_XEN_GNTDEV_DMABUFthen why shouldn't it be ingntdev-dmabuf.c? In my view that's the file where all dma-related "stuff" lives.Agree, but IMO
grant_mapstuff for dma-buf importer is right in its place ingntdev.c
and all the rest of dma-buf specifics live ingntdev-dmabuf.cas they shouldReview
Quoted 6 lines
(quoted diff) +0
-2-boris -borisThank you,
Oleksandr
Re: [PATCH v2 6/9] xen/gntdev: Add initial support for dma-buf UAPI
Quoted 55 lines · Boris Ostrovsky
Quoted 48 lines · Oleksandr Andrushchenko
Quoted 17 lines · Boris Ostrovsky
Quoted 8 lines · Oleksandr Andrushchenko
Quoted 7 lines · Boris Ostrovsky
Quoted 4 lines
drivers/xen/gntdev.c +0
-0...
Quoted 1 line
+#ifdef
CONFIG_XEN_GNTDEV_DMABUFQuoted 8 lines
Quoted 1 line
This code belongs in
gntdev-dmabuf.c.The reason I have this code here is that it is heavily tied to gntdev's internal functionality, e.g. map/unmap. I do not want to extend gntdev's API, so gntdev-dmabuf can access these. What is more dma-buf doesn't need to know about maps done by gntdev as there is no use of that information in gntdev-dmabuf. So, it seems more naturally to have dma-buf's related map/unmap code where it is: in gntdev.
Quoted 3 lines
Sorry, I don't follow. Why would this require extending the API? It's just moving routines to a different file that is linked to the same module.
I do understand your intention here and tried to avoid dma-buf related code in
gntdev.cas much as possible. So, let me explain my decision in more detail.There are 2 use-cases we have: dma-buf import and export.
While importing a dma-buf all the dma-buf related functionality can easily be kept inside
gntdev-dmabuf.cw/o any issue as all we need fromgntdev.cis dev,dma_buf_fd, count and domid for that.But in case of dma-buf export we need to:
1. structgrant_map*map =gntdev_alloc_map(priv, count, dmabuf_flags);
2.gntdev_add_map(priv, map);
3. Setmap->flags
4. ret =map_grant_pages(map);
5. And only now we are all set to export the new dma-buf from *map->pages*So, until 5) we use private gtndev.c's API not exported to outside world:
a. structgrant_map
b. static structgrant_map*gntdev_alloc_map(structgntdev_priv*priv, int count,
intdma_flags)
c. static voidgntdev_add_map(struct gntdev_priv *priv, struct grant_map *add)
d. static intmap_grant_pages(struct grant_map *map)Quoted 4 lines
Thus, all the above cannot be accessed from
gntdev-dmabuf.cThis is why I say that gntdev.c's API will need to be extended to provide the above
a-d if we want all dma-buf export code to leave ingntdev-dmabuf.c.
Quoted 4 lines
I still don't understand why you feel this would be extending the API. These routines and the struct can be declared in local header file and this header file will not be visible to anyone but
gntdev.candgntdev-dmabuf.c.
Ok, this is what I meant: I will need to move private structures and some function prototypes from gntdev.c into a header file, thus extending its API: before the header nothing were exposed. Sorry for not being clear here.
Quoted 2 lines
You can, for example, put this into
gntdev-dmabuf.h
(and then rename it to something else, likegntdev-common.h).
Sure, I will move all I need into that shared header
Quoted 20 lines
Quoted 10 lines
But that doesn't seem good to me and what is more a-d are really gntdev.c's
functionality, not dma-buf's which only needs pages and doesn't really care from
where those come.
That was the reason I partitioned export into 2 chunks: gntdev + gntdev-dmabuf.Quoted 9 lines
You might also ask why importing side does Xen related things (granting references+)
in gntdev-dmabuf, not gntdev so it is consistent with the dma-buf exporter?
This is because importer uses grant-table's API which seems to be not natural forgntdev.c,
so it can leave ingntdev-dmabuf.cwhich has a use-case for that, while gntdev
remains the same.
Quoted 8 lines
Yet another reason why this code should be moved: importing and exporting functionalities logically belong together. The fat that they are implemented using different methods is not relevant IMO.
If you have code which is under ifdef
CONFIG_GNTDEV_DMABUFand you have file calledgntdev-dmabuf.cit sort of implies that this code should live in that file (unless that code is intertwined with other code, which is not the case here).
Ok, will move as discussed above
Quoted 2 lines
-boris
Thank you,
Oleksandr
Quoted 9 lines
Quoted 9 lines
Quoted 5 lines
Since this is under
CONFIG_XEN_GNTDEV_DMABUFthen why shouldn't it be ingntdev-dmabuf.c? In my view that's the file where all dma-related "stuff" lives.Agree, but IMO
grant_mapstuff for dma-buf importer is right in its place ingntdev.c
and all the rest of dma-buf specifics live ingntdev-dmabuf.cas they should
Quoted 7 lines
Quoted 7 lines
Review
Quoted 5 lines
(quoted diff) +0
-2-boris -borisThank you,
Oleksandr
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 6/9] xen/gntdev: Add initial support for dma-buf UAPI
In reply to Boris OstrovskyQuoted 55 lines · Boris Ostrovsky
Quoted 48 lines · Oleksandr Andrushchenko
Quoted 17 lines · Boris Ostrovsky
Quoted 8 lines · Oleksandr Andrushchenko
Quoted 7 lines · Boris Ostrovsky
Quoted 4 lines
drivers/xen/gntdev.c +0
-0...
Quoted 1 line
+#ifdef
CONFIG_XEN_GNTDEV_DMABUFQuoted 8 lines
Quoted 1 line
This code belongs in
gntdev-dmabuf.c.The reason I have this code here is that it is heavily tied to gntdev's internal functionality, e.g. map/unmap. I do not want to extend gntdev's API, so gntdev-dmabuf can access these. What is more dma-buf doesn't need to know about maps done by gntdev as there is no use of that information in gntdev-dmabuf. So, it seems more naturally to have dma-buf's related map/unmap code where it is: in gntdev.
Quoted 3 lines
Sorry, I don't follow. Why would this require extending the API? It's just moving routines to a different file that is linked to the same module.
I do understand your intention here and tried to avoid dma-buf related code in
gntdev.cas much as possible. So, let me explain my decision in more detail.There are 2 use-cases we have: dma-buf import and export.
While importing a dma-buf all the dma-buf related functionality can easily be kept inside
gntdev-dmabuf.cw/o any issue as all we need fromgntdev.cis dev,dma_buf_fd, count and domid for that.But in case of dma-buf export we need to:
1. structgrant_map*map =gntdev_alloc_map(priv, count, dmabuf_flags);
2.gntdev_add_map(priv, map);
3. Setmap->flags
4. ret =map_grant_pages(map);
5. And only now we are all set to export the new dma-buf from *map->pages*So, until 5) we use private gtndev.c's API not exported to outside world:
a. structgrant_map
b. static structgrant_map*gntdev_alloc_map(structgntdev_priv*priv, int count,
intdma_flags)
c. static voidgntdev_add_map(struct gntdev_priv *priv, struct grant_map *add)
d. static intmap_grant_pages(struct grant_map *map)Quoted 4 lines
Thus, all the above cannot be accessed from
gntdev-dmabuf.cThis is why I say that gntdev.c's API will need to be extended to provide the above
a-d if we want all dma-buf export code to leave ingntdev-dmabuf.c.
Quoted 4 lines
I still don't understand why you feel this would be extending the API. These routines and the struct can be declared in local header file and this header file will not be visible to anyone but
gntdev.candgntdev-dmabuf.c.
Ok, this is what I meant: I will need to move private structures and some function prototypes from gntdev.c into a header file, thus extending its API: before the header nothing were exposed. Sorry for not being clear here.
Quoted 2 lines
You can, for example, put this into
gntdev-dmabuf.h
(and then rename it to something else, likegntdev-common.h).
Sure, I will move all I need into that shared header
Quoted 20 lines
Quoted 10 lines
But that doesn't seem good to me and what is more a-d are really gntdev.c's
functionality, not dma-buf's which only needs pages and doesn't really care from
where those come.
That was the reason I partitioned export into 2 chunks: gntdev + gntdev-dmabuf.Quoted 9 lines
You might also ask why importing side does Xen related things (granting references+)
in gntdev-dmabuf, not gntdev so it is consistent with the dma-buf exporter?
This is because importer uses grant-table's API which seems to be not natural forgntdev.c,
so it can leave ingntdev-dmabuf.cwhich has a use-case for that, while gntdev
remains the same.
Quoted 8 lines
Yet another reason why this code should be moved: importing and exporting functionalities logically belong together. The fat that they are implemented using different methods is not relevant IMO.
If you have code which is under ifdef
CONFIG_GNTDEV_DMABUFand you have file calledgntdev-dmabuf.cit sort of implies that this code should live in that file (unless that code is intertwined with other code, which is not the case here).
Ok, will move as discussed above
Quoted 2 lines
-boris
Thank you,
Oleksandr
Quoted 9 lines
Quoted 9 lines
Quoted 5 lines
Since this is under
CONFIG_XEN_GNTDEV_DMABUFthen why shouldn't it be ingntdev-dmabuf.c? In my view that's the file where all dma-related "stuff" lives.Agree, but IMO
grant_mapstuff for dma-buf importer is right in its place ingntdev.c
and all the rest of dma-buf specifics live ingntdev-dmabuf.cas they should
Quoted 7 lines
Quoted 7 lines
Review
Quoted 5 lines
(quoted diff) +0
-2-boris -borisThank you,
Oleksandr
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 6/9] xen/gntdev: Add initial support for dma-buf UAPI
In reply to Boris OstrovskyQuoted 7 lines · Boris Ostrovsky
Quoted 6 lines · Oleksandr Andrushchenko
Quoted 5 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev-dmabuf.h new file +3
-0+struct gntdev_dmabuf_export_args { + int dummy; +};
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Please define the full structure (at least what you have in the next patch) here.
Ok, will define what I have in the next patch, but won't initialize anything until the next patch. Will this work for you?
Sure, I just didn't see the need for the dummy argument that you remove later.
Ok
Quoted 15 lines
Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
drivers/xen/gntdev.c +0
-0...
Quoted 1 line
+#ifdef
CONFIG_XEN_GNTDEV_DMABUFQuoted 8 lines
Quoted 1 line
This code belongs in
gntdev-dmabuf.c.The reason I have this code here is that it is heavily tied to gntdev's internal functionality, e.g. map/unmap. I do not want to extend gntdev's API, so gntdev-dmabuf can access these. What is more dma-buf doesn't need to know about maps done by gntdev as there is no use of that information in gntdev-dmabuf. So, it seems more naturally to have dma-buf's related map/unmap code where it is: in gntdev.
Quoted 2 lines
Sorry, I don't follow. Why would this require extending the API? It's just moving routines to a different file that is linked to the same module.
I do understand your intention here and tried to avoid dma-buf related code in gntdev.c as much as possible. So, let me explain my decision in more detail.
There are 2 use-cases we have: dma-buf import and export.
While importing a dma-buf all the dma-buf related functionality can easily be kept inside gntdev-dmabuf.c w/o any issue as all we need from gntdev.c is dev, dma_buf_fd, count and domid for that.
But in case of dma-buf export we need to:
1. struct grant_map *map = gntdev_alloc_map(priv, count, dmabuf_flags);
2. gntdev_add_map(priv, map);
3. Set map->flags
4. ret = map_grant_pages(map);
5. And only now we are all set to export the new dma-buf from *map->pages*
So, until 5) we use private gtndev.c's API not exported to outside world:
a. struct grant_map
b. static struct grant_map *gntdev_alloc_map(struct gntdev_priv *priv, int count, int dma_flags)
c. static void gntdev_add_map(struct gntdev_priv *priv, struct grant_map *add) d. static int map_grant_pages(struct grant_map *map)
Thus, all the above cannot be accessed from gntdev-dmabuf.c
This is why I say that gntdev.c's API will need to be extended to provide the above a-d if we want all dma-buf export code to leave in gntdev-dmabuf.c. But that doesn't seem good to me and what is more a-d are really gntdev.c's functionality, not dma-buf's which only needs pages and doesn't really care from where those come.
That was the reason I partitioned export into 2 chunks: gntdev + gntdev-dmabuf.
You might also ask why importing side does Xen related things (granting references+) in gntdev-dmabuf, not gntdev so it is consistent with the dma-buf exporter? This is because importer uses grant-table's API which seems to be not natural for gntdev.c, so it can leave in gntdev-dmabuf.c which has a use-case for that, while gntdev remains the same.
Quoted 3 lines
Since this is under
CONFIG_XEN_GNTDEV_DMABUFthen why shouldn't it be ingntdev-dmabuf.c? In my view that's the file where all dma-related "stuff" lives.
Agree, but IMO grant_map stuff for dma-buf importer is right in its place in gntdev.c and all the rest of dma-buf specifics live in gntdev-dmabuf.c as they should
Review
Quoted 6 lines
(quoted diff) +0
-2-boris -boris
Thank you,
Oleksandr
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 6/9] xen/gntdev: Add initial support for dma-buf UAPI
In reply to Boris OstrovskyQuoted 12 lines · Boris Ostrovsky
Quoted 10 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Add UAPI and IOCTLs for dma-buf grant device driver extension:
the extension allows userspace processes and kernel modules to use Xen backed dma-buf implementation. With this extension grant references to the pages of an imported dma-buf can be exported for other domain use and grant references coming from a foreign domain can be converted into a local dma-buf for local export. Implement basic initialization and stubs for Xen DMA buffers' support.
Quoted 2 lines
It would be very helpful if people advocating for this interface reviewed it as well.
I would also love to see their comments here ;)
Quoted 21 lines
Quoted 21 lines
Signed-off-by Oleksandr Andrushchenko <[email protected]>--- drivers/xen/Kconfig | 10 +++ drivers/xen/Makefile | 1 + drivers/xen/gntdev-dmabuf.c | 75 +++++++++++++++++++ drivers/xen/gntdev-dmabuf.h | 41 +++++++++++ drivers/xen/gntdev.c | 142 ++++++++++++++++++++++++++++++++++++ include/uapi/xen/gntdev.h | 91 +++++++++++++++++++++++ 6 files changed, 360 insertions(+)create mode 100644
drivers/xen/gntdev-dmabuf.c
create mode 100644drivers/xen/gntdev-dmabuf.hdrivers/xen/Kconfig +0
-0@@ -152,6 +152,16 @@ config XEN_GNTDEV help Allows userspace processes to use grants.
Quoted 5 lines
drivers/xen/Kconfig config XEN_GNTDEV · line 157
Quoted 3 lines
drivers/xen/Kconfig +3
-0+config XEN_GNTDEV_DMABUF + bool "Add support for dma-buf grant access device driver extension" + depends on XEN_GNTDEV && XEN_GRANT_DMA_ALLOC && DMA_SHARED_BUFFERIs there a reason to have
XEN_GRANT_DMA_ALLOCwithoutXEN_GNTDEV_DMABUF?
One can use grant-table's DMA API without using dma-buf at all, e.g. dma-buf is sort of functionality on top of DMA allocated memory. We have a use-case for a driver domain (guest domain in fact) backed with IOMMU and still requiring allocations created as contiguous/DMA memory, so those buffers can be passed around to drivers expecting DMA-only buffers.
So, IMO this is a valid use-case "to have XEN_GRANT_DMA_ALLOC without XEN_GNTDEV_DMABUF"
Quoted 44 lines
Quoted 44 lines
drivers/xen/Kconfig +7
-0+ help + Allows userspace processes and kernel modules to use Xen backed + dma-buf implementation. With this extension grant references to + the pages of an imported dma-buf can be exported for other domain + use and grant references coming from a foreign domain can be + converted into a local dma-buf for local export. + config XEN_GRANT_DEV_ALLOC tristate "User-space grant reference allocator driver" depends on XENdrivers/xen/Makefile +1
-0@@ -41,5 +41,6 @@ obj-$(CONFIG_XEN_PVCALLS_BACKEND) += pvcalls-back.o obj-$(CONFIG_XEN_PVCALLS_FRONTEND) += pvcalls-front.o xen-evtchn-y := evtchn.o xen-gntdev-y := gntdev.o +xen-gntdev-$(CONFIG_XEN_GNTDEV_DMABUF) += gntdev-dmabuf.o xen-gntalloc-y := gntalloc.o xen-privcmd-y := privcmd.odrivers/xen/gntdev-dmabuf.c new file +16
-0@@ -0,0 +1,75 @@ +// SPDX-License-Identifier: GPL-2.0 + +/* +* Xen dma-buf functionality for gntdev. +* +* Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. +*/ + +#include <linux/slab.h> + +#include "gntdev-dmabuf.h" + +struct gntdev_dmabuf_priv { +int dummy; +}; +
Quoted 8 lines
drivers/xen/gntdev-dmabuf.c line 23
Quoted 7 lines
drivers/xen/gntdev-dmabuf.c new file +7
-0+/* ------------------------------------------------------------------ */ +/* DMA buffer export support. */ +/* ------------------------------------------------------------------ */ + +/* ------------------------------------------------------------------ */ +/* Implementation of wait for exported DMA buffer to be released. */ +/* ------------------------------------------------------------------ */ Why this comment style?
Just a copy-paste from gntdev, will change to usual /*..*/
Quoted 76 lines
Quoted 76 lines
drivers/xen/gntdev-dmabuf.c new file +52
-0+ +int gntdev_dmabuf_exp_wait_released (struct gntdev_dmabuf_priv *priv,int fd, +int wait_to_ms) +{ +return -EINVAL ; +} + +/* ------------------------------------------------------------------ */ +/* DMA buffer export support. */ +/* ------------------------------------------------------------------ */ + +int gntdev_dmabuf_exp_from_pages (struct gntdev_dmabuf_export_args *args) +{ +return -EINVAL ; +} + +/* ------------------------------------------------------------------ */ +/* DMA buffer import support. */ +/* ------------------------------------------------------------------ */ + +struct gntdev_dmabuf * +gntdev_dmabuf_imp_to_refs (struct gntdev_dmabuf_priv *priv,struct device *dev, +int fd,int count,int domid) +{ +return ERR_PTR (-ENOMEM ); +} + +u32 *gntdev_dmabuf_imp_get_refs (struct gntdev_dmabuf *gntdev_dmabuf) +{ +return NULL ; +} + +int gntdev_dmabuf_imp_release (struct gntdev_dmabuf_priv *priv,u32 fd) +{ +return -EINVAL ; +} + +struct gntdev_dmabuf_priv *gntdev_dmabuf_init (void ) +{ +struct gntdev_dmabuf_priv *priv; + + priv =kzalloc (sizeof (*priv),GFP_KERNEL ); +if (!priv) +return ERR_PTR (-ENOMEM ); + +return priv; +} + +void gntdev_dmabuf_fini (struct gntdev_dmabuf_priv *priv) +{ +kfree (priv); +}drivers/xen/gntdev-dmabuf.h new file +17
-0@@ -0,0 +1,41 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +/* +* Xen dma-buf functionality for gntdev. +* +* Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. +*/ + +#ifndef _GNTDEV_DMABUF_H +#define _GNTDEV_DMABUF_H + +#include <linux/kernel.h> +#include <linux/errno.h> +#include <linux/types.h> + +struct gntdev_dmabuf_priv ; +struct gntdev_dmabuf ;
Quoted 8 lines
drivers/xen/gntdev-dmabuf.h line 22
Quoted 5 lines
drivers/xen/gntdev-dmabuf.h new file +5
-0+struct device ; + +struct gntdev_dmabuf_export_args { +int dummy; +};Please define the full structure (at least what you have in the next patch) here.
Ok, will define what I have in the next patch, but won't initialize anything until the next patch. Will this work for you?
Quoted 27 lines
Quoted 24 lines
drivers/xen/gntdev-dmabuf.h new file +19
-0+ +struct gntdev_dmabuf_priv *gntdev_dmabuf_init (void ); + +void gntdev_dmabuf_fini (struct gntdev_dmabuf_priv *priv); + +int gntdev_dmabuf_exp_from_pages (struct gntdev_dmabuf_export_args *args); + +int gntdev_dmabuf_exp_wait_released (struct gntdev_dmabuf_priv *priv,int fd, +int wait_to_ms); + +struct gntdev_dmabuf * +gntdev_dmabuf_imp_to_refs (struct gntdev_dmabuf_priv *priv,struct device *dev, +int fd,int count,int domid); + +u32 *gntdev_dmabuf_imp_get_refs (struct gntdev_dmabuf *gntdev_dmabuf); + +int gntdev_dmabuf_imp_release (struct gntdev_dmabuf_priv *priv,u32 fd); + +#endif drivers/xen/gntdev.c +0
-0...
Quoted 1 line
Quoted 2 lines
Quoted 1 line
+#ifdef
CONFIG_XEN_GNTDEV_DMABUFThis code belongs in
gntdev-dmabuf.c.
The reason I have this code here is that it is heavily tied to gntdev's internal functionality, e.g. map/unmap. I do not want to extend gntdev's API, so gntdev-dmabuf can access these. What is more dma-buf doesn't need to know about maps done by gntdev as there is no use of that information in gntdev-dmabuf. So, it seems more naturally to have dma-buf's related map/unmap code where it is: in gntdev.
Quoted 11 lines
drivers/xen/gntdev.c static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) · line 1069
Quoted 9 lines
drivers/xen/gntdev.c +8
-0+/* ------------------------------------------------------------------ */ +/* DMA buffer export support. */ +/* ------------------------------------------------------------------ */ + +int gntdev_dmabuf_exp_from_refs (struct gntdev_priv *priv,int flags, +int count,u32 domid,u32 *refs,u32 *fd) +{ +/* XXX: this will need to work with gntdev's map, so leave it here. */ This doesn't help understanding what's going on (at least to me) and is removed in the next patch. So no need for this comment.
Will remove the comment
Quoted 6 lines
-boris
drivers/xen/gntdev.c static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) · line 1072
Quoted 3 lines
drivers/xen/gntdev.c +3
-0+ *fd =-1 ; +return -EINVAL ; +}
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 6/9] xen/gntdev: Add initial support for dma-buf UAPI
In reply to Oleksandr AndrushchenkoQuoted 10 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Add UAPI and IOCTLs for dma-buf grant device driver extension:
the extension allows userspace processes and kernel modules to use Xen backed dma-buf implementation. With this extension grant references to the pages of an imported dma-buf can be exported for other domain use and grant references coming from a foreign domain can be converted into a local dma-buf for local export. Implement basic initialization and stubs for Xen DMA buffers' support.
It would be very helpful if people advocating for this interface reviewed it as well.
Quoted 18 lines
Signed-off-by Oleksandr Andrushchenko <[email protected]>--- drivers/xen/Kconfig | 10 +++ drivers/xen/Makefile | 1 + drivers/xen/gntdev-dmabuf.c | 75 +++++++++++++++++++ drivers/xen/gntdev-dmabuf.h | 41 +++++++++++ drivers/xen/gntdev.c | 142 ++++++++++++++++++++++++++++++++++++ include/uapi/xen/gntdev.h | 91 +++++++++++++++++++++++ 6 files changed, 360 insertions(+) create mode 100644 drivers/xen/gntdev-dmabuf.c create mode 100644 drivers/xen/gntdev-dmabuf.hdrivers/xen/Kconfig +0
-0
drivers/xen/Kconfig config XEN_GNTDEV · line 157
Quoted 6 lines
drivers/xen/Kconfig +3
-0@@ -152,6 +152,16 @@ config XEN_GNTDEV help Allows userspace processes to use grants. +config XEN_GNTDEV_DMABUF + bool "Add support for dma-buf grant access device driver extension" + depends on XEN_GNTDEV && XEN_GRANT_DMA_ALLOC && DMA_SHARED_BUFFER
Is there a reason to have XEN_GRANT_DMA_ALLOC without XEN_GNTDEV_DMABUF?
Quoted 40 lines
drivers/xen/Kconfig +7
-0+ help + Allows userspace processes and kernel modules to use Xen backed + dma-buf implementation. With this extension grant references to + the pages of an imported dma-buf can be exported for other domain + use and grant references coming from a foreign domain can be + converted into a local dma-buf for local export. + config XEN_GRANT_DEV_ALLOC tristate "User-space grant reference allocator driver" depends on XENdrivers/xen/Makefile +1
-0@@ -41,5 +41,6 @@ obj-$(CONFIG_XEN_PVCALLS_BACKEND) += pvcalls-back.o obj-$(CONFIG_XEN_PVCALLS_FRONTEND) += pvcalls-front.o xen-evtchn-y := evtchn.o xen-gntdev-y := gntdev.o +xen-gntdev-$(CONFIG_XEN_GNTDEV_DMABUF) += gntdev-dmabuf.o xen-gntalloc-y := gntalloc.o xen-privcmd-y := privcmd.odrivers/xen/gntdev-dmabuf.c new file +13
-0@@ -0,0 +1,75 @@ +// SPDX-License-Identifier: GPL-2.0 + +/* +* Xen dma-buf functionality for gntdev. +* +* Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. +*/ + +#include <linux/slab.h> + +#include "gntdev-dmabuf.h" + +struct gntdev_dmabuf_priv {
drivers/xen/gntdev-dmabuf.c line 23
Quoted 10 lines
drivers/xen/gntdev-dmabuf.c new file +10
-0+int dummy; +}; + +/* ------------------------------------------------------------------ */ +/* DMA buffer export support. */ +/* ------------------------------------------------------------------ */ + +/* ------------------------------------------------------------------ */ +/* Implementation of wait for exported DMA buffer to be released. */ +/* ------------------------------------------------------------------ */
Why this comment style?
Quoted 70 lines
drivers/xen/gntdev-dmabuf.c new file +52
-0+ +int gntdev_dmabuf_exp_wait_released (struct gntdev_dmabuf_priv *priv,int fd, +int wait_to_ms) +{ +return -EINVAL ; +} + +/* ------------------------------------------------------------------ */ +/* DMA buffer export support. */ +/* ------------------------------------------------------------------ */ + +int gntdev_dmabuf_exp_from_pages (struct gntdev_dmabuf_export_args *args) +{ +return -EINVAL ; +} + +/* ------------------------------------------------------------------ */ +/* DMA buffer import support. */ +/* ------------------------------------------------------------------ */ + +struct gntdev_dmabuf * +gntdev_dmabuf_imp_to_refs (struct gntdev_dmabuf_priv *priv,struct device *dev, +int fd,int count,int domid) +{ +return ERR_PTR (-ENOMEM ); +} + +u32 *gntdev_dmabuf_imp_get_refs (struct gntdev_dmabuf *gntdev_dmabuf) +{ +return NULL ; +} + +int gntdev_dmabuf_imp_release (struct gntdev_dmabuf_priv *priv,u32 fd) +{ +return -EINVAL ; +} + +struct gntdev_dmabuf_priv *gntdev_dmabuf_init (void ) +{ +struct gntdev_dmabuf_priv *priv; + + priv =kzalloc (sizeof (*priv),GFP_KERNEL ); +if (!priv) +return ERR_PTR (-ENOMEM ); + +return priv; +} + +void gntdev_dmabuf_fini (struct gntdev_dmabuf_priv *priv) +{ +kfree (priv); +}drivers/xen/gntdev-dmabuf.h new file +12
-0@@ -0,0 +1,41 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +/* +* Xen dma-buf functionality for gntdev. +* +* Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. +*/ + +#ifndef _GNTDEV_DMABUF_H +#define _GNTDEV_DMABUF_H + +#include <linux/kernel.h>
drivers/xen/gntdev-dmabuf.h line 22
Quoted 10 lines
drivers/xen/gntdev-dmabuf.h new file +10
-0+#include <linux/errno.h> +#include <linux/types.h> + +struct gntdev_dmabuf_priv ; +struct gntdev_dmabuf ; +struct device ; + +struct gntdev_dmabuf_export_args { +int dummy; +};
Please define the full structure (at least what you have in the next patch) here.
Quoted 23 lines
drivers/xen/gntdev-dmabuf.h new file +19
-0+ +struct gntdev_dmabuf_priv *gntdev_dmabuf_init (void ); + +void gntdev_dmabuf_fini (struct gntdev_dmabuf_priv *priv); + +int gntdev_dmabuf_exp_from_pages (struct gntdev_dmabuf_export_args *args); + +int gntdev_dmabuf_exp_wait_released (struct gntdev_dmabuf_priv *priv,int fd, +int wait_to_ms); + +struct gntdev_dmabuf * +gntdev_dmabuf_imp_to_refs (struct gntdev_dmabuf_priv *priv,struct device *dev, +int fd,int count,int domid); + +u32 *gntdev_dmabuf_imp_get_refs (struct gntdev_dmabuf *gntdev_dmabuf); + +int gntdev_dmabuf_imp_release (struct gntdev_dmabuf_priv *priv,u32 fd); + +#endif drivers/xen/gntdev.c +0
-0
...
Quoted 2 lines
+#ifdef
CONFIG_XEN_GNTDEV_DMABUF
This code belongs in gntdev-dmabuf.c.
drivers/xen/gntdev.c static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) · line 1069
Quoted 8 lines
drivers/xen/gntdev.c +8
-0+/* ------------------------------------------------------------------ */ +/* DMA buffer export support. */ +/* ------------------------------------------------------------------ */ + +int gntdev_dmabuf_exp_from_refs (struct gntdev_priv *priv,int flags, +int count,u32 domid,u32 *refs,u32 *fd) +{ +/* XXX: this will need to work with gntdev's map, so leave it here. */
This doesn't help understanding what's going on (at least to me) and is removed in the next patch. So no need for this comment.
-boris
drivers/xen/gntdev.c static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) · line 1072
Quoted 3 lines
drivers/xen/gntdev.c +3
-0+ *fd =-1 ; +return -EINVAL ; +}
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v2 6/9 xen/gntdev: Add initial support for dma-buf UAPI
In reply to Oleksandr AndrushchenkoFrom: Oleksandr Andrushchenko <[email protected]>
Add UAPI and IOCTLs for dma-buf grant device driver extension:
the extension allows userspace processes and kernel modules to use Xen backed dma-buf implementation. With this extension grant references to the pages of an imported dma-buf can be exported for other domain use and grant references coming from a foreign domain can be converted into a local dma-buf for local export. Implement basic initialization and stubs for Xen DMA buffers' support.
--- drivers/xen/Kconfig | 10 +++ drivers/xen/Makefile | 1 + drivers/xen/gntdev-dmabuf.c | 75 +++++++++++++++++++ drivers/xen/gntdev-dmabuf.h | 41 +++++++++++ drivers/xen/gntdev.c | 142 ++++++++++++++++++++++++++++++++++++ include/uapi/xen/gntdev.h | 91 +++++++++++++++++++++++ 6 files changed, 360 insertions(+) create mode 100644 drivers/xen/gntdev-dmabuf.c create mode 100644 drivers/xen/gntdev-dmabuf.h
drivers/xen/Kconfig +10 -0
@@ -152,6 +152,16 @@ config XEN_GNTDEV help Allows userspace processes to use grants. +config XEN_GNTDEV_DMABUF + bool "Add support for dma-buf grant access device driver extension" + depends on XEN_GNTDEV && XEN_GRANT_DMA_ALLOC && DMA_SHARED_BUFFER + help + Allows userspace processes and kernel modules to use Xen backed + dma-buf implementation. With this extension grant references to + the pages of an imported dma-buf can be exported for other domain + use and grant references coming from a foreign domain can be + converted into a local dma-buf for local export. + config XEN_GRANT_DEV_ALLOC tristate "User-space grant reference allocator driver" depends on XEN
drivers/xen/Makefile +1 -0
@@ -41,5 +41,6 @@ obj-$(CONFIG_XEN_PVCALLS_BACKEND) += pvcalls-back.o obj-$(CONFIG_XEN_PVCALLS_FRONTEND) += pvcalls-front.o xen-evtchn-y := evtchn.o xen-gntdev-y := gntdev.o +xen-gntdev-$(CONFIG_XEN_GNTDEV_DMABUF) += gntdev-dmabuf.o xen-gntalloc-y := gntalloc.o xen-privcmd-y := privcmd.o
drivers/xen/gntdev-dmabuf.c new file +75 -0
75 lines not on this page · raw message
drivers/xen/gntdev-dmabuf.h new file +41 -0
41 lines not on this page · raw message
drivers/xen/gntdev.c +142 -0
186 lines not on this page · raw message
include/uapi/xen/gntdev.h +91 -0
101 lines not on this page · raw message
Signature · 7 lines
2.17.0 _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v2 7/9 xen/gntdev: Implement dma-buf export functionality
In reply to Oleksandr AndrushchenkoFrom: Oleksandr Andrushchenko <[email protected]>
1. Create a dma-buf from grant references provided by the foreign domain. By default dma-buf is backed by system memory pages, but by providing GNTDEV_DMA_FLAG_XXX flags it can also be created as a DMA write-combine/coherent buffer, e.g. allocated with corresponding dma_alloc_xxx API.
Export the resulting buffer as a new dma-buf.
2. Implement waiting for the dma-buf to be released: block until the dma-buf with the file descriptor provided is released.
If within the time-out provided the buffer is not released then -ETIMEDOUT error is returned. If the buffer with the file descriptor does not exist or has already been released, then -ENOENT is returned. For valid file descriptors this must not be treated as error.
--- drivers/xen/gntdev-dmabuf.c | 393 +++++++++++++++++++++++++++++++++++- drivers/xen/gntdev-dmabuf.h | 9 +- drivers/xen/gntdev.c | 90 ++++++++- 3 files changed, 486 insertions(+), 6 deletions(-)
drivers/xen/gntdev-dmabuf.c +390 -3
@@ -3,15 +3,58 @@/* * Xen dma-buf functionality for gntdev. * +* DMA buffer implementation is based on drivers/gpu/drm/drm_prime.c. +* * Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. */ +#include <linux/dma-buf.h> #include <linux/slab.h> #include "gntdev-dmabuf.h" +struct gntdev_dmabuf { +struct gntdev_dmabuf_priv *priv; +struct dma_buf *dmabuf; +struct list_head next; +int fd; + +union { +struct { +/* Exported buffers are reference counted. */ +struct kref refcount; + +struct gntdev_priv *priv; +struct grant_map *map; +void (*release)(struct gntdev_priv *priv, +struct grant_map *map); + } exp; + } u; + +/* Number of pages this buffer has. */ +int nr_pages; +/* Pages of this buffer. */ +struct page **pages; +}; + +struct gntdev_dmabuf_wait_obj { +struct list_head next; +struct gntdev_dmabuf *gntdev_dmabuf; +struct completion completion; +}; + +struct gntdev_dmabuf_attachment { +struct sg_table *sgt; +enum dma_data_direction dir; +}; +struct gntdev_dmabuf_priv { -int dummy; +/* List of exported DMA buffers. */ +struct list_head exp_list; +/* List of wait objects. */ +struct list_head exp_wait_list; +/* This is the lock which protects dma_buf_xxx lists. */ +struct mutex lock; };/* ------------------------------------------------------------------ */
@@ -22,19 +65,359 @@ struct gntdev_dmabuf_priv {/* Implementation of wait for exported DMA buffer to be released. */ /* ------------------------------------------------------------------ */ +static void dmabuf_exp_release (struct kref *kref); + +static struct gntdev_dmabuf_wait_obj * +dmabuf_exp_wait_obj_new (struct gntdev_dmabuf_priv *priv, +struct gntdev_dmabuf *gntdev_dmabuf) +{ +struct gntdev_dmabuf_wait_obj *obj; + + obj =kzalloc (sizeof (*obj),GFP_KERNEL ); +if (!obj) +return ERR_PTR (-ENOMEM ); + +init_completion (&obj->completion); + obj->gntdev_dmabuf = gntdev_dmabuf; + +mutex_lock (&priv->lock); +list_add (&obj->next, &priv->exp_wait_list); +/* Put our reference and wait for gntdev_dmabuf's release to fire. */ +kref_put (&gntdev_dmabuf->u.exp.refcount, dmabuf_exp_release); +mutex_unlock (&priv->lock); +return obj; +} + +static void dmabuf_exp_wait_obj_free (struct gntdev_dmabuf_priv *priv, +struct gntdev_dmabuf_wait_obj *obj) +{ +struct gntdev_dmabuf_wait_obj *cur_obj, *q; + +mutex_lock (&priv->lock); +list_for_each_entry_safe (cur_obj, q, &priv->exp_wait_list, next) +if (cur_obj == obj) { +list_del (&obj->next); +kfree (obj); +break ; + } +mutex_unlock (&priv->lock); +} + +static int dmabuf_exp_wait_obj_wait (struct gntdev_dmabuf_wait_obj *obj, +u32 wait_to_ms) +{ +if (wait_for_completion_timeout (&obj->completion, +msecs_to_jiffies (wait_to_ms)) <=0 ) +return -ETIMEDOUT ; + +return 0 ; +} + +static void dmabuf_exp_wait_obj_signal (struct gntdev_dmabuf_priv *priv, +struct gntdev_dmabuf *gntdev_dmabuf) +{ +struct gntdev_dmabuf_wait_obj *obj, *q; + +list_for_each_entry_safe (obj, q, &priv->exp_wait_list, next) +if (obj->gntdev_dmabuf == gntdev_dmabuf) { +pr_debug ("Found gntdev_dmabuf in the wait list, wake\n" ); +complete_all (&obj->completion); + } +} + +static struct gntdev_dmabuf * +dmabuf_exp_wait_obj_get_by_fd (struct gntdev_dmabuf_priv *priv,int fd) +{ +struct gntdev_dmabuf *q, *gntdev_dmabuf, *ret =ERR_PTR (-ENOENT ); + +mutex_lock (&priv->lock); +list_for_each_entry_safe (gntdev_dmabuf, q, &priv->exp_list, next) +if (gntdev_dmabuf->fd == fd) { +pr_debug ("Found gntdev_dmabuf in the wait list\n" ); +kref_get (&gntdev_dmabuf->u.exp.refcount); + ret = gntdev_dmabuf; +break ; + } +mutex_unlock (&priv->lock); +return ret; +} +int gntdev_dmabuf_exp_wait_released (struct gntdev_dmabuf_priv *priv,int fd,int wait_to_ms) { -return -EINVAL ; +struct gntdev_dmabuf *gntdev_dmabuf; +struct gntdev_dmabuf_wait_obj *obj; +int ret; + +pr_debug ("Will wait for dma-buf with fd %d\n" , fd); +/* +* Try to find the DMA buffer: if not found means that +* either the buffer has already been released or file descriptor +* provided is wrong. +*/ + gntdev_dmabuf =dmabuf_exp_wait_obj_get_by_fd (priv, fd); +if (IS_ERR (gntdev_dmabuf)) +return PTR_ERR (gntdev_dmabuf); + +/* +* gntdev_dmabuf still exists and is reference count locked by us now, +* so prepare to wait: allocate wait object and add it to the wait list, +* so we can find it on release. +*/ + obj =dmabuf_exp_wait_obj_new (priv, gntdev_dmabuf); +if (IS_ERR (obj)) { +pr_err ("Failed to setup wait object, ret %ld\n" ,PTR_ERR (obj)); +return PTR_ERR (obj); +} + + ret =dmabuf_exp_wait_obj_wait (obj, wait_to_ms); +dmabuf_exp_wait_obj_free (priv, obj); +return ret; }/* ------------------------------------------------------------------ */ /* DMA buffer export support. */ /* ------------------------------------------------------------------ */ +static struct sg_table * +dmabuf_pages_to_sgt (struct page **pages,unsigned int nr_pages) +{ +struct sg_table *sgt; +int ret; + + sgt =kmalloc (sizeof (*sgt),GFP_KERNEL ); +if (!sgt) { + ret = -ENOMEM ; + goto out; + } + + ret =sg_alloc_table_from_pages (sgt, pages, nr_pages,0 , + nr_pages <<PAGE_SHIFT , +GFP_KERNEL ); +if (ret) + goto out; + +return sgt; + +out: +kfree (sgt); +return ERR_PTR (ret); +} + +static int dmabuf_exp_ops_attach (struct dma_buf *dma_buf, +struct device *target_dev, +struct dma_buf_attachment *attach) +{ +struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach; + + gntdev_dmabuf_attach =kzalloc (sizeof (*gntdev_dmabuf_attach), +GFP_KERNEL ); +if (!gntdev_dmabuf_attach) +return -ENOMEM ; + + gntdev_dmabuf_attach->dir =DMA_NONE ; + attach->priv = gntdev_dmabuf_attach; +/* Might need to pin the pages of the buffer now. */ +return 0 ; +} + +static void dmabuf_exp_ops_detach (struct dma_buf *dma_buf, +struct dma_buf_attachment *attach) +{ +struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach = attach->priv; + +if (gntdev_dmabuf_attach) { +struct sg_table *sgt = gntdev_dmabuf_attach->sgt; + +if (sgt) { +if (gntdev_dmabuf_attach->dir !=DMA_NONE ) +dma_unmap_sg_attrs (attach->dev, sgt->sgl, + sgt->nents, + gntdev_dmabuf_attach->dir, +DMA_ATTR_SKIP_CPU_SYNC ); +sg_free_table (sgt); + } + +kfree (sgt); +kfree (gntdev_dmabuf_attach); + attach->priv =NULL ; + } +/* Might need to unpin the pages of the buffer now. */ +} + +static struct sg_table * +dmabuf_exp_ops_map_dma_buf (struct dma_buf_attachment *attach, +enum dma_data_direction dir) +{ +struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach = attach->priv; +struct gntdev_dmabuf *gntdev_dmabuf = attach->dmabuf->priv; +struct sg_table *sgt; + +pr_debug ("Mapping %d pages for dev %p\n" , gntdev_dmabuf->nr_pages, + attach->dev); + +if (WARN_ON (dir ==DMA_NONE || !gntdev_dmabuf_attach)) +return ERR_PTR (-EINVAL ); + +/* Return the cached mapping when possible. */ +if (gntdev_dmabuf_attach->dir == dir) +return gntdev_dmabuf_attach->sgt; + +/* +* Two mappings with different directions for the same attachment are +* not allowed. +*/ +if (WARN_ON (gntdev_dmabuf_attach->dir !=DMA_NONE )) +return ERR_PTR (-EBUSY ); + + sgt =dmabuf_pages_to_sgt (gntdev_dmabuf->pages, + gntdev_dmabuf->nr_pages); +if (!IS_ERR (sgt)) { +if (!dma_map_sg_attrs (attach->dev, sgt->sgl, sgt->nents, dir, +DMA_ATTR_SKIP_CPU_SYNC )) { +sg_free_table (sgt); +kfree (sgt); + sgt =ERR_PTR (-ENOMEM ); + }else { + gntdev_dmabuf_attach->sgt = sgt; + gntdev_dmabuf_attach->dir = dir; + } + } +if (IS_ERR (sgt)) +pr_err ("Failed to map sg table for dev %p\n" , attach->dev); +return sgt; +} + +static void dmabuf_exp_ops_unmap_dma_buf (struct dma_buf_attachment *attach, +struct sg_table *sgt, +enum dma_data_direction dir) +{ +/* Not implemented. The unmap is done at dmabuf_exp_ops_detach(). */ +} + +static void dmabuf_exp_release (struct kref *kref) +{ +struct gntdev_dmabuf *gntdev_dmabuf = + container_of(kref, struct gntdev_dmabuf, u.exp.refcount); + +dmabuf_exp_wait_obj_signal (gntdev_dmabuf->priv, gntdev_dmabuf); +list_del (&gntdev_dmabuf->next); +kfree (gntdev_dmabuf); +} + +static void dmabuf_exp_ops_release (struct dma_buf *dma_buf) +{ +struct gntdev_dmabuf *gntdev_dmabuf = dma_buf->priv; +struct gntdev_dmabuf_priv *priv = gntdev_dmabuf->priv; + + gntdev_dmabuf->u.exp.release (gntdev_dmabuf->u.exp.priv, + gntdev_dmabuf->u.exp.map); +mutex_lock (&priv->lock); +kref_put (&gntdev_dmabuf->u.exp.refcount, dmabuf_exp_release); +mutex_unlock (&priv->lock); +} + +static void *dmabuf_exp_ops_kmap_atomic (struct dma_buf *dma_buf, +unsigned long page_num) +{ +/* Not implemented. */ +return NULL ; +} + +static void dmabuf_exp_ops_kunmap_atomic (struct dma_buf *dma_buf, +unsigned long page_num,void *addr) +{ +/* Not implemented. */ +} + +static void *dmabuf_exp_ops_kmap (struct dma_buf *dma_buf, +unsigned long page_num) +{ +/* Not implemented. */ +return NULL ; +} + +static void dmabuf_exp_ops_kunmap (struct dma_buf *dma_buf, +unsigned long page_num,void *addr) +{ +/* Not implemented. */ +} + +static int dmabuf_exp_ops_mmap (struct dma_buf *dma_buf, +struct vm_area_struct *vma) +{ +/* Not implemented. */ +return 0 ; +} + +static const struct dma_buf_ops dmabuf_exp_ops = { + .attach = dmabuf_exp_ops_attach, + .detach = dmabuf_exp_ops_detach, + .map_dma_buf = dmabuf_exp_ops_map_dma_buf, + .unmap_dma_buf = dmabuf_exp_ops_unmap_dma_buf, + .release = dmabuf_exp_ops_release, + .map = dmabuf_exp_ops_kmap, + .map_atomic = dmabuf_exp_ops_kmap_atomic, + .unmap = dmabuf_exp_ops_kunmap, + .unmap_atomic = dmabuf_exp_ops_kunmap_atomic, + .mmap = dmabuf_exp_ops_mmap, +}; +int gntdev_dmabuf_exp_from_pages (struct gntdev_dmabuf_export_args *args) { -return -EINVAL ; +DEFINE_DMA_BUF_EXPORT_INFO (exp_info); +struct gntdev_dmabuf *gntdev_dmabuf; +int ret =0 ; + + gntdev_dmabuf =kzalloc (sizeof (*gntdev_dmabuf),GFP_KERNEL ); +if (!gntdev_dmabuf) +return -ENOMEM ; + +kref_init (&gntdev_dmabuf->u.exp.refcount); + + gntdev_dmabuf->priv = args->dmabuf_priv; + gntdev_dmabuf->nr_pages = args->count; + gntdev_dmabuf->pages = args->pages; + gntdev_dmabuf->u.exp.priv = args->priv; + gntdev_dmabuf->u.exp.map = args->map; + gntdev_dmabuf->u.exp.release = args->release; + + exp_info.exp_name =KBUILD_MODNAME ; +if (args->dev->driver && args->dev->driver->owner) + exp_info.owner = args->dev->driver->owner; +else + exp_info.owner =THIS_MODULE ; + exp_info.ops = &dmabuf_exp_ops; + exp_info.size = args->count <<PAGE_SHIFT ; + exp_info.flags =O_RDWR ; + exp_info.priv = gntdev_dmabuf; + + gntdev_dmabuf->dmabuf =dma_buf_export (&exp_info); +if (IS_ERR (gntdev_dmabuf->dmabuf)) { + ret =PTR_ERR (gntdev_dmabuf->dmabuf); + gntdev_dmabuf->dmabuf =NULL ; + goto fail; + } + + ret =dma_buf_fd (gntdev_dmabuf->dmabuf,O_CLOEXEC ); +if (ret <0 ) + goto fail; + + gntdev_dmabuf->fd = ret; + args->fd = ret; + +pr_debug ("Exporting DMA buffer with fd %d\n" , ret); + +mutex_lock (&args->dmabuf_priv->lock); +list_add (&gntdev_dmabuf->next, &args->dmabuf_priv->exp_list); +mutex_unlock (&args->dmabuf_priv->lock); +return 0 ; + +fail: +if (gntdev_dmabuf->dmabuf) +dma_buf_put (gntdev_dmabuf->dmabuf); +kfree (gntdev_dmabuf); +return ret; }/* ------------------------------------------------------------------ */
@@ -66,6 +449,10 @@ struct gntdev_dmabuf_priv *gntdev_dmabuf_init(void)if (!priv)return ERR_PTR (-ENOMEM ); +mutex_init (&priv->lock); +INIT_LIST_HEAD (&priv->exp_list); +INIT_LIST_HEAD (&priv->exp_wait_list); +return priv; }
drivers/xen/gntdev-dmabuf.h +8 -1
@@ -18,7 +18,14 @@ struct gntdev_dmabuf;struct device ;struct gntdev_dmabuf_export_args { -int dummy; +struct gntdev_priv *priv; +struct grant_map *map; +void (*release)(struct gntdev_priv *priv,struct grant_map *map); +struct gntdev_dmabuf_priv *dmabuf_priv; +struct device *dev; +int count; +struct page **pages; +u32 fd; };struct gntdev_dmabuf_priv *gntdev_dmabuf_init (void );
drivers/xen/gntdev.c +88 -2
106 lines not on this page · raw message
Signature · 6 lines
2.17.0 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 7/9] xen/gntdev: Implement dma-buf export functionality
Quoted 139 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
1. Create a dma-buf from grant references provided by the foreign domain. By default dma-buf is backed by system memory pages, but by providing
GNTDEV_DMA_FLAG_XXXflags it can also be created as a DMA write-combine/coherent buffer, e.g. allocated with correspondingdma_alloc_xxxAPI.
Export the resulting buffer as a new dma-buf.2. Implement waiting for the dma-buf to be released: block until the dma-buf with the file descriptor provided is released.
If within the time-out provided the buffer is not released then-ETIMEDOUTerror is returned. If the buffer with the file descriptor does not exist or has already been released, then-ENOENTis returned. For valid file descriptors this must not be treated as error.Signed-off-by Oleksandr Andrushchenko <[email protected]>--- drivers/xen/gntdev-dmabuf.c | 393 +++++++++++++++++++++++++++++++++++- drivers/xen/gntdev-dmabuf.h | 9 +- drivers/xen/gntdev.c | 90 ++++++++- 3 files changed, 486 insertions(+), 6 deletions(-)drivers/xen/gntdev-dmabuf.c +91
-1@@ -3,15 +3,58 @@/* * Xen dma-buf functionality for gntdev. * +* DMA buffer implementation is based on drivers/gpu/drm/drm_prime.c. +* * Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. */ +#include <linux/dma-buf.h> #include <linux/slab.h> #include "gntdev-dmabuf.h" +struct gntdev_dmabuf { +struct gntdev_dmabuf_priv *priv; +struct dma_buf *dmabuf; +struct list_head next; +int fd; + +union { +struct { +/* Exported buffers are reference counted. */ +struct kref refcount; + +struct gntdev_priv *priv; +struct grant_map *map; +void (*release)(struct gntdev_priv *priv, +struct grant_map *map); + } exp; + } u; + +/* Number of pages this buffer has. */ +int nr_pages; +/* Pages of this buffer. */ +struct page **pages; +}; + +struct gntdev_dmabuf_wait_obj { +struct list_head next; +struct gntdev_dmabuf *gntdev_dmabuf; +struct completion completion; +}; + +struct gntdev_dmabuf_attachment { +struct sg_table *sgt; +enum dma_data_direction dir; +}; +struct gntdev_dmabuf_priv { -int dummy; +/* List of exported DMA buffers. */ +struct list_head exp_list; +/* List of wait objects. */ +struct list_head exp_wait_list; +/* This is the lock which protects dma_buf_xxx lists. */ +struct mutex lock; };/* ------------------------------------------------------------------ */ @@ -22,19 +65,359 @@ struct gntdev_dmabuf_priv {/* Implementation of wait for exported DMA buffer to be released. */ /* ------------------------------------------------------------------ */ +static void dmabuf_exp_release (struct kref *kref); + +static struct gntdev_dmabuf_wait_obj * +dmabuf_exp_wait_obj_new (struct gntdev_dmabuf_priv *priv, +struct gntdev_dmabuf *gntdev_dmabuf) +{ +struct gntdev_dmabuf_wait_obj *obj; + + obj =kzalloc (sizeof (*obj),GFP_KERNEL ); +if (!obj) +return ERR_PTR (-ENOMEM ); + +init_completion (&obj->completion); + obj->gntdev_dmabuf = gntdev_dmabuf; + +mutex_lock (&priv->lock); +list_add (&obj->next, &priv->exp_wait_list); +/* Put our reference and wait for gntdev_dmabuf's release to fire. */ +kref_put (&gntdev_dmabuf->u.exp.refcount, dmabuf_exp_release); +mutex_unlock (&priv->lock); +return obj; +} + +static void dmabuf_exp_wait_obj_free (struct gntdev_dmabuf_priv *priv, +struct gntdev_dmabuf_wait_obj *obj) +{ +struct gntdev_dmabuf_wait_obj *cur_obj, *q; + +mutex_lock (&priv->lock); +list_for_each_entry_safe (cur_obj, q, &priv->exp_wait_list, next) +if (cur_obj == obj) { +list_del (&obj->next); +kfree (obj); +break ; + } +mutex_unlock (&priv->lock); +} + +static int dmabuf_exp_wait_obj_wait (struct gntdev_dmabuf_wait_obj *obj, +u32 wait_to_ms) +{ +if (wait_for_completion_timeout (&obj->completion, +msecs_to_jiffies (wait_to_ms)) <=0 ) +return -ETIMEDOUT ; + +return 0 ; +}
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 124
Quoted 10 lines
drivers/xen/gntdev-dmabuf.c +10
-0+ +static void dmabuf_exp_wait_obj_signal (struct gntdev_dmabuf_priv *priv, +struct gntdev_dmabuf *gntdev_dmabuf) +{ +struct gntdev_dmabuf_wait_obj *obj, *q; + +list_for_each_entry_safe (obj, q, &priv->exp_wait_list, next) +if (obj->gntdev_dmabuf == gntdev_dmabuf) { +pr_debug ("Found gntdev_dmabuf in the wait list, wake\n" ); +complete_all (&obj->completion);
break ?
Quoted 36 lines
drivers/xen/gntdev-dmabuf.c +32
-1+ } +} + +static struct gntdev_dmabuf * +dmabuf_exp_wait_obj_get_by_fd (struct gntdev_dmabuf_priv *priv,int fd) +{ +struct gntdev_dmabuf *q, *gntdev_dmabuf, *ret =ERR_PTR (-ENOENT ); + +mutex_lock (&priv->lock); +list_for_each_entry_safe (gntdev_dmabuf, q, &priv->exp_list, next) +if (gntdev_dmabuf->fd == fd) { +pr_debug ("Found gntdev_dmabuf in the wait list\n" ); +kref_get (&gntdev_dmabuf->u.exp.refcount); + ret = gntdev_dmabuf; +break ; + } +mutex_unlock (&priv->lock); +return ret; +} +int gntdev_dmabuf_exp_wait_released (struct gntdev_dmabuf_priv *priv,int fd,int wait_to_ms) { -return -EINVAL ; +struct gntdev_dmabuf *gntdev_dmabuf; +struct gntdev_dmabuf_wait_obj *obj; +int ret; + +pr_debug ("Will wait for dma-buf with fd %d\n" , fd); +/* +* Try to find the DMA buffer: if not found means that +* either the buffer has already been released or file descriptor +* provided is wrong. +*/ + gntdev_dmabuf =dmabuf_exp_wait_obj_get_by_fd (priv, fd); +if (IS_ERR (gntdev_dmabuf))
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 169
Quoted 10 lines
drivers/xen/gntdev-dmabuf.c +10
-0+return PTR_ERR (gntdev_dmabuf); + +/* +* gntdev_dmabuf still exists and is reference count locked by us now, +* so prepare to wait: allocate wait object and add it to the wait list, +* so we can find it on release. +*/ + obj =dmabuf_exp_wait_obj_new (priv, gntdev_dmabuf); +if (IS_ERR (obj)) { +pr_err ("Failed to setup wait object, ret %ld\n" ,PTR_ERR (obj));
No need for pr_err. We are out of memory.
Quoted 41 lines
drivers/xen/gntdev-dmabuf.c +35
-0+return PTR_ERR (obj); +} + + ret =dmabuf_exp_wait_obj_wait (obj, wait_to_ms); +dmabuf_exp_wait_obj_free (priv, obj); +return ret; }/* ------------------------------------------------------------------ */ /* DMA buffer export support. */ /* ------------------------------------------------------------------ */ +static struct sg_table * +dmabuf_pages_to_sgt (struct page **pages,unsigned int nr_pages) +{ +struct sg_table *sgt; +int ret; + + sgt =kmalloc (sizeof (*sgt),GFP_KERNEL ); +if (!sgt) { + ret = -ENOMEM ; + goto out; + } + + ret =sg_alloc_table_from_pages (sgt, pages, nr_pages,0 , + nr_pages <<PAGE_SHIFT , +GFP_KERNEL ); +if (ret) + goto out; + +return sgt; + +out: +kfree (sgt); +return ERR_PTR (ret); +} + +static int dmabuf_exp_ops_attach (struct dma_buf *dma_buf, +struct device *target_dev, +struct dma_buf_attachment *attach) +{
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 220
Quoted 10 lines
drivers/xen/gntdev-dmabuf.c +10
-0+struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach; + + gntdev_dmabuf_attach =kzalloc (sizeof (*gntdev_dmabuf_attach), +GFP_KERNEL ); +if (!gntdev_dmabuf_attach) +return -ENOMEM ; + + gntdev_dmabuf_attach->dir =DMA_NONE ; + attach->priv = gntdev_dmabuf_attach; +/* Might need to pin the pages of the buffer now. */
Who is supposed to pin the pages? The caller?
Quoted 15 lines
drivers/xen/gntdev-dmabuf.c +15
-0+return 0 ; +} + +static void dmabuf_exp_ops_detach (struct dma_buf *dma_buf, +struct dma_buf_attachment *attach) +{ +struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach = attach->priv; + +if (gntdev_dmabuf_attach) { +struct sg_table *sgt = gntdev_dmabuf_attach->sgt; + +if (sgt) { +if (gntdev_dmabuf_attach->dir !=DMA_NONE ) + dma_unmap_sg_attrs(attach->dev, sgt->sgl, + sgt->nents,
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 245
Quoted 10 lines
drivers/xen/gntdev-dmabuf.c +10
-0+ gntdev_dmabuf_attach->dir, + DMA_ATTR_SKIP_CPU_SYNC); +sg_free_table (sgt); + } + +kfree (sgt); +kfree (gntdev_dmabuf_attach); + attach->priv =NULL ; + } +/* Might need to unpin the pages of the buffer now. */
Same question.
Quoted 4 lines
drivers/xen/gntdev-dmabuf.c +4
-0+} + +static struct sg_table * +dmabuf_exp_ops_map_dma_buf(struct dma_buf_attachment *attach,
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 259
Quoted 10 lines
drivers/xen/gntdev-dmabuf.c +10
-0+ enum dma_data_direction dir) +{ +struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach = attach->priv; +struct gntdev_dmabuf *gntdev_dmabuf = attach->dmabuf->priv; +struct sg_table *sgt; + +pr_debug ("Mapping %d pages for dev %p\n" , gntdev_dmabuf->nr_pages, + attach->dev); + +if (WARN_ON (dir ==DMA_NONE || !gntdev_dmabuf_attach))
WARN_ON_ONCE. Here and elsewhere.
Quoted 252 lines
drivers/xen/gntdev-dmabuf.c +163
-1+return ERR_PTR (-EINVAL ); + +/* Return the cached mapping when possible. */ +if (gntdev_dmabuf_attach->dir == dir) +return gntdev_dmabuf_attach->sgt; + +/* +* Two mappings with different directions for the same attachment are +* not allowed. +*/ +if (WARN_ON (gntdev_dmabuf_attach->dir !=DMA_NONE )) +return ERR_PTR (-EBUSY ); + + sgt =dmabuf_pages_to_sgt (gntdev_dmabuf->pages, + gntdev_dmabuf->nr_pages); +if (!IS_ERR (sgt)) { +if (!dma_map_sg_attrs (attach->dev, sgt->sgl, sgt->nents, dir, +DMA_ATTR_SKIP_CPU_SYNC )) { +sg_free_table (sgt); +kfree (sgt); + sgt =ERR_PTR (-ENOMEM ); + }else { + gntdev_dmabuf_attach->sgt = sgt; + gntdev_dmabuf_attach->dir = dir; + } + } +if (IS_ERR (sgt)) +pr_err ("Failed to map sg table for dev %p\n" , attach->dev); +return sgt; +} + +static void dmabuf_exp_ops_unmap_dma_buf (struct dma_buf_attachment *attach, +struct sg_table *sgt, +enum dma_data_direction dir) +{ +/* Not implemented. The unmap is done at dmabuf_exp_ops_detach(). */ +} + +static void dmabuf_exp_release (struct kref *kref) +{ +struct gntdev_dmabuf *gntdev_dmabuf = + container_of(kref, struct gntdev_dmabuf, u.exp.refcount); + +dmabuf_exp_wait_obj_signal (gntdev_dmabuf->priv, gntdev_dmabuf); +list_del (&gntdev_dmabuf->next); +kfree (gntdev_dmabuf); +} + +static void dmabuf_exp_ops_release (struct dma_buf *dma_buf) +{ +struct gntdev_dmabuf *gntdev_dmabuf = dma_buf->priv; +struct gntdev_dmabuf_priv *priv = gntdev_dmabuf->priv; + + gntdev_dmabuf->u.exp.release (gntdev_dmabuf->u.exp.priv, + gntdev_dmabuf->u.exp.map); +mutex_lock (&priv->lock); +kref_put (&gntdev_dmabuf->u.exp.refcount, dmabuf_exp_release); +mutex_unlock (&priv->lock); +} + +static void *dmabuf_exp_ops_kmap_atomic (struct dma_buf *dma_buf, +unsigned long page_num) +{ +/* Not implemented. */ +return NULL ; +} + +static void dmabuf_exp_ops_kunmap_atomic (struct dma_buf *dma_buf, +unsigned long page_num,void *addr) +{ +/* Not implemented. */ +} + +static void *dmabuf_exp_ops_kmap (struct dma_buf *dma_buf, +unsigned long page_num) +{ +/* Not implemented. */ +return NULL ; +} + +static void dmabuf_exp_ops_kunmap (struct dma_buf *dma_buf, +unsigned long page_num,void *addr) +{ +/* Not implemented. */ +} + +static int dmabuf_exp_ops_mmap (struct dma_buf *dma_buf, +struct vm_area_struct *vma) +{ +/* Not implemented. */ +return 0 ; +} + +static const struct dma_buf_ops dmabuf_exp_ops = { + .attach = dmabuf_exp_ops_attach, + .detach = dmabuf_exp_ops_detach, + .map_dma_buf = dmabuf_exp_ops_map_dma_buf, + .unmap_dma_buf = dmabuf_exp_ops_unmap_dma_buf, + .release = dmabuf_exp_ops_release, + .map = dmabuf_exp_ops_kmap, + .map_atomic = dmabuf_exp_ops_kmap_atomic, + .unmap = dmabuf_exp_ops_kunmap, + .unmap_atomic = dmabuf_exp_ops_kunmap_atomic, + .mmap = dmabuf_exp_ops_mmap, +}; +int gntdev_dmabuf_exp_from_pages (struct gntdev_dmabuf_export_args *args) { -return -EINVAL ; +DEFINE_DMA_BUF_EXPORT_INFO (exp_info); +struct gntdev_dmabuf *gntdev_dmabuf; +int ret =0 ; + + gntdev_dmabuf =kzalloc (sizeof (*gntdev_dmabuf),GFP_KERNEL ); +if (!gntdev_dmabuf) +return -ENOMEM ; + +kref_init (&gntdev_dmabuf->u.exp.refcount); + + gntdev_dmabuf->priv = args->dmabuf_priv; + gntdev_dmabuf->nr_pages = args->count; + gntdev_dmabuf->pages = args->pages; + gntdev_dmabuf->u.exp.priv = args->priv; + gntdev_dmabuf->u.exp.map = args->map; + gntdev_dmabuf->u.exp.release = args->release; + + exp_info.exp_name =KBUILD_MODNAME ; +if (args->dev->driver && args->dev->driver->owner) + exp_info.owner = args->dev->driver->owner; +else + exp_info.owner =THIS_MODULE ; + exp_info.ops = &dmabuf_exp_ops; + exp_info.size = args->count <<PAGE_SHIFT ; + exp_info.flags =O_RDWR ; + exp_info.priv = gntdev_dmabuf; + + gntdev_dmabuf->dmabuf =dma_buf_export (&exp_info); +if (IS_ERR (gntdev_dmabuf->dmabuf)) { + ret =PTR_ERR (gntdev_dmabuf->dmabuf); + gntdev_dmabuf->dmabuf =NULL ; + goto fail; + } + + ret =dma_buf_fd (gntdev_dmabuf->dmabuf,O_CLOEXEC ); +if (ret <0 ) + goto fail; + + gntdev_dmabuf->fd = ret; + args->fd = ret; + +pr_debug ("Exporting DMA buffer with fd %d\n" , ret); + +mutex_lock (&args->dmabuf_priv->lock); +list_add (&gntdev_dmabuf->next, &args->dmabuf_priv->exp_list); +mutex_unlock (&args->dmabuf_priv->lock); +return 0 ; + +fail: +if (gntdev_dmabuf->dmabuf) +dma_buf_put (gntdev_dmabuf->dmabuf); +kfree (gntdev_dmabuf); +return ret; }/* ------------------------------------------------------------------ */ @@ -66,6 +449,10 @@ struct gntdev_dmabuf_priv *gntdev_dmabuf_init(void)if (!priv)return ERR_PTR (-ENOMEM ); +mutex_init (&priv->lock); +INIT_LIST_HEAD (&priv->exp_list); +INIT_LIST_HEAD (&priv->exp_wait_list); +return priv; }drivers/xen/gntdev-dmabuf.h +8
-1@@ -18,7 +18,14 @@ struct gntdev_dmabuf;struct device ;struct gntdev_dmabuf_export_args { -int dummy; +struct gntdev_priv *priv; +struct grant_map *map; +void (*release)(struct gntdev_priv *priv,struct grant_map *map); +struct gntdev_dmabuf_priv *dmabuf_priv; +struct device *dev; +int count; +struct page **pages; +u32 fd; };struct gntdev_dmabuf_priv *gntdev_dmabuf_init (void );drivers/xen/gntdev.c +37
-1@@ -319,6 +319,16 @@ static void gntdev_put_map(struct gntdev_priv *priv, struct grant_map *map)gntdev_free_map (map); } +#ifdef CONFIG_XEN_GNTDEV_DMABUF +static void gntdev_remove_map (struct gntdev_priv *priv,struct grant_map *map) +{ +mutex_lock (&priv->lock); +list_del (&map->next); +gntdev_put_map (NULL /* already removed */ , map); +mutex_unlock (&priv->lock); +} +#endif +/* ------------------------------------------------------------------ */ static int find_grant_ptes(pte_t *pte, pgtable_t token,@@ -1063,12 +1073,88 @@ static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u)/* DMA buffer export support. */ /* ------------------------------------------------------------------ */ +static struct grant_map * +dmabuf_exp_alloc_backing_storage (struct gntdev_priv *priv,int dmabuf_flags, +int count) +{ +struct grant_map *map; + +if (unlikely (count <=0 )) +return ERR_PTR (-EINVAL ); + +if ((dmabuf_flags &GNTDEV_DMA_FLAG_WC ) && + (dmabuf_flags &GNTDEV_DMA_FLAG_COHERENT )) { +pr_err ("Wrong dma-buf flags: either WC or coherent, not both\n" ); +return ERR_PTR (-EINVAL ); + } + + map =gntdev_alloc_map (priv, count, dmabuf_flags); +if (!map) +return ERR_PTR (-ENOMEM ); + +if (unlikely (atomic_add_return (count, &pages_mapped) > limit)) { +pr_err ("can't map: over limit\n" ); +gntdev_put_map (NULL , map); +return ERR_PTR (-ENOMEM ); + } +return map; +} +int gntdev_dmabuf_exp_from_refs (struct gntdev_priv *priv,int flags,int count,u32 domid,u32 *refs,u32 *fd) { -/* XXX: this will need to work with gntdev's map, so leave it here. */
drivers/xen/gntdev.c static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) · line 1114
Quoted 10 lines
drivers/xen/gntdev.c +8
-1+struct grant_map *map; +struct gntdev_dmabuf_export_args args; +int i, ret; + *fd =-1 ; -return -EINVAL ; + +if (use_ptemod) { +pr_err ("Cannot provide dma-buf: use_ptemode %d\n" , + use_ptemod);
No pr_err here please. This can potentially become a DoS vector as it comes directly from ioctl.
I would, in fact, revisit other uses of pr_err in this file.
drivers/xen/gntdev.c static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) · line 1118
Quoted 4 lines
drivers/xen/gntdev.c +4
-0+return -EINVAL ; + } + + map =dmabuf_exp_alloc_backing_storage (priv, flags, count);
@count comes from userspace. dmabuf_exp_alloc_backing_storage only checks for it to be >0. Should it be checked for some sane max value?
-boris
Quoted 32 lines
drivers/xen/gntdev.c +32
-0+if (IS_ERR (map)) +return PTR_ERR (map); + +for (i =0 ; i < count; i++) { + map->grants[i].domid = domid; + map->grants[i].ref = refs[i]; + } + +mutex_lock (&priv->lock); +gntdev_add_map (priv, map); +mutex_unlock (&priv->lock); + + map->flags |= GNTMAP_host_map; +#if defined(CONFIG_X86 ) + map->flags |= GNTMAP_device_map; +#endif + + ret =map_grant_pages (map); +if (ret <0 ) + goto out; + + args.priv = priv; + args.map = map; + args.release = gntdev_remove_map; + args.dev = priv->dma_dev; + args.dmabuf_priv = priv->dmabuf_priv; + args.count = map->count; + args.pages = map->pages; + + ret =gntdev_dmabuf_exp_from_pages (&args); +if (ret <0 ) + goto out;
drivers/xen/gntdev.c static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) · line 1160
Quoted 10 lines
drivers/xen/gntdev.c +7
-0+ + *fd = args.fd; +return 0 ; + +out: +gntdev_remove_map (priv, map); +return ret; }/* ------------------------------------------------------------------ */
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 7/9] xen/gntdev: Implement dma-buf export functionality
In reply to Oleksandr AndrushchenkoQuoted 139 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
1. Create a dma-buf from grant references provided by the foreign domain. By default dma-buf is backed by system memory pages, but by providing
GNTDEV_DMA_FLAG_XXXflags it can also be created as a DMA write-combine/coherent buffer, e.g. allocated with correspondingdma_alloc_xxxAPI.
Export the resulting buffer as a new dma-buf.2. Implement waiting for the dma-buf to be released: block until the dma-buf with the file descriptor provided is released.
If within the time-out provided the buffer is not released then-ETIMEDOUTerror is returned. If the buffer with the file descriptor does not exist or has already been released, then-ENOENTis returned. For valid file descriptors this must not be treated as error.Signed-off-by Oleksandr Andrushchenko <[email protected]>--- drivers/xen/gntdev-dmabuf.c | 393 +++++++++++++++++++++++++++++++++++- drivers/xen/gntdev-dmabuf.h | 9 +- drivers/xen/gntdev.c | 90 ++++++++- 3 files changed, 486 insertions(+), 6 deletions(-)drivers/xen/gntdev-dmabuf.c +91
-1@@ -3,15 +3,58 @@/* * Xen dma-buf functionality for gntdev. * +* DMA buffer implementation is based on drivers/gpu/drm/drm_prime.c. +* * Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. */ +#include <linux/dma-buf.h> #include <linux/slab.h> #include "gntdev-dmabuf.h" +struct gntdev_dmabuf { +struct gntdev_dmabuf_priv *priv; +struct dma_buf *dmabuf; +struct list_head next; +int fd; + +union { +struct { +/* Exported buffers are reference counted. */ +struct kref refcount; + +struct gntdev_priv *priv; +struct grant_map *map; +void (*release)(struct gntdev_priv *priv, +struct grant_map *map); + } exp; + } u; + +/* Number of pages this buffer has. */ +int nr_pages; +/* Pages of this buffer. */ +struct page **pages; +}; + +struct gntdev_dmabuf_wait_obj { +struct list_head next; +struct gntdev_dmabuf *gntdev_dmabuf; +struct completion completion; +}; + +struct gntdev_dmabuf_attachment { +struct sg_table *sgt; +enum dma_data_direction dir; +}; +struct gntdev_dmabuf_priv { -int dummy; +/* List of exported DMA buffers. */ +struct list_head exp_list; +/* List of wait objects. */ +struct list_head exp_wait_list; +/* This is the lock which protects dma_buf_xxx lists. */ +struct mutex lock; };/* ------------------------------------------------------------------ */ @@ -22,19 +65,359 @@ struct gntdev_dmabuf_priv {/* Implementation of wait for exported DMA buffer to be released. */ /* ------------------------------------------------------------------ */ +static void dmabuf_exp_release (struct kref *kref); + +static struct gntdev_dmabuf_wait_obj * +dmabuf_exp_wait_obj_new (struct gntdev_dmabuf_priv *priv, +struct gntdev_dmabuf *gntdev_dmabuf) +{ +struct gntdev_dmabuf_wait_obj *obj; + + obj =kzalloc (sizeof (*obj),GFP_KERNEL ); +if (!obj) +return ERR_PTR (-ENOMEM ); + +init_completion (&obj->completion); + obj->gntdev_dmabuf = gntdev_dmabuf; + +mutex_lock (&priv->lock); +list_add (&obj->next, &priv->exp_wait_list); +/* Put our reference and wait for gntdev_dmabuf's release to fire. */ +kref_put (&gntdev_dmabuf->u.exp.refcount, dmabuf_exp_release); +mutex_unlock (&priv->lock); +return obj; +} + +static void dmabuf_exp_wait_obj_free (struct gntdev_dmabuf_priv *priv, +struct gntdev_dmabuf_wait_obj *obj) +{ +struct gntdev_dmabuf_wait_obj *cur_obj, *q; + +mutex_lock (&priv->lock); +list_for_each_entry_safe (cur_obj, q, &priv->exp_wait_list, next) +if (cur_obj == obj) { +list_del (&obj->next); +kfree (obj); +break ; + } +mutex_unlock (&priv->lock); +} + +static int dmabuf_exp_wait_obj_wait (struct gntdev_dmabuf_wait_obj *obj, +u32 wait_to_ms) +{ +if (wait_for_completion_timeout (&obj->completion, +msecs_to_jiffies (wait_to_ms)) <=0 ) +return -ETIMEDOUT ; + +return 0 ; +}
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 124
Quoted 10 lines
drivers/xen/gntdev-dmabuf.c +10
-0+ +static void dmabuf_exp_wait_obj_signal (struct gntdev_dmabuf_priv *priv, +struct gntdev_dmabuf *gntdev_dmabuf) +{ +struct gntdev_dmabuf_wait_obj *obj, *q; + +list_for_each_entry_safe (obj, q, &priv->exp_wait_list, next) +if (obj->gntdev_dmabuf == gntdev_dmabuf) { +pr_debug ("Found gntdev_dmabuf in the wait list, wake\n" ); +complete_all (&obj->completion);
break ?
Quoted 36 lines
drivers/xen/gntdev-dmabuf.c +32
-1+ } +} + +static struct gntdev_dmabuf * +dmabuf_exp_wait_obj_get_by_fd (struct gntdev_dmabuf_priv *priv,int fd) +{ +struct gntdev_dmabuf *q, *gntdev_dmabuf, *ret =ERR_PTR (-ENOENT ); + +mutex_lock (&priv->lock); +list_for_each_entry_safe (gntdev_dmabuf, q, &priv->exp_list, next) +if (gntdev_dmabuf->fd == fd) { +pr_debug ("Found gntdev_dmabuf in the wait list\n" ); +kref_get (&gntdev_dmabuf->u.exp.refcount); + ret = gntdev_dmabuf; +break ; + } +mutex_unlock (&priv->lock); +return ret; +} +int gntdev_dmabuf_exp_wait_released (struct gntdev_dmabuf_priv *priv,int fd,int wait_to_ms) { -return -EINVAL ; +struct gntdev_dmabuf *gntdev_dmabuf; +struct gntdev_dmabuf_wait_obj *obj; +int ret; + +pr_debug ("Will wait for dma-buf with fd %d\n" , fd); +/* +* Try to find the DMA buffer: if not found means that +* either the buffer has already been released or file descriptor +* provided is wrong. +*/ + gntdev_dmabuf =dmabuf_exp_wait_obj_get_by_fd (priv, fd); +if (IS_ERR (gntdev_dmabuf))
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 169
Quoted 10 lines
drivers/xen/gntdev-dmabuf.c +10
-0+return PTR_ERR (gntdev_dmabuf); + +/* +* gntdev_dmabuf still exists and is reference count locked by us now, +* so prepare to wait: allocate wait object and add it to the wait list, +* so we can find it on release. +*/ + obj =dmabuf_exp_wait_obj_new (priv, gntdev_dmabuf); +if (IS_ERR (obj)) { +pr_err ("Failed to setup wait object, ret %ld\n" ,PTR_ERR (obj));
No need for pr_err. We are out of memory.
Quoted 41 lines
drivers/xen/gntdev-dmabuf.c +35
-0+return PTR_ERR (obj); +} + + ret =dmabuf_exp_wait_obj_wait (obj, wait_to_ms); +dmabuf_exp_wait_obj_free (priv, obj); +return ret; }/* ------------------------------------------------------------------ */ /* DMA buffer export support. */ /* ------------------------------------------------------------------ */ +static struct sg_table * +dmabuf_pages_to_sgt (struct page **pages,unsigned int nr_pages) +{ +struct sg_table *sgt; +int ret; + + sgt =kmalloc (sizeof (*sgt),GFP_KERNEL ); +if (!sgt) { + ret = -ENOMEM ; + goto out; + } + + ret =sg_alloc_table_from_pages (sgt, pages, nr_pages,0 , + nr_pages <<PAGE_SHIFT , +GFP_KERNEL ); +if (ret) + goto out; + +return sgt; + +out: +kfree (sgt); +return ERR_PTR (ret); +} + +static int dmabuf_exp_ops_attach (struct dma_buf *dma_buf, +struct device *target_dev, +struct dma_buf_attachment *attach) +{
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 220
Quoted 10 lines
drivers/xen/gntdev-dmabuf.c +10
-0+struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach; + + gntdev_dmabuf_attach =kzalloc (sizeof (*gntdev_dmabuf_attach), +GFP_KERNEL ); +if (!gntdev_dmabuf_attach) +return -ENOMEM ; + + gntdev_dmabuf_attach->dir =DMA_NONE ; + attach->priv = gntdev_dmabuf_attach; +/* Might need to pin the pages of the buffer now. */
Who is supposed to pin the pages? The caller?
Quoted 15 lines
drivers/xen/gntdev-dmabuf.c +15
-0+return 0 ; +} + +static void dmabuf_exp_ops_detach (struct dma_buf *dma_buf, +struct dma_buf_attachment *attach) +{ +struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach = attach->priv; + +if (gntdev_dmabuf_attach) { +struct sg_table *sgt = gntdev_dmabuf_attach->sgt; + +if (sgt) { +if (gntdev_dmabuf_attach->dir !=DMA_NONE ) + dma_unmap_sg_attrs(attach->dev, sgt->sgl, + sgt->nents,
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 245
Quoted 10 lines
drivers/xen/gntdev-dmabuf.c +10
-0+ gntdev_dmabuf_attach->dir, + DMA_ATTR_SKIP_CPU_SYNC); +sg_free_table (sgt); + } + +kfree (sgt); +kfree (gntdev_dmabuf_attach); + attach->priv =NULL ; + } +/* Might need to unpin the pages of the buffer now. */
Same question.
Quoted 4 lines
drivers/xen/gntdev-dmabuf.c +4
-0+} + +static struct sg_table * +dmabuf_exp_ops_map_dma_buf(struct dma_buf_attachment *attach,
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 259
Quoted 10 lines
drivers/xen/gntdev-dmabuf.c +10
-0+ enum dma_data_direction dir) +{ +struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach = attach->priv; +struct gntdev_dmabuf *gntdev_dmabuf = attach->dmabuf->priv; +struct sg_table *sgt; + +pr_debug ("Mapping %d pages for dev %p\n" , gntdev_dmabuf->nr_pages, + attach->dev); + +if (WARN_ON (dir ==DMA_NONE || !gntdev_dmabuf_attach))
WARN_ON_ONCE. Here and elsewhere.
Quoted 252 lines
drivers/xen/gntdev-dmabuf.c +163
-1+return ERR_PTR (-EINVAL ); + +/* Return the cached mapping when possible. */ +if (gntdev_dmabuf_attach->dir == dir) +return gntdev_dmabuf_attach->sgt; + +/* +* Two mappings with different directions for the same attachment are +* not allowed. +*/ +if (WARN_ON (gntdev_dmabuf_attach->dir !=DMA_NONE )) +return ERR_PTR (-EBUSY ); + + sgt =dmabuf_pages_to_sgt (gntdev_dmabuf->pages, + gntdev_dmabuf->nr_pages); +if (!IS_ERR (sgt)) { +if (!dma_map_sg_attrs (attach->dev, sgt->sgl, sgt->nents, dir, +DMA_ATTR_SKIP_CPU_SYNC )) { +sg_free_table (sgt); +kfree (sgt); + sgt =ERR_PTR (-ENOMEM ); + }else { + gntdev_dmabuf_attach->sgt = sgt; + gntdev_dmabuf_attach->dir = dir; + } + } +if (IS_ERR (sgt)) +pr_err ("Failed to map sg table for dev %p\n" , attach->dev); +return sgt; +} + +static void dmabuf_exp_ops_unmap_dma_buf (struct dma_buf_attachment *attach, +struct sg_table *sgt, +enum dma_data_direction dir) +{ +/* Not implemented. The unmap is done at dmabuf_exp_ops_detach(). */ +} + +static void dmabuf_exp_release (struct kref *kref) +{ +struct gntdev_dmabuf *gntdev_dmabuf = + container_of(kref, struct gntdev_dmabuf, u.exp.refcount); + +dmabuf_exp_wait_obj_signal (gntdev_dmabuf->priv, gntdev_dmabuf); +list_del (&gntdev_dmabuf->next); +kfree (gntdev_dmabuf); +} + +static void dmabuf_exp_ops_release (struct dma_buf *dma_buf) +{ +struct gntdev_dmabuf *gntdev_dmabuf = dma_buf->priv; +struct gntdev_dmabuf_priv *priv = gntdev_dmabuf->priv; + + gntdev_dmabuf->u.exp.release (gntdev_dmabuf->u.exp.priv, + gntdev_dmabuf->u.exp.map); +mutex_lock (&priv->lock); +kref_put (&gntdev_dmabuf->u.exp.refcount, dmabuf_exp_release); +mutex_unlock (&priv->lock); +} + +static void *dmabuf_exp_ops_kmap_atomic (struct dma_buf *dma_buf, +unsigned long page_num) +{ +/* Not implemented. */ +return NULL ; +} + +static void dmabuf_exp_ops_kunmap_atomic (struct dma_buf *dma_buf, +unsigned long page_num,void *addr) +{ +/* Not implemented. */ +} + +static void *dmabuf_exp_ops_kmap (struct dma_buf *dma_buf, +unsigned long page_num) +{ +/* Not implemented. */ +return NULL ; +} + +static void dmabuf_exp_ops_kunmap (struct dma_buf *dma_buf, +unsigned long page_num,void *addr) +{ +/* Not implemented. */ +} + +static int dmabuf_exp_ops_mmap (struct dma_buf *dma_buf, +struct vm_area_struct *vma) +{ +/* Not implemented. */ +return 0 ; +} + +static const struct dma_buf_ops dmabuf_exp_ops = { + .attach = dmabuf_exp_ops_attach, + .detach = dmabuf_exp_ops_detach, + .map_dma_buf = dmabuf_exp_ops_map_dma_buf, + .unmap_dma_buf = dmabuf_exp_ops_unmap_dma_buf, + .release = dmabuf_exp_ops_release, + .map = dmabuf_exp_ops_kmap, + .map_atomic = dmabuf_exp_ops_kmap_atomic, + .unmap = dmabuf_exp_ops_kunmap, + .unmap_atomic = dmabuf_exp_ops_kunmap_atomic, + .mmap = dmabuf_exp_ops_mmap, +}; +int gntdev_dmabuf_exp_from_pages (struct gntdev_dmabuf_export_args *args) { -return -EINVAL ; +DEFINE_DMA_BUF_EXPORT_INFO (exp_info); +struct gntdev_dmabuf *gntdev_dmabuf; +int ret =0 ; + + gntdev_dmabuf =kzalloc (sizeof (*gntdev_dmabuf),GFP_KERNEL ); +if (!gntdev_dmabuf) +return -ENOMEM ; + +kref_init (&gntdev_dmabuf->u.exp.refcount); + + gntdev_dmabuf->priv = args->dmabuf_priv; + gntdev_dmabuf->nr_pages = args->count; + gntdev_dmabuf->pages = args->pages; + gntdev_dmabuf->u.exp.priv = args->priv; + gntdev_dmabuf->u.exp.map = args->map; + gntdev_dmabuf->u.exp.release = args->release; + + exp_info.exp_name =KBUILD_MODNAME ; +if (args->dev->driver && args->dev->driver->owner) + exp_info.owner = args->dev->driver->owner; +else + exp_info.owner =THIS_MODULE ; + exp_info.ops = &dmabuf_exp_ops; + exp_info.size = args->count <<PAGE_SHIFT ; + exp_info.flags =O_RDWR ; + exp_info.priv = gntdev_dmabuf; + + gntdev_dmabuf->dmabuf =dma_buf_export (&exp_info); +if (IS_ERR (gntdev_dmabuf->dmabuf)) { + ret =PTR_ERR (gntdev_dmabuf->dmabuf); + gntdev_dmabuf->dmabuf =NULL ; + goto fail; + } + + ret =dma_buf_fd (gntdev_dmabuf->dmabuf,O_CLOEXEC ); +if (ret <0 ) + goto fail; + + gntdev_dmabuf->fd = ret; + args->fd = ret; + +pr_debug ("Exporting DMA buffer with fd %d\n" , ret); + +mutex_lock (&args->dmabuf_priv->lock); +list_add (&gntdev_dmabuf->next, &args->dmabuf_priv->exp_list); +mutex_unlock (&args->dmabuf_priv->lock); +return 0 ; + +fail: +if (gntdev_dmabuf->dmabuf) +dma_buf_put (gntdev_dmabuf->dmabuf); +kfree (gntdev_dmabuf); +return ret; }/* ------------------------------------------------------------------ */ @@ -66,6 +449,10 @@ struct gntdev_dmabuf_priv *gntdev_dmabuf_init(void)if (!priv)return ERR_PTR (-ENOMEM ); +mutex_init (&priv->lock); +INIT_LIST_HEAD (&priv->exp_list); +INIT_LIST_HEAD (&priv->exp_wait_list); +return priv; }drivers/xen/gntdev-dmabuf.h +8
-1@@ -18,7 +18,14 @@ struct gntdev_dmabuf;struct device ;struct gntdev_dmabuf_export_args { -int dummy; +struct gntdev_priv *priv; +struct grant_map *map; +void (*release)(struct gntdev_priv *priv,struct grant_map *map); +struct gntdev_dmabuf_priv *dmabuf_priv; +struct device *dev; +int count; +struct page **pages; +u32 fd; };struct gntdev_dmabuf_priv *gntdev_dmabuf_init (void );drivers/xen/gntdev.c +37
-1@@ -319,6 +319,16 @@ static void gntdev_put_map(struct gntdev_priv *priv, struct grant_map *map)gntdev_free_map (map); } +#ifdef CONFIG_XEN_GNTDEV_DMABUF +static void gntdev_remove_map (struct gntdev_priv *priv,struct grant_map *map) +{ +mutex_lock (&priv->lock); +list_del (&map->next); +gntdev_put_map (NULL /* already removed */ , map); +mutex_unlock (&priv->lock); +} +#endif +/* ------------------------------------------------------------------ */ static int find_grant_ptes(pte_t *pte, pgtable_t token,@@ -1063,12 +1073,88 @@ static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u)/* DMA buffer export support. */ /* ------------------------------------------------------------------ */ +static struct grant_map * +dmabuf_exp_alloc_backing_storage (struct gntdev_priv *priv,int dmabuf_flags, +int count) +{ +struct grant_map *map; + +if (unlikely (count <=0 )) +return ERR_PTR (-EINVAL ); + +if ((dmabuf_flags &GNTDEV_DMA_FLAG_WC ) && + (dmabuf_flags &GNTDEV_DMA_FLAG_COHERENT )) { +pr_err ("Wrong dma-buf flags: either WC or coherent, not both\n" ); +return ERR_PTR (-EINVAL ); + } + + map =gntdev_alloc_map (priv, count, dmabuf_flags); +if (!map) +return ERR_PTR (-ENOMEM ); + +if (unlikely (atomic_add_return (count, &pages_mapped) > limit)) { +pr_err ("can't map: over limit\n" ); +gntdev_put_map (NULL , map); +return ERR_PTR (-ENOMEM ); + } +return map; +} +int gntdev_dmabuf_exp_from_refs (struct gntdev_priv *priv,int flags,int count,u32 domid,u32 *refs,u32 *fd) { -/* XXX: this will need to work with gntdev's map, so leave it here. */
drivers/xen/gntdev.c static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) · line 1114
Quoted 10 lines
drivers/xen/gntdev.c +8
-1+struct grant_map *map; +struct gntdev_dmabuf_export_args args; +int i, ret; + *fd =-1 ; -return -EINVAL ; + +if (use_ptemod) { +pr_err ("Cannot provide dma-buf: use_ptemode %d\n" , + use_ptemod);
No pr_err here please. This can potentially become a DoS vector as it comes directly from ioctl.
I would, in fact, revisit other uses of pr_err in this file.
drivers/xen/gntdev.c static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) · line 1118
Quoted 4 lines
drivers/xen/gntdev.c +4
-0+return -EINVAL ; + } + + map =dmabuf_exp_alloc_backing_storage (priv, flags, count);
@count comes from userspace. dmabuf_exp_alloc_backing_storage only checks for it to be >0. Should it be checked for some sane max value?
-boris
Quoted 42 lines
drivers/xen/gntdev.c +39
-0+if (IS_ERR (map)) +return PTR_ERR (map); + +for (i =0 ; i < count; i++) { + map->grants[i].domid = domid; + map->grants[i].ref = refs[i]; + } + +mutex_lock (&priv->lock); +gntdev_add_map (priv, map); +mutex_unlock (&priv->lock); + + map->flags |= GNTMAP_host_map; +#if defined(CONFIG_X86 ) + map->flags |= GNTMAP_device_map; +#endif + + ret =map_grant_pages (map); +if (ret <0 ) + goto out; + + args.priv = priv; + args.map = map; + args.release = gntdev_remove_map; + args.dev = priv->dma_dev; + args.dmabuf_priv = priv->dmabuf_priv; + args.count = map->count; + args.pages = map->pages; + + ret =gntdev_dmabuf_exp_from_pages (&args); +if (ret <0 ) + goto out; + + *fd = args.fd; +return 0 ; + +out: +gntdev_remove_map (priv, map); +return ret; }/* ------------------------------------------------------------------ */
Re: [PATCH v2 7/9] xen/gntdev: Implement dma-buf export functionality
Quoted 143 lines · Boris Ostrovsky
Quoted 142 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
1. Create a dma-buf from grant references provided by the foreign domain. By default dma-buf is backed by system memory pages, but by providing
GNTDEV_DMA_FLAG_XXXflags it can also be created as a DMA write-combine/coherent buffer, e.g. allocated with correspondingdma_alloc_xxxAPI.
Export the resulting buffer as a new dma-buf.2. Implement waiting for the dma-buf to be released: block until the dma-buf with the file descriptor provided is released. If within the time-out provided the buffer is not released then
-ETIMEDOUTerror is returned. If the buffer with the file descriptor does not exist or has already been released, then-ENOENTis returned. For valid file descriptors this must not be treated as error.Signed-off-by Oleksandr Andrushchenko <[email protected]>--- drivers/xen/gntdev-dmabuf.c | 393 +++++++++++++++++++++++++++++++++++- drivers/xen/gntdev-dmabuf.h | 9 +- drivers/xen/gntdev.c | 90 ++++++++- 3 files changed, 486 insertions(+), 6 deletions(-)drivers/xen/gntdev-dmabuf.c +94
-1@@ -3,15 +3,58 @@/* * Xen dma-buf functionality for gntdev. * +* DMA buffer implementation is based on drivers/gpu/drm/drm_prime.c. +* * Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. */ +#include <linux/dma-buf.h> #include <linux/slab.h> #include "gntdev-dmabuf.h" +struct gntdev_dmabuf { +struct gntdev_dmabuf_priv *priv; +struct dma_buf *dmabuf; +struct list_head next; +int fd; + +union { +struct { +/* Exported buffers are reference counted. */ +struct kref refcount; + +struct gntdev_priv *priv; +struct grant_map *map; +void (*release)(struct gntdev_priv *priv, +struct grant_map *map); + } exp; + } u; + +/* Number of pages this buffer has. */ +int nr_pages; +/* Pages of this buffer. */ +struct page **pages; +}; + +struct gntdev_dmabuf_wait_obj { +struct list_head next; +struct gntdev_dmabuf *gntdev_dmabuf; +struct completion completion; +}; + +struct gntdev_dmabuf_attachment { +struct sg_table *sgt; +enum dma_data_direction dir; +}; +struct gntdev_dmabuf_priv { -int dummy; +/* List of exported DMA buffers. */ +struct list_head exp_list; +/* List of wait objects. */ +struct list_head exp_wait_list; +/* This is the lock which protects dma_buf_xxx lists. */ +struct mutex lock; };/* ------------------------------------------------------------------ */ @@ -22,19 +65,359 @@ struct gntdev_dmabuf_priv {/* Implementation of wait for exported DMA buffer to be released. */ /* ------------------------------------------------------------------ */ +static void dmabuf_exp_release (struct kref *kref); + +static struct gntdev_dmabuf_wait_obj * +dmabuf_exp_wait_obj_new (struct gntdev_dmabuf_priv *priv, +struct gntdev_dmabuf *gntdev_dmabuf) +{ +struct gntdev_dmabuf_wait_obj *obj; + + obj =kzalloc (sizeof (*obj),GFP_KERNEL ); +if (!obj) +return ERR_PTR (-ENOMEM ); + +init_completion (&obj->completion); + obj->gntdev_dmabuf = gntdev_dmabuf; + +mutex_lock (&priv->lock); +list_add (&obj->next, &priv->exp_wait_list); +/* Put our reference and wait for gntdev_dmabuf's release to fire. */ +kref_put (&gntdev_dmabuf->u.exp.refcount, dmabuf_exp_release); +mutex_unlock (&priv->lock); +return obj; +} + +static void dmabuf_exp_wait_obj_free (struct gntdev_dmabuf_priv *priv, +struct gntdev_dmabuf_wait_obj *obj) +{ +struct gntdev_dmabuf_wait_obj *cur_obj, *q; + +mutex_lock (&priv->lock); +list_for_each_entry_safe (cur_obj, q, &priv->exp_wait_list, next) +if (cur_obj == obj) { +list_del (&obj->next); +kfree (obj); +break ; + } +mutex_unlock (&priv->lock); +} + +static int dmabuf_exp_wait_obj_wait (struct gntdev_dmabuf_wait_obj *obj, +u32 wait_to_ms) +{ +if (wait_for_completion_timeout (&obj->completion, +msecs_to_jiffies (wait_to_ms)) <=0 ) +return -ETIMEDOUT ; + +return 0 ; +} + +static void dmabuf_exp_wait_obj_signal (struct gntdev_dmabuf_priv *priv, +struct gntdev_dmabuf *gntdev_dmabuf)
Quoted 8 lines
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 124
Quoted 7 lines
drivers/xen/gntdev-dmabuf.c +7
-0+{ +struct gntdev_dmabuf_wait_obj *obj, *q; + +list_for_each_entry_safe (obj, q, &priv->exp_wait_list, next) +if (obj->gntdev_dmabuf == gntdev_dmabuf) { +pr_debug ("Found gntdev_dmabuf in the wait list, wake\n" ); +complete_all (&obj->completion);break ?
sure, thank you
Quoted 40 lines
Quoted 40 lines
drivers/xen/gntdev-dmabuf.c +36
-1+ } +} + +static struct gntdev_dmabuf * +dmabuf_exp_wait_obj_get_by_fd (struct gntdev_dmabuf_priv *priv,int fd) +{ +struct gntdev_dmabuf *q, *gntdev_dmabuf, *ret =ERR_PTR (-ENOENT ); + +mutex_lock (&priv->lock); +list_for_each_entry_safe (gntdev_dmabuf, q, &priv->exp_list, next) +if (gntdev_dmabuf->fd == fd) { +pr_debug ("Found gntdev_dmabuf in the wait list\n" ); +kref_get (&gntdev_dmabuf->u.exp.refcount); + ret = gntdev_dmabuf; +break ; + } +mutex_unlock (&priv->lock); +return ret; +} +int gntdev_dmabuf_exp_wait_released (struct gntdev_dmabuf_priv *priv,int fd,int wait_to_ms) { -return -EINVAL ; +struct gntdev_dmabuf *gntdev_dmabuf; +struct gntdev_dmabuf_wait_obj *obj; +int ret; + +pr_debug ("Will wait for dma-buf with fd %d\n" , fd); +/* +* Try to find the DMA buffer: if not found means that +* either the buffer has already been released or file descriptor +* provided is wrong. +*/ + gntdev_dmabuf =dmabuf_exp_wait_obj_get_by_fd (priv, fd); +if (IS_ERR (gntdev_dmabuf)) +return PTR_ERR (gntdev_dmabuf); + +/* +* gntdev_dmabuf still exists and is reference count locked by us now,
Quoted 8 lines
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 169
Quoted 6 lines
drivers/xen/gntdev-dmabuf.c +6
-0+* so prepare to wait: allocate wait object and add it to the wait list, +* so we can find it on release. +*/ + obj =dmabuf_exp_wait_obj_new (priv, gntdev_dmabuf); +if (IS_ERR (obj)) { +pr_err ("Failed to setup wait object, ret %ld\n" ,PTR_ERR (obj));No need for
pr_err. We are out of memory.
Will remove
Quoted 46 lines
Quoted 46 lines
drivers/xen/gntdev-dmabuf.c +39
-0+return PTR_ERR (obj); +} + + ret =dmabuf_exp_wait_obj_wait (obj, wait_to_ms); +dmabuf_exp_wait_obj_free (priv, obj); +return ret; }/* ------------------------------------------------------------------ */ /* DMA buffer export support. */ /* ------------------------------------------------------------------ */ +static struct sg_table * +dmabuf_pages_to_sgt (struct page **pages,unsigned int nr_pages) +{ +struct sg_table *sgt; +int ret; + + sgt =kmalloc (sizeof (*sgt),GFP_KERNEL ); +if (!sgt) { + ret = -ENOMEM ; + goto out; + } + + ret =sg_alloc_table_from_pages (sgt, pages, nr_pages,0 , + nr_pages <<PAGE_SHIFT , +GFP_KERNEL ); +if (ret) + goto out; + +return sgt; + +out: +kfree (sgt); +return ERR_PTR (ret); +} + +static int dmabuf_exp_ops_attach (struct dma_buf *dma_buf, +struct device *target_dev, +struct dma_buf_attachment *attach) +{ +struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach; + + gntdev_dmabuf_attach =kzalloc (sizeof (*gntdev_dmabuf_attach), +GFP_KERNEL );
Quoted 8 lines
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 220
Quoted 6 lines
drivers/xen/gntdev-dmabuf.c +6
-0+if (!gntdev_dmabuf_attach) +return -ENOMEM ; + + gntdev_dmabuf_attach->dir =DMA_NONE ; + attach->priv = gntdev_dmabuf_attach; +/* Might need to pin the pages of the buffer now. */ Who is supposed to pin the pages? The caller?
Ok, as we do not implement .mmap for Xen dma-buf and there is no plan to mmap kernel memory (either ballooned or dma_alloc'ed), then we can remove this comment as there is no need to pin/unpin pages.
Quoted 19 lines
Quoted 19 lines
drivers/xen/gntdev-dmabuf.c +18
-0+return 0 ; +} + +static void dmabuf_exp_ops_detach (struct dma_buf *dma_buf, +struct dma_buf_attachment *attach) +{ +struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach = attach->priv; + +if (gntdev_dmabuf_attach) { +struct sg_table *sgt = gntdev_dmabuf_attach->sgt; + +if (sgt) { +if (gntdev_dmabuf_attach->dir !=DMA_NONE ) +dma_unmap_sg_attrs (attach->dev, sgt->sgl, + sgt->nents, + gntdev_dmabuf_attach->dir, +DMA_ATTR_SKIP_CPU_SYNC ); +sg_free_table (sgt);
Quoted 8 lines
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 245
Quoted 7 lines
drivers/xen/gntdev-dmabuf.c +7
-0+ } + +kfree (sgt); +kfree (gntdev_dmabuf_attach); + attach->priv =NULL ; + } +/* Might need to unpin the pages of the buffer now. */ Same question.
Please see above
Quoted 8 lines
Quoted 8 lines
drivers/xen/gntdev-dmabuf.c +8
-0+} + +static struct sg_table * +dmabuf_exp_ops_map_dma_buf (struct dma_buf_attachment *attach, +enum dma_data_direction dir) +{ +struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach = attach->priv; +struct gntdev_dmabuf *gntdev_dmabuf = attach->dmabuf->priv;
Quoted 8 lines
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 259
Quoted 6 lines
drivers/xen/gntdev-dmabuf.c +6
-0+struct sg_table *sgt; + +pr_debug ("Mapping %d pages for dev %p\n" , gntdev_dmabuf->nr_pages, + attach->dev); + +if (WARN_ON (dir ==DMA_NONE || !gntdev_dmabuf_attach))
WARN_ON_ONCE. Here and elsewhere.
Why? The UAPI may be used by different applications, thus we might lose warnings for some of them. Having WARN_ON will show problems for multiple users, not for the first one.
Does this make sense to still use WARN_ON?
Quoted 266 lines
Quoted 253 lines
drivers/xen/gntdev-dmabuf.c +163
-1+return ERR_PTR (-EINVAL ); + +/* Return the cached mapping when possible. */ +if (gntdev_dmabuf_attach->dir == dir) +return gntdev_dmabuf_attach->sgt; + +/* +* Two mappings with different directions for the same attachment are +* not allowed. +*/ +if (WARN_ON (gntdev_dmabuf_attach->dir !=DMA_NONE )) +return ERR_PTR (-EBUSY ); + + sgt =dmabuf_pages_to_sgt (gntdev_dmabuf->pages, + gntdev_dmabuf->nr_pages); +if (!IS_ERR (sgt)) { +if (!dma_map_sg_attrs (attach->dev, sgt->sgl, sgt->nents, dir, +DMA_ATTR_SKIP_CPU_SYNC )) { +sg_free_table (sgt); +kfree (sgt); + sgt =ERR_PTR (-ENOMEM ); + }else { + gntdev_dmabuf_attach->sgt = sgt; + gntdev_dmabuf_attach->dir = dir; + } + } +if (IS_ERR (sgt)) +pr_err ("Failed to map sg table for dev %p\n" , attach->dev); +return sgt; +} + +static void dmabuf_exp_ops_unmap_dma_buf (struct dma_buf_attachment *attach, +struct sg_table *sgt, +enum dma_data_direction dir) +{ +/* Not implemented. The unmap is done at dmabuf_exp_ops_detach(). */ +} + +static void dmabuf_exp_release (struct kref *kref) +{ +struct gntdev_dmabuf *gntdev_dmabuf = + container_of(kref, struct gntdev_dmabuf, u.exp.refcount); + +dmabuf_exp_wait_obj_signal (gntdev_dmabuf->priv, gntdev_dmabuf); +list_del (&gntdev_dmabuf->next); +kfree (gntdev_dmabuf); +} + +static void dmabuf_exp_ops_release (struct dma_buf *dma_buf) +{ +struct gntdev_dmabuf *gntdev_dmabuf = dma_buf->priv; +struct gntdev_dmabuf_priv *priv = gntdev_dmabuf->priv; + + gntdev_dmabuf->u.exp.release (gntdev_dmabuf->u.exp.priv, + gntdev_dmabuf->u.exp.map); +mutex_lock (&priv->lock); +kref_put (&gntdev_dmabuf->u.exp.refcount, dmabuf_exp_release); +mutex_unlock (&priv->lock); +} + +static void *dmabuf_exp_ops_kmap_atomic (struct dma_buf *dma_buf, +unsigned long page_num) +{ +/* Not implemented. */ +return NULL ; +} + +static void dmabuf_exp_ops_kunmap_atomic (struct dma_buf *dma_buf, +unsigned long page_num,void *addr) +{ +/* Not implemented. */ +} + +static void *dmabuf_exp_ops_kmap (struct dma_buf *dma_buf, +unsigned long page_num) +{ +/* Not implemented. */ +return NULL ; +} + +static void dmabuf_exp_ops_kunmap (struct dma_buf *dma_buf, +unsigned long page_num,void *addr) +{ +/* Not implemented. */ +} + +static int dmabuf_exp_ops_mmap (struct dma_buf *dma_buf, +struct vm_area_struct *vma) +{ +/* Not implemented. */ +return 0 ; +} + +static const struct dma_buf_ops dmabuf_exp_ops = { + .attach = dmabuf_exp_ops_attach, + .detach = dmabuf_exp_ops_detach, + .map_dma_buf = dmabuf_exp_ops_map_dma_buf, + .unmap_dma_buf = dmabuf_exp_ops_unmap_dma_buf, + .release = dmabuf_exp_ops_release, + .map = dmabuf_exp_ops_kmap, + .map_atomic = dmabuf_exp_ops_kmap_atomic, + .unmap = dmabuf_exp_ops_kunmap, + .unmap_atomic = dmabuf_exp_ops_kunmap_atomic, + .mmap = dmabuf_exp_ops_mmap, +}; +int gntdev_dmabuf_exp_from_pages (struct gntdev_dmabuf_export_args *args) { -return -EINVAL ; +DEFINE_DMA_BUF_EXPORT_INFO (exp_info); +struct gntdev_dmabuf *gntdev_dmabuf; +int ret =0 ; + + gntdev_dmabuf =kzalloc (sizeof (*gntdev_dmabuf),GFP_KERNEL ); +if (!gntdev_dmabuf) +return -ENOMEM ; + +kref_init (&gntdev_dmabuf->u.exp.refcount); + + gntdev_dmabuf->priv = args->dmabuf_priv; + gntdev_dmabuf->nr_pages = args->count; + gntdev_dmabuf->pages = args->pages; + gntdev_dmabuf->u.exp.priv = args->priv; + gntdev_dmabuf->u.exp.map = args->map; + gntdev_dmabuf->u.exp.release = args->release; + + exp_info.exp_name =KBUILD_MODNAME ; +if (args->dev->driver && args->dev->driver->owner) + exp_info.owner = args->dev->driver->owner; +else + exp_info.owner =THIS_MODULE ; + exp_info.ops = &dmabuf_exp_ops; + exp_info.size = args->count <<PAGE_SHIFT ; + exp_info.flags =O_RDWR ; + exp_info.priv = gntdev_dmabuf; + + gntdev_dmabuf->dmabuf =dma_buf_export (&exp_info); +if (IS_ERR (gntdev_dmabuf->dmabuf)) { + ret =PTR_ERR (gntdev_dmabuf->dmabuf); + gntdev_dmabuf->dmabuf =NULL ; + goto fail; + } + + ret =dma_buf_fd (gntdev_dmabuf->dmabuf,O_CLOEXEC ); +if (ret <0 ) + goto fail; + + gntdev_dmabuf->fd = ret; + args->fd = ret; + +pr_debug ("Exporting DMA buffer with fd %d\n" , ret); + +mutex_lock (&args->dmabuf_priv->lock); +list_add (&gntdev_dmabuf->next, &args->dmabuf_priv->exp_list); +mutex_unlock (&args->dmabuf_priv->lock); +return 0 ; + +fail: +if (gntdev_dmabuf->dmabuf) +dma_buf_put (gntdev_dmabuf->dmabuf); +kfree (gntdev_dmabuf); +return ret; }/* ------------------------------------------------------------------ */ @@ -66,6 +449,10 @@ struct gntdev_dmabuf_priv *gntdev_dmabuf_init(void)if (!priv)return ERR_PTR (-ENOMEM ); +mutex_init (&priv->lock); +INIT_LIST_HEAD (&priv->exp_list); +INIT_LIST_HEAD (&priv->exp_wait_list); +return priv; }drivers/xen/gntdev-dmabuf.h +8
-1@@ -18,7 +18,14 @@ struct gntdev_dmabuf;struct device ;struct gntdev_dmabuf_export_args { -int dummy; +struct gntdev_priv *priv; +struct grant_map *map; +void (*release)(struct gntdev_priv *priv,struct grant_map *map); +struct gntdev_dmabuf_priv *dmabuf_priv; +struct device *dev; +int count; +struct page **pages; +u32 fd; };struct gntdev_dmabuf_priv *gntdev_dmabuf_init (void );drivers/xen/gntdev.c +37
-1@@ -319,6 +319,16 @@ static void gntdev_put_map(struct gntdev_priv *priv, struct grant_map *map)gntdev_free_map (map); } +#ifdef CONFIG_XEN_GNTDEV_DMABUF +static void gntdev_remove_map (struct gntdev_priv *priv,struct grant_map *map) +{ +mutex_lock (&priv->lock); +list_del (&map->next); +gntdev_put_map (NULL /* already removed */ , map); +mutex_unlock (&priv->lock); +} +#endif +/* ------------------------------------------------------------------ */ static int find_grant_ptes(pte_t *pte, pgtable_t token,@@ -1063,12 +1073,88 @@ static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u)/* DMA buffer export support. */ /* ------------------------------------------------------------------ */ +static struct grant_map * +dmabuf_exp_alloc_backing_storage (struct gntdev_priv *priv,int dmabuf_flags, +int count) +{ +struct grant_map *map; + +if (unlikely (count <=0 )) +return ERR_PTR (-EINVAL ); + +if ((dmabuf_flags &GNTDEV_DMA_FLAG_WC ) && + (dmabuf_flags &GNTDEV_DMA_FLAG_COHERENT )) { +pr_err ("Wrong dma-buf flags: either WC or coherent, not both\n" ); +return ERR_PTR (-EINVAL ); + } + + map =gntdev_alloc_map (priv, count, dmabuf_flags); +if (!map) +return ERR_PTR (-ENOMEM ); + +if (unlikely (atomic_add_return (count, &pages_mapped) > limit)) { +pr_err ("can't map: over limit\n" ); +gntdev_put_map (NULL , map); +return ERR_PTR (-ENOMEM ); + } +return map; +} +int gntdev_dmabuf_exp_from_refs (struct gntdev_priv *priv,int flags,int count,u32 domid,u32 *refs,u32 *fd) { -/* XXX: this will need to work with gntdev's map, so leave it here. */ drivers/xen/gntdev.c static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) · line 1114
Quoted 10 lines
drivers/xen/gntdev.c +8
-1+struct grant_map *map; +struct gntdev_dmabuf_export_args args; +int i, ret; + *fd =-1 ; -return -EINVAL ; + +if (use_ptemod) { +pr_err ("Cannot provide dma-buf: use_ptemode %d\n" , + use_ptemod);No
pr_errhere please. This can potentially become a DoS vector as it comes directly from ioctl.
Quoted 1 line
I would, in fact, revisit other uses of
pr_errin this file.
Sure, all of pr_err can actually be pr_debug...
Quoted 7 lines
drivers/xen/gntdev.c static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) · line 1118
Quoted 4 lines
drivers/xen/gntdev.c +4
-0+return -EINVAL ; + } + + map =dmabuf_exp_alloc_backing_storage (priv, flags, count);@count comes from userspace.
dmabuf_exp_alloc_backing_storageonly checks for it to be >0. Should it be checked for some sane max value?
This is not easy as it is hard to tell what could be that max value. For DMA buffers if count is too big then allocation will fail, so need to check for max here (dma_alloc_{xxx} will filter out too big allocations).
For Xen balloon allocations I cannot tell what could be that max value neither. Tough question how to limit.
Quoted 2 lines
-boris
Thank you,
Oleksandr
Quoted 41 lines
Quoted 41 lines
drivers/xen/gntdev.c +39
-0+if (IS_ERR (map)) +return PTR_ERR (map); + +for (i =0 ; i < count; i++) { + map->grants[i].domid = domid; + map->grants[i].ref = refs[i]; + } + +mutex_lock (&priv->lock); +gntdev_add_map (priv, map); +mutex_unlock (&priv->lock); + + map->flags |= GNTMAP_host_map; +#if defined(CONFIG_X86 ) + map->flags |= GNTMAP_device_map; +#endif + + ret =map_grant_pages (map); +if (ret <0 ) + goto out; + + args.priv = priv; + args.map = map; + args.release = gntdev_remove_map; + args.dev = priv->dma_dev; + args.dmabuf_priv = priv->dmabuf_priv; + args.count = map->count; + args.pages = map->pages; + + ret =gntdev_dmabuf_exp_from_pages (&args); +if (ret <0 ) + goto out; + + *fd = args.fd; +return 0 ; + +out: +gntdev_remove_map (priv, map); +return ret; }
Quoted 1 line
drivers/xen/gntdev.c static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) · line 1160
Quoted 1 line
drivers/xen/gntdev.c +0
-0/* ------------------------------------------------------------------ */
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 7/9] xen/gntdev: Implement dma-buf export functionality
Quoted 19 lines · Oleksandr Andrushchenko
Quoted 18 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev-dmabuf.c +6
-0+ +static struct sg_table * +dmabuf_exp_ops_map_dma_buf (struct dma_buf_attachment *attach, + enum dma_data_direction dir) +{ + struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach =
attach->priv;
+ structgntdev_dmabuf*gntdev_dmabuf=attach->dmabuf->priv; + structsg_table*sgt;drivers/xen/gntdev-dmabuf.c +5
-0+ + pr_debug("Mapping %d pages for dev %p\n", gntdev_dmabuf->nr_pages, + attach->dev); + + if (WARN_ON(dir == DMA_NONE || !gntdev_dmabuf_attach))
Quoted 5 lines
Quoted 1 line
WARN_ON_ONCE. Here and elsewhere.Why? The UAPI may be used by different applications, thus we might lose warnings for some of them. Having
WARN_ONwill show problems for multiple users, not for the first one.
Does this make sense to still useWARN_ON?
Just as with pr_err call somewhere else the concern here is that userland (which I think is where this is eventually called from?) may intentionally trigger the error, flooding the log.
And even this is not directly called from userland there is still a possibility of triggering this error multiple times.
Quoted 10 lines
Quoted 9 lines
Quoted 5 lines
+
+ if (use_ptemod) {
+pr_err("Cannot provide dma-buf: use_ptemode %d\n", + use_ptemod);No
pr_errhere please. This can potentially become a DoS vector as it comes directly from ioctl.I would, in fact, revisit other uses of
pr_errin this file.Sure, all of
pr_errcan actually bepr_debug...
I'd check even further and see if any prink is needed. I think I saw a couple that were not especially useful.
Quoted 11 lines
Quoted 7 lines
Quoted 4 lines
+ return
-EINVAL;
+ }
+
+ map =dmabuf_exp_alloc_backing_storage(priv, flags, count);@count comes from userspace.
dmabuf_exp_alloc_backing_storageonly checks for it to be >0. Should it be checked for some sane max value?This is not easy as it is hard to tell what could be that max value. For DMA buffers if count is too big then allocation will fail, so need to check for max here (dma_alloc_{xxx} will filter out too big allocations).
OK, that may be sufficient. BTW, I believe there were other loops with @count being the control variable. Please see if a user can pass a bogus value.
Quoted 2 lines
For Xen balloon allocations I cannot tell what could be that max value neither. Tough question how to limit.
I think in balloon there is also a guarantee (of sorts) that something prior to a loop will fail.
-boris
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 7/9] xen/gntdev: Implement dma-buf export functionality
In reply to Oleksandr AndrushchenkoQuoted 19 lines · Oleksandr Andrushchenko
Quoted 18 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev-dmabuf.c +6
-0+ +static struct sg_table * +dmabuf_exp_ops_map_dma_buf (struct dma_buf_attachment *attach, + enum dma_data_direction dir) +{ + struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach =
attach->priv;
+ structgntdev_dmabuf*gntdev_dmabuf=attach->dmabuf->priv; + structsg_table*sgt;drivers/xen/gntdev-dmabuf.c +5
-0+ + pr_debug("Mapping %d pages for dev %p\n", gntdev_dmabuf->nr_pages, + attach->dev); + + if (WARN_ON(dir == DMA_NONE || !gntdev_dmabuf_attach))
Quoted 5 lines
Quoted 1 line
WARN_ON_ONCE. Here and elsewhere.Why? The UAPI may be used by different applications, thus we might lose warnings for some of them. Having
WARN_ONwill show problems for multiple users, not for the first one.
Does this make sense to still useWARN_ON?
Just as with pr_err call somewhere else the concern here is that userland (which I think is where this is eventually called from?) may intentionally trigger the error, flooding the log.
And even this is not directly called from userland there is still a possibility of triggering this error multiple times.
Quoted 10 lines
Quoted 9 lines
Quoted 5 lines
+
+ if (use_ptemod) {
+pr_err("Cannot provide dma-buf: use_ptemode %d\n", + use_ptemod);No
pr_errhere please. This can potentially become a DoS vector as it comes directly from ioctl.I would, in fact, revisit other uses of
pr_errin this file.Sure, all of
pr_errcan actually bepr_debug...
I'd check even further and see if any prink is needed. I think I saw a couple that were not especially useful.
Quoted 11 lines
Quoted 7 lines
Quoted 4 lines
+ return
-EINVAL;
+ }
+
+ map =dmabuf_exp_alloc_backing_storage(priv, flags, count);@count comes from userspace.
dmabuf_exp_alloc_backing_storageonly checks for it to be >0. Should it be checked for some sane max value?This is not easy as it is hard to tell what could be that max value. For DMA buffers if count is too big then allocation will fail, so need to check for max here (dma_alloc_{xxx} will filter out too big allocations).
OK, that may be sufficient. BTW, I believe there were other loops with @count being the control variable. Please see if a user can pass a bogus value.
Quoted 2 lines
For Xen balloon allocations I cannot tell what could be that max value neither. Tough question how to limit.
I think in balloon there is also a guarantee (of sorts) that something prior to a loop will fail.
-boris
Re: [PATCH v2 7/9] xen/gntdev: Implement dma-buf export functionality
Quoted 25 lines · Boris Ostrovsky
Quoted 18 lines · Oleksandr Andrushchenko
Quoted 17 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev-dmabuf.c +6
-0+ +static struct sg_table * +dmabuf_exp_ops_map_dma_buf (struct dma_buf_attachment *attach, + enum dma_data_direction dir) +{ + struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach =
attach->priv;
+ structgntdev_dmabuf*gntdev_dmabuf=attach->dmabuf->priv; + structsg_table*sgt;drivers/xen/gntdev-dmabuf.c +5
-0+ + pr_debug("Mapping %d pages for dev %p\n", gntdev_dmabuf->nr_pages, + attach->dev); + + if (WARN_ON(dir == DMA_NONE || !gntdev_dmabuf_attach))Quoted 5 lines
Quoted 1 line
WARN_ON_ONCE. Here and elsewhere.Why? The UAPI may be used by different applications, thus we might lose warnings for some of them. Having
WARN_ONwill show problems for multiple users, not for the first one.
Does this make sense to still useWARN_ON?
Quoted 6 lines
Just as with
pr_errcall somewhere else the concern here is that userland (which I think is where this is eventually called from?) may intentionally trigger the error, flooding the log.And even this is not directly called from userland there is still a possibility of triggering this error multiple times.
Ok, will use WARN_ON_ONCE
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
+
+ if (use_ptemod) {
+pr_err("Cannot provide dma-buf: use_ptemode %d\n", + use_ptemod);
Quoted 7 lines
Quoted 5 lines
Quoted 4 lines
No
pr_errhere please. This can potentially become a DoS vector as it comes directly from ioctl.I would, in fact, revisit other uses of
pr_errin this file.Sure, all of
pr_errcan actually bepr_debug...I'd check even further and see if any prink is needed. I think I saw a couple that were not especially useful.
All those were useful while debugging the code and use-cases, so I would prefer to have them all still available, but as pr_debug instead of pr_err
If hyper_dmabuf will use this Xen dma-buf solution then I believe those will help as well
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
+ return
-EINVAL;
+ }
+
+ map =dmabuf_exp_alloc_backing_storage(priv, flags, count);@count comes from userspace.
dmabuf_exp_alloc_backing_storageonly checks for it to be >0. Should it be checked for some sane max value?
Quoted 7 lines
Quoted 4 lines
This is not easy as it is hard to tell what could be that max value. For DMA buffers if count is too big then allocation will fail, so need to check for max here (dma_alloc_{xxx} will filter out too big allocations).
OK, that may be sufficient. BTW, I believe there were other loops with @count being the control variable. Please see if a user can pass a bogus value.
Will check for op.count in IOCTLs
Quoted 7 lines
Quoted 2 lines
For Xen balloon allocations I cannot tell what could be that max value neither. Tough question how to limit.
I think in balloon there is also a guarantee (of sorts) that something prior to a loop will fail.
-boris
Thank you,
Oleksandr
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 7/9] xen/gntdev: Implement dma-buf export functionality
Quoted 27 lines · Oleksandr Andrushchenko
Quoted 26 lines · Boris Ostrovsky
Quoted 24 lines · Oleksandr Andrushchenko
Quoted 18 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev-dmabuf.c +6
-0+ +static struct sg_table * +dmabuf_exp_ops_map_dma_buf (struct dma_buf_attachment *attach, + enum dma_data_direction dir) +{ + struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach =
attach->priv;
+ structgntdev_dmabuf*gntdev_dmabuf=attach->dmabuf->priv; + structsg_table*sgt;
+
+ pr_debug("Mapping %d pages for dev %p\n",gntdev_dmabuf->nr_pages,
+attach->dev);
+
+ if (WARN_ON(dir == DMA_NONE || !gntdev_dmabuf_attach))Quoted 1 line
WARN_ON_ONCE. Here and elsewhere.Why? The UAPI may be used by different applications, thus we might lose warnings for some of them. Having
WARN_ONwill show problems for multiple users, not for the first one.
Does this make sense to still useWARN_ON?
Quoted 7 lines
Quoted 6 lines
Just as with
pr_errcall somewhere else the concern here is that userland (which I think is where this is eventually called from?) may intentionally trigger the error, flooding the log.And even this is not directly called from userland there is still a possibility of triggering this error multiple times.
Ok, will use
WARN_ON_ONCE
In fact, is there a reason to use WARN at all? Does this condition indicate some sort of internal inconsistency/error?
-boris
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 7/9] xen/gntdev: Implement dma-buf export functionality
In reply to Oleksandr AndrushchenkoQuoted 27 lines · Oleksandr Andrushchenko
Quoted 26 lines · Boris Ostrovsky
Quoted 24 lines · Oleksandr Andrushchenko
Quoted 18 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev-dmabuf.c +6
-0+ +static struct sg_table * +dmabuf_exp_ops_map_dma_buf (struct dma_buf_attachment *attach, + enum dma_data_direction dir) +{ + struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach =
attach->priv;
+ structgntdev_dmabuf*gntdev_dmabuf=attach->dmabuf->priv; + structsg_table*sgt;
+
+ pr_debug("Mapping %d pages for dev %p\n",gntdev_dmabuf->nr_pages,
+attach->dev);
+
+ if (WARN_ON(dir == DMA_NONE || !gntdev_dmabuf_attach))Quoted 1 line
WARN_ON_ONCE. Here and elsewhere.Why? The UAPI may be used by different applications, thus we might lose warnings for some of them. Having
WARN_ONwill show problems for multiple users, not for the first one.
Does this make sense to still useWARN_ON?
Quoted 7 lines
Quoted 6 lines
Just as with
pr_errcall somewhere else the concern here is that userland (which I think is where this is eventually called from?) may intentionally trigger the error, flooding the log.And even this is not directly called from userland there is still a possibility of triggering this error multiple times.
Ok, will use
WARN_ON_ONCE
In fact, is there a reason to use WARN at all? Does this condition indicate some sort of internal inconsistency/error?
-boris
Re: [PATCH v2 7/9] xen/gntdev: Implement dma-buf export functionality
Quoted 30 lines · Boris Ostrovsky
Quoted 29 lines · Oleksandr Andrushchenko
Quoted 28 lines · Boris Ostrovsky
Quoted 18 lines · Oleksandr Andrushchenko
Quoted 17 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev-dmabuf.c +6
-0+ +static struct sg_table * +dmabuf_exp_ops_map_dma_buf (struct dma_buf_attachment *attach, + enum dma_data_direction dir) +{ + struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach =
attach->priv;
+ structgntdev_dmabuf*gntdev_dmabuf=attach->dmabuf->priv; + structsg_table*sgt;
+
+ pr_debug("Mapping %d pages for dev %p\n",gntdev_dmabuf->nr_pages,
+attach->dev);
+
+ if (WARN_ON(dir == DMA_NONE || !gntdev_dmabuf_attach))Quoted 5 lines
Quoted 1 line
WARN_ON_ONCE. Here and elsewhere.Why? The UAPI may be used by different applications, thus we might lose warnings for some of them. Having
WARN_ONwill show problems for multiple users, not for the first one.
Does this make sense to still useWARN_ON?Just as with
pr_errcall somewhere else the concern here is that userland (which I think is where this is eventually called from?) may intentionally trigger the error, flooding the log.
Quoted 6 lines
Quoted 3 lines
Quoted 2 lines
And even this is not directly called from userland there is still a possibility of triggering this error multiple times.
Ok, will use
WARN_ON_ONCEIn fact, is there a reason to use WARN at all? Does this condition indicate some sort of internal inconsistency/error?
Well, the corresponding errors are anyways handled, so I will remove WARN
Quoted 4 lines
-boris
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 7/9] xen/gntdev: Implement dma-buf export functionality
In reply to Boris OstrovskyQuoted 30 lines · Boris Ostrovsky
Quoted 29 lines · Oleksandr Andrushchenko
Quoted 28 lines · Boris Ostrovsky
Quoted 18 lines · Oleksandr Andrushchenko
Quoted 17 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev-dmabuf.c +6
-0+ +static struct sg_table * +dmabuf_exp_ops_map_dma_buf (struct dma_buf_attachment *attach, + enum dma_data_direction dir) +{ + struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach =
attach->priv;
+ structgntdev_dmabuf*gntdev_dmabuf=attach->dmabuf->priv; + structsg_table*sgt;
+
+ pr_debug("Mapping %d pages for dev %p\n",gntdev_dmabuf->nr_pages,
+attach->dev);
+
+ if (WARN_ON(dir == DMA_NONE || !gntdev_dmabuf_attach))Quoted 5 lines
Quoted 1 line
WARN_ON_ONCE. Here and elsewhere.Why? The UAPI may be used by different applications, thus we might lose warnings for some of them. Having
WARN_ONwill show problems for multiple users, not for the first one.
Does this make sense to still useWARN_ON?Just as with
pr_errcall somewhere else the concern here is that userland (which I think is where this is eventually called from?) may intentionally trigger the error, flooding the log.
Quoted 6 lines
Quoted 3 lines
Quoted 2 lines
And even this is not directly called from userland there is still a possibility of triggering this error multiple times.
Ok, will use
WARN_ON_ONCEIn fact, is there a reason to use WARN at all? Does this condition indicate some sort of internal inconsistency/error?
Well, the corresponding errors are anyways handled, so I will remove WARN
Quoted 4 lines
-boris
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 7/9] xen/gntdev: Implement dma-buf export functionality
In reply to Boris OstrovskyQuoted 25 lines · Boris Ostrovsky
Quoted 18 lines · Oleksandr Andrushchenko
Quoted 17 lines · Boris Ostrovsky
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
drivers/xen/gntdev-dmabuf.c +6
-0+ +static struct sg_table * +dmabuf_exp_ops_map_dma_buf (struct dma_buf_attachment *attach, + enum dma_data_direction dir) +{ + struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach =
attach->priv;
+ structgntdev_dmabuf*gntdev_dmabuf=attach->dmabuf->priv; + structsg_table*sgt;drivers/xen/gntdev-dmabuf.c +5
-0+ + pr_debug("Mapping %d pages for dev %p\n", gntdev_dmabuf->nr_pages, + attach->dev); + + if (WARN_ON(dir == DMA_NONE || !gntdev_dmabuf_attach))Quoted 5 lines
Quoted 1 line
WARN_ON_ONCE. Here and elsewhere.Why? The UAPI may be used by different applications, thus we might lose warnings for some of them. Having
WARN_ONwill show problems for multiple users, not for the first one.
Does this make sense to still useWARN_ON?
Quoted 6 lines
Just as with
pr_errcall somewhere else the concern here is that userland (which I think is where this is eventually called from?) may intentionally trigger the error, flooding the log.And even this is not directly called from userland there is still a possibility of triggering this error multiple times.
Ok, will use WARN_ON_ONCE
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
+
+ if (use_ptemod) {
+pr_err("Cannot provide dma-buf: use_ptemode %d\n", + use_ptemod);
Quoted 7 lines
Quoted 5 lines
Quoted 4 lines
No
pr_errhere please. This can potentially become a DoS vector as it comes directly from ioctl.I would, in fact, revisit other uses of
pr_errin this file.Sure, all of
pr_errcan actually bepr_debug...I'd check even further and see if any prink is needed. I think I saw a couple that were not especially useful.
All those were useful while debugging the code and use-cases, so I would prefer to have them all still available, but as pr_debug instead of pr_err
If hyper_dmabuf will use this Xen dma-buf solution then I believe those will help as well
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
+ return
-EINVAL;
+ }
+
+ map =dmabuf_exp_alloc_backing_storage(priv, flags, count);@count comes from userspace.
dmabuf_exp_alloc_backing_storageonly checks for it to be >0. Should it be checked for some sane max value?
Quoted 7 lines
Quoted 4 lines
This is not easy as it is hard to tell what could be that max value. For DMA buffers if count is too big then allocation will fail, so need to check for max here (dma_alloc_{xxx} will filter out too big allocations).
OK, that may be sufficient. BTW, I believe there were other loops with @count being the control variable. Please see if a user can pass a bogus value.
Will check for op.count in IOCTLs
Quoted 7 lines
Quoted 2 lines
For Xen balloon allocations I cannot tell what could be that max value neither. Tough question how to limit.
I think in balloon there is also a guarantee (of sorts) that something prior to a loop will fail.
-boris
Thank you,
Oleksandr
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 7/9] xen/gntdev: Implement dma-buf export functionality
In reply to Boris OstrovskyQuoted 143 lines · Boris Ostrovsky
Quoted 142 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
1. Create a dma-buf from grant references provided by the foreign domain. By default dma-buf is backed by system memory pages, but by providing
GNTDEV_DMA_FLAG_XXXflags it can also be created as a DMA write-combine/coherent buffer, e.g. allocated with correspondingdma_alloc_xxxAPI.
Export the resulting buffer as a new dma-buf.2. Implement waiting for the dma-buf to be released: block until the dma-buf with the file descriptor provided is released. If within the time-out provided the buffer is not released then
-ETIMEDOUTerror is returned. If the buffer with the file descriptor does not exist or has already been released, then-ENOENTis returned. For valid file descriptors this must not be treated as error.Signed-off-by Oleksandr Andrushchenko <[email protected]>--- drivers/xen/gntdev-dmabuf.c | 393 +++++++++++++++++++++++++++++++++++- drivers/xen/gntdev-dmabuf.h | 9 +- drivers/xen/gntdev.c | 90 ++++++++- 3 files changed, 486 insertions(+), 6 deletions(-)drivers/xen/gntdev-dmabuf.c +94
-1@@ -3,15 +3,58 @@/* * Xen dma-buf functionality for gntdev. * +* DMA buffer implementation is based on drivers/gpu/drm/drm_prime.c. +* * Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. */ +#include <linux/dma-buf.h> #include <linux/slab.h> #include "gntdev-dmabuf.h" +struct gntdev_dmabuf { +struct gntdev_dmabuf_priv *priv; +struct dma_buf *dmabuf; +struct list_head next; +int fd; + +union { +struct { +/* Exported buffers are reference counted. */ +struct kref refcount; + +struct gntdev_priv *priv; +struct grant_map *map; +void (*release)(struct gntdev_priv *priv, +struct grant_map *map); + } exp; + } u; + +/* Number of pages this buffer has. */ +int nr_pages; +/* Pages of this buffer. */ +struct page **pages; +}; + +struct gntdev_dmabuf_wait_obj { +struct list_head next; +struct gntdev_dmabuf *gntdev_dmabuf; +struct completion completion; +}; + +struct gntdev_dmabuf_attachment { +struct sg_table *sgt; +enum dma_data_direction dir; +}; +struct gntdev_dmabuf_priv { -int dummy; +/* List of exported DMA buffers. */ +struct list_head exp_list; +/* List of wait objects. */ +struct list_head exp_wait_list; +/* This is the lock which protects dma_buf_xxx lists. */ +struct mutex lock; };/* ------------------------------------------------------------------ */ @@ -22,19 +65,359 @@ struct gntdev_dmabuf_priv {/* Implementation of wait for exported DMA buffer to be released. */ /* ------------------------------------------------------------------ */ +static void dmabuf_exp_release (struct kref *kref); + +static struct gntdev_dmabuf_wait_obj * +dmabuf_exp_wait_obj_new (struct gntdev_dmabuf_priv *priv, +struct gntdev_dmabuf *gntdev_dmabuf) +{ +struct gntdev_dmabuf_wait_obj *obj; + + obj =kzalloc (sizeof (*obj),GFP_KERNEL ); +if (!obj) +return ERR_PTR (-ENOMEM ); + +init_completion (&obj->completion); + obj->gntdev_dmabuf = gntdev_dmabuf; + +mutex_lock (&priv->lock); +list_add (&obj->next, &priv->exp_wait_list); +/* Put our reference and wait for gntdev_dmabuf's release to fire. */ +kref_put (&gntdev_dmabuf->u.exp.refcount, dmabuf_exp_release); +mutex_unlock (&priv->lock); +return obj; +} + +static void dmabuf_exp_wait_obj_free (struct gntdev_dmabuf_priv *priv, +struct gntdev_dmabuf_wait_obj *obj) +{ +struct gntdev_dmabuf_wait_obj *cur_obj, *q; + +mutex_lock (&priv->lock); +list_for_each_entry_safe (cur_obj, q, &priv->exp_wait_list, next) +if (cur_obj == obj) { +list_del (&obj->next); +kfree (obj); +break ; + } +mutex_unlock (&priv->lock); +} + +static int dmabuf_exp_wait_obj_wait (struct gntdev_dmabuf_wait_obj *obj, +u32 wait_to_ms) +{ +if (wait_for_completion_timeout (&obj->completion, +msecs_to_jiffies (wait_to_ms)) <=0 ) +return -ETIMEDOUT ; + +return 0 ; +} + +static void dmabuf_exp_wait_obj_signal (struct gntdev_dmabuf_priv *priv, +struct gntdev_dmabuf *gntdev_dmabuf)
Quoted 8 lines
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 124
Quoted 7 lines
drivers/xen/gntdev-dmabuf.c +7
-0+{ +struct gntdev_dmabuf_wait_obj *obj, *q; + +list_for_each_entry_safe (obj, q, &priv->exp_wait_list, next) +if (obj->gntdev_dmabuf == gntdev_dmabuf) { +pr_debug ("Found gntdev_dmabuf in the wait list, wake\n" ); +complete_all (&obj->completion);break ?
sure, thank you
Quoted 40 lines
Quoted 40 lines
drivers/xen/gntdev-dmabuf.c +36
-1+ } +} + +static struct gntdev_dmabuf * +dmabuf_exp_wait_obj_get_by_fd (struct gntdev_dmabuf_priv *priv,int fd) +{ +struct gntdev_dmabuf *q, *gntdev_dmabuf, *ret =ERR_PTR (-ENOENT ); + +mutex_lock (&priv->lock); +list_for_each_entry_safe (gntdev_dmabuf, q, &priv->exp_list, next) +if (gntdev_dmabuf->fd == fd) { +pr_debug ("Found gntdev_dmabuf in the wait list\n" ); +kref_get (&gntdev_dmabuf->u.exp.refcount); + ret = gntdev_dmabuf; +break ; + } +mutex_unlock (&priv->lock); +return ret; +} +int gntdev_dmabuf_exp_wait_released (struct gntdev_dmabuf_priv *priv,int fd,int wait_to_ms) { -return -EINVAL ; +struct gntdev_dmabuf *gntdev_dmabuf; +struct gntdev_dmabuf_wait_obj *obj; +int ret; + +pr_debug ("Will wait for dma-buf with fd %d\n" , fd); +/* +* Try to find the DMA buffer: if not found means that +* either the buffer has already been released or file descriptor +* provided is wrong. +*/ + gntdev_dmabuf =dmabuf_exp_wait_obj_get_by_fd (priv, fd); +if (IS_ERR (gntdev_dmabuf)) +return PTR_ERR (gntdev_dmabuf); + +/* +* gntdev_dmabuf still exists and is reference count locked by us now,
Quoted 8 lines
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 169
Quoted 6 lines
drivers/xen/gntdev-dmabuf.c +6
-0+* so prepare to wait: allocate wait object and add it to the wait list, +* so we can find it on release. +*/ + obj =dmabuf_exp_wait_obj_new (priv, gntdev_dmabuf); +if (IS_ERR (obj)) { +pr_err ("Failed to setup wait object, ret %ld\n" ,PTR_ERR (obj));No need for
pr_err. We are out of memory.
Will remove
Quoted 46 lines
Quoted 46 lines
drivers/xen/gntdev-dmabuf.c +39
-0+return PTR_ERR (obj); +} + + ret =dmabuf_exp_wait_obj_wait (obj, wait_to_ms); +dmabuf_exp_wait_obj_free (priv, obj); +return ret; }/* ------------------------------------------------------------------ */ /* DMA buffer export support. */ /* ------------------------------------------------------------------ */ +static struct sg_table * +dmabuf_pages_to_sgt (struct page **pages,unsigned int nr_pages) +{ +struct sg_table *sgt; +int ret; + + sgt =kmalloc (sizeof (*sgt),GFP_KERNEL ); +if (!sgt) { + ret = -ENOMEM ; + goto out; + } + + ret =sg_alloc_table_from_pages (sgt, pages, nr_pages,0 , + nr_pages <<PAGE_SHIFT , +GFP_KERNEL ); +if (ret) + goto out; + +return sgt; + +out: +kfree (sgt); +return ERR_PTR (ret); +} + +static int dmabuf_exp_ops_attach (struct dma_buf *dma_buf, +struct device *target_dev, +struct dma_buf_attachment *attach) +{ +struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach; + + gntdev_dmabuf_attach =kzalloc (sizeof (*gntdev_dmabuf_attach), +GFP_KERNEL );
Quoted 8 lines
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 220
Quoted 6 lines
drivers/xen/gntdev-dmabuf.c +6
-0+if (!gntdev_dmabuf_attach) +return -ENOMEM ; + + gntdev_dmabuf_attach->dir =DMA_NONE ; + attach->priv = gntdev_dmabuf_attach; +/* Might need to pin the pages of the buffer now. */ Who is supposed to pin the pages? The caller?
Ok, as we do not implement .mmap for Xen dma-buf and there is no plan to mmap kernel memory (either ballooned or dma_alloc'ed), then we can remove this comment as there is no need to pin/unpin pages.
Quoted 19 lines
Quoted 19 lines
drivers/xen/gntdev-dmabuf.c +18
-0+return 0 ; +} + +static void dmabuf_exp_ops_detach (struct dma_buf *dma_buf, +struct dma_buf_attachment *attach) +{ +struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach = attach->priv; + +if (gntdev_dmabuf_attach) { +struct sg_table *sgt = gntdev_dmabuf_attach->sgt; + +if (sgt) { +if (gntdev_dmabuf_attach->dir !=DMA_NONE ) +dma_unmap_sg_attrs (attach->dev, sgt->sgl, + sgt->nents, + gntdev_dmabuf_attach->dir, +DMA_ATTR_SKIP_CPU_SYNC ); +sg_free_table (sgt);
Quoted 8 lines
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 245
Quoted 7 lines
drivers/xen/gntdev-dmabuf.c +7
-0+ } + +kfree (sgt); +kfree (gntdev_dmabuf_attach); + attach->priv =NULL ; + } +/* Might need to unpin the pages of the buffer now. */ Same question.
Please see above
Quoted 8 lines
Quoted 8 lines
drivers/xen/gntdev-dmabuf.c +8
-0+} + +static struct sg_table * +dmabuf_exp_ops_map_dma_buf (struct dma_buf_attachment *attach, +enum dma_data_direction dir) +{ +struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach = attach->priv; +struct gntdev_dmabuf *gntdev_dmabuf = attach->dmabuf->priv;
Quoted 8 lines
drivers/xen/gntdev-dmabuf.c struct gntdev_dmabuf_priv { · line 259
Quoted 6 lines
drivers/xen/gntdev-dmabuf.c +6
-0+struct sg_table *sgt; + +pr_debug ("Mapping %d pages for dev %p\n" , gntdev_dmabuf->nr_pages, + attach->dev); + +if (WARN_ON (dir ==DMA_NONE || !gntdev_dmabuf_attach))
WARN_ON_ONCE. Here and elsewhere.
Why? The UAPI may be used by different applications, thus we might lose warnings for some of them. Having WARN_ON will show problems for multiple users, not for the first one.
Does this make sense to still use WARN_ON?
Quoted 266 lines
Quoted 253 lines
drivers/xen/gntdev-dmabuf.c +163
-1+return ERR_PTR (-EINVAL ); + +/* Return the cached mapping when possible. */ +if (gntdev_dmabuf_attach->dir == dir) +return gntdev_dmabuf_attach->sgt; + +/* +* Two mappings with different directions for the same attachment are +* not allowed. +*/ +if (WARN_ON (gntdev_dmabuf_attach->dir !=DMA_NONE )) +return ERR_PTR (-EBUSY ); + + sgt =dmabuf_pages_to_sgt (gntdev_dmabuf->pages, + gntdev_dmabuf->nr_pages); +if (!IS_ERR (sgt)) { +if (!dma_map_sg_attrs (attach->dev, sgt->sgl, sgt->nents, dir, +DMA_ATTR_SKIP_CPU_SYNC )) { +sg_free_table (sgt); +kfree (sgt); + sgt =ERR_PTR (-ENOMEM ); + }else { + gntdev_dmabuf_attach->sgt = sgt; + gntdev_dmabuf_attach->dir = dir; + } + } +if (IS_ERR (sgt)) +pr_err ("Failed to map sg table for dev %p\n" , attach->dev); +return sgt; +} + +static void dmabuf_exp_ops_unmap_dma_buf (struct dma_buf_attachment *attach, +struct sg_table *sgt, +enum dma_data_direction dir) +{ +/* Not implemented. The unmap is done at dmabuf_exp_ops_detach(). */ +} + +static void dmabuf_exp_release (struct kref *kref) +{ +struct gntdev_dmabuf *gntdev_dmabuf = + container_of(kref, struct gntdev_dmabuf, u.exp.refcount); + +dmabuf_exp_wait_obj_signal (gntdev_dmabuf->priv, gntdev_dmabuf); +list_del (&gntdev_dmabuf->next); +kfree (gntdev_dmabuf); +} + +static void dmabuf_exp_ops_release (struct dma_buf *dma_buf) +{ +struct gntdev_dmabuf *gntdev_dmabuf = dma_buf->priv; +struct gntdev_dmabuf_priv *priv = gntdev_dmabuf->priv; + + gntdev_dmabuf->u.exp.release (gntdev_dmabuf->u.exp.priv, + gntdev_dmabuf->u.exp.map); +mutex_lock (&priv->lock); +kref_put (&gntdev_dmabuf->u.exp.refcount, dmabuf_exp_release); +mutex_unlock (&priv->lock); +} + +static void *dmabuf_exp_ops_kmap_atomic (struct dma_buf *dma_buf, +unsigned long page_num) +{ +/* Not implemented. */ +return NULL ; +} + +static void dmabuf_exp_ops_kunmap_atomic (struct dma_buf *dma_buf, +unsigned long page_num,void *addr) +{ +/* Not implemented. */ +} + +static void *dmabuf_exp_ops_kmap (struct dma_buf *dma_buf, +unsigned long page_num) +{ +/* Not implemented. */ +return NULL ; +} + +static void dmabuf_exp_ops_kunmap (struct dma_buf *dma_buf, +unsigned long page_num,void *addr) +{ +/* Not implemented. */ +} + +static int dmabuf_exp_ops_mmap (struct dma_buf *dma_buf, +struct vm_area_struct *vma) +{ +/* Not implemented. */ +return 0 ; +} + +static const struct dma_buf_ops dmabuf_exp_ops = { + .attach = dmabuf_exp_ops_attach, + .detach = dmabuf_exp_ops_detach, + .map_dma_buf = dmabuf_exp_ops_map_dma_buf, + .unmap_dma_buf = dmabuf_exp_ops_unmap_dma_buf, + .release = dmabuf_exp_ops_release, + .map = dmabuf_exp_ops_kmap, + .map_atomic = dmabuf_exp_ops_kmap_atomic, + .unmap = dmabuf_exp_ops_kunmap, + .unmap_atomic = dmabuf_exp_ops_kunmap_atomic, + .mmap = dmabuf_exp_ops_mmap, +}; +int gntdev_dmabuf_exp_from_pages (struct gntdev_dmabuf_export_args *args) { -return -EINVAL ; +DEFINE_DMA_BUF_EXPORT_INFO (exp_info); +struct gntdev_dmabuf *gntdev_dmabuf; +int ret =0 ; + + gntdev_dmabuf =kzalloc (sizeof (*gntdev_dmabuf),GFP_KERNEL ); +if (!gntdev_dmabuf) +return -ENOMEM ; + +kref_init (&gntdev_dmabuf->u.exp.refcount); + + gntdev_dmabuf->priv = args->dmabuf_priv; + gntdev_dmabuf->nr_pages = args->count; + gntdev_dmabuf->pages = args->pages; + gntdev_dmabuf->u.exp.priv = args->priv; + gntdev_dmabuf->u.exp.map = args->map; + gntdev_dmabuf->u.exp.release = args->release; + + exp_info.exp_name =KBUILD_MODNAME ; +if (args->dev->driver && args->dev->driver->owner) + exp_info.owner = args->dev->driver->owner; +else + exp_info.owner =THIS_MODULE ; + exp_info.ops = &dmabuf_exp_ops; + exp_info.size = args->count <<PAGE_SHIFT ; + exp_info.flags =O_RDWR ; + exp_info.priv = gntdev_dmabuf; + + gntdev_dmabuf->dmabuf =dma_buf_export (&exp_info); +if (IS_ERR (gntdev_dmabuf->dmabuf)) { + ret =PTR_ERR (gntdev_dmabuf->dmabuf); + gntdev_dmabuf->dmabuf =NULL ; + goto fail; + } + + ret =dma_buf_fd (gntdev_dmabuf->dmabuf,O_CLOEXEC ); +if (ret <0 ) + goto fail; + + gntdev_dmabuf->fd = ret; + args->fd = ret; + +pr_debug ("Exporting DMA buffer with fd %d\n" , ret); + +mutex_lock (&args->dmabuf_priv->lock); +list_add (&gntdev_dmabuf->next, &args->dmabuf_priv->exp_list); +mutex_unlock (&args->dmabuf_priv->lock); +return 0 ; + +fail: +if (gntdev_dmabuf->dmabuf) +dma_buf_put (gntdev_dmabuf->dmabuf); +kfree (gntdev_dmabuf); +return ret; }/* ------------------------------------------------------------------ */ @@ -66,6 +449,10 @@ struct gntdev_dmabuf_priv *gntdev_dmabuf_init(void)if (!priv)return ERR_PTR (-ENOMEM ); +mutex_init (&priv->lock); +INIT_LIST_HEAD (&priv->exp_list); +INIT_LIST_HEAD (&priv->exp_wait_list); +return priv; }drivers/xen/gntdev-dmabuf.h +8
-1@@ -18,7 +18,14 @@ struct gntdev_dmabuf;struct device ;struct gntdev_dmabuf_export_args { -int dummy; +struct gntdev_priv *priv; +struct grant_map *map; +void (*release)(struct gntdev_priv *priv,struct grant_map *map); +struct gntdev_dmabuf_priv *dmabuf_priv; +struct device *dev; +int count; +struct page **pages; +u32 fd; };struct gntdev_dmabuf_priv *gntdev_dmabuf_init (void );drivers/xen/gntdev.c +37
-1@@ -319,6 +319,16 @@ static void gntdev_put_map(struct gntdev_priv *priv, struct grant_map *map)gntdev_free_map (map); } +#ifdef CONFIG_XEN_GNTDEV_DMABUF +static void gntdev_remove_map (struct gntdev_priv *priv,struct grant_map *map) +{ +mutex_lock (&priv->lock); +list_del (&map->next); +gntdev_put_map (NULL /* already removed */ , map); +mutex_unlock (&priv->lock); +} +#endif +/* ------------------------------------------------------------------ */ static int find_grant_ptes(pte_t *pte, pgtable_t token,@@ -1063,12 +1073,88 @@ static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u)/* DMA buffer export support. */ /* ------------------------------------------------------------------ */ +static struct grant_map * +dmabuf_exp_alloc_backing_storage (struct gntdev_priv *priv,int dmabuf_flags, +int count) +{ +struct grant_map *map; + +if (unlikely (count <=0 )) +return ERR_PTR (-EINVAL ); + +if ((dmabuf_flags &GNTDEV_DMA_FLAG_WC ) && + (dmabuf_flags &GNTDEV_DMA_FLAG_COHERENT )) { +pr_err ("Wrong dma-buf flags: either WC or coherent, not both\n" ); +return ERR_PTR (-EINVAL ); + } + + map =gntdev_alloc_map (priv, count, dmabuf_flags); +if (!map) +return ERR_PTR (-ENOMEM ); + +if (unlikely (atomic_add_return (count, &pages_mapped) > limit)) { +pr_err ("can't map: over limit\n" ); +gntdev_put_map (NULL , map); +return ERR_PTR (-ENOMEM ); + } +return map; +} +int gntdev_dmabuf_exp_from_refs (struct gntdev_priv *priv,int flags,int count,u32 domid,u32 *refs,u32 *fd) { -/* XXX: this will need to work with gntdev's map, so leave it here. */ drivers/xen/gntdev.c static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) · line 1114
Quoted 10 lines
drivers/xen/gntdev.c +8
-1+struct grant_map *map; +struct gntdev_dmabuf_export_args args; +int i, ret; + *fd =-1 ; -return -EINVAL ; + +if (use_ptemod) { +pr_err ("Cannot provide dma-buf: use_ptemode %d\n" , + use_ptemod);No
pr_errhere please. This can potentially become a DoS vector as it comes directly from ioctl.
Quoted 1 line
I would, in fact, revisit other uses of
pr_errin this file.
Sure, all of pr_err can actually be pr_debug...
Quoted 7 lines
drivers/xen/gntdev.c static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) · line 1118
Quoted 4 lines
drivers/xen/gntdev.c +4
-0+return -EINVAL ; + } + + map =dmabuf_exp_alloc_backing_storage (priv, flags, count);@count comes from userspace.
dmabuf_exp_alloc_backing_storageonly checks for it to be >0. Should it be checked for some sane max value?
This is not easy as it is hard to tell what could be that max value. For DMA buffers if count is too big then allocation will fail, so need to check for max here (dma_alloc_{xxx} will filter out too big allocations).
For Xen balloon allocations I cannot tell what could be that max value neither. Tough question how to limit.
Quoted 2 lines
-boris
Thank you,
Oleksandr
Quoted 41 lines
Quoted 41 lines
drivers/xen/gntdev.c +39
-0+if (IS_ERR (map)) +return PTR_ERR (map); + +for (i =0 ; i < count; i++) { + map->grants[i].domid = domid; + map->grants[i].ref = refs[i]; + } + +mutex_lock (&priv->lock); +gntdev_add_map (priv, map); +mutex_unlock (&priv->lock); + + map->flags |= GNTMAP_host_map; +#if defined(CONFIG_X86 ) + map->flags |= GNTMAP_device_map; +#endif + + ret =map_grant_pages (map); +if (ret <0 ) + goto out; + + args.priv = priv; + args.map = map; + args.release = gntdev_remove_map; + args.dev = priv->dma_dev; + args.dmabuf_priv = priv->dmabuf_priv; + args.count = map->count; + args.pages = map->pages; + + ret =gntdev_dmabuf_exp_from_pages (&args); +if (ret <0 ) + goto out; + + *fd = args.fd; +return 0 ; + +out: +gntdev_remove_map (priv, map); +return ret; }
Quoted 1 line
drivers/xen/gntdev.c static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) · line 1160
Quoted 1 line
drivers/xen/gntdev.c +0
-0/* ------------------------------------------------------------------ */
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v2 7/9 xen/gntdev: Implement dma-buf export functionality
In reply to Oleksandr AndrushchenkoFrom: Oleksandr Andrushchenko <[email protected]>
1. Create a dma-buf from grant references provided by the foreign domain. By default dma-buf is backed by system memory pages, but by providing GNTDEV_DMA_FLAG_XXX flags it can also be created as a DMA write-combine/coherent buffer, e.g. allocated with corresponding dma_alloc_xxx API.
Export the resulting buffer as a new dma-buf.
2. Implement waiting for the dma-buf to be released: block until the dma-buf with the file descriptor provided is released.
If within the time-out provided the buffer is not released then -ETIMEDOUT error is returned. If the buffer with the file descriptor does not exist or has already been released, then -ENOENT is returned. For valid file descriptors this must not be treated as error.
--- drivers/xen/gntdev-dmabuf.c | 393 +++++++++++++++++++++++++++++++++++- drivers/xen/gntdev-dmabuf.h | 9 +- drivers/xen/gntdev.c | 90 ++++++++- 3 files changed, 486 insertions(+), 6 deletions(-)
drivers/xen/gntdev-dmabuf.c +390 -3
@@ -3,15 +3,58 @@/* * Xen dma-buf functionality for gntdev. * +* DMA buffer implementation is based on drivers/gpu/drm/drm_prime.c. +* * Copyright (c) 2018 Oleksandr Andrushchenko, EPAM Systems Inc. */ +#include <linux/dma-buf.h> #include <linux/slab.h> #include "gntdev-dmabuf.h" +struct gntdev_dmabuf { +struct gntdev_dmabuf_priv *priv; +struct dma_buf *dmabuf; +struct list_head next; +int fd; + +union { +struct { +/* Exported buffers are reference counted. */ +struct kref refcount; + +struct gntdev_priv *priv; +struct grant_map *map; +void (*release)(struct gntdev_priv *priv, +struct grant_map *map); + } exp; + } u; + +/* Number of pages this buffer has. */ +int nr_pages; +/* Pages of this buffer. */ +struct page **pages; +}; + +struct gntdev_dmabuf_wait_obj { +struct list_head next; +struct gntdev_dmabuf *gntdev_dmabuf; +struct completion completion; +}; + +struct gntdev_dmabuf_attachment { +struct sg_table *sgt; +enum dma_data_direction dir; +}; +struct gntdev_dmabuf_priv { -int dummy; +/* List of exported DMA buffers. */ +struct list_head exp_list; +/* List of wait objects. */ +struct list_head exp_wait_list; +/* This is the lock which protects dma_buf_xxx lists. */ +struct mutex lock; };/* ------------------------------------------------------------------ */
@@ -22,19 +65,359 @@ struct gntdev_dmabuf_priv {/* Implementation of wait for exported DMA buffer to be released. */ /* ------------------------------------------------------------------ */ +static void dmabuf_exp_release (struct kref *kref); + +static struct gntdev_dmabuf_wait_obj * +dmabuf_exp_wait_obj_new (struct gntdev_dmabuf_priv *priv, +struct gntdev_dmabuf *gntdev_dmabuf) +{ +struct gntdev_dmabuf_wait_obj *obj; + + obj =kzalloc (sizeof (*obj),GFP_KERNEL ); +if (!obj) +return ERR_PTR (-ENOMEM ); + +init_completion (&obj->completion); + obj->gntdev_dmabuf = gntdev_dmabuf; + +mutex_lock (&priv->lock); +list_add (&obj->next, &priv->exp_wait_list); +/* Put our reference and wait for gntdev_dmabuf's release to fire. */ +kref_put (&gntdev_dmabuf->u.exp.refcount, dmabuf_exp_release); +mutex_unlock (&priv->lock); +return obj; +} + +static void dmabuf_exp_wait_obj_free (struct gntdev_dmabuf_priv *priv, +struct gntdev_dmabuf_wait_obj *obj) +{ +struct gntdev_dmabuf_wait_obj *cur_obj, *q; + +mutex_lock (&priv->lock); +list_for_each_entry_safe (cur_obj, q, &priv->exp_wait_list, next) +if (cur_obj == obj) { +list_del (&obj->next); +kfree (obj); +break ; + } +mutex_unlock (&priv->lock); +} + +static int dmabuf_exp_wait_obj_wait (struct gntdev_dmabuf_wait_obj *obj, +u32 wait_to_ms) +{ +if (wait_for_completion_timeout (&obj->completion, +msecs_to_jiffies (wait_to_ms)) <=0 ) +return -ETIMEDOUT ; + +return 0 ; +} + +static void dmabuf_exp_wait_obj_signal (struct gntdev_dmabuf_priv *priv, +struct gntdev_dmabuf *gntdev_dmabuf) +{ +struct gntdev_dmabuf_wait_obj *obj, *q; + +list_for_each_entry_safe (obj, q, &priv->exp_wait_list, next) +if (obj->gntdev_dmabuf == gntdev_dmabuf) { +pr_debug ("Found gntdev_dmabuf in the wait list, wake\n" ); +complete_all (&obj->completion); + } +} + +static struct gntdev_dmabuf * +dmabuf_exp_wait_obj_get_by_fd (struct gntdev_dmabuf_priv *priv,int fd) +{ +struct gntdev_dmabuf *q, *gntdev_dmabuf, *ret =ERR_PTR (-ENOENT ); + +mutex_lock (&priv->lock); +list_for_each_entry_safe (gntdev_dmabuf, q, &priv->exp_list, next) +if (gntdev_dmabuf->fd == fd) { +pr_debug ("Found gntdev_dmabuf in the wait list\n" ); +kref_get (&gntdev_dmabuf->u.exp.refcount); + ret = gntdev_dmabuf; +break ; + } +mutex_unlock (&priv->lock); +return ret; +} +int gntdev_dmabuf_exp_wait_released (struct gntdev_dmabuf_priv *priv,int fd,int wait_to_ms) { -return -EINVAL ; +struct gntdev_dmabuf *gntdev_dmabuf; +struct gntdev_dmabuf_wait_obj *obj; +int ret; + +pr_debug ("Will wait for dma-buf with fd %d\n" , fd); +/* +* Try to find the DMA buffer: if not found means that +* either the buffer has already been released or file descriptor +* provided is wrong. +*/ + gntdev_dmabuf =dmabuf_exp_wait_obj_get_by_fd (priv, fd); +if (IS_ERR (gntdev_dmabuf)) +return PTR_ERR (gntdev_dmabuf); + +/* +* gntdev_dmabuf still exists and is reference count locked by us now, +* so prepare to wait: allocate wait object and add it to the wait list, +* so we can find it on release. +*/ + obj =dmabuf_exp_wait_obj_new (priv, gntdev_dmabuf); +if (IS_ERR (obj)) { +pr_err ("Failed to setup wait object, ret %ld\n" ,PTR_ERR (obj)); +return PTR_ERR (obj); +} + + ret =dmabuf_exp_wait_obj_wait (obj, wait_to_ms); +dmabuf_exp_wait_obj_free (priv, obj); +return ret; }/* ------------------------------------------------------------------ */ /* DMA buffer export support. */ /* ------------------------------------------------------------------ */ +static struct sg_table * +dmabuf_pages_to_sgt (struct page **pages,unsigned int nr_pages) +{ +struct sg_table *sgt; +int ret; + + sgt =kmalloc (sizeof (*sgt),GFP_KERNEL ); +if (!sgt) { + ret = -ENOMEM ; + goto out; + } + + ret =sg_alloc_table_from_pages (sgt, pages, nr_pages,0 , + nr_pages <<PAGE_SHIFT , +GFP_KERNEL ); +if (ret) + goto out; + +return sgt; + +out: +kfree (sgt); +return ERR_PTR (ret); +} + +static int dmabuf_exp_ops_attach (struct dma_buf *dma_buf, +struct device *target_dev, +struct dma_buf_attachment *attach) +{ +struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach; + + gntdev_dmabuf_attach =kzalloc (sizeof (*gntdev_dmabuf_attach), +GFP_KERNEL ); +if (!gntdev_dmabuf_attach) +return -ENOMEM ; + + gntdev_dmabuf_attach->dir =DMA_NONE ; + attach->priv = gntdev_dmabuf_attach; +/* Might need to pin the pages of the buffer now. */ +return 0 ; +} + +static void dmabuf_exp_ops_detach (struct dma_buf *dma_buf, +struct dma_buf_attachment *attach) +{ +struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach = attach->priv; + +if (gntdev_dmabuf_attach) { +struct sg_table *sgt = gntdev_dmabuf_attach->sgt; + +if (sgt) { +if (gntdev_dmabuf_attach->dir !=DMA_NONE ) +dma_unmap_sg_attrs (attach->dev, sgt->sgl, + sgt->nents, + gntdev_dmabuf_attach->dir, +DMA_ATTR_SKIP_CPU_SYNC ); +sg_free_table (sgt); + } + +kfree (sgt); +kfree (gntdev_dmabuf_attach); + attach->priv =NULL ; + } +/* Might need to unpin the pages of the buffer now. */ +} + +static struct sg_table * +dmabuf_exp_ops_map_dma_buf (struct dma_buf_attachment *attach, +enum dma_data_direction dir) +{ +struct gntdev_dmabuf_attachment *gntdev_dmabuf_attach = attach->priv; +struct gntdev_dmabuf *gntdev_dmabuf = attach->dmabuf->priv; +struct sg_table *sgt; + +pr_debug ("Mapping %d pages for dev %p\n" , gntdev_dmabuf->nr_pages, + attach->dev); + +if (WARN_ON (dir ==DMA_NONE || !gntdev_dmabuf_attach)) +return ERR_PTR (-EINVAL ); + +/* Return the cached mapping when possible. */ +if (gntdev_dmabuf_attach->dir == dir) +return gntdev_dmabuf_attach->sgt; + +/* +* Two mappings with different directions for the same attachment are +* not allowed. +*/ +if (WARN_ON (gntdev_dmabuf_attach->dir !=DMA_NONE )) +return ERR_PTR (-EBUSY ); + + sgt =dmabuf_pages_to_sgt (gntdev_dmabuf->pages, + gntdev_dmabuf->nr_pages); +if (!IS_ERR (sgt)) { +if (!dma_map_sg_attrs (attach->dev, sgt->sgl, sgt->nents, dir, +DMA_ATTR_SKIP_CPU_SYNC )) { +sg_free_table (sgt); +kfree (sgt); + sgt =ERR_PTR (-ENOMEM ); + }else { + gntdev_dmabuf_attach->sgt = sgt; + gntdev_dmabuf_attach->dir = dir; + } + } +if (IS_ERR (sgt)) +pr_err ("Failed to map sg table for dev %p\n" , attach->dev); +return sgt; +} + +static void dmabuf_exp_ops_unmap_dma_buf (struct dma_buf_attachment *attach, +struct sg_table *sgt, +enum dma_data_direction dir) +{ +/* Not implemented. The unmap is done at dmabuf_exp_ops_detach(). */ +} + +static void dmabuf_exp_release (struct kref *kref) +{ +struct gntdev_dmabuf *gntdev_dmabuf = + container_of(kref, struct gntdev_dmabuf, u.exp.refcount); + +dmabuf_exp_wait_obj_signal (gntdev_dmabuf->priv, gntdev_dmabuf); +list_del (&gntdev_dmabuf->next); +kfree (gntdev_dmabuf); +} + +static void dmabuf_exp_ops_release (struct dma_buf *dma_buf) +{ +struct gntdev_dmabuf *gntdev_dmabuf = dma_buf->priv; +struct gntdev_dmabuf_priv *priv = gntdev_dmabuf->priv; + + gntdev_dmabuf->u.exp.release (gntdev_dmabuf->u.exp.priv, + gntdev_dmabuf->u.exp.map); +mutex_lock (&priv->lock); +kref_put (&gntdev_dmabuf->u.exp.refcount, dmabuf_exp_release); +mutex_unlock (&priv->lock); +} + +static void *dmabuf_exp_ops_kmap_atomic (struct dma_buf *dma_buf, +unsigned long page_num) +{ +/* Not implemented. */ +return NULL ; +} + +static void dmabuf_exp_ops_kunmap_atomic (struct dma_buf *dma_buf, +unsigned long page_num,void *addr) +{ +/* Not implemented. */ +} + +static void *dmabuf_exp_ops_kmap (struct dma_buf *dma_buf, +unsigned long page_num) +{ +/* Not implemented. */ +return NULL ; +} + +static void dmabuf_exp_ops_kunmap (struct dma_buf *dma_buf, +unsigned long page_num,void *addr) +{ +/* Not implemented. */ +} + +static int dmabuf_exp_ops_mmap (struct dma_buf *dma_buf, +struct vm_area_struct *vma) +{ +/* Not implemented. */ +return 0 ; +} + +static const struct dma_buf_ops dmabuf_exp_ops = { + .attach = dmabuf_exp_ops_attach, + .detach = dmabuf_exp_ops_detach, + .map_dma_buf = dmabuf_exp_ops_map_dma_buf, + .unmap_dma_buf = dmabuf_exp_ops_unmap_dma_buf, + .release = dmabuf_exp_ops_release, + .map = dmabuf_exp_ops_kmap, + .map_atomic = dmabuf_exp_ops_kmap_atomic, + .unmap = dmabuf_exp_ops_kunmap, + .unmap_atomic = dmabuf_exp_ops_kunmap_atomic, + .mmap = dmabuf_exp_ops_mmap, +}; +int gntdev_dmabuf_exp_from_pages (struct gntdev_dmabuf_export_args *args) { -return -EINVAL ; +DEFINE_DMA_BUF_EXPORT_INFO (exp_info); +struct gntdev_dmabuf *gntdev_dmabuf; +int ret =0 ; + + gntdev_dmabuf =kzalloc (sizeof (*gntdev_dmabuf),GFP_KERNEL ); +if (!gntdev_dmabuf) +return -ENOMEM ; + +kref_init (&gntdev_dmabuf->u.exp.refcount); + + gntdev_dmabuf->priv = args->dmabuf_priv; + gntdev_dmabuf->nr_pages = args->count; + gntdev_dmabuf->pages = args->pages; + gntdev_dmabuf->u.exp.priv = args->priv; + gntdev_dmabuf->u.exp.map = args->map; + gntdev_dmabuf->u.exp.release = args->release; + + exp_info.exp_name =KBUILD_MODNAME ; +if (args->dev->driver && args->dev->driver->owner) + exp_info.owner = args->dev->driver->owner; +else + exp_info.owner =THIS_MODULE ; + exp_info.ops = &dmabuf_exp_ops; + exp_info.size = args->count <<PAGE_SHIFT ; + exp_info.flags =O_RDWR ; + exp_info.priv = gntdev_dmabuf; + + gntdev_dmabuf->dmabuf =dma_buf_export (&exp_info); +if (IS_ERR (gntdev_dmabuf->dmabuf)) { + ret =PTR_ERR (gntdev_dmabuf->dmabuf); + gntdev_dmabuf->dmabuf =NULL ; + goto fail; + } + + ret =dma_buf_fd (gntdev_dmabuf->dmabuf,O_CLOEXEC ); +if (ret <0 ) + goto fail; + + gntdev_dmabuf->fd = ret; + args->fd = ret; + +pr_debug ("Exporting DMA buffer with fd %d\n" , ret); + +mutex_lock (&args->dmabuf_priv->lock); +list_add (&gntdev_dmabuf->next, &args->dmabuf_priv->exp_list); +mutex_unlock (&args->dmabuf_priv->lock); +return 0 ; + +fail: +if (gntdev_dmabuf->dmabuf) +dma_buf_put (gntdev_dmabuf->dmabuf); +kfree (gntdev_dmabuf); +return ret; }/* ------------------------------------------------------------------ */
@@ -66,6 +449,10 @@ struct gntdev_dmabuf_priv *gntdev_dmabuf_init(void)if (!priv)return ERR_PTR (-ENOMEM ); +mutex_init (&priv->lock); +INIT_LIST_HEAD (&priv->exp_list); +INIT_LIST_HEAD (&priv->exp_wait_list); +return priv; }
drivers/xen/gntdev-dmabuf.h +8 -1
@@ -18,7 +18,14 @@ struct gntdev_dmabuf;struct device ;struct gntdev_dmabuf_export_args { -int dummy; +struct gntdev_priv *priv; +struct grant_map *map; +void (*release)(struct gntdev_priv *priv,struct grant_map *map); +struct gntdev_dmabuf_priv *dmabuf_priv; +struct device *dev; +int count; +struct page **pages; +u32 fd; };struct gntdev_dmabuf_priv *gntdev_dmabuf_init (void );
drivers/xen/gntdev.c +88 -2
106 lines not on this page · raw message
Signature · 7 lines
2.17.0 _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v2 8/9 xen/gntdev: Implement dma-buf import functionality
In reply to Oleksandr AndrushchenkoFrom: Oleksandr Andrushchenko <[email protected]>
1. Import a dma-buf with the file descriptor provided and export granted references to the pages of that dma-buf into the array of grant references.
2. Add API to close all references to an imported buffer, so it can be released by the owner. This is only valid for buffers created with IOCTL_GNTDEV_DMABUF_IMP_TO_REFS.
--- drivers/xen/gntdev-dmabuf.c | 243 +++++++++++++++++++++++++++++++++++- 1 file changed, 241 insertions(+), 2 deletions(-)
drivers/xen/gntdev-dmabuf.c +241 -2
@@ -11,8 +11,20 @@#include <linux/dma-buf.h> #include <linux/slab.h> +#include <xen/xen.h> +#include <xen/grant_table.h> +#include "gntdev-dmabuf.h" +#ifndef GRANT_INVALID_REF +/* +* Note on usage of grant reference 0 as invalid grant reference: +* grant reference 0 is valid, but never exposed to a driver, +* because of the fact it is already in use/reserved by the PV console. +*/ +#define GRANT_INVALID_REF 0 +#endif +struct gntdev_dmabuf {struct gntdev_dmabuf_priv *priv;struct dma_buf *dmabuf;
@@ -29,6 +41,14 @@ struct gntdev_dmabuf {void (*release)(struct gntdev_priv *priv,struct grant_map *map); } exp; +struct { +/* Granted references of the imported buffer. */ +grant_ref_t *refs; +/* Scatter-gather table of the imported buffer. */ +struct sg_table *sgt; +/* dma-buf attachment of the imported buffer. */ +struct dma_buf_attachment *attach; + } imp; } u;/* Number of pages this buffer has. */
@@ -53,6 +73,8 @@ struct gntdev_dmabuf_priv {struct list_head exp_list;/* List of wait objects. */ struct list_head exp_wait_list; +/* List of imported DMA buffers. */ +struct list_head imp_list;/* This is the lock which protects dma_buf_xxx lists. */ struct mutex lock; };
@@ -424,21 +446,237 @@ int gntdev_dmabuf_exp_from_pages(struct gntdev_dmabuf_export_args *args)/* DMA buffer import support. */ /* ------------------------------------------------------------------ */ +static int +dmabuf_imp_grant_foreign_access (struct page **pages,u32 *refs, +int count,int domid) +{ +grant_ref_t priv_gref_head; +int i, ret; + + ret =gnttab_alloc_grant_references (count, &priv_gref_head); +if (ret <0 ) { +pr_err ("Cannot allocate grant references, ret %d\n" , ret); +return ret; + } + +for (i =0 ; i < count; i++) { +int cur_ref; + + cur_ref =gnttab_claim_grant_reference (&priv_gref_head); +if (cur_ref <0 ) { + ret = cur_ref; +pr_err ("Cannot claim grant reference, ret %d\n" , ret); + goto out; + } + +gnttab_grant_foreign_access_ref (cur_ref, domid, +xen_page_to_gfn (pages[i]),0 ); + refs[i] = cur_ref; + } + + ret =0 ; + +out: +gnttab_free_grant_references (priv_gref_head); +return ret; +} + +static void dmabuf_imp_end_foreign_access (u32 *refs,int count) +{ +int i; + +for (i =0 ; i < count; i++) +if (refs[i] !=GRANT_INVALID_REF ) +gnttab_end_foreign_access (refs[i],0 ,0UL ); +} + +static void dmabuf_imp_free_storage (struct gntdev_dmabuf *gntdev_dmabuf) +{ +kfree (gntdev_dmabuf->pages); +kfree (gntdev_dmabuf->u.imp.refs); +kfree (gntdev_dmabuf); +} + +static struct gntdev_dmabuf *dmabuf_imp_alloc_storage (int count) +{ +struct gntdev_dmabuf *gntdev_dmabuf; +int i; + + gntdev_dmabuf =kzalloc (sizeof (*gntdev_dmabuf),GFP_KERNEL ); +if (!gntdev_dmabuf) + goto fail; + + gntdev_dmabuf->u.imp.refs =kcalloc (count, +sizeof (gntdev_dmabuf->u.imp.refs[0 ]), +GFP_KERNEL ); +if (!gntdev_dmabuf->u.imp.refs) + goto fail; + + gntdev_dmabuf->pages =kcalloc (count, +sizeof (gntdev_dmabuf->pages[0 ]), +GFP_KERNEL ); +if (!gntdev_dmabuf->pages) + goto fail; + + gntdev_dmabuf->nr_pages = count; + +for (i =0 ; i < count; i++) + gntdev_dmabuf->u.imp.refs[i] =GRANT_INVALID_REF ; + +return gntdev_dmabuf; + +fail: +dmabuf_imp_free_storage (gntdev_dmabuf); +return ERR_PTR (-ENOMEM ); +} +struct gntdev_dmabuf *gntdev_dmabuf_imp_to_refs (struct gntdev_dmabuf_priv *priv,struct device *dev,int fd,int count,int domid) { -return ERR_PTR (-ENOMEM ); +struct gntdev_dmabuf *gntdev_dmabuf, *ret; +struct dma_buf *dma_buf; +struct dma_buf_attachment *attach; +struct sg_table *sgt; +struct sg_page_iter sg_iter; +int i; + + dma_buf =dma_buf_get (fd); +if (IS_ERR (dma_buf)) +return ERR_CAST (dma_buf); + + gntdev_dmabuf =dmabuf_imp_alloc_storage (count); +if (IS_ERR (gntdev_dmabuf)) { + ret = gntdev_dmabuf; + goto fail_put; +} + + gntdev_dmabuf->priv = priv; + gntdev_dmabuf->fd = fd; + + attach =dma_buf_attach (dma_buf, dev); +if (IS_ERR (attach)) { + ret =ERR_CAST (attach); + goto fail_free_obj; + } + + gntdev_dmabuf->u.imp.attach = attach; + + sgt =dma_buf_map_attachment (attach,DMA_BIDIRECTIONAL ); +if (IS_ERR (sgt)) { + ret =ERR_CAST (sgt); + goto fail_detach; + } + +/* Check number of pages that imported buffer has. */ +if (attach->dmabuf->size != gntdev_dmabuf->nr_pages <<PAGE_SHIFT ) { + ret =ERR_PTR (-EINVAL ); +pr_err ("DMA buffer has %zu pages, user-space expects %d\n" , + attach->dmabuf->size, gntdev_dmabuf->nr_pages); + goto fail_unmap; + } + + gntdev_dmabuf->u.imp.sgt = sgt; + +/* Now convert sgt to array of pages and check for page validity. */ + i =0 ; +for_each_sg_page (sgt->sgl, &sg_iter, sgt->nents,0 ) { +struct page *page =sg_page_iter_page (&sg_iter); +/* +* Check if page is valid: this can happen if we are given +* a page from VRAM or other resources which are not backed +* by a struct page. +*/ +if (!pfn_valid (page_to_pfn (page))) { + ret =ERR_PTR (-EINVAL ); + goto fail_unmap; + } + + gntdev_dmabuf->pages[i++] = page; + } + + ret =ERR_PTR (dmabuf_imp_grant_foreign_access (gntdev_dmabuf->pages, + gntdev_dmabuf->u.imp.refs, + count, domid)); +if (IS_ERR (ret)) + goto fail_end_access; + +pr_debug ("Imported DMA buffer with fd %d\n" , fd); + +mutex_lock (&priv->lock); +list_add (&gntdev_dmabuf->next, &priv->imp_list); +mutex_unlock (&priv->lock); + +return gntdev_dmabuf; + +fail_end_access: +dmabuf_imp_end_foreign_access (gntdev_dmabuf->u.imp.refs, count); +fail_unmap: +dma_buf_unmap_attachment (attach, sgt,DMA_BIDIRECTIONAL ); +fail_detach: +dma_buf_detach (dma_buf, attach); +fail_free_obj: +dmabuf_imp_free_storage (gntdev_dmabuf); +fail_put: +dma_buf_put (dma_buf); +return ret; }u32 *gntdev_dmabuf_imp_get_refs (struct gntdev_dmabuf *gntdev_dmabuf) { +if (gntdev_dmabuf) +return gntdev_dmabuf->u.imp.refs; +return NULL ; } +/* +* Find the hyper dma-buf by its file descriptor and remove +* it from the buffer's list. +*/ +static struct gntdev_dmabuf * +dmabuf_imp_find_unlink (struct gntdev_dmabuf_priv *priv,int fd) +{ +struct gntdev_dmabuf *q, *gntdev_dmabuf, *ret =ERR_PTR (-ENOENT ); + +mutex_lock (&priv->lock); +list_for_each_entry_safe (gntdev_dmabuf, q, &priv->imp_list, next) { +if (gntdev_dmabuf->fd == fd) { +pr_debug ("Found gntdev_dmabuf in the import list\n" ); + ret = gntdev_dmabuf; +list_del (&gntdev_dmabuf->next); +break ; + } + } +mutex_unlock (&priv->lock); +return ret; +} +int gntdev_dmabuf_imp_release (struct gntdev_dmabuf_priv *priv,u32 fd) { -return -EINVAL ; +struct gntdev_dmabuf *gntdev_dmabuf; +struct dma_buf_attachment *attach; +struct dma_buf *dma_buf; + + gntdev_dmabuf =dmabuf_imp_find_unlink (priv, fd); +if (IS_ERR (gntdev_dmabuf)) +return PTR_ERR (gntdev_dmabuf); + +pr_debug ("Releasing DMA buffer with fd %d\n" , fd); + + attach = gntdev_dmabuf->u.imp.attach; + +if (gntdev_dmabuf->u.imp.sgt) +dma_buf_unmap_attachment (attach, gntdev_dmabuf->u.imp.sgt, +DMA_BIDIRECTIONAL ); + dma_buf = attach->dmabuf; +dma_buf_detach (attach->dmabuf, attach); +dma_buf_put (dma_buf); + +dmabuf_imp_end_foreign_access (gntdev_dmabuf->u.imp.refs, + gntdev_dmabuf->nr_pages); +dmabuf_imp_free_storage (gntdev_dmabuf); +return 0 ; }struct gntdev_dmabuf_priv *gntdev_dmabuf_init (void )
@@ -452,6 +690,7 @@ struct gntdev_dmabuf_priv *gntdev_dmabuf_init(void)mutex_init (&priv->lock);INIT_LIST_HEAD (&priv->exp_list);INIT_LIST_HEAD (&priv->exp_wait_list); +INIT_LIST_HEAD (&priv->imp_list);return priv; }
Signature · 6 lines
2.17.0 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2 8/9] xen/gntdev: Implement dma-buf import functionality
Quoted 21 lines · Oleksandr Andrushchenko
/* ------------------------------------------------------------------ */
drivers/xen/gntdev-dmabuf.c +19
-0+static int +dmabuf_imp_grant_foreign_access (struct page **pages,u32 *refs, +int count,int domid) +{ +grant_ref_t priv_gref_head; +int i, ret; + + ret =gnttab_alloc_grant_references (count, &priv_gref_head); +if (ret <0 ) { +pr_err ("Cannot allocate grant references, ret %d\n" , ret); +return ret; + } + +for (i =0 ; i < count; i++) { +int cur_ref; + + cur_ref =gnttab_claim_grant_reference (&priv_gref_head); +if (cur_ref <0 ) { + ret = cur_ref;
drivers/xen/gntdev-dmabuf.c int gntdev_dmabuf_exp_from_pages(struct gntdev_dmabuf_export_args *args) · line 477
Quoted 10 lines
drivers/xen/gntdev-dmabuf.c +10
-0+pr_err ("Cannot claim grant reference, ret %d\n" , ret); + goto out; + } + +gnttab_grant_foreign_access_ref (cur_ref, domid, +xen_page_to_gfn (pages[i]),0 ); + refs[i] = cur_ref; + } + + ret =0 ;
return 0?
Quoted 6 lines
drivers/xen/gntdev-dmabuf.c +6
-0+ +out: +gnttab_free_grant_references (priv_gref_head); +return ret; +} +
Re: [PATCH v2 8/9] xen/gntdev: Implement dma-buf import functionality
Quoted 25 lines · Boris Ostrovsky
Quoted 24 lines · Oleksandr Andrushchenko
/* ------------------------------------------------------------------ */
drivers/xen/gntdev-dmabuf.c +22
-0+static int +dmabuf_imp_grant_foreign_access (struct page **pages,u32 *refs, +int count,int domid) +{ +grant_ref_t priv_gref_head; +int i, ret; + + ret =gnttab_alloc_grant_references (count, &priv_gref_head); +if (ret <0 ) { +pr_err ("Cannot allocate grant references, ret %d\n" , ret); +return ret; + } + +for (i =0 ; i < count; i++) { +int cur_ref; + + cur_ref =gnttab_claim_grant_reference (&priv_gref_head); +if (cur_ref <0 ) { + ret = cur_ref; +pr_err ("Cannot claim grant reference, ret %d\n" , ret); + goto out; + }
Quoted 8 lines
drivers/xen/gntdev-dmabuf.c int gntdev_dmabuf_exp_from_pages(struct gntdev_dmabuf_export_args *args) · line 477
Quoted 7 lines
drivers/xen/gntdev-dmabuf.c +7
-0+ +gnttab_grant_foreign_access_ref (cur_ref, domid, +xen_page_to_gfn (pages[i]),0 ); + refs[i] = cur_ref; + } + + ret =0 ;return 0?
My bad, thank you
Quoted 6 lines
Quoted 6 lines
drivers/xen/gntdev-dmabuf.c +6
-0+ +out: +gnttab_free_grant_references (priv_gref_head); +return ret; +} +
Re: [PATCH v2 8/9] xen/gntdev: Implement dma-buf import functionality
In reply to Boris OstrovskyQuoted 25 lines · Boris Ostrovsky
Quoted 24 lines · Oleksandr Andrushchenko
/* ------------------------------------------------------------------ */
drivers/xen/gntdev-dmabuf.c +22
-0+static int +dmabuf_imp_grant_foreign_access (struct page **pages,u32 *refs, +int count,int domid) +{ +grant_ref_t priv_gref_head; +int i, ret; + + ret =gnttab_alloc_grant_references (count, &priv_gref_head); +if (ret <0 ) { +pr_err ("Cannot allocate grant references, ret %d\n" , ret); +return ret; + } + +for (i =0 ; i < count; i++) { +int cur_ref; + + cur_ref =gnttab_claim_grant_reference (&priv_gref_head); +if (cur_ref <0 ) { + ret = cur_ref; +pr_err ("Cannot claim grant reference, ret %d\n" , ret); + goto out; + }
Quoted 8 lines
drivers/xen/gntdev-dmabuf.c int gntdev_dmabuf_exp_from_pages(struct gntdev_dmabuf_export_args *args) · line 477
Quoted 7 lines
drivers/xen/gntdev-dmabuf.c +7
-0+ +gnttab_grant_foreign_access_ref (cur_ref, domid, +xen_page_to_gfn (pages[i]),0 ); + refs[i] = cur_ref; + } + + ret =0 ;return 0?
My bad, thank you
Quoted 6 lines
drivers/xen/gntdev-dmabuf.c int gntdev_dmabuf_exp_from_pages(struct gntdev_dmabuf_export_args *args) · line 483
Quoted 6 lines
drivers/xen/gntdev-dmabuf.c +6
-0+ +out: +gnttab_free_grant_references (priv_gref_head); +return ret; +} +
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 8/9] xen/gntdev: Implement dma-buf import functionality
In reply to Oleksandr AndrushchenkoQuoted 21 lines · Oleksandr Andrushchenko
/* ------------------------------------------------------------------ */
drivers/xen/gntdev-dmabuf.c +19
-0+static int +dmabuf_imp_grant_foreign_access (struct page **pages,u32 *refs, +int count,int domid) +{ +grant_ref_t priv_gref_head; +int i, ret; + + ret =gnttab_alloc_grant_references (count, &priv_gref_head); +if (ret <0 ) { +pr_err ("Cannot allocate grant references, ret %d\n" , ret); +return ret; + } + +for (i =0 ; i < count; i++) { +int cur_ref; + + cur_ref =gnttab_claim_grant_reference (&priv_gref_head); +if (cur_ref <0 ) { + ret = cur_ref;
drivers/xen/gntdev-dmabuf.c int gntdev_dmabuf_exp_from_pages(struct gntdev_dmabuf_export_args *args) · line 477
Quoted 10 lines
drivers/xen/gntdev-dmabuf.c +10
-0+pr_err ("Cannot claim grant reference, ret %d\n" , ret); + goto out; + } + +gnttab_grant_foreign_access_ref (cur_ref, domid, +xen_page_to_gfn (pages[i]),0 ); + refs[i] = cur_ref; + } + + ret =0 ;
return 0?
drivers/xen/gntdev-dmabuf.c int gntdev_dmabuf_exp_from_pages(struct gntdev_dmabuf_export_args *args) · line 483
Quoted 6 lines
drivers/xen/gntdev-dmabuf.c +6
-0+ +out: +gnttab_free_grant_references (priv_gref_head); +return ret; +} +
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v2 8/9 xen/gntdev: Implement dma-buf import functionality
In reply to Oleksandr AndrushchenkoFrom: Oleksandr Andrushchenko <[email protected]>
1. Import a dma-buf with the file descriptor provided and export granted references to the pages of that dma-buf into the array of grant references.
2. Add API to close all references to an imported buffer, so it can be released by the owner. This is only valid for buffers created with IOCTL_GNTDEV_DMABUF_IMP_TO_REFS.
--- drivers/xen/gntdev-dmabuf.c | 243 +++++++++++++++++++++++++++++++++++- 1 file changed, 241 insertions(+), 2 deletions(-)
drivers/xen/gntdev-dmabuf.c +241 -2
@@ -11,8 +11,20 @@#include <linux/dma-buf.h> #include <linux/slab.h> +#include <xen/xen.h> +#include <xen/grant_table.h> +#include "gntdev-dmabuf.h" +#ifndef GRANT_INVALID_REF +/* +* Note on usage of grant reference 0 as invalid grant reference: +* grant reference 0 is valid, but never exposed to a driver, +* because of the fact it is already in use/reserved by the PV console. +*/ +#define GRANT_INVALID_REF 0 +#endif +struct gntdev_dmabuf {struct gntdev_dmabuf_priv *priv;struct dma_buf *dmabuf;
@@ -29,6 +41,14 @@ struct gntdev_dmabuf {void (*release)(struct gntdev_priv *priv,struct grant_map *map); } exp; +struct { +/* Granted references of the imported buffer. */ +grant_ref_t *refs; +/* Scatter-gather table of the imported buffer. */ +struct sg_table *sgt; +/* dma-buf attachment of the imported buffer. */ +struct dma_buf_attachment *attach; + } imp; } u;/* Number of pages this buffer has. */
@@ -53,6 +73,8 @@ struct gntdev_dmabuf_priv {struct list_head exp_list;/* List of wait objects. */ struct list_head exp_wait_list; +/* List of imported DMA buffers. */ +struct list_head imp_list;/* This is the lock which protects dma_buf_xxx lists. */ struct mutex lock; };
@@ -424,21 +446,237 @@ int gntdev_dmabuf_exp_from_pages(struct gntdev_dmabuf_export_args *args)/* DMA buffer import support. */ /* ------------------------------------------------------------------ */ +static int +dmabuf_imp_grant_foreign_access (struct page **pages,u32 *refs, +int count,int domid) +{ +grant_ref_t priv_gref_head; +int i, ret; + + ret =gnttab_alloc_grant_references (count, &priv_gref_head); +if (ret <0 ) { +pr_err ("Cannot allocate grant references, ret %d\n" , ret); +return ret; + } + +for (i =0 ; i < count; i++) { +int cur_ref; + + cur_ref =gnttab_claim_grant_reference (&priv_gref_head); +if (cur_ref <0 ) { + ret = cur_ref; +pr_err ("Cannot claim grant reference, ret %d\n" , ret); + goto out; + } + +gnttab_grant_foreign_access_ref (cur_ref, domid, +xen_page_to_gfn (pages[i]),0 ); + refs[i] = cur_ref; + } + + ret =0 ; + +out: +gnttab_free_grant_references (priv_gref_head); +return ret; +} + +static void dmabuf_imp_end_foreign_access (u32 *refs,int count) +{ +int i; + +for (i =0 ; i < count; i++) +if (refs[i] !=GRANT_INVALID_REF ) +gnttab_end_foreign_access (refs[i],0 ,0UL ); +} + +static void dmabuf_imp_free_storage (struct gntdev_dmabuf *gntdev_dmabuf) +{ +kfree (gntdev_dmabuf->pages); +kfree (gntdev_dmabuf->u.imp.refs); +kfree (gntdev_dmabuf); +} + +static struct gntdev_dmabuf *dmabuf_imp_alloc_storage (int count) +{ +struct gntdev_dmabuf *gntdev_dmabuf; +int i; + + gntdev_dmabuf =kzalloc (sizeof (*gntdev_dmabuf),GFP_KERNEL ); +if (!gntdev_dmabuf) + goto fail; + + gntdev_dmabuf->u.imp.refs =kcalloc (count, +sizeof (gntdev_dmabuf->u.imp.refs[0 ]), +GFP_KERNEL ); +if (!gntdev_dmabuf->u.imp.refs) + goto fail; + + gntdev_dmabuf->pages =kcalloc (count, +sizeof (gntdev_dmabuf->pages[0 ]), +GFP_KERNEL ); +if (!gntdev_dmabuf->pages) + goto fail; + + gntdev_dmabuf->nr_pages = count; + +for (i =0 ; i < count; i++) + gntdev_dmabuf->u.imp.refs[i] =GRANT_INVALID_REF ; + +return gntdev_dmabuf; + +fail: +dmabuf_imp_free_storage (gntdev_dmabuf); +return ERR_PTR (-ENOMEM ); +} +struct gntdev_dmabuf *gntdev_dmabuf_imp_to_refs (struct gntdev_dmabuf_priv *priv,struct device *dev,int fd,int count,int domid) { -return ERR_PTR (-ENOMEM ); +struct gntdev_dmabuf *gntdev_dmabuf, *ret; +struct dma_buf *dma_buf; +struct dma_buf_attachment *attach; +struct sg_table *sgt; +struct sg_page_iter sg_iter; +int i; + + dma_buf =dma_buf_get (fd); +if (IS_ERR (dma_buf)) +return ERR_CAST (dma_buf); + + gntdev_dmabuf =dmabuf_imp_alloc_storage (count); +if (IS_ERR (gntdev_dmabuf)) { + ret = gntdev_dmabuf; + goto fail_put; +} + + gntdev_dmabuf->priv = priv; + gntdev_dmabuf->fd = fd; + + attach =dma_buf_attach (dma_buf, dev); +if (IS_ERR (attach)) { + ret =ERR_CAST (attach); + goto fail_free_obj; + } + + gntdev_dmabuf->u.imp.attach = attach; + + sgt =dma_buf_map_attachment (attach,DMA_BIDIRECTIONAL ); +if (IS_ERR (sgt)) { + ret =ERR_CAST (sgt); + goto fail_detach; + } + +/* Check number of pages that imported buffer has. */ +if (attach->dmabuf->size != gntdev_dmabuf->nr_pages <<PAGE_SHIFT ) { + ret =ERR_PTR (-EINVAL ); +pr_err ("DMA buffer has %zu pages, user-space expects %d\n" , + attach->dmabuf->size, gntdev_dmabuf->nr_pages); + goto fail_unmap; + } + + gntdev_dmabuf->u.imp.sgt = sgt; + +/* Now convert sgt to array of pages and check for page validity. */ + i =0 ; +for_each_sg_page (sgt->sgl, &sg_iter, sgt->nents,0 ) { +struct page *page =sg_page_iter_page (&sg_iter); +/* +* Check if page is valid: this can happen if we are given +* a page from VRAM or other resources which are not backed +* by a struct page. +*/ +if (!pfn_valid (page_to_pfn (page))) { + ret =ERR_PTR (-EINVAL ); + goto fail_unmap; + } + + gntdev_dmabuf->pages[i++] = page; + } + + ret =ERR_PTR (dmabuf_imp_grant_foreign_access (gntdev_dmabuf->pages, + gntdev_dmabuf->u.imp.refs, + count, domid)); +if (IS_ERR (ret)) + goto fail_end_access; + +pr_debug ("Imported DMA buffer with fd %d\n" , fd); + +mutex_lock (&priv->lock); +list_add (&gntdev_dmabuf->next, &priv->imp_list); +mutex_unlock (&priv->lock); + +return gntdev_dmabuf; + +fail_end_access: +dmabuf_imp_end_foreign_access (gntdev_dmabuf->u.imp.refs, count); +fail_unmap: +dma_buf_unmap_attachment (attach, sgt,DMA_BIDIRECTIONAL ); +fail_detach: +dma_buf_detach (dma_buf, attach); +fail_free_obj: +dmabuf_imp_free_storage (gntdev_dmabuf); +fail_put: +dma_buf_put (dma_buf); +return ret; }u32 *gntdev_dmabuf_imp_get_refs (struct gntdev_dmabuf *gntdev_dmabuf) { +if (gntdev_dmabuf) +return gntdev_dmabuf->u.imp.refs; +return NULL ; } +/* +* Find the hyper dma-buf by its file descriptor and remove +* it from the buffer's list. +*/ +static struct gntdev_dmabuf * +dmabuf_imp_find_unlink (struct gntdev_dmabuf_priv *priv,int fd) +{ +struct gntdev_dmabuf *q, *gntdev_dmabuf, *ret =ERR_PTR (-ENOENT ); + +mutex_lock (&priv->lock); +list_for_each_entry_safe (gntdev_dmabuf, q, &priv->imp_list, next) { +if (gntdev_dmabuf->fd == fd) { +pr_debug ("Found gntdev_dmabuf in the import list\n" ); + ret = gntdev_dmabuf; +list_del (&gntdev_dmabuf->next); +break ; + } + } +mutex_unlock (&priv->lock); +return ret; +} +int gntdev_dmabuf_imp_release (struct gntdev_dmabuf_priv *priv,u32 fd) { -return -EINVAL ; +struct gntdev_dmabuf *gntdev_dmabuf; +struct dma_buf_attachment *attach; +struct dma_buf *dma_buf; + + gntdev_dmabuf =dmabuf_imp_find_unlink (priv, fd); +if (IS_ERR (gntdev_dmabuf)) +return PTR_ERR (gntdev_dmabuf); + +pr_debug ("Releasing DMA buffer with fd %d\n" , fd); + + attach = gntdev_dmabuf->u.imp.attach; + +if (gntdev_dmabuf->u.imp.sgt) +dma_buf_unmap_attachment (attach, gntdev_dmabuf->u.imp.sgt, +DMA_BIDIRECTIONAL ); + dma_buf = attach->dmabuf; +dma_buf_detach (attach->dmabuf, attach); +dma_buf_put (dma_buf); + +dmabuf_imp_end_foreign_access (gntdev_dmabuf->u.imp.refs, + gntdev_dmabuf->nr_pages); +dmabuf_imp_free_storage (gntdev_dmabuf); +return 0 ; }struct gntdev_dmabuf_priv *gntdev_dmabuf_init (void )
@@ -452,6 +690,7 @@ struct gntdev_dmabuf_priv *gntdev_dmabuf_init(void)mutex_init (&priv->lock);INIT_LIST_HEAD (&priv->exp_list);INIT_LIST_HEAD (&priv->exp_wait_list); +INIT_LIST_HEAD (&priv->imp_list);return priv; }
Signature · 7 lines
2.17.0 _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v2 9/9 xen/gntdev: Expose gntdev's dma-buf API for in-kernel use
In reply to Oleksandr AndrushchenkoFrom: Oleksandr Andrushchenko <[email protected]>
Allow creating grant device context for use by kernel modules which require functionality, provided by gntdev. Export symbols for dma-buf API provided by the module.
--- drivers/xen/gntdev-dmabuf.c | 6 +++ drivers/xen/gntdev.c | 92 +++++++++++++++++++++++-------------- include/xen/grant_dev.h | 37 +++++++++++++++ 3 files changed, 101 insertions(+), 34 deletions(-) create mode 100644 include/xen/grant_dev.h
drivers/xen/gntdev-dmabuf.c +6 -0
@@ -196,6 +196,7 @@ int gntdev_dmabuf_exp_wait_released(struct gntdev_dmabuf_priv *priv, int fd,dmabuf_exp_wait_obj_free (priv, obj);return ret; } +EXPORT_SYMBOL_GPL (gntdev_dmabuf_exp_wait_released);/* ------------------------------------------------------------------ */ /* DMA buffer export support. */
@@ -621,6 +622,7 @@ gntdev_dmabuf_imp_to_refs(struct gntdev_dmabuf_priv *priv, struct device *dev,dma_buf_put (dma_buf);return ret; } +EXPORT_SYMBOL_GPL (gntdev_dmabuf_imp_to_refs);u32 *gntdev_dmabuf_imp_get_refs (struct gntdev_dmabuf *gntdev_dmabuf) {
@@ -629,6 +631,7 @@ u32 *gntdev_dmabuf_imp_get_refs(struct gntdev_dmabuf *gntdev_dmabuf)return NULL ; } +EXPORT_SYMBOL_GPL (gntdev_dmabuf_imp_get_refs);/* * Find the hyper dma-buf by its file descriptor and remove
@@ -678,6 +681,7 @@ int gntdev_dmabuf_imp_release(struct gntdev_dmabuf_priv *priv, u32 fd)dmabuf_imp_free_storage (gntdev_dmabuf);return 0 ; } +EXPORT_SYMBOL_GPL (gntdev_dmabuf_imp_release);struct gntdev_dmabuf_priv *gntdev_dmabuf_init (void ) {
@@ -694,8 +698,10 @@ struct gntdev_dmabuf_priv *gntdev_dmabuf_init(void)return priv; } +EXPORT_SYMBOL_GPL (gntdev_dmabuf_init);void gntdev_dmabuf_fini (struct gntdev_dmabuf_priv *priv) {kfree (priv); } +EXPORT_SYMBOL_GPL (gntdev_dmabuf_fini);
drivers/xen/gntdev.c +58 -34
140 lines not on this page · raw message
include/xen/grant_dev.h new file +37 -0
@@ -0,0 +1,37 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +/* +* Grant device kernel API +* +* Copyright (C) 2018 EPAM Systems Inc. +* +* Author: Oleksandr Andrushchenko <[email protected]> +*/ + +#ifndef _GRANT_DEV_H +#define _GRANT_DEV_H + +#include <linux/types.h> + +struct device ; +struct gntdev_priv ; +#ifdef CONFIG_XEN_GNTDEV_DMABUF +struct xen_dmabuf ; +#endif + +struct gntdev_priv *gntdev_alloc_context (struct device *dev); +void gntdev_free_context (struct gntdev_priv *priv); + +#ifdef CONFIG_XEN_GNTDEV_DMABUF +int gntdev_dmabuf_exp_from_refs (struct gntdev_priv *priv,int flags, +int count,u32 domid,u32 *refs,u32 *fd); +int gntdev_dmabuf_exp_wait_released (struct gntdev_priv *priv,int fd, +int wait_to_ms); + +struct xen_dmabuf *gntdev_dmabuf_imp_to_refs (struct gntdev_priv *priv, +int fd,int count,int domid); +u32 *gntdev_dmabuf_imp_get_refs (struct xen_dmabuf *xen_dmabuf); +int gntdev_dmabuf_imp_release (struct gntdev_priv *priv,u32 fd); +#endif + +#endif
Signature · 1 line
2.17.0
Re: [PATCH v2 9/9] xen/gntdev: Expose gntdev's dma-buf API for in-kernel use
Quoted 5 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Allow creating grant device context for use by kernel modules which require functionality, provided by gntdev. Export symbols for dma-buf API provided by the module.
Can you give an example of who'd be using these interfaces?
-boris
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH v2 9/9] xen/gntdev: Expose gntdev's dma-buf API for in-kernel use
In reply to Oleksandr AndrushchenkoQuoted 5 lines · Oleksandr Andrushchenko
From: Oleksandr Andrushchenko <[email protected]>
Allow creating grant device context for use by kernel modules which require functionality, provided by gntdev. Export symbols for dma-buf API provided by the module.
Can you give an example of who'd be using these interfaces?
-boris