dri-devel March 2021

dri-devel@lists.freedesktop.org

326 participants
867 discussions

Re: [PATCH 14/17] iommu: remove DOMAIN_ATTR_DMA_USE_FLUSH_QUEUE
by Robin Murphy 16 Mar '21

16 Mar '21

On 2021-03-15 08:33, Christoph Hellwig wrote: > On Fri, Mar 12, 2021 at 04:18:24PM +0000, Robin Murphy wrote: >>> Let me know what you think of the version here: >>> >>> http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/iommu-clean… >>> >>> I'll happily switch the patch to you as the author if you're fine with >>> that as well. >> >> I still have reservations about removing the attribute API entirely and >> pretending that io_pgtable_cfg is anything other than a SoC-specific >> private interface, > > I think a private inteface would make more sense. For now I've just > condensed it down to a generic set of quirk bits and dropped the > attrs structure, which seems like an ok middle ground for now. That > being said I wonder why that quirk isn't simply set in the device > tree? Because it's a software policy decision rather than any inherent property of the platform, and the DT certainly doesn't know *when* any particular device might prefer its IOMMU to use cacheable pagetables to minimise TLB miss latency vs. saving the cache capacity for larger data buffers. It really is most logical to decide this at the driver level. In truth the overall concept *is* relatively generic (a trend towards larger system caches and cleverer usage is about both raw performance and saving power on off-SoC DRAM traffic), it's just the particular implementation of using io-pgtable to set an outer-cacheable walk attribute in an SMMU TCR that's pretty much specific to Qualcomm SoCs. Hence why having a common abstraction at the iommu_domain level, but where the exact details are free to vary across different IOMMUs and their respective client drivers, is in many ways an ideal fit. >> but the reworked patch on its own looks reasonable to >> me, thanks! (I wasn't too convinced about the iommu_cmd_line wrappers >> either...) Just iommu_get_dma_strict() needs an export since the SMMU >> drivers can be modular - I consciously didn't add that myself since I was >> mistakenly thinking only iommu-dma would call it. > > Fixed. Can I get your signoff for the patch? Then I'll switch it to > over to being attributed to you. Sure - I would have thought that the one I originally posted still stands, but for the avoidance of doubt, for the parts of commit 8b6d45c495bd in your tree that remain from what I wrote: Signed-off-by: Robin Murphy <robin.murphy(a)arm.com> Cheers, Robin.

1 0

Need -fixes commit in drm-misc-next
by Noralf Trønnes 16 Mar '21

16 Mar '21

Hi drm-misc maintainers, I have this series: GUD USB Display driver https://patchwork.freedesktop.org/series/87044/#rev3 That depends on this drm-misc-fixes commit: 3a3fe21242a3 ("drm: Use USB controller's DMA mask when importing dmabufs") I would would be nice if it would show up in drm-misc-next soon. Noralf.

2 2

[RFC 0/6] Default request/fence expiry + watchdog
by Tvrtko Ursulin 16 Mar '21

16 Mar '21

From: Tvrtko Ursulin <tvrtko.ursulin(a)intel.com> "Watchdog" aka "restoring hangcheck" aka default request/fence expiry - first post of a somewhat controversial feature so may be somewhat rough in commit messages, commentary and implementation. So only RFC for now. I parenthesise the "watchdog" becuase in classical sense watchdog would allow userspace to ping it and so remain alive. I parenthesise "restoring hangcheck" because this series, contrary to the old hangcheck, is not looking at whether the workload is making any progress from the kernel side either. (Althoguh disclaimer my memory may be leaky - Daniel suspects old hangcheck had some stricter, more indiscriminatory, angles to it. But apart from being prone to both false negatives and false positives I can't remember that myself.) Short version - ask is to fail any user submissions after a set time period. In this RFC that time is ten seconds. Time counts from the moment user submission is "runnable" (implicit and explicit dependencies have been cleared) and keeps counting regardless of the GPU contetion caused by other users of the system. So semantics are really a bit weak but again, I understand this is really wanted by the DRM core. As an attempt to compensate for this brutish nature, I proposed adding extendable configurability via a context param as part of the series. That could allow userspace to pick different semantics (always going more restrictive than the system default) and so implement interesting things like long desired media watchdog. Module trickyness of the implementation there. Test-with: 20210312093329.1639502-1-tvrtko.ursulin(a)linux.intel.com Cc: Daniel Vetter <daniel.vetter(a)ffwll.ch> Chris Wilson (1): drm/i915: Individual request cancellation Tvrtko Ursulin (5): drm/i915: Restrict sentinel requests further drm/i915: Request watchdog infrastructure drm/i915: Allow userspace to configure the watchdog drm/i915: Fail too long user submissions by default drm/i915: Allow configuring default request expiry via modparam drivers/gpu/drm/i915/Kconfig.profile | 8 + drivers/gpu/drm/i915/gem/i915_gem_context.c | 92 ++++++ .../gpu/drm/i915/gem/i915_gem_context_types.h | 4 + drivers/gpu/drm/i915/gt/intel_context_param.h | 11 +- drivers/gpu/drm/i915/gt/intel_context_types.h | 4 + .../gpu/drm/i915/gt/intel_engine_heartbeat.c | 1 + .../drm/i915/gt/intel_execlists_submission.c | 11 +- .../drm/i915/gt/intel_execlists_submission.h | 2 + drivers/gpu/drm/i915/gt/intel_gt.c | 3 + drivers/gpu/drm/i915/gt/intel_gt.h | 2 + drivers/gpu/drm/i915/gt/intel_gt_requests.c | 21 ++ drivers/gpu/drm/i915/gt/intel_gt_types.h | 7 + drivers/gpu/drm/i915/i915_params.c | 5 + drivers/gpu/drm/i915/i915_params.h | 1 + drivers/gpu/drm/i915/i915_request.c | 129 +++++++- drivers/gpu/drm/i915/i915_request.h | 12 +- drivers/gpu/drm/i915/selftests/i915_request.c | 275 ++++++++++++++++++ include/uapi/drm/i915_drm.h | 5 +- 18 files changed, 584 insertions(+), 9 deletions(-) -- 2.27.0

2 11

[PATCH 1/3] drm/qxl: clean up qxl_bo_move_notify
by Christian König 16 Mar '21

16 Mar '21

Remove the unused evict parameter and drop swapping bo->mem. Signed-off-by: Christian König <christian.koenig(a)amd.com> --- drivers/gpu/drm/qxl/qxl_ttm.c | 16 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-) diff --git a/drivers/gpu/drm/qxl/qxl_ttm.c b/drivers/gpu/drm/qxl/qxl_ttm.c index b7f77eb685cb..47afe95d04a1 100644 --- a/drivers/gpu/drm/qxl/qxl_ttm.c +++ b/drivers/gpu/drm/qxl/qxl_ttm.c @@ -121,7 +121,6 @@ static struct ttm_tt *qxl_ttm_tt_create(struct ttm_buffer_object *bo, } static void qxl_bo_move_notify(struct ttm_buffer_object *bo, - bool evict, struct ttm_resource *new_mem) { struct qxl_bo *qbo; @@ -144,29 +143,22 @@ static int qxl_bo_move(struct ttm_buffer_object *bo, bool evict, struct ttm_resource *old_mem = &bo->mem; int ret; - qxl_bo_move_notify(bo, evict, new_mem); + qxl_bo_move_notify(bo, new_mem); ret = ttm_bo_wait_ctx(bo, ctx); if (ret) - goto out; + return ret; if (old_mem->mem_type == TTM_PL_SYSTEM && bo->ttm == NULL) { ttm_bo_move_null(bo, new_mem); return 0; } - ret = ttm_bo_move_memcpy(bo, ctx, new_mem); -out: - if (ret) { - swap(*new_mem, bo->mem); - qxl_bo_move_notify(bo, false, new_mem); - swap(*new_mem, bo->mem); - } - return ret; + return ttm_bo_move_memcpy(bo, ctx, new_mem); } static void qxl_bo_delete_mem_notify(struct ttm_buffer_object *bo) { - qxl_bo_move_notify(bo, false, NULL); + qxl_bo_move_notify(bo, NULL); } static struct ttm_device_funcs qxl_bo_driver = { -- 2.25.1

2 3

[PATCH] drm/amdgpu: nuke the ih reentrant lock
by Christian König 16 Mar '21

16 Mar '21

Interrupts on are non-reentrant on linux. This is just an ancient leftover from radeon where irq processing was kicked of from different places. Signed-off-by: Christian König <christian.koenig(a)amd.com> --- drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 1 - drivers/gpu/drm/amd/amdgpu/amdgpu_ih.c | 5 ----- drivers/gpu/drm/amd/amdgpu/amdgpu_ih.h | 1 - 3 files changed, 7 deletions(-) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c index a15f1b604733..886625fb464b 100644 --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c @@ -3284,7 +3284,6 @@ int amdgpu_device_init(struct amdgpu_device *adev, /* mutex initialization are all done here so we * can recall function without having locking issues */ - atomic_set(&adev->irq.ih.lock, 0); mutex_init(&adev->firmware.mutex); mutex_init(&adev->pm.mutex); mutex_init(&adev->gfx.gpu_clock_mutex); diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ih.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_ih.c index 1024065f1f03..faaa6aa2faaf 100644 --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ih.c +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ih.c @@ -228,10 +228,6 @@ int amdgpu_ih_process(struct amdgpu_device *adev, struct amdgpu_ih_ring *ih) wptr = amdgpu_ih_get_wptr(adev, ih); restart_ih: - /* is somebody else already processing irqs? */ - if (atomic_xchg(&ih->lock, 1)) - return IRQ_NONE; - DRM_DEBUG("%s: rptr %d, wptr %d\n", __func__, ih->rptr, wptr); /* Order reading of wptr vs. reading of IH ring data */ @@ -244,7 +240,6 @@ int amdgpu_ih_process(struct amdgpu_device *adev, struct amdgpu_ih_ring *ih) amdgpu_ih_set_rptr(adev, ih); wake_up_all(&ih->wait_process); - atomic_set(&ih->lock, 0); /* make sure wptr hasn't changed while processing */ wptr = amdgpu_ih_get_wptr(adev, ih); diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ih.h b/drivers/gpu/drm/amd/amdgpu/amdgpu_ih.h index 87ec6d20dbe0..0649b59830a5 100644 --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ih.h +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ih.h @@ -64,7 +64,6 @@ struct amdgpu_ih_ring { bool enabled; unsigned rptr; - atomic_t lock; struct amdgpu_ih_regs ih_regs; /* For waiting on IH processing at checkpoint. */ -- 2.25.1

2 6

[syzbot] upstream boot error: WARNING in vkms_vblank_simulate
by syzbot 16 Mar '21

16 Mar '21

Hello, syzbot found the following issue on: HEAD commit: f78d76e7 Merge tag 'drm-fixes-2021-03-12-1' of git://anong.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=11c16ba2d00000 kernel config: https://syzkaller.appspot.com/x/.config?x=dc02c6afcb046874 dashboard link: https://syzkaller.appspot.com/bug?extid=333bd014262fd5d0a418 userspace arch: arm IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+333bd014262fd5d0a418(a)syzkaller.appspotmail.com ------------[ cut here ]------------ WARNING: CPU: 0 PID: 0 at drivers/gpu/drm/vkms/vkms_crtc.c:21 vkms_vblank_simulate+0x26c/0x2f4 drivers/gpu/drm/vkms/vkms_crtc.c:41 Modules linked in: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.12.0-rc2-syzkaller-00338-gf78d76e72a46 #0 Hardware name: linux,dummy-virt (DT) pstate: 20000085 (nzCv daIf -PAN -UAO -TCO BTYPE=--) pc : vkms_vblank_simulate+0x26c/0x2f4 drivers/gpu/drm/vkms/vkms_crtc.c:21 lr : hrtimer_forward_now include/linux/hrtimer.h:510 [inline] lr : vkms_vblank_simulate+0x90/0x2f4 drivers/gpu/drm/vkms/vkms_crtc.c:19 sp : ffff00006a693cd0 x29: ffff00006a693cd0 x28: ffff00000c9d1e58 x27: dfff800000000000 x26: ffff00006a67f540 x25: 1fffe0000d4cfeb1 x24: 1fffe0000d4cfeaa x23: ffff00000c9d0d30 x22: 0000000000fe4c00 x21: ffff00006a67f540 x20: ffff00000c9d0e58 x19: ffff00000c9d1e58 x18: ffff00006a6a1b48 x17: 1fffe00001952345 x16: 0000000000000000 x15: ffff8000197bf810 x14: 1fffe0000d4d2750 x13: 0000000000000001 x12: 0000000000000033 x11: 1ffff00002fb4936 x10: 0000000000000007 x9 : 1ffff00002fb4943 x8 : ffff800017d14c00 x7 : 00000000f1f1f1f1 x6 : dfff800000000000 x5 : 7fffffffffffffff x4 : 00000008e44f6b90 x3 : 00000008e54db790 x2 : 00000008e44f6b90 x1 : 00000008e54db790 x0 : 0000000000000002 Call trace: vkms_vblank_simulate+0x26c/0x2f4 drivers/gpu/drm/vkms/vkms_crtc.c:41 __run_hrtimer kernel/time/hrtimer.c:1519 [inline] __hrtimer_run_queues+0x590/0xe40 kernel/time/hrtimer.c:1583 hrtimer_interrupt+0x2d4/0x810 kernel/time/hrtimer.c:1645 timer_handler drivers/clocksource/arm_arch_timer.c:647 [inline] arch_timer_handler_phys+0x4c/0x70 drivers/clocksource/arm_arch_timer.c:665 handle_percpu_devid_irq+0x19c/0x330 kernel/irq/chip.c:930 generic_handle_irq_desc include/linux/irqdesc.h:158 [inline] generic_handle_irq kernel/irq/irqdesc.c:652 [inline] __handle_domain_irq+0x11c/0x1f0 kernel/irq/irqdesc.c:689 handle_domain_irq include/linux/irqdesc.h:176 [inline] gic_handle_irq+0x5c/0x1b0 drivers/irqchip/irq-gic.c:370 el1_irq+0xb4/0x180 arch/arm64/kernel/entry.S:669 arch_local_irq_restore arch/arm64/include/asm/irqflags.h:124 [inline] queue_work_on+0x74/0x110 kernel/workqueue.c:1528 queue_work include/linux/workqueue.h:507 [inline] cursor_timer_handler+0x64/0x100 drivers/video/fbdev/core/fbcon.c:397 call_timer_fn+0x1d4/0x9c4 kernel/time/timer.c:1431 expire_timers kernel/time/timer.c:1476 [inline] __run_timers.part.0+0x530/0xa00 kernel/time/timer.c:1745 __run_timers kernel/time/timer.c:1726 [inline] run_timer_softirq+0xa4/0x1a0 kernel/time/timer.c:1758 _stext+0x2b4/0x1084 do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline] invoke_softirq kernel/softirq.c:228 [inline] __irq_exit_rcu+0x46c/0x510 kernel/softirq.c:422 irq_exit+0x14/0x84 kernel/softirq.c:446 __handle_domain_irq+0x120/0x1f0 kernel/irq/irqdesc.c:692 handle_domain_irq include/linux/irqdesc.h:176 [inline] gic_handle_irq+0x5c/0x1b0 drivers/irqchip/irq-gic.c:370 el1_irq+0xb4/0x180 arch/arm64/kernel/entry.S:669 arch_local_irq_enable+0xc/0x14 arch/arm64/include/asm/irqflags.h:37 default_idle_call+0x64/0xf4 kernel/sched/idle.c:112 cpuidle_idle_call kernel/sched/idle.c:194 [inline] do_idle+0x38c/0x4ec kernel/sched/idle.c:300 cpu_startup_entry+0x28/0x80 kernel/sched/idle.c:397 rest_init+0x1d0/0x2cc init/main.c:721 arch_call_rest_init+0x10/0x1c start_kernel+0x3b0/0x3e8 init/main.c:1064 0x0 --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller(a)googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

3 4

[PULL] drm-misc-next
by Maxime Ripard 16 Mar '21

16 Mar '21

Hi, It's been a fairly quiet week, but here are the changes for drm-misc-next Thanks! Maxime drm-misc-next-2021-03-16: drm-misc-next for 5.13: UAPI Changes: - Documentation for the DRM_CAP_* defines Cross-subsystem Changes: Core Changes: - dma-fence: More documentation for the recoverable page faults - fb_defio: Remove custom address_space operations Driver Changes: - panel: Support for the Innolux N116BCA-EA1 - stm: Use simple encoder for lcdc - virtio: Fix potential virtio_gpu_object_array leak The following changes since commit 762949bb1da78941b25e63f7e952af037eee15a9: drm: fix drm_mode_create_blob comment (2021-03-02 20:43:34 +0100) are available in the Git repository at: git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2021-03-16 for you to fetch changes up to ccf953d8f3d68e85e577e843fdcde8872b0a9769: fb_defio: Remove custom address_space_operations (2021-03-12 15:10:03 +0100) ---------------------------------------------------------------- drm-misc-next for 5.13: UAPI Changes: - Documentation for the DRM_CAP_* defines Cross-subsystem Changes: Core Changes: - dma-fence: More documentation for the recoverable page faults - fb_defio: Remove custom address_space operations Driver Changes: - panel: Support for the Innolux N116BCA-EA1 - stm: Use simple encoder for lcdc - virtio: Fix potential virtio_gpu_object_array leak ---------------------------------------------------------------- Christian König (1): drm/sched: select new rq even if there is only one v3 Daniel Vetter (1): dma-fence: Document recoverable page fault implications Douglas Anderson (6): drm/panel-simple: Undo enable if HPD never asserts drm/panel-simple: Don't wait longer for HPD than hpd_absent_delay drm/panel-simple: Retry if we timeout waiting for HPD dt-bindings: dt-bindings: display: simple: Add N116BCA-EA1 drm/panel-simple: Add N116BCA-EA1 drm: panel: simple: Set enable delay for BOE NV110WTM-N61 Jagan Teki (1): drm/stm: ltdc: Use simple encoder Jianhui Zhao (1): docs: gpu: fix typo Linus Walleij (1): drm/mcde/panel: Inverse misunderstood flag Matthew Wilcox (Oracle) (1): fb_defio: Remove custom address_space_operations Paul Cercueil (1): drm/ingenic: Fix non-OSD mode Simon Ser (1): drm/uapi: document kernel capabilities Tian Tao (1): drm/vboxvideo: Use managed VRAM-helper initialization Yannick Fertre (1): drm/stm: dsi: Avoid printing errors for -EPROBE_DEFER xndcn (1): drm/virtio: fix possible leak/unlock virtio_gpu_object_array .../bindings/display/panel/panel-simple.yaml | 2 + Documentation/driver-api/dma-buf.rst | 76 +++++++++++++ Documentation/gpu/todo.rst | 2 +- drivers/gpu/drm/ingenic/ingenic-drm-drv.c | 11 +- drivers/gpu/drm/mcde/mcde_dsi.c | 2 +- drivers/gpu/drm/panel/panel-novatek-nt35510.c | 3 +- drivers/gpu/drm/panel/panel-samsung-s6d16d0.c | 4 +- drivers/gpu/drm/panel/panel-samsung-s6e63m0-dsi.c | 1 - drivers/gpu/drm/panel/panel-simple.c | 85 +++++++++++++- drivers/gpu/drm/panel/panel-sony-acx424akp.c | 3 +- drivers/gpu/drm/scheduler/sched_entity.c | 6 +- drivers/gpu/drm/stm/dw_mipi_dsi-stm.c | 9 +- drivers/gpu/drm/stm/ltdc.c | 12 +- drivers/gpu/drm/vboxvideo/vbox_ttm.c | 7 +- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 2 +- drivers/gpu/drm/virtio/virtgpu_object.c | 1 + drivers/video/fbdev/core/fb_defio.c | 35 ------ drivers/video/fbdev/core/fbmem.c | 4 - include/linux/fb.h | 3 - include/uapi/drm/drm.h | 125 ++++++++++++++++++++- 20 files changed, 303 insertions(+), 90 deletions(-)

1 0

[GIT FIXES FOR v5.12] R-Car DU fix
by Laurent Pinchart 16 Mar '21

16 Mar '21

The following changes since commit 4042160c2e5433e0759782c402292a90b5bf458d: drm/nouveau: fix dma syncing for loops (v2) (2021-03-12 11:21:47 +1000) are available in the Git repository at: git://linuxtv.org/pinchartl/media.git tags/du-fixes-20210316 for you to fetch changes up to 7a1adbd2399023177508836c2b13a6c723035409: drm: rcar-du: Use drmm_encoder_alloc() to manage encoder (2021-03-16 03:12:36 +0200) ---------------------------------------------------------------- R-Car DU v5.12 fix ---------------------------------------------------------------- Kieran Bingham (1): drm: rcar-du: Use drmm_encoder_alloc() to manage encoder drivers/gpu/drm/rcar-du/rcar_du_encoder.c | 31 ++++++------------------------- 1 file changed, 6 insertions(+), 25 deletions(-) -- Regards, Laurent Pinchart

1 0

[Bug 212279] New: AMDGPU doesn’t expose any way of setting the full RGB range [ryzen+ mobile]
by bugzilla-daemon＠bugzilla.kernel.org 15 Mar '21

15 Mar '21

https://bugzilla.kernel.org/show_bug.cgi?id=212279 Bug ID: 212279 Summary: AMDGPU doesn’t expose any way of setting the full RGB range [ryzen+ mobile] Product: Drivers Version: 2.5 Kernel Version: all Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: enhancement Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: ledufff(a)hotmail.com Regression: No Hello, I'd like to address that there's no way to set full RGB range to HDMI for my Thinkpad E495 (AMD Ryzen 5 3500U). I tried editing the edid.bin with wxedid but had no luck. Is there a plan to enable this in the near future?. Thanks. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

1 3

[drm-intel:topic/core-for-CI 20/30] include/linux/kconfig.h:7:10: fatal error: generated/autoconf.h: No such file or directory
by kernel test robot 15 Mar '21

15 Mar '21

tree: git://anongit.freedesktop.org/drm-intel topic/core-for-CI head: 785b066b32b630e4735ca6e51acbb067703e2d3a commit: 98a674f9cd22c2cf6f507ccc1f26fae3c91d1271 [20/30] Revert "drm/i915: Don't select BROKEN" config: alpha-randconfig-r033-20210315 (attached as .config) compiler: alpha-linux-gcc (GCC) 9.3.0 reproduce (this is a W=1 build): wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross git remote add drm-intel git://anongit.freedesktop.org/drm-intel git fetch --no-tags drm-intel topic/core-for-CI git checkout 98a674f9cd22c2cf6f507ccc1f26fae3c91d1271 # save the attached .config to linux build tree COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=alpha If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot <lkp(a)intel.com> All errors (new ones prefixed by >>): In file included from scripts/selinux/mdp/mdp.c:22: >> include/linux/kconfig.h:7:10: fatal error: generated/autoconf.h: No such file or directory 7 | #include <generated/autoconf.h> | ^~~~~~~~~~~~~~~~~~~~~~ compilation terminated. -- Makefile arch include kernel scripts source usr [scripts/kconfig/Makefile:63: syncconfig] Error 1 Makefile arch include kernel scripts source usr [Makefile:600: syncconfig] Error 2 Makefile arch include kernel scripts source usr [Makefile:709: include/config/auto.conf.cmd] Error 2 Failed to remake makefile 'include/config/auto.conf.cmd'. Failed to remake makefile 'include/config/auto.conf'. In file included from scripts/selinux/mdp/mdp.c:22: >> include/linux/kconfig.h:7:10: fatal error: generated/autoconf.h: No such file or directory 7 | #include <generated/autoconf.h> | ^~~~~~~~~~~~~~~~~~~~~~ compilation terminated. Makefile arch include kernel scripts source usr [scripts/Makefile.host:95: scripts/selinux/mdp/mdp] Error 1 Target '__build' not remade because of errors. Makefile arch include kernel scripts source usr [scripts/Makefile.build:514: scripts/selinux/mdp] Error 2 Target '__build' not remade because of errors. Makefile arch include kernel scripts source usr [scripts/Makefile.build:514: scripts/selinux] Error 2 Target '__build' not remade because of errors. Makefile arch include kernel scripts source usr [Makefile:1217: scripts] Error 2 Target 'modules_prepare' not remade because of errors. make: Makefile arch include kernel scripts source usr [Makefile:215: __sub-make] Error 2 make: Target 'modules_prepare' not remade because of errors. -- Makefile arch include kernel scripts source usr [scripts/kconfig/Makefile:63: syncconfig] Error 1 Makefile arch include kernel scripts source usr [Makefile:600: syncconfig] Error 2 Makefile arch include kernel scripts source usr [Makefile:709: include/config/auto.conf.cmd] Error 2 Failed to remake makefile 'include/config/auto.conf.cmd'. Failed to remake makefile 'include/config/auto.conf'. In file included from scripts/selinux/mdp/mdp.c:22: >> include/linux/kconfig.h:7:10: fatal error: generated/autoconf.h: No such file or directory 7 | #include <generated/autoconf.h> | ^~~~~~~~~~~~~~~~~~~~~~ compilation terminated. Makefile arch include kernel scripts source usr [scripts/Makefile.host:95: scripts/selinux/mdp/mdp] Error 1 Target '__build' not remade because of errors. Makefile arch include kernel scripts source usr [scripts/Makefile.build:514: scripts/selinux/mdp] Error 2 Target '__build' not remade because of errors. Makefile arch include kernel scripts source usr [scripts/Makefile.build:514: scripts/selinux] Error 2 Target '__build' not remade because of errors. Makefile arch include kernel scripts source usr [Makefile:1217: scripts] Error 2 Target 'prepare' not remade because of errors. make: Makefile arch include kernel scripts source usr [Makefile:215: __sub-make] Error 2 make: Target 'prepare' not remade because of errors. vim +7 include/linux/kconfig.h 8b59cd81dc5e72 Masahiro Yamada 2020-04-23 6 2a11c8ea20bf85 Michal Marek 2011-07-20 @7 #include <generated/autoconf.h> 2a11c8ea20bf85 Michal Marek 2011-07-20 8 :::::: The code at line 7 was first introduced by commit :::::: 2a11c8ea20bf850b3a2c60db8c2e7497d28aba99 kconfig: Introduce IS_ENABLED(), IS_BUILTIN() and IS_MODULE() :::::: TO: Michal Marek <mmarek(a)suse.cz> :::::: CC: Michal Marek <mmarek(a)suse.cz> --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

1 0

← Newer
1
...
54
55
56
57
58
59
60
...
87
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2021