From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: Alexander Monakov <amonakov@ispras.ru>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch][v5] libgomp/nvptx: Prepare for reverse-offload callback handling
Date: Mon, 24 Oct 2022 16:07:25 +0200 [thread overview]
Message-ID: <Y1acHbIiMIBI5MP/@tucnak> (raw)
In-Reply-To: <1e56b27f-3c74-8bc2-028b-9091fa1ae7b1@codesourcery.com>
On Wed, Oct 12, 2022 at 10:55:26AM +0200, Tobias Burnus wrote:
> libgomp/nvptx: Prepare for reverse-offload callback handling
>
> This patch adds a stub 'gomp_target_rev' in the host's target.c, which will
> later handle the reverse offload.
> For nvptx, it adds support for forwarding the offload gomp_target_ext call
> to the host by setting values in a struct on the device and querying it on
> the host - invoking gomp_target_rev on the result.
>
> include/ChangeLog:
>
> * cuda/cuda.h (enum CUdevice_attribute): Add
> CU_DEVICE_ATTRIBUTE_UNIFIED_ADDRESSING.
> (CU_MEMHOSTALLOC_DEVICEMAP): Define.
> (cuMemHostAlloc): Add prototype.
>
> libgomp/ChangeLog:
>
> * config/nvptx/icv-device.c (GOMP_DEVICE_NUM_VAR): Remove
> 'static' for this variable.
> * config/nvptx/libgomp-nvptx.h: New file.
> * config/nvptx/target.c: Include it.
> (GOMP_ADDITIONAL_ICVS): Declare extern var.
> (GOMP_REV_OFFLOAD_VAR): Declare var.
> (GOMP_target_ext): Handle reverse offload.
> * libgomp-plugin.h (GOMP_PLUGIN_target_rev): New prototype.
> * libgomp-plugin.c (GOMP_PLUGIN_target_rev): New, call ...
> * target.c (gomp_target_rev): ... this new stub function.
> * libgomp.h (gomp_target_rev): Declare.
> * libgomp.map (GOMP_PLUGIN_1.4): New; add GOMP_PLUGIN_target_rev.
> * plugin/cuda-lib.def (cuMemHostAlloc): Add.
> * plugin/plugin-nvptx.c: Include libgomp-nvptx.h.
> (struct ptx_device): Add rev_data member.
> (nvptx_open_device): Remove async_engines query, last used in
> r10-304-g1f4c5b9b; add unified-address assert check.
> (GOMP_OFFLOAD_get_num_devices): Claim unified address
> support.
> (GOMP_OFFLOAD_load_image): Free rev_fn_table if no
> offload functions exist. Make offload var available
> on host and device.
> (rev_off_dev_to_host_cpy, rev_off_host_to_dev_cpy): New.
> (GOMP_OFFLOAD_run): Handle reverse offload.
Ok, thanks.
Jakub
next prev parent reply other threads:[~2022-10-24 14:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 9:07 [Patch] " Tobias Burnus
2022-08-26 9:07 ` Tobias Burnus
2022-08-26 14:56 ` Alexander Monakov
2022-09-09 15:49 ` Jakub Jelinek
2022-09-09 15:51 ` Jakub Jelinek
2022-09-13 7:07 ` Tobias Burnus
2022-09-21 20:06 ` Alexander Monakov
2022-09-26 15:07 ` Tobias Burnus
2022-09-26 17:45 ` Alexander Monakov
2022-09-27 9:23 ` Tobias Burnus
2022-09-28 13:16 ` Alexander Monakov
2022-10-02 18:13 ` Tobias Burnus
2022-10-07 14:26 ` [Patch][v5] " Tobias Burnus
2022-10-11 10:49 ` Jakub Jelinek
2022-10-11 11:12 ` Alexander Monakov
2022-10-12 8:55 ` Tobias Burnus
2022-10-17 7:35 ` *ping* / " Tobias Burnus
2022-10-19 15:53 ` Alexander Monakov
2022-10-24 14:07 ` Jakub Jelinek [this message]
2022-10-24 19:05 ` Thomas Schwinge
2022-10-24 19:11 ` Thomas Schwinge
2022-10-24 19:46 ` Tobias Burnus
2022-10-24 19:51 ` libgomp/nvptx: Prepare for reverse-offload callback handling, resolve spurious SIGSEGVs (was: [Patch][v5] libgomp/nvptx: Prepare for reverse-offload callback handling) Thomas Schwinge
2023-03-21 15:53 ` libgomp: Simplify OpenMP reverse offload host <-> device memory copy implementation (was: [Patch] " Thomas Schwinge
2023-03-24 15:43 ` [og12] " Thomas Schwinge
2023-04-28 8:48 ` Tobias Burnus
2023-04-28 9:31 ` Thomas Schwinge
2023-04-28 10:51 ` Tobias Burnus
2023-04-04 14:40 ` [Patch] libgomp/nvptx: Prepare for reverse-offload callback handling Thomas Schwinge
2023-04-28 8:28 ` Tobias Burnus
2023-04-28 9:23 ` Thomas Schwinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y1acHbIiMIBI5MP/@tucnak \
--to=jakub@redhat.com \
--cc=amonakov@ispras.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=tobias@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).