From: Erik Quanstrom <quanstro@quanstro.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] arm fun
Date: Tue, 13 May 2014 22:33:54 -0400 [thread overview]
Message-ID: <4i2lfm4l5tuolyg6hyyqbpis.1400034834998@email.android.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
the lock is in the bss. maybe the wrong page gets accessed after fork.
Charles Forsyth <charles.forsyth@gmail.com> wrote:
>I've got one of those that was fine last time I tried it. I'll try it in the morning.
>
>I wonder whether the change of lock to use semacquire instead of tas doesn't work well on the (that) ARM.
>
>It seems a strange coincidence that it always fails there.
>
>
>
[-- Attachment #2: Type: text/html, Size: 591 bytes --]
next reply other threads:[~2014-05-14 2:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 2:33 Erik Quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-13 18:31 Jeff Sickel
2014-05-13 18:51 ` erik quanstrom
2014-05-14 2:14 ` Charles Forsyth
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=4i2lfm4l5tuolyg6hyyqbpis.1400034834998@email.android.com \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).