AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Bert Karwatzki" <spasswolf@web.de>,
	"Christian König" <christian.koenig@amd.com>,
	"Balbir Singh" <balbirs@nvidia.com>,
	"Kees Cook" <kees@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Andy Lutomirski" <luto@kernel.org>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org
Subject: Re: commit 7ffb791423c7 breaks steam game
Date: Thu, 27 Mar 2025 11:40:58 +0100	[thread overview]
Message-ID: <Z-UrOtLLMTNFLRfU@gmail.com> (raw)
In-Reply-To: <CAHk-=wh5Suzp0z7AnK0NgSKfEAWQJw7Dgv5eku=rzBuM1ugQDg@mail.gmail.com>


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Wed, 26 Mar 2025 at 15:00, Bert Karwatzki <spasswolf@web.de> wrote:
> >
> > As Balbir Singh found out this memory comes from amdkfd
> > (kgd2kfd_init_zone_device()) with CONFIG_HSA_AMD_SVM=y. The memory gets placed
> > by devm_request_free_mem_region() which places the memory at the end of the
> > physical address space (DIRECT_MAP_PHYSMEM_END). DIRECT_MAP_PHYSMEM_END changes
> > when using nokaslr and so the memory shifts.
> 
> So I just want to say that having followed the thread as a spectator,
> big kudos to everybody involved in this thing. Particularly to you,
> Bart, for all your debugging and testing, and to Balbir for following
> up and figuring it out.
> 
> Because this was a strange one.

I'd like to second that praise - Bert went above and beyond what could 
be expected from or even hoped from someone who reports a regression 
that broke his machine. Also, Balbir diligently followed down the 
regression to a root cause that was far away from his original code of 
interest. It was nice to lurk in this thread.

Thanks,

	Ingo

  parent reply	other threads:[~2025-03-27 10:41 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 10:14 commit 7ffb791423c7 breaks steam game Bert Karwatzki
2025-03-25 12:23 ` Christian König
2025-03-26 22:00   ` Bert Karwatzki
2025-03-26 22:58     ` Linus Torvalds
2025-03-27  0:57       ` Balbir Singh
2025-03-27  0:58       ` Bert Karwatzki
2025-03-27 10:40       ` Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-24 23:07 Bert Karwatzki
2025-03-25  8:36 ` Christian König
2025-03-25 10:25   ` Balbir Singh
2025-03-22 12:23 Bert Karwatzki
2025-03-23  6:51 ` Balbir Singh
2025-03-24 11:23   ` Bert Karwatzki
2025-03-24 12:14     ` Christian König
2025-03-24 22:48       ` Balbir Singh
2025-03-25  7:35         ` Christian König
2025-03-25 22:45           ` Balbir Singh
2025-03-25 23:21             ` Bert Karwatzki
2025-03-25 23:43               ` Balbir Singh
2025-03-26  1:50                 ` Balbir Singh
2025-03-26 10:10                   ` Bert Karwatzki
2025-03-26 10:36                     ` Balbir Singh
2025-03-26 11:14                       ` Bert Karwatzki
2025-03-27 10:53                       ` Ingo Molnar
2025-03-27 22:03                         ` Balbir Singh
2025-03-24 21:43     ` Balbir Singh
     [not found] <20250310112206.4168-1-spasswolf@web.de>
     [not found] ` <951f9d13-72e4-41c3-9ace-8639e2a9485d@nvidia.com>
     [not found]   ` <ce940e2a-632d-41be-9f13-e5b11d49b0db@nvidia.com>
     [not found]     ` <09131c563332c892284ec7fb4ce706996131db8c.camel@web.de>
     [not found]       ` <9a5df5627d3d72b2a97f501dfb7d944cc1e9920f.camel@web.de>
     [not found]         ` <fdea59fe-f570-489f-bf88-1ffd47119cac@nvidia.com>
     [not found]           ` <414f4deb8c7670a159854006b0c410ce05a6049e.camel@web.de>
     [not found]             ` <12d950ee-4152-4ad6-b93e-7c5b75804b1a@nvidia.com>
     [not found]               ` <705e95cec3dc5181ca2aa73722e6b84f63f3e91d.camel@web.de>
     [not found]                 ` <20b5823e-247a-456a-bb55-d50f212a9f5a@nvidia.com>
     [not found]                   ` <a34a1ae0b1d226b1bac7d73daa24da8e5899cb3e.camel@web.de>
     [not found]                     ` <c7bb0bd1-529d-466d-9cce-abbac4b480ab@nvidia.com>
     [not found]                       ` <146277bb0ecbb392d490683c424b8ae0dfa82838.camel@web.de>
2025-03-13 21:54                         ` Balbir Singh
2025-03-13 22:22                           ` Bert Karwatzki
2025-03-14  6:14                             ` Balbir Singh
2025-03-14 13:34                               ` Balbir Singh
2025-03-14 14:18                                 ` Bert Karwatzki
2025-03-15  0:16                                   ` Balbir Singh
2025-03-15 17:40                                     ` Alex Deucher
2025-03-16 13:09                                       ` Bert Karwatzki
2025-03-16 20:06                                         ` Bert Karwatzki
2025-03-17  9:13                                         ` Balbir Singh
2025-03-20  9:01                                           ` Ingo Molnar
2025-03-20 23:55                                             ` Balbir Singh
2025-03-21 10:24                                               ` Ingo Molnar
2025-03-21 11:05                                                 ` Balbir Singh
2025-03-22  8:04                                                   ` Ingo Molnar
2025-03-22  9:40                                                     ` Balbir Singh
2025-03-20 23:43                                           ` Bert Karwatzki
2025-03-21  4:55                                             ` Balbir Singh
2025-03-21 12:26                                               ` Bert Karwatzki
2025-03-22  2:06                                                 ` Balbir Singh

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=Z-UrOtLLMTNFLRfU@gmail.com \
    --to=mingo@kernel.org \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=balbirs@nvidia.com \
    --cc=bhelgaas@google.com \
    --cc=christian.koenig@amd.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=peterz@infradead.org \
    --cc=spasswolf@web.de \
    --cc=torvalds@linux-foundation.org \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox