Attachment 142039 Details for Bug 108381 – sample code to reproduce the issue

sample code to reproduce the issue

amdgpu_bug.c (text/x-csrc), 1.44 KB, created by Yong Zhang on 2018-10-16 05:11:55 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Yong Zhang

Created: 2018-10-16 05:11:55 UTC

Size: 1.44 KB

patch

obsolete

>//
>// Created by root on 18-10-16.
>//
>
>#include <gbm.h>
>#include <xf86drm.h>
>#include <fcntl.h>
>#include <stdio.h>
>#include <unistd.h>
>
>int main() {
>    static const int width = 720, height = 1280, format = GBM_FORMAT_ABGR8888;
>
>    int drm_fd = open("/dev/dri/renderD128", O_RDWR | O_CLOEXEC);
>    auto gbm = gbm_create_device(drm_fd);
>    auto bo1 = gbm_bo_create(gbm, width, height, format, GBM_BO_USE_RENDERING);
>    auto handle = gbm_bo_get_handle(bo1);
>
>    auto fd = gbm_bo_get_fd(bo1);
>    auto stride = gbm_bo_get_stride(bo1);
>    auto offset = gbm_bo_get_offset(bo1, 0);
>    auto modifier = gbm_bo_get_modifier(bo1);
>
>    gbm_bo_destroy(bo1);
>
>    struct gbm_import_fd_modifier_data data = {};
>
>    data.width = width;
>    data.height = height;
>    data.format = format;
>
>    data.num_fds = 1;
>    data.fds[0] = fd;
>    data.strides[0] = stride;
>    data.offsets[0] = offset;
>    data.modifier = modifier;
>
>    auto bo2 = gbm_bo_import(gbm, GBM_BO_IMPORT_FD_MODIFIER, &data, 0);
>    auto bo3 = gbm_bo_import(gbm, GBM_BO_IMPORT_FD_MODIFIER, &data, 0);
>
>    close(fd);
>
>    handle = gbm_bo_get_handle(bo2);
>
>    fprintf(stderr, "gem_name=0x%08x bo1=%p bo2=%p\n", handle.u32, bo2, bo3);
>    getchar();
>
>    gbm_bo_destroy(bo2);
>    gbm_bo_destroy(bo3);
>
>    fprintf(stderr, "execute cat /sys/kernel/debug/dri/0/amdgpu_gem_info, you will find gem 0x%08x is still active\n", handle.u32);
>    getchar();
>
>    gbm_device_destroy(gbm);
>    close(drm_fd);
>
>    return 0;
>}

Actions: View

Attachments on bug 108381: 142039 | 142040

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.