From: "Christian König" <christian.koenig@amd.com> To: Andrey Grodzovsky <Andrey.Grodzovsky@amd.com>, Daniel Vetter <daniel@ffwll.ch> Cc: "daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>, "amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>, "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>, "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>, "Deucher, Alexander" <Alexander.Deucher@amd.com>, "yuq825@gmail.com" <yuq825@gmail.com> Subject: Re: [PATCH v3 01/12] drm: Add dummy page per device or GEM object Date: Wed, 13 Jan 2021 10:14:29 +0100 [thread overview] Message-ID: <20669765-8656-0933-ff86-15fc722f9bd8@amd.com> (raw) In-Reply-To: <f869b0dc-2678-07e4-511f-739c025579d0@amd.com> Am 12.01.21 um 16:59 schrieb Andrey Grodzovsky: > > On 1/12/21 7:32 AM, Christian König wrote: >> Am 12.01.21 um 10:10 schrieb Daniel Vetter: >>> On Mon, Jan 11, 2021 at 03:45:10PM -0500, Andrey Grodzovsky wrote: >>>> On 1/11/21 11:15 AM, Daniel Vetter wrote: >>>>> On Mon, Jan 11, 2021 at 05:13:56PM +0100, Daniel Vetter wrote: >>>>>> On Fri, Jan 08, 2021 at 04:49:55PM +0000, Grodzovsky, Andrey wrote: >>>>>>> Ok then, I guess I will proceed with the dummy pages list >>>>>>> implementation then. >>>>>>> >>>>>>> Andrey >>>>>>> >>>>>>> ________________________________ >>>>>>> From: Koenig, Christian <Christian.Koenig@amd.com> >>>>>>> Sent: 08 January 2021 09:52 >>>>>>> To: Grodzovsky, Andrey <Andrey.Grodzovsky@amd.com>; Daniel >>>>>>> Vetter <daniel@ffwll.ch> >>>>>>> Cc: amd-gfx@lists.freedesktop.org >>>>>>> <amd-gfx@lists.freedesktop.org>; dri-devel@lists.freedesktop.org >>>>>>> <dri-devel@lists.freedesktop.org>; daniel.vetter@ffwll.ch >>>>>>> <daniel.vetter@ffwll.ch>; robh@kernel.org <robh@kernel.org>; >>>>>>> l.stach@pengutronix.de <l.stach@pengutronix.de>; >>>>>>> yuq825@gmail.com <yuq825@gmail.com>; eric@anholt.net >>>>>>> <eric@anholt.net>; Deucher, Alexander >>>>>>> <Alexander.Deucher@amd.com>; gregkh@linuxfoundation.org >>>>>>> <gregkh@linuxfoundation.org>; ppaalanen@gmail.com >>>>>>> <ppaalanen@gmail.com>; Wentland, Harry <Harry.Wentland@amd.com> >>>>>>> Subject: Re: [PATCH v3 01/12] drm: Add dummy page per device or >>>>>>> GEM object >>>>>>> >>>>>>> Mhm, I'm not aware of any let over pointer between TTM and GEM >>>>>>> and we >>>>>>> worked quite hard on reducing the size of the amdgpu_bo, so another >>>>>>> extra pointer just for that corner case would suck quite a bit. >>>>>> We have a ton of other pointers in struct amdgpu_bo (or any of >>>>>> it's lower >>>>>> things) which are fairly single-use, so I'm really not much >>>>>> seeing the >>>>>> point in making this a special case. It also means the lifetime >>>>>> management >>>>>> becomes a bit iffy, since we can't throw away the dummy page then >>>>>> the last >>>>>> reference to the bo is released (since we don't track it there), >>>>>> but only >>>>>> when the last pointer to the device is released. Potentially this >>>>>> means a >>>>>> pile of dangling pages hanging around for too long. >>>>> Also if you really, really, really want to have this list, please >>>>> don't >>>>> reinvent it since we have it already. drmm_ is exactly meant for >>>>> resources >>>>> that should be freed when the final drm_device reference disappears. >>>>> -Daniel >>>> >>>> I maybe was eager to early, see i need to explicitly allocate the >>>> dummy page >>>> using page_alloc so >>>> i cannot use drmm_kmalloc for this, so once again like with the >>>> list i need >>>> to wrap it with a container struct >>>> which i can then allocate using drmm_kmalloc and inside there will >>>> be page >>>> pointer. But then >>>> on release it needs to free the page and so i supposedly need to >>>> use drmm_add_action >>>> to free the page before the container struct is released but >>>> drmm_kmalloc >>>> doesn't allow to set >>>> release action on struct allocation. So I created a new >>>> drmm_kmalloc_with_action API function >>>> but then you also need to supply the optional data pointer for the >>>> release >>>> action (the struct page in this case) >>>> and so this all becomes a bit overcomplicated (but doable). Is this >>>> extra >>>> API worth adding ? Maybe it can >>>> be useful in general. >>> drm_add_action_or_reset (for better control flow) has both a void * >>> data >>> and a cleanup function (and it internally allocates the tracking >>> structure >>> for that for you). So should work as-is? Allocating a tracking >>> structure >>> for our tracking structure for a page would definitely be a bit too >>> much. >>> >>> Essentiall drmm_add_action is your kcalloc_with_action function you >>> want, >>> as long as all you need is a single void * pointer (we could do the >>> kzalloc_with_action though, there's enough space, just no need yet >>> for any >>> of the current users). >> >> Yeah, but my thinking was that we should use the page LRU for this >> and not another container structure. >> >> Christian. > > > Which specific list did you mean ? The struct page * you get from get_free_page() already has an lru member of type list_head. This way you can link pages together for later destruction without the need of a container object. Christian. > > Andrey > > >> >>> -Daniel >> _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <christian.koenig@amd.com> To: Andrey Grodzovsky <Andrey.Grodzovsky@amd.com>, Daniel Vetter <daniel@ffwll.ch> Cc: "robh@kernel.org" <robh@kernel.org>, "daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>, "amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>, "eric@anholt.net" <eric@anholt.net>, "ppaalanen@gmail.com" <ppaalanen@gmail.com>, "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>, "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>, "Deucher, Alexander" <Alexander.Deucher@amd.com>, "l.stach@pengutronix.de" <l.stach@pengutronix.de>, "Wentland, Harry" <Harry.Wentland@amd.com>, "yuq825@gmail.com" <yuq825@gmail.com> Subject: Re: [PATCH v3 01/12] drm: Add dummy page per device or GEM object Date: Wed, 13 Jan 2021 10:14:29 +0100 [thread overview] Message-ID: <20669765-8656-0933-ff86-15fc722f9bd8@amd.com> (raw) In-Reply-To: <f869b0dc-2678-07e4-511f-739c025579d0@amd.com> Am 12.01.21 um 16:59 schrieb Andrey Grodzovsky: > > On 1/12/21 7:32 AM, Christian König wrote: >> Am 12.01.21 um 10:10 schrieb Daniel Vetter: >>> On Mon, Jan 11, 2021 at 03:45:10PM -0500, Andrey Grodzovsky wrote: >>>> On 1/11/21 11:15 AM, Daniel Vetter wrote: >>>>> On Mon, Jan 11, 2021 at 05:13:56PM +0100, Daniel Vetter wrote: >>>>>> On Fri, Jan 08, 2021 at 04:49:55PM +0000, Grodzovsky, Andrey wrote: >>>>>>> Ok then, I guess I will proceed with the dummy pages list >>>>>>> implementation then. >>>>>>> >>>>>>> Andrey >>>>>>> >>>>>>> ________________________________ >>>>>>> From: Koenig, Christian <Christian.Koenig@amd.com> >>>>>>> Sent: 08 January 2021 09:52 >>>>>>> To: Grodzovsky, Andrey <Andrey.Grodzovsky@amd.com>; Daniel >>>>>>> Vetter <daniel@ffwll.ch> >>>>>>> Cc: amd-gfx@lists.freedesktop.org >>>>>>> <amd-gfx@lists.freedesktop.org>; dri-devel@lists.freedesktop.org >>>>>>> <dri-devel@lists.freedesktop.org>; daniel.vetter@ffwll.ch >>>>>>> <daniel.vetter@ffwll.ch>; robh@kernel.org <robh@kernel.org>; >>>>>>> l.stach@pengutronix.de <l.stach@pengutronix.de>; >>>>>>> yuq825@gmail.com <yuq825@gmail.com>; eric@anholt.net >>>>>>> <eric@anholt.net>; Deucher, Alexander >>>>>>> <Alexander.Deucher@amd.com>; gregkh@linuxfoundation.org >>>>>>> <gregkh@linuxfoundation.org>; ppaalanen@gmail.com >>>>>>> <ppaalanen@gmail.com>; Wentland, Harry <Harry.Wentland@amd.com> >>>>>>> Subject: Re: [PATCH v3 01/12] drm: Add dummy page per device or >>>>>>> GEM object >>>>>>> >>>>>>> Mhm, I'm not aware of any let over pointer between TTM and GEM >>>>>>> and we >>>>>>> worked quite hard on reducing the size of the amdgpu_bo, so another >>>>>>> extra pointer just for that corner case would suck quite a bit. >>>>>> We have a ton of other pointers in struct amdgpu_bo (or any of >>>>>> it's lower >>>>>> things) which are fairly single-use, so I'm really not much >>>>>> seeing the >>>>>> point in making this a special case. It also means the lifetime >>>>>> management >>>>>> becomes a bit iffy, since we can't throw away the dummy page then >>>>>> the last >>>>>> reference to the bo is released (since we don't track it there), >>>>>> but only >>>>>> when the last pointer to the device is released. Potentially this >>>>>> means a >>>>>> pile of dangling pages hanging around for too long. >>>>> Also if you really, really, really want to have this list, please >>>>> don't >>>>> reinvent it since we have it already. drmm_ is exactly meant for >>>>> resources >>>>> that should be freed when the final drm_device reference disappears. >>>>> -Daniel >>>> >>>> I maybe was eager to early, see i need to explicitly allocate the >>>> dummy page >>>> using page_alloc so >>>> i cannot use drmm_kmalloc for this, so once again like with the >>>> list i need >>>> to wrap it with a container struct >>>> which i can then allocate using drmm_kmalloc and inside there will >>>> be page >>>> pointer. But then >>>> on release it needs to free the page and so i supposedly need to >>>> use drmm_add_action >>>> to free the page before the container struct is released but >>>> drmm_kmalloc >>>> doesn't allow to set >>>> release action on struct allocation. So I created a new >>>> drmm_kmalloc_with_action API function >>>> but then you also need to supply the optional data pointer for the >>>> release >>>> action (the struct page in this case) >>>> and so this all becomes a bit overcomplicated (but doable). Is this >>>> extra >>>> API worth adding ? Maybe it can >>>> be useful in general. >>> drm_add_action_or_reset (for better control flow) has both a void * >>> data >>> and a cleanup function (and it internally allocates the tracking >>> structure >>> for that for you). So should work as-is? Allocating a tracking >>> structure >>> for our tracking structure for a page would definitely be a bit too >>> much. >>> >>> Essentiall drmm_add_action is your kcalloc_with_action function you >>> want, >>> as long as all you need is a single void * pointer (we could do the >>> kzalloc_with_action though, there's enough space, just no need yet >>> for any >>> of the current users). >> >> Yeah, but my thinking was that we should use the page LRU for this >> and not another container structure. >> >> Christian. > > > Which specific list did you mean ? The struct page * you get from get_free_page() already has an lru member of type list_head. This way you can link pages together for later destruction without the need of a container object. Christian. > > Andrey > > >> >>> -Daniel >> _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2021-01-13 9:14 UTC|newest] Thread overview: 212+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-21 5:21 [PATCH v3 00/12] RFC Support hot device unplug in amdgpu Andrey Grodzovsky 2020-11-21 5:21 ` Andrey Grodzovsky 2020-11-21 5:21 ` [PATCH v3 01/12] drm: Add dummy page per device or GEM object Andrey Grodzovsky 2020-11-21 5:21 ` Andrey Grodzovsky 2020-11-21 14:15 ` Christian König 2020-11-21 14:15 ` Christian König 2020-11-23 4:54 ` Andrey Grodzovsky 2020-11-23 4:54 ` Andrey Grodzovsky 2020-11-23 8:01 ` Christian König 2020-11-23 8:01 ` Christian König 2021-01-05 21:04 ` Andrey Grodzovsky 2021-01-05 21:04 ` Andrey Grodzovsky 2021-01-07 16:21 ` Daniel Vetter 2021-01-07 16:21 ` Daniel Vetter 2021-01-07 16:26 ` Andrey Grodzovsky 2021-01-07 16:26 ` Andrey Grodzovsky 2021-01-07 16:28 ` Andrey Grodzovsky 2021-01-07 16:28 ` Andrey Grodzovsky 2021-01-07 16:30 ` Daniel Vetter 2021-01-07 16:30 ` Daniel Vetter 2021-01-07 16:37 ` Andrey Grodzovsky 2021-01-07 16:37 ` Andrey Grodzovsky 2021-01-08 14:26 ` Andrey Grodzovsky 2021-01-08 14:26 ` Andrey Grodzovsky 2021-01-08 14:33 ` Christian König 2021-01-08 14:33 ` Christian König 2021-01-08 14:46 ` Andrey Grodzovsky 2021-01-08 14:46 ` Andrey Grodzovsky 2021-01-08 14:52 ` Christian König 2021-01-08 14:52 ` Christian König 2021-01-08 16:49 ` Grodzovsky, Andrey 2021-01-08 16:49 ` Grodzovsky, Andrey 2021-01-11 16:13 ` Daniel Vetter 2021-01-11 16:13 ` Daniel Vetter 2021-01-11 16:15 ` Daniel Vetter 2021-01-11 16:15 ` Daniel Vetter 2021-01-11 17:41 ` Andrey Grodzovsky 2021-01-11 17:41 ` Andrey Grodzovsky 2021-01-11 18:31 ` Andrey Grodzovsky 2021-01-12 9:07 ` Daniel Vetter 2021-01-11 20:45 ` Andrey Grodzovsky 2021-01-11 20:45 ` Andrey Grodzovsky 2021-01-12 9:10 ` Daniel Vetter 2021-01-12 9:10 ` Daniel Vetter 2021-01-12 12:32 ` Christian König 2021-01-12 12:32 ` Christian König 2021-01-12 15:59 ` Andrey Grodzovsky 2021-01-12 15:59 ` Andrey Grodzovsky 2021-01-13 9:14 ` Christian König [this message] 2021-01-13 9:14 ` Christian König 2021-01-13 14:40 ` Andrey Grodzovsky 2021-01-13 14:40 ` Andrey Grodzovsky 2021-01-12 15:54 ` Andrey Grodzovsky 2021-01-12 15:54 ` Andrey Grodzovsky 2021-01-12 8:12 ` Christian König 2021-01-12 8:12 ` Christian König 2021-01-12 9:13 ` Daniel Vetter 2021-01-12 9:13 ` Daniel Vetter 2020-11-21 5:21 ` [PATCH v3 02/12] drm: Unamp the entire device address space on device unplug Andrey Grodzovsky 2020-11-21 5:21 ` Andrey Grodzovsky 2020-11-21 14:16 ` Christian König 2020-11-21 14:16 ` Christian König 2020-11-24 14:44 ` Daniel Vetter 2020-11-24 14:44 ` Daniel Vetter 2020-11-21 5:21 ` [PATCH v3 03/12] drm/ttm: Remap all page faults to per process dummy page Andrey Grodzovsky 2020-11-21 5:21 ` Andrey Grodzovsky 2020-11-21 5:21 ` [PATCH v3 04/12] drm/ttm: Set dma addr to null after freee Andrey Grodzovsky 2020-11-21 5:21 ` Andrey Grodzovsky 2020-11-21 14:13 ` Christian König 2020-11-21 14:13 ` Christian König 2020-11-23 5:15 ` Andrey Grodzovsky 2020-11-23 5:15 ` Andrey Grodzovsky 2020-11-23 8:04 ` Christian König 2020-11-23 8:04 ` Christian König 2020-11-21 5:21 ` [PATCH v3 05/12] drm/ttm: Expose ttm_tt_unpopulate for driver use Andrey Grodzovsky 2020-11-21 5:21 ` Andrey Grodzovsky 2020-11-25 10:42 ` Christian König 2020-11-25 10:42 ` Christian König 2020-11-23 20:05 ` Andrey Grodzovsky 2020-11-23 20:05 ` Andrey Grodzovsky 2020-11-23 20:20 ` Christian König 2020-11-23 20:20 ` Christian König 2020-11-23 20:38 ` Andrey Grodzovsky 2020-11-23 20:38 ` Andrey Grodzovsky 2020-11-23 20:41 ` Christian König 2020-11-23 20:41 ` Christian König 2020-11-23 21:08 ` Andrey Grodzovsky 2020-11-23 21:08 ` Andrey Grodzovsky 2020-11-24 7:41 ` Christian König 2020-11-24 7:41 ` Christian König 2020-11-24 16:22 ` Andrey Grodzovsky 2020-11-24 16:22 ` Andrey Grodzovsky 2020-11-24 16:44 ` Christian König 2020-11-24 16:44 ` Christian König 2020-11-25 10:40 ` Daniel Vetter 2020-11-25 10:40 ` Daniel Vetter 2020-11-25 12:57 ` Christian König 2020-11-25 12:57 ` Christian König 2020-11-25 16:36 ` Daniel Vetter 2020-11-25 16:36 ` Daniel Vetter 2020-11-25 19:34 ` Andrey Grodzovsky 2020-11-25 19:34 ` Andrey Grodzovsky 2020-11-27 13:10 ` Grodzovsky, Andrey 2020-11-27 13:10 ` Grodzovsky, Andrey 2020-11-27 14:59 ` Daniel Vetter 2020-11-27 14:59 ` Daniel Vetter 2020-11-27 16:04 ` Andrey Grodzovsky 2020-11-27 16:04 ` Andrey Grodzovsky 2020-11-30 14:15 ` Daniel Vetter 2020-11-30 14:15 ` Daniel Vetter 2020-11-25 16:56 ` Michel Dänzer 2020-11-25 16:56 ` Michel Dänzer 2020-11-25 17:02 ` Daniel Vetter 2020-11-25 17:02 ` Daniel Vetter 2020-12-15 20:18 ` Andrey Grodzovsky 2020-12-15 20:18 ` Andrey Grodzovsky 2020-12-16 8:04 ` Christian König 2020-12-16 8:04 ` Christian König 2020-12-16 14:21 ` Daniel Vetter 2020-12-16 14:21 ` Daniel Vetter 2020-12-16 16:13 ` Andrey Grodzovsky 2020-12-16 16:13 ` Andrey Grodzovsky 2020-12-16 16:18 ` Christian König 2020-12-16 16:18 ` Christian König 2020-12-16 17:12 ` Daniel Vetter 2020-12-16 17:12 ` Daniel Vetter 2020-12-16 17:20 ` Daniel Vetter 2020-12-16 17:20 ` Daniel Vetter 2020-12-16 18:26 ` Andrey Grodzovsky 2020-12-16 18:26 ` Andrey Grodzovsky 2020-12-16 23:15 ` Daniel Vetter 2020-12-16 23:15 ` Daniel Vetter 2020-12-17 0:20 ` Andrey Grodzovsky 2020-12-17 0:20 ` Andrey Grodzovsky 2020-12-17 12:01 ` Daniel Vetter 2020-12-17 12:01 ` Daniel Vetter 2020-12-17 19:19 ` Andrey Grodzovsky 2020-12-17 19:19 ` Andrey Grodzovsky 2020-12-17 20:10 ` Christian König 2020-12-17 20:10 ` Christian König 2020-12-17 20:38 ` Andrey Grodzovsky 2020-12-17 20:38 ` Andrey Grodzovsky 2020-12-17 20:48 ` Daniel Vetter 2020-12-17 20:48 ` Daniel Vetter 2020-12-17 21:06 ` Andrey Grodzovsky 2020-12-17 21:06 ` Andrey Grodzovsky 2020-12-18 14:30 ` Daniel Vetter 2020-12-18 14:30 ` Daniel Vetter 2020-12-17 20:42 ` Daniel Vetter 2020-12-17 20:42 ` Daniel Vetter 2020-12-17 21:13 ` Andrey Grodzovsky 2020-12-17 21:13 ` Andrey Grodzovsky 2021-01-04 16:33 ` Andrey Grodzovsky 2021-01-04 16:33 ` Andrey Grodzovsky 2020-11-21 5:21 ` [PATCH v3 06/12] drm/sched: Cancel and flush all oustatdning jobs before finish Andrey Grodzovsky 2020-11-21 5:21 ` Andrey Grodzovsky 2020-11-22 11:56 ` Christian König 2020-11-22 11:56 ` Christian König 2020-11-21 5:21 ` [PATCH v3 07/12] drm/sched: Prevent any job recoveries after device is unplugged Andrey Grodzovsky 2020-11-21 5:21 ` Andrey Grodzovsky 2020-11-22 11:57 ` Christian König 2020-11-22 11:57 ` Christian König 2020-11-23 5:37 ` Andrey Grodzovsky 2020-11-23 5:37 ` Andrey Grodzovsky 2020-11-23 8:06 ` Christian König 2020-11-23 8:06 ` Christian König 2020-11-24 1:12 ` Luben Tuikov 2020-11-24 1:12 ` Luben Tuikov 2020-11-24 7:50 ` Christian König 2020-11-24 7:50 ` Christian König 2020-11-24 17:11 ` Luben Tuikov 2020-11-24 17:11 ` Luben Tuikov 2020-11-24 17:17 ` Andrey Grodzovsky 2020-11-24 17:17 ` Andrey Grodzovsky 2020-11-24 17:41 ` Luben Tuikov 2020-11-24 17:41 ` Luben Tuikov 2020-11-24 17:40 ` Christian König 2020-11-24 17:40 ` Christian König 2020-11-24 17:44 ` Luben Tuikov 2020-11-24 17:44 ` Luben Tuikov 2020-11-21 5:21 ` [PATCH v3 08/12] drm/amdgpu: Split amdgpu_device_fini into early and late Andrey Grodzovsky 2020-11-21 5:21 ` Andrey Grodzovsky 2020-11-24 14:53 ` Daniel Vetter 2020-11-24 14:53 ` Daniel Vetter 2020-11-24 15:51 ` Andrey Grodzovsky 2020-11-24 15:51 ` Andrey Grodzovsky 2020-11-25 10:41 ` Daniel Vetter 2020-11-25 10:41 ` Daniel Vetter 2020-11-25 17:41 ` Andrey Grodzovsky 2020-11-25 17:41 ` Andrey Grodzovsky 2020-11-21 5:21 ` [PATCH v3 09/12] drm/amdgpu: Add early fini callback Andrey Grodzovsky 2020-11-21 5:21 ` Andrey Grodzovsky 2020-11-21 5:21 ` [PATCH v3 10/12] drm/amdgpu: Avoid sysfs dirs removal post device unplug Andrey Grodzovsky 2020-11-21 5:21 ` Andrey Grodzovsky 2020-11-24 14:49 ` Daniel Vetter 2020-11-24 14:49 ` Daniel Vetter 2020-11-24 22:27 ` Andrey Grodzovsky 2020-11-24 22:27 ` Andrey Grodzovsky 2020-11-25 9:04 ` Daniel Vetter 2020-11-25 9:04 ` Daniel Vetter 2020-11-25 17:39 ` Andrey Grodzovsky 2020-11-25 17:39 ` Andrey Grodzovsky 2020-11-27 13:12 ` Grodzovsky, Andrey 2020-11-27 13:12 ` Grodzovsky, Andrey 2020-11-27 15:04 ` Daniel Vetter 2020-11-27 15:04 ` Daniel Vetter 2020-11-27 15:34 ` Andrey Grodzovsky 2020-11-27 15:34 ` Andrey Grodzovsky 2020-11-21 5:21 ` [PATCH v3 11/12] drm/amdgpu: Register IOMMU topology notifier per device Andrey Grodzovsky 2020-11-21 5:21 ` Andrey Grodzovsky 2020-11-21 5:21 ` [PATCH v3 12/12] drm/amdgpu: Fix a bunch of sdma code crash post device unplug Andrey Grodzovsky 2020-11-21 5:21 ` Andrey Grodzovsky
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=20669765-8656-0933-ff86-15fc722f9bd8@amd.com \ --to=christian.koenig@amd.com \ --cc=Alexander.Deucher@amd.com \ --cc=Andrey.Grodzovsky@amd.com \ --cc=amd-gfx@lists.freedesktop.org \ --cc=daniel.vetter@ffwll.ch \ --cc=daniel@ffwll.ch \ --cc=dri-devel@lists.freedesktop.org \ --cc=gregkh@linuxfoundation.org \ --cc=yuq825@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.