tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 48e8992e33abf054bcc0bb2e77b2d43bb899212e Add linux-next specific
files for 20231213
Error/Warning reports:
https://lore.kernel.org/oe-kbuild-all/202312131758.ned6tvqk-...@intel.com
https
[AMD Official Use Only - General]
This patch is
Reviewed-by: Likun Gao .
Regards,
Likun
-Original Message-
From: amd-gfx On Behalf Of Kenneth Feng
Sent: Wednesday, December 13, 2023 3:02 PM
To: amd-gfx@lists.freedesktop.org
Cc: Feng, Kenneth
Subject: [PATCH] drm/amd/pm: add power save
- Original Message -
> From: "Samuel Holland"
> To: "Michael Ellerman"
> Cc: "linux-kernel" , "amd-gfx"
> , "linux-arch"
> , "linux-arm-kernel"
> , loonga...@lists.linux.dev,
> "linuxppc-dev" , "x86" ,
> linux-ri...@lists.infradead.org, "Christoph
> Hellwig" , "Timothy Pearson"
>
Fix up on mes process context flush to prevent non-mes devices from
spamming error messages or running into undefined behaviour during
process termination.
Fixes: 73204d028eb5 ("drm/amdkfd: fix mes set shader debugger process
management")
Signed-off-by: Jonathan Kim
---
[Public]
The series is.
Reviewed-by: Lang Yu
>-Original Message-
>From: Lee, Peyton
>Sent: Wednesday, December 13, 2023 10:49 AM
>To: amd-gfx@lists.freedesktop.org
>Cc: Deucher, Alexander ; Zhang, Yifan
>; Ma, Li ; Yu, Lang
>; Lee, Peyton
>Subject: [PATCH 2/2] drm/amdgpu/vpe: enable
From: Xiaogang Chen
v2:
-not need calculate vram page number for new registered svm range, only
do it for split vram pages.
v3:
-use dma address to calculate vram page number of split svm range;
use migrate_vma from hmm to calculate page number that migrate to vram.
v4:
-combine calculating of
[Public]
Check the MES API, It's my fault , originally I think it will use trap_en as
parameter to tell MES to enable/disable shader debugger , but actually it's not
. So we either need to add a parameter for this (ex . add flag for
enable/disable) or as your solution add flag for flush.
Hi Dave, Sima,
Fixes for 6.7.
The following changes since commit b7b5a56acec819bb8dcd03c687e97a091b29d28f:
Merge tag 'exynos-drm-next-for-v6.7-rc5' of
git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into drm-fixes
(2023-12-08 13:55:32 +1000)
are available in the Git
On 2023-12-07 13:02, Alex Deucher wrote:
Show buffers as shared if they are shared via dma-buf as well
(e.g., shared with v4l or some other subsystem).
You can add KFD to that list. With the in-progress CUDA11 VM changes and
improved interop between KFD and render nodes, sharing DMABufs
Some chips provide both average and input power. Previously
we just exposed average power, add a new query for input
power.
Example userspace:
https://github.com/Umio-Yasuno/libdrm-amdgpu-sys-rs/tree/input_power
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c | 9
On APUs power is SoC power, not just GPU.
Clarify that for UVD/VCE/VCN the IP is powered down,
not disabled which can confusing and lead to concerns
that the IP is actually not available.
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/amd/pm/amdgpu_pm.c | 28 ++--
1
For backwards compatibility with userspace.
Fixes: 47f1724db4fe ("drm/amd: Introduce `AMDGPU_PP_SENSOR_GPU_INPUT_POWER`")
Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2897
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c | 7 ++-
1 file changed, 6
Hawaii, Bonaire, Fiji, and Tonga support average power, the others
support current power.
Signed-off-by: Alex Deucher
---
.../gpu/drm/amd/pm/powerplay/hwmgr/smu7_hwmgr.c | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git
For 2.1, ATOM_VRAM_BLOCK_SRIOV_MSG_SHARE_RESERVATION is SR-IOV only.
For 2.2, return usage_bytes properly for the non-SR-IOV case.
Fixes: 4864f2ee9ee2 ("drm/amdgpu: add vram reservation based on
vram_usagebyfirmware_v2_2")
Link: https://bugzilla.opensuse.org/show_bug.cgi?id=1215802
The changes to support vram_usagebyfirmware v2.2 changed the behavior
to explicitly match 2.1 for everything older rather than just using it
by default. If the version is 2.2 or newer, use the 2.2 parsing, for
everything else, use the 2.1 parsing. This restores the previous
behavior for tables
Before trying to use them in the debugfs register access functions.
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c
On Thu, Dec 7, 2023 at 1:03 PM Alex Deucher wrote:
>
> We had a request to add shared buffer stats to fdinfo for amdgpu and
> while implementing that, Christian mentioned that just looking at
> the GEM handle count doesn't take into account buffers shared with other
> subsystems like V4L or RDMA.
Some systems with MP1 13.0.4 or 13.0.11 have a firmware bug that
causes the first MES packet after resume to fail. Typically this
packet is used to flush the TLB when GART is enabled.
This issue is fixed in newer firmware, but as OEMs may not roll this
out to the field, introduce a workaround
On Wed, Dec 13, 2023 at 2:32 PM Mario Limonciello
wrote:
>
> On 12/13/2023 13:12, Mario Limonciello wrote:
> > On 12/13/2023 13:07, Alex Deucher wrote:
> >> On Wed, Dec 13, 2023 at 1:00 PM Mario Limonciello
> >> wrote:
> >>>
> >>> Some systems with MP1 13.0.4 or 13.0.11 have a firmware bug that
On 12/13/2023 13:12, Mario Limonciello wrote:
On 12/13/2023 13:07, Alex Deucher wrote:
On Wed, Dec 13, 2023 at 1:00 PM Mario Limonciello
wrote:
Some systems with MP1 13.0.4 or 13.0.11 have a firmware bug that
causes the first MES packet after resume to fail. This packet is
used to flush the
On 12/13/2023 13:07, Alex Deucher wrote:
On Wed, Dec 13, 2023 at 1:00 PM Mario Limonciello
wrote:
Some systems with MP1 13.0.4 or 13.0.11 have a firmware bug that
causes the first MES packet after resume to fail. This packet is
used to flush the TLB when GART is enabled.
This issue is fixed
On Wed, Dec 13, 2023 at 1:00 PM Mario Limonciello
wrote:
>
> Some systems with MP1 13.0.4 or 13.0.11 have a firmware bug that
> causes the first MES packet after resume to fail. This packet is
> used to flush the TLB when GART is enabled.
>
> This issue is fixed in newer firmware, but as OEMs may
Applied manually. Please double check how you are sending the
patches. git complained about a malformed patch. I'd suggest using
git-send-email.
Thanks,
Alex
On Wed, Dec 13, 2023 at 1:45 AM Christian König
wrote:
>
> Am 13.12.23 um 00:31 schrieb Woody Suwalski:
> > Fix to avoid multiple
Some systems with MP1 13.0.4 or 13.0.11 have a firmware bug that
causes the first MES packet after resume to fail. This packet is
used to flush the TLB when GART is enabled.
This issue is fixed in newer firmware, but as OEMs may not roll this
out to the field, introduce a workaround that will
On 2023-12-13 11:23, Felix Kuehling wrote:
On 2023-12-13 10:24, James Zhu wrote:
Ping ...
On 2023-12-08 18:01, James Zhu wrote:
When application tries to allocate all system memory and cause memory
to swap out. Needs more time for hmm_range_fault to validate the
remaining page for
On 12/8/23 13:54, Samuel Holland wrote:
LoongArch already provides kernel_fpu_begin() and kernel_fpu_end() in
asm/fpu.h, so it only needs to add kernel_fpu_available() and export
the CFLAGS adjustments.
Signed-off-by: Samuel Holland
---
arch/loongarch/Kconfig | 1 +
On 2023-12-13 10:24, James Zhu wrote:
Ping ...
On 2023-12-08 18:01, James Zhu wrote:
When application tries to allocate all system memory and cause memory
to swap out. Needs more time for hmm_range_fault to validate the
remaining page for allocation. To be safe, increase timeout value to
1
On Thu, Dec 07, 2023 at 09:54:34PM -0800, Samuel Holland wrote:
> arm64 provides an equivalent to the common kernel-mode FPU API, but in a
> different header and using different function names. Add a wrapper
> header, and export CFLAGS adjustments as found in lib/raid6/Makefile.
>
>
[AMD Official Use Only - General]
From: Zhu, James
Sent: Wednesday, December 13, 2023 10:41 AM
To: Yat Sin, David ; Zhu, James ;
amd-gfx@lists.freedesktop.org
Cc: Kuehling, Felix ; Greathouse, Joseph
Subject: Re: [PATCH v2 03/23] drm/amdkfd: enable pc sampling query
On 2023-12-12 19:55,
On 2023-12-13 16:39, Felix Kuehling wrote:
> On 2023-12-13 9:20, Christian König wrote:
>> Am 12.12.23 um 00:32 schrieb Felix Kuehling:
>>> On 2023-12-11 04:50, Christian König wrote:
Am 08.12.23 um 20:53 schrieb Alex Deucher:
> [SNIP]
>> You also need a functionality which resets all
Am 13.12.23 um 16:39 schrieb Felix Kuehling:
On 2023-12-13 9:20, Christian König wrote:
Am 12.12.23 um 00:32 schrieb Felix Kuehling:
On 2023-12-11 04:50, Christian König wrote:
Am 08.12.23 um 20:53 schrieb Alex Deucher:
[SNIP]
You also need a functionality which resets all cleared blocks
On 2023-12-12 19:55, Yat Sin, David wrote:
[AMD Official Use Only - General]
-Original Message-
From: Zhu, James
Sent: Thursday, December 7, 2023 5:54 PM
To:amd-gfx@lists.freedesktop.org
Cc: Kuehling, Felix; Greathouse, Joseph
; Yat Sin, David;
Zhu, James
Subject: [PATCH v2 03/23]
On 2023-12-13 9:20, Christian König wrote:
Am 12.12.23 um 00:32 schrieb Felix Kuehling:
On 2023-12-11 04:50, Christian König wrote:
Am 08.12.23 um 20:53 schrieb Alex Deucher:
[SNIP]
You also need a functionality which resets all cleared blocks to
uncleared after suspend/resume.
No idea how
Ping ...
On 2023-12-08 18:01, James Zhu wrote:
When application tries to allocate all system memory and cause memory
to swap out. Needs more time for hmm_range_fault to validate the
remaining page for allocation. To be safe, increase timeout value to
1 second for 64MB range.
Signed-off-by:
On 12/13/2023 08:17, Alex Deucher wrote:
On Tue, Dec 12, 2023 at 9:00 PM Mario Limonciello
wrote:
On 12/12/2023 18:08, Oliver Schmidt wrote:
Hi Wayne,
On 12.12.23 17:06, Mario Limonciello wrote:
I looked through your bugs related to this and I didn't see a reference to the
specific docking
Am 06.12.23 um 22:44 schrieb Felix Kuehling:
DMABuf imports in compute VMs are not wrapped in a kgd_mem object on the
process_info->kfd_bo_list. There is no explicit KFD API call to validate
them or add eviction fences to them.
This patch automatically validates and fences dymanic DMABuf
[AMD Official Use Only - General]
Hi Peyton,
After the format problem fixed, this patch is
Reviewed-by: Li Ma
BRs,
Li
-Original Message-
From: Lee, Peyton
Sent: Wednesday, December 13, 2023 10:49 AM
To: amd-gfx@lists.freedesktop.org
Cc: Deucher, Alexander ; Zhang, Yifan
; Ma, Li ;
Am 12.12.23 um 00:32 schrieb Felix Kuehling:
On 2023-12-11 04:50, Christian König wrote:
Am 08.12.23 um 20:53 schrieb Alex Deucher:
[SNIP]
You also need a functionality which resets all cleared blocks to
uncleared after suspend/resume.
No idea how to do this, maybe Alex knows of hand.
Since
On Wed, Dec 13, 2023 at 3:40 AM Wayne Lin wrote:
>
> From: Alvin Lee
>
> [Description]
> Revert commit 8c5660987ee1 ("drm/amd/display: Use channel_width = 2 for vram
> table 3.0")
> Because the issue is being fixed from VBIOS side.
>
> Reviewed-by: Samson Tam
> Acked-by: Wayne Lin
>
On Tue, Dec 12, 2023 at 9:00 PM Mario Limonciello
wrote:
>
> On 12/12/2023 18:08, Oliver Schmidt wrote:
> > Hi Wayne,
> >
> > On 12.12.23 17:06, Mario Limonciello wrote:
> >> I looked through your bugs related to this and I didn't see a reference to
> >> the
> >> specific docking station model.
On 13.12.23 02:21, Mario Limonciello wrote:
> By chance do you have access to any other dock or monitor combinations that
> you can conclude it only happens on this dock or only a certain monitor, or
> only a certain monitor connected to this dock?
Mario, that was a good suggestion! I indeed had
Am 13.12.23 um 08:27 schrieb Wang, Beyond:
[AMD Official Use Only - General]
Issue: during evict or validate happened on amdgpu_bo, the 'from' and
'to' is always same in ftrace event of amdgpu_bo_move
where calling the 'trace_amdgpu_bo_move', the comment says move_notify
is called before
Fix to avoid multiple debug error lines printed on every suspend by
Radeon driver's debugfs.
radeon_debugfs_init() calls debugfs_create_file() for every ring.
This results in printing multiple error lines to the screen and dmesg
similar to this:
[ 92.378726] debugfs: File
Hi Wayne,
On 12.12.23 17:06, Mario Limonciello wrote:
> I looked through your bugs related to this and I didn't see a reference to the
> specific docking station model.
> The logs mentioned "Thinkpad dock" but no model.
> Could you share more about it so that AMD can try to reproduce it?
Yes, it
44 matches
Mail list logo
