Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 28 Dec 2024 18:35:32 +0000
From:      bugzilla-noreply@freebsd.org
To:        virtualization@FreeBSD.org
Subject:   [Bug 283103] Yet another Parallels arm64 panic
Message-ID:  <bug-283103-27103-w5g0Ck8Q0v@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-283103-27103@https.bugs.freebsd.org/bugzilla/>
References:  <bug-283103-27103@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=283103

--- Comment #7 from Andriy Gapon <avg@FreeBSD.org> ---
(In reply to Andrew Turner from comment #3)
I've been thinking about sleeping ithreads for another reason, sorry for
hijacking this bug report.

There could be a chip connected, e.g., via I2C.
And that chip could also be capable of generating a signal (an interrupt) via a
GPIO line.
It's not a problem to configure the GPIO interrupt but it may become a problem
if the interrupt handler needs to access the chip via a bus that requires
waiting / sleeping.

I think that at present the described setup can only work if we force the bus
to spinning / polling but that may be sub-optimal.

-- 
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-283103-27103-w5g0Ck8Q0v>