-----Original Message-----
>From: Ian Lance Taylor <[email protected]>
>Sent: Apr 8, 2019 2:24 PM
>To: Cholerae Hu <[email protected]>, Austin Clements <[email protected]>
>Cc: golang-nuts <[email protected]>
>Subject: Re: [go-nuts] Why will it deadlock if a goroutine acquire a mutex
>while pinned to its P?
>
>[ + austin ]
>
>On Sun, Apr 7, 2019 at 11:31 PM Cholerae Hu <[email protected]> wrote:
>>
>> I'm reading this commit
>> https://github.com/golang/go/commit/d5fd2dd6a17a816b7dfd99d4df70a85f1bf0de31
>> . Inside runtime_procPin we only increases the m.lock count, why will it
>> cause deadlock when acquiring a mutex after pin?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "golang-nuts" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>
>--
>You received this message because you are subscribed to the Google Groups
>"golang-nuts" group.
>To unsubscribe from this group and stop receiving emails from it, send an
>email to [email protected].
>For more options, visit https://groups.google.com/d/optout.
Apologies not warranted. I was only pointing out that it didn't seem correct to
me.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
