Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 03 Sep 2024 13:23:45 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 276985] crash in LinuxKPI/drm
Message-ID:  <bug-276985-227-WMbuGQaQDn@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-276985-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-276985-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D276985

--- Comment #37 from feh@fehcom.de ---
(In reply to Olivier Certner from comment #35)

I just checked both drm versions (5.15 and 6.1) briefly, but the difference=
 is
significant, so it will be hard to tell whether the new version is the corr=
ect
solution.=20

AMD needs of course to provide driver for their new GPUs. As said, their
development focuses on the Linux kernel. One particular mechanism here is '=
rcu'
- Ready/Copy/Update.
I'm wondering how is is realized under FreeBSD.=20

@Oliver: Is there any whitepaper or so, detailing this, perhaps while
reverse-engineering the code base?

And regarding:

> I wouldn't fly a plane whose code hasn't both been proved correct *and* t=
ested.

In this sector of the industry, formal proof methods will be applied. Hardw=
are
redundancy/diversity is also important.=20

We have to thank all volunteers here to come close that quality for an OS y=
ou
can get for free and running realiably on HW for just $300 (like mine).

--eh.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-276985-227-WMbuGQaQDn>