dotnet/runtime

[NativeAOT] Signalless Hijack

Open

#78,724 opened on Nov 22, 2022

View on GitHub
 (7 comments) (0 reactions) (1 assignee)C# (5,445 forks)batch import
area-NativeAOT-coreclrhelp wanted

Repository metrics

Stars
 (17,886 stars)
PR merge metrics
 (Avg merge 12d 11h) (661 merged PRs in 30d)

Description

This relates to https://github.com/dotnet/runtime/issues/74355

We've updated the console ports to .NET 7.0 and the above issue is still occurring with concurrent GC enabled. After further investigation, this is because we cannot implement the equivalent of PalHijack as POSIX signals are not supported on nearly all game console platforms.

I know this is a feature request but it would be great if there was a way to mimic PalHijack behaviour without relying on pthread_kill so that we can have high performance GC in video games.

(Note: All this work is being done as part of the FNA community)

Contributor guide

Research direction
Investigate alternatives to pthread kill for thread hijacking in NativeAOT, such as cooperative suspension, managed polling, or hardware based mechanisms, to achieve signal less hijacking for GC on platforms without POSIX signals.
Tech stack
csharp
Domain
backendperformance
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C#.NET runtime internalsGarbage collection knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20