From: Felix Kuehling <felix.kuehling@amd.com> To: Adrian Reber <adrian@lisas.de> Cc: Alexander Mihalicyn <alexander@mihalicyn.com>, Pavel Emelyanov <ovzxemul@gmail.com>, Pavel Tikhomirov <snorcht@gmail.com>, DRI Development <dri-devel@lists.freedesktop.org>, "Bhardwaj, Rajneesh" <Rajneesh.Bhardwaj@amd.com>, criu@openvz.org, "Yat Sin, David" <David.YatSin@amd.com>, amd-gfx list <amd-gfx@lists.freedesktop.org> Subject: Re: [RFC] CRIU support for ROCm Date: Fri, 18 Jun 2021 17:48:33 -0400 [thread overview] Message-ID: <e6a70c3c-c710-5566-4152-876324ddeb73@amd.com> (raw) In-Reply-To: <YI2J97Rg4+1+KVNs@lisas.de> Am 2021-05-01 um 1:03 p.m. schrieb Adrian Reber: > > It would also be good to have your patchset submitted as a PR on github > to have our normal CI test coverage of the changes. Hi Adrian, We moved our work to a new github repository that is a fork of checkpoint-restore/criu so that we could send a pull request: https://github.com/checkpoint-restore/criu/pull/1519. This is still an RFC. It has some updates that Rajneesh explained in the pull request. Two big things still missing that we are working on now are: * New ioctl API to make it maintainable and extensible for the future * Using DMA engines for saving/restoring VRAM contents We should have another update with those two things in about two weeks. We'd really appreciate feedback on the changes we had to make to core CRIU, and the build system changes for the new plugin directory. Thanks, Felix > > Adrian
WARNING: multiple messages have this Message-ID (diff)
From: Felix Kuehling <felix.kuehling@amd.com> To: Adrian Reber <adrian@lisas.de> Cc: Alexander Mihalicyn <alexander@mihalicyn.com>, Pavel Emelyanov <ovzxemul@gmail.com>, Pavel Tikhomirov <snorcht@gmail.com>, DRI Development <dri-devel@lists.freedesktop.org>, "Bhardwaj, Rajneesh" <Rajneesh.Bhardwaj@amd.com>, criu@openvz.org, "Yat Sin, David" <David.YatSin@amd.com>, amd-gfx list <amd-gfx@lists.freedesktop.org> Subject: Re: [RFC] CRIU support for ROCm Date: Fri, 18 Jun 2021 17:48:33 -0400 [thread overview] Message-ID: <e6a70c3c-c710-5566-4152-876324ddeb73@amd.com> (raw) In-Reply-To: <YI2J97Rg4+1+KVNs@lisas.de> Am 2021-05-01 um 1:03 p.m. schrieb Adrian Reber: > > It would also be good to have your patchset submitted as a PR on github > to have our normal CI test coverage of the changes. Hi Adrian, We moved our work to a new github repository that is a fork of checkpoint-restore/criu so that we could send a pull request: https://github.com/checkpoint-restore/criu/pull/1519. This is still an RFC. It has some updates that Rajneesh explained in the pull request. Two big things still missing that we are working on now are: * New ioctl API to make it maintainable and extensible for the future * Using DMA engines for saving/restoring VRAM contents We should have another update with those two things in about two weeks. We'd really appreciate feedback on the changes we had to make to core CRIU, and the build system changes for the new plugin directory. Thanks, Felix > > Adrian _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2021-06-18 21:48 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-01 1:57 [RFC] CRIU support for ROCm Felix Kuehling 2021-05-01 1:57 ` Felix Kuehling 2021-05-01 17:03 ` Adrian Reber 2021-05-01 17:03 ` Adrian Reber 2021-05-03 18:21 ` Felix Kuehling 2021-05-03 18:21 ` Felix Kuehling 2021-05-04 12:32 ` Adrian Reber 2021-05-04 12:32 ` Adrian Reber 2021-06-18 21:48 ` Felix Kuehling [this message] 2021-06-18 21:48 ` Felix Kuehling 2021-06-21 8:13 ` Adrian Reber 2021-06-21 8:13 ` Adrian Reber 2021-05-04 13:00 ` Daniel Vetter 2021-05-04 13:00 ` Daniel Vetter 2021-05-06 16:10 ` Felix Kuehling 2021-05-06 16:10 ` Felix Kuehling 2021-05-07 9:32 ` Daniel Vetter 2021-05-07 9:32 ` Daniel Vetter
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=e6a70c3c-c710-5566-4152-876324ddeb73@amd.com \ --to=felix.kuehling@amd.com \ --cc=David.YatSin@amd.com \ --cc=Rajneesh.Bhardwaj@amd.com \ --cc=adrian@lisas.de \ --cc=alexander@mihalicyn.com \ --cc=amd-gfx@lists.freedesktop.org \ --cc=criu@openvz.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=ovzxemul@gmail.com \ --cc=snorcht@gmail.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.