linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mikulas Patocka <mpatocka@redhat.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"David Hildenbrand" <david@redhat.com>,
	amd-gfx@lists.freedesktop.org, linux-mm@kvack.org,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	"Vlastimil Babka" <vbabka@suse.cz>,
	"Jann Horn" <jannh@google.com>,
	"Pedro Falcato" <pfalcato@suse.de>
Subject: Re: [PATCH v2] fix AMDGPU failure with periodic signal
Date: Sun, 4 Jan 2026 22:12:50 +0100 (CET)	[thread overview]
Message-ID: <4e45bbf5-29ce-7cd6-8b01-8fb1331ac758@redhat.com> (raw)
In-Reply-To: <0826eb09-216c-4d00-b4eb-ed1a2ba204bf@lucifer.local>



On Fri, 2 Jan 2026, Lorenzo Stoakes wrote:

> +cc literally everyone you should have cc'd in mm :/
> 
> Hi Mikulas,
> 
> You really need to check MAINTAINERS, you've sent a patch that changes mm/vma.c
> without cc'ing a single maintainer or reviewer of that file. I just happened to
> notice this by chance, even lei seemed to mess up the file query for some
> reason.

I saw

MEMORY MANAGEMENT
M:      Andrew Morton <akpm@linux-foundation.org>
L:      linux-mm@kvack.org
S:      Maintained

in the MAINTAINERS file, so I sent the patch to Andrew and to 
linux-mm@kvack.org. I should have sent it also to people on the "MEMORY 
MANAGEMENT - CORE" section, but I missed it.

> I'm confused in general about this patch, you sent it on 7th Nov? And it's been
> ignored until now and then taken without review to the hotfixes queue?

I'm developing code that translates parallelizable loops written in the 
Ajla programming language (www.ajla-lang.cz) into OpenCL and runs them on 
the graphics card. Ajla sets up a periodic timer that sends a signal for 
scheduling purposes and this signal interferes with OpenCL, causing the 
-EINTR failures.

So far, I worked around this bug by blocking all signals around the 
functions clGetPlatformIDs and clGetDeviceIDs - but it would be better to 
fix it in the Linux kernel and remove the signal-blocking hacks.

Mikulas



  parent reply	other threads:[~2026-01-04 21:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-07 17:48 Mikulas Patocka
2026-01-02 19:02 ` Lorenzo Stoakes
2026-01-02 19:08   ` Lorenzo Stoakes
2026-01-03 17:58     ` Andrew Morton
2026-01-05 10:43       ` Lorenzo Stoakes
2026-01-04 21:12   ` Mikulas Patocka [this message]
2026-01-05 10:45     ` Lorenzo Stoakes
2026-01-05 10:59       ` Lorenzo Stoakes
2026-01-02 19:15 ` Lorenzo Stoakes
2026-01-06 11:51 ` Lorenzo Stoakes
2026-01-06 18:12   ` Andrew Morton
2026-01-06 18:24     ` Lorenzo Stoakes
2026-01-06 20:59       ` Andrew Morton
2026-01-06 21:52         ` Pedro Falcato
2026-01-08  6:26           ` Finding mm patches to review before those are pulled into the mainline (was "Re: [PATCH v2] fix AMDGPU failure with periodic signal") SeongJae Park
2026-01-08  9:05             ` Lorenzo Stoakes
2026-01-07 12:33         ` [PATCH v2] fix AMDGPU failure with periodic signal Lorenzo Stoakes

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=4e45bbf5-29ce-7cd6-8b01-8fb1331ac758@redhat.com \
    --to=mpatocka@redhat.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=david@redhat.com \
    --cc=jannh@google.com \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=pfalcato@suse.de \
    --cc=vbabka@suse.cz \
    /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