dri-devel March 2018

dri-devel@lists.freedesktop.org

263 participants
1856 discussions

[git pull] drm fixes for 4.16-rc6
by Dave Airlie 16 Mar '18

16 Mar '18

Hi Linus, i915 has a backlight fix for some panels, a pm and a fencing fix, along with some GVT fixes. amdgpu has a backlight fix across suspend/resume, an object destruction ordering issue fix, and a displayport fix nouveau has two backlight fixes, and a fix for some lockups. Pretty quiet week, seems like everyone was fixing backlights. Dave. The following changes since commit 0c8efd610b58cb23cefdfa12015799079aef94ae: Linux 4.16-rc5 (2018-03-11 17:25:09 -0700) are available in the Git … [View More]repository at: git://people.freedesktop.org/~airlied/linux tags/drm-fixes-for-v4.16-rc6 for you to fetch changes up to 3a1b5de36fdf403d1b004e537dc13997633d65df: Merge tag 'drm-intel-fixes-2018-03-15' of git://anongit.freedesktop.org/drm/drm-intel into drm-fixes (2018-03-16 12:51:35 +1000) ---------------------------------------------------------------- i915, amd and nouveau fixes ---------------------------------------------------------------- Alex Deucher (1): drm/amdgpu: save/restore backlight level in legacy dce code Chris Wilson (2): drm/i915: Only prune fences after wait-for-all drm/i915: Kick the rps worker when changing the boost frequency Christian König (2): drm/amdgpu: fix prime teardown order drm/radeon: fix prime teardown order Dave Airlie (4): Merge branch 'drm-fixes-4.16' of git://people.freedesktop.org/~agd5f/linux into drm-fixes Merge tag 'drm-intel-fixes-2018-03-14' of git://anongit.freedesktop.org/drm/drm-intel into drm-fixes Merge branch 'linux-4.16' of git://github.com/skeggsb/linux into drm-fixes Merge tag 'drm-intel-fixes-2018-03-15' of git://anongit.freedesktop.org/drm/drm-intel into drm-fixes Karol Herbst (1): drm/nouveau/bl: fix backlight regression Lukas Wunner (1): drm/nouveau/bl: Fix oops on driver unbind Michel Dänzer (1): drm/amdgpu/dce: Don't turn off DP sink when disconnected Min He (1): drm/i915/gvt: keep oa config in shadow ctx Mustamin B Mustaffa (1): drm/i915: Enable VBT based BL control for DP Māris Nartišs (1): drm/nouveau/mmu: ALIGN_DOWN correct variable Rodrigo Vivi (1): Merge tag 'gvt-fixes-2018-03-15' of https://github.com/intel/gvt-linux into drm-intel-fixes Xiong Zhang (1): drm/i915/gvt: Add runtime_pm_get/put into gvt_switch_mmio Zhenyu Wang (1): drm/i915/gvt: fix user copy warning by whitelist workload rb_tail field fred gao (1): drm/i915/gvt: Correct the privilege shadow batch buffer address drivers/gpu/drm/amd/amdgpu/amdgpu_connectors.c | 31 +++++------ drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c | 2 - drivers/gpu/drm/amd/amdgpu/amdgpu_mode.h | 1 + drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 2 + drivers/gpu/drm/amd/amdgpu/atombios_encoders.c | 4 +- drivers/gpu/drm/amd/amdgpu/atombios_encoders.h | 5 ++ drivers/gpu/drm/amd/amdgpu/dce_v10_0.c | 8 +++ drivers/gpu/drm/amd/amdgpu/dce_v11_0.c | 8 +++ drivers/gpu/drm/amd/amdgpu/dce_v6_0.c | 8 +++ drivers/gpu/drm/amd/amdgpu/dce_v8_0.c | 8 +++ drivers/gpu/drm/i915/gvt/cmd_parser.c | 8 +++ drivers/gpu/drm/i915/gvt/mmio_context.c | 2 + drivers/gpu/drm/i915/gvt/scheduler.c | 71 ++++++++++++++++++++++++-- drivers/gpu/drm/i915/gvt/scheduler.h | 5 ++ drivers/gpu/drm/i915/i915_gem.c | 16 ++++-- drivers/gpu/drm/i915/i915_sysfs.c | 10 +++- drivers/gpu/drm/i915/intel_dp.c | 10 ++-- drivers/gpu/drm/nouveau/nouveau_backlight.c | 14 ++--- drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmm.c | 2 +- drivers/gpu/drm/radeon/radeon_gem.c | 2 - drivers/gpu/drm/radeon/radeon_object.c | 2 + 21 files changed, 169 insertions(+), 50 deletions(-) [View Less]

1 0

[Bug 105401] Unable to start X on Vega AMDGPU(0): amdgpu_setup_kernel_mem failed
by bugzilla-daemon＠freedesktop.org 16 Mar '18

16 Mar '18

https://bugs.freedesktop.org/show_bug.cgi?id=105401 Bug ID: 105401 Summary: Unable to start X on Vega AMDGPU(0): amdgpu_setup_kernel_mem failed Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: tpearson(a)… [View More]

1 7

[PULL] drm-intel-fixes
by Rodrigo Vivi 15 Mar '18

15 Mar '18

Hi Dave, Sorry for the last minute and for sending 2 pull requests in a short time, but we just got a pull request from GVT. It passes our CI-fast-feedback and the full run is still running. Please if we still have time please consider pulling it, otherwise this will be part of next regular one. Here goes drm-intel-fixes-2018-03-15: Only GVT fixes: - Two warnings fix for runtime pm and usr copy (Xiong, Zhenyu) - OA context fix for vGPU profiling (Min) - privilege batch buffer reloc fix (… [View More]

1 0

[PATCH 0/8] Use clk bulk API in exynos5433 drivers
by Maciej Purski 15 Mar '18

15 Mar '18

Hi all, the main goal of this patchset is to simplify clk management code in exynos5433 drivers by using clk bulk API. In order to achieve that, patch #1 adds a new function to clk core, which dynamically allocates clk_bulk_data array and fills its id fields. Best regards, Maciej Purski Maciej Purski (8): clk: Add clk_bulk_alloc functions media: s5p-jpeg: Use bulk clk API drm/exynos/decon: Use clk bulk API drm/exynos/dsi: Use clk bulk API drm/exynos: mic: Use clk bulk API drm/… [View More]

6 17

fbcon non-desktop display use
by Charles Lohr 15 Mar '18

15 Mar '18

There was a patch submitted by Keith Packard which prevents fbcon from using non-desktop displays, but this breaks vive, and other HMD development/use on embedded and other fbdev systems ( https://patchwork.kernel.org/patch/10053989/ ). Even if the vive is the only device connected, it will still not permit it to be operated. See https://github.com/linux-sunxi/linux-sunxi/issues/291 for dri with a lot of debugging turned on. I can understand that most users would probably prefer that the … [View More]

3 4

[maintainer-tools PATCH] doc: how to become a drm-intel committer
by Jani Nikula 15 Mar '18

15 Mar '18

Until now, the drm-intel commit access have been handed out ad hoc, without transparency, consistency, or fairness. With pressure to add more committers, this is no longer tenable, if it ever was. Document the requirements and expectations around becoming a drm-intel committer. The Linux kernel operates in a model where, by and large, only maintainers commit patches. Maintainer teams are no longer rare, but the drm-intel and drm-misc maintainer/committer model is definitely an outlier. The … [View More]drm-intel maintainers believe that a reasonable level of experience and track record of working on the driver, as well as actively engaging in the community upstream, are necessary before becoming a committer. While the requirements outlined here may seem strict in contrast with many projects, they are extremely liberal by kernel standards. Finally, no rules are carved in stone. We fully expect the requirements to be adjusted later. However, it will be much easier to start strict and relax the requirements later than the other way round. Cc: Gustavo Padovan <gustavo(a)padovan.org> Cc: Maarten Lankhorst <maarten.lankhorst(a)linux.intel.com> Cc: Sean Paul <seanpaul(a)chromium.org> Cc: Dave Airlie <airlied(a)gmail.com> Cc: dim-tools(a)lists.freedesktop.org Cc: dri-devel(a)lists.freedesktop.org Cc: intel-gfx(a)lists.freedesktop.org Signed-off-by: Jani Nikula <jani.nikula(a)intel.com> Signed-off-by: Joonas Lahtinen <joonas.lahtinen(a)linux.intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi(a)intel.com> --- We encourage the drm-misc maintainers to consider and document your requirements for committers. While there's certain appeal to aligning on the rules between drm-misc and drm-intel, we don't think they necessarily have to be the same. --- commit-access.rst | 143 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ index.rst | 1 + 2 files changed, 144 insertions(+) create mode 100644 commit-access.rst diff --git a/commit-access.rst b/commit-access.rst new file mode 100644 index 000000000000..dbc50f2b5bd3 --- /dev/null +++ b/commit-access.rst @@ -0,0 +1,143 @@ +=============== + Commit Access +=============== + +The drm-misc and drm-intel repositories operate in a maintainer/committer model +with a large pool committers who can push patches in accordance with the stated +merge criteria, and maintainers handling pull requests, topic branches, merges, +and so on. + +This document outlines the requirements for becoming a committer. + +drm-misc +-------- + +TBD. + +drm-intel +--------- + +Requirements +~~~~~~~~~~~~ + +The baseline requirements for becoming a drm-intel committer are: + +- Comfortable with the open collaboration model we have. + +- Enough experience to gauge reasonably well how much review a patch needs, and + when pushing a patch, whether it needs acks from domain experts or + maintainers. + +- Strong presence in the project communication channels (intel-gfx mailing list + and #intel-gfx IRC channel) for topics in their area of expertise. + +Since everyone is different and has different focus in their work, there are no +hard and fast rules, but just indicators and some judgement. + +Positive indicators are: + +- Decent amount of non-trivial patches merged in the past year (25+ patches, + excluding simple code movement, typo fixes and similar patches). + +- Decent amount of in-depth review, again 25+ in the past year as the threshold. + +- Lots of experience and commit rights in related open-source projects, like + Mesa, or kernel trees like drm-misc, since the processes are very similar. 2+ + years as the threshold here, and this is also fulfilled after 2+ years of + working in the virtual upstream team (product tree hacking doesn't count). + +- Already merged a complex feature, e.g. spanning multiple subsystems or even + involving userspace. + +- Active member on freedesktop.org bugzilla. A developer that besides submitting + patches to fix bugs is also engaged on bugs discussion giving constructive + comments helping to drive the bug entry to a solution. Hence keeping bug list + active, clean, and under control. + +Contra-indicators are: + +- Not around on IRC (taking timezones into account of course). + +- Mostly simple patches and rubber-stamping reviews not resulting in in-depth + discussions. + +- No complete feature patch set merged yet. + +As a rule of thumb, commit rights will be granted when most positive indicators +are fulfilled and no negative indicators present. The current project +maintainers assess whether a candidate meets the requirements, and make the +decisions about commit rights. + +Nomination +~~~~~~~~~~ + +Any developer, who already have demonstrated some of positive requirements, can +be nominated at any time by anyone: maintainers, committers, managers, peers, +and even self nomination are accepted. + +Nomination process is simply sending an email to the drm-intel +maintainers. Please nominate one person per email, and Cc: the +nominee. Nominations are processed by the maintainers on a first come, first +served basis, as nominations are received. + +Nomination is not a guarantee of the commit rights. In case a nomination is +rejected, the maintainers will give constructive feedback on what areas the +nominee should try to work on. + +When there are several nominees at the same time, the ramp-up time on the tools +and processes, and the support bandwidth limit the amount of rights that can be +distributed at once. Maintainers are responsible for collecting all the +candidates in a list that will be sorted out following some criteria: + +- More recent activity. It is easier to absorb and ramp-up a committer that is + currently active on i915 with pending patches to get merged. + +- More positive indicators. + +- Fewer contra-indicators. + +After the nomination has been processed and a decision has been made about +giving or postponing giving out the commit rights to the nominee, there will be +a reply from the maintainers to the the nominated person only. + +In case the nominee is accepted as a committer and accepts the new role, the +nominee will need to request a freedesktop.org account according to +https://www.freedesktop.org/wiki/AccountRequests/, and the drm-intel maintainers +will ack adding the account with drm-intel access on the account request bug. If +the nominee already has a freedesktop.org account, the drm-intel maintainers +will file the access request bug. + +Revocation +~~~~~~~~~~ + +- Self abdicate. Anyone at any time can explicitly request to be removed from + the list of drm-intel committers. + +- Long period of inactivity on DRM projects and community. It is very common to + have people changing jobs and not contributing anymore to DRM related + projects. So, in order to keep the list clean and under control, after one + year of inactivity, commit rights can be withdrawn with or without + notification. + +- Repeatedly breaking the rules on pushing patches. Everyone makes mistakes, + especially when ramping up and getting used to the maintainer tools. However, + commit rights could be revoked when a committer has been repeatedly observed, + and notified, of: + + - Pushing patches without review (or acks from maintainers or domain experts + when required). + + - Pushing patches that had a clear rejection from maintainers or other + committers or unresolved review comments. + + - Pushing patches without proper tags or links. + + - Pushing patches to other branches than drm-intel-next-queued. + + - Pushing patches without using dim tools. + + - Pushing patches that didn’t pass CI. + +- Freedesktop.org Code of Conduct violations may lead to temporary or permanent + account or commit rights suspension according to freedesktop.org umbrella + rules. diff --git a/index.rst b/index.rst index d2142a7898f8..2db033161196 100644 --- a/index.rst +++ b/index.rst @@ -23,6 +23,7 @@ Contents: :maxdepth: 2 repositories + commit-access drm-misc drm-intel dim -- 2.11.0 [View Less]

2 3

[PATCH v5 0/6] dt-bindings: add bindings for USB physical connector
by Andrzej Hajda 15 Mar '18

15 Mar '18

Hi, Thanks for reviews of previous iterations. This patchset introduces USB physical connector bindings, together with working example. I have removed RFC prefix - the patchset seems to be heading to a happy end :) v5: fixed extra parenthesis in dts, renamed extcon function. v4: improved binding descriptions, added missing reg in dts. v3: Separate binding for Samsung 11-pin connector, added full-blown USB-C example. v2: I have addressed comments by Rob and Laurent, thanks Changes in … [View More]

7 36

[Bug 198985] New: BUG: KASAN: use-after-free in amdgpu_job_free_cb+0x26/0xb0 [amdgpu]
by bugzilla-daemon＠bugzilla.kernel.org 15 Mar '18

15 Mar '18

https://bugzilla.kernel.org/show_bug.cgi?id=198985 Bug ID: 198985 Summary: BUG: KASAN: use-after-free in amdgpu_job_free_cb+0x26/0xb0 [amdgpu] Product: Drivers Version: 2.5 Kernel Version: 4.15.7 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-… [View More]dri(a)kernel-bugs.osdl.org Reporter: fredrik(a)planet-express.se Regression: No I've hit a bunch of complete & partial lockups with 4.15. I finally built a kasan kernel and caught this: [50772.217692] ================================================================== [50772.217773] BUG: KASAN: use-after-free in amdgpu_job_free_cb+0x26/0xb0 [amdgpu] [50772.217776] Read of size 8 at addr ffff880ccf431a48 by task kworker/7:1/112 [50772.217781] CPU: 7 PID: 112 Comm: kworker/7:1 Not tainted 4.15.7 #18 [50772.217782] Hardware name: System manufacturer System Product Name/PRIME X370-PRO, BIOS 3803 01/22/2018 [50772.217861] Workqueue: events amd_sched_job_finish [amdgpu] [50772.217863] Call Trace: [50772.217869] dump_stack+0x46/0x5a [50772.217874] print_address_description+0x82/0x2c0 [50772.217878] kasan_report+0x289/0x380 [50772.217973] ? amdgpu_job_free_cb+0x26/0xb0 [amdgpu] [50772.218047] amdgpu_job_free_cb+0x26/0xb0 [amdgpu] [50772.218052] process_one_work+0x3cd/0x660 [50772.218055] worker_thread+0x81/0x7b0 [50772.218058] ? create_worker+0x2a0/0x2a0 [50772.218060] kthread+0x1ae/0x1d0 [50772.218062] ? kthread_create_worker+0xd0/0xd0 [50772.218065] ret_from_fork+0x22/0x40 [50772.218069] Allocated by task 489: [50772.218072] kasan_kmalloc+0xb0/0xf0 [50772.218132] amdgpu_driver_open_kms+0x8c/0x1f0 [amdgpu] [50772.218136] drm_open+0x39e/0x720 [50772.218138] drm_stub_open+0x155/0x1d0 [50772.218140] chrdev_open+0x168/0x300 [50772.218143] do_dentry_open.isra.20+0x325/0x510 [50772.218145] path_openat+0x7f6/0x1ac0 [50772.218148] do_filp_open+0x125/0x1d0 [50772.218149] do_sys_open+0x251/0x300 [50772.218152] do_syscall_64+0xf3/0x2b0 [50772.218154] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [50772.218155] Freed by task 19848: [50772.218158] kasan_slab_free+0x7c/0xe0 [50772.218160] kfree+0x91/0x1a0 [50772.218220] amdgpu_driver_postclose_kms+0x154/0x360 [amdgpu] [50772.218222] drm_release+0x45e/0x5f0 [50772.218224] __fput+0x14e/0x2e0 [50772.218226] task_work_run+0xa0/0xc0 [50772.218229] do_exit+0x3c4/0x10f0 [50772.218231] do_group_exit+0x74/0x110 [50772.218234] get_signal+0x1ab/0x760 [50772.218237] do_signal+0xb4/0xa80 [50772.218238] exit_to_usermode_loop+0x74/0xa0 [50772.218240] do_syscall_64+0x2a0/0x2b0 [50772.218242] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [50772.218245] The buggy address belongs to the object at ffff880ccf431980 which belongs to the cache kmalloc-2048 of size 2048 [50772.218247] The buggy address is located 200 bytes inside of 2048-byte region [ffff880ccf431980, ffff880ccf432180) [50772.218249] The buggy address belongs to the page: [50772.218252] page:ffffea00333d0c00 count:1 mapcount:0 mapping: (null) index:0x0 compound_mapcount: 0 [50772.218255] flags: 0x8000000000008100(slab|head) [50772.218260] raw: 8000000000008100 0000000000000000 0000000000000000 00000001000f000f [50772.218263] raw: dead000000000100 dead000000000200 ffff880f98c03040 0000000000000000 [50772.218264] page dumped because: kasan: bad access detected [50772.218265] Memory state around the buggy address: [50772.218267] ffff880ccf431900: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc [50772.218270] ffff880ccf431980: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb [50772.218272] >ffff880ccf431a00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb [50772.218273] ^ [50772.218275] ffff880ccf431a80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb [50772.218277] ffff880ccf431b00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb [50772.218278] ================================================================== lspci: 0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580] (rev cf) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 53 Region 0: Memory at e0000000 (64-bit, prefetchable) [size=256M] Region 2: Memory at f0000000 (64-bit, prefetchable) [size=2M] Region 4: I/O ports at e000 [size=256] Region 5: Memory at fe800000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 256 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L1, Exit Latency L1 <1us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Not Supported AtomicOpsCap: 32bit+ 64bit+ 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn- LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+, EqualizationPhase1+ EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest- Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000fee00000 Data: 0000 Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150 v2] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn- MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- HeaderLog: 00000000 00000000 00000000 00000000 Capabilities: [200 v1] #15 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 00000020, Page Request Allocation: 00000000 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec+ Priv+, Max PASID Width: 10 PASIDCtl: Enable- Exec- Priv- Capabilities: [320 v1] Latency Tolerance Reporting Max snoop latency: 0ns Max no snoop latency: 0ns Capabilities: [328 v1] Alternative Routing-ID Interpretation (ARI) ARICap: MFVC- ACS-, Next Function: 1 ARICtl: MFVC- ACS-, Function Group: 0 Capabilities: [370 v1] L1 PM Substates L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+ PortCommonModeRestoreTime=0us PortTPowerOnTime=170us L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1- T_CommonMode=0us LTR1.2_Threshold=0ns L1SubCtl2: T_PwrOn=10us Kernel driver in use: amdgpu Kernel modules: amdgpu -- You are receiving this mail because: You are watching the assignee of the bug. [View Less]

1 4

[PATCH] [v3] gpu: ipu-v3: prg: avoid possible array underflow
by Arnd Bergmann 15 Mar '18

15 Mar '18

gcc-8 reports that we access an array with a negative index in an error case: drivers/gpu/ipu-v3/ipu-prg.c: In function 'ipu_prg_channel_disable': drivers/gpu/ipu-v3/ipu-prg.c:252:43: error: array subscript -22 is below array bounds of 'struct ipu_prg_channel[3]' [-Werror=array-bounds] This moves the range check in front of the first time that variable gets used. Signed-off-by: Arnd Bergmann <arnd(a)arndb.de> ---- v1: Originally sent on Dec 4, 2017. v2: Sent again on Jan 16, after no … [View More]

2 1

[PATCH libdrm] tests/exynos: remove dead condition
by Seung-Woo Kim 15 Mar '18

15 Mar '18

There is already condition checking input values between 2 and 4096 so condition checking 0 is always false. Remove the dead condition. Signed-off-by: Seung-Woo Kim <sw0312.kim(a)samsung.com> --- tests/exynos/exynos_fimg2d_perf.c | 7 ------- 1 files changed, 0 insertions(+), 7 deletions(-) diff --git a/tests/exynos/exynos_fimg2d_perf.c b/tests/exynos/exynos_fimg2d_perf.c index a2d5c19..97691a7 100644 --- a/tests/exynos/exynos_fimg2d_perf.c +++ b/tests/exynos/exynos_fimg2d_perf.c @@ … [View More]

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2018