From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <9c496848706c4dfbd85617b81e4d9a6b@9netics.com> To: 9fans@9fans.net Date: Thu, 31 Dec 2015 00:39:22 -0800 From: Skip Tavakkolian <9nut@9netics.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: [9fans] any updates on go for plan9/arm? Topicbox-Message-UUID: 7c160608-ead9-11e9-9d60-3106f5b1d025 I just tried cross compiling go1.6beta1 for plan9/arm, using os x, but no luck. is it still planned for go1.6? From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@9fans.net Date: Thu, 31 Dec 2015 10:53:33 +0200 From: lucio@proxima.alt.za In-Reply-To: <9c496848706c4dfbd85617b81e4d9a6b@9netics.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] any updates on go for plan9/arm? Topicbox-Message-UUID: 7c1bf888-ead9-11e9-9d60-3106f5b1d025 > I just tried cross compiling go1.6beta1 for plan9/arm, using os > x, but no luck. is it still planned for go1.6? I don't recall any formal submission for that and I'm pretty sure that it was not on the road map for 1.6. I know Richard did all the hard work to port Go, but it really is in the hand of the Go community to make it happen. What Richard submitted was more in the line of proof of concept and will need some adjusting (I seem to recall a tar archive?). Cherry got Go on linux/mips64 going practically alone, it can't be beyond our means to do it for plan9/arm (and plan9/mips?). Lucio. From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <9c496848706c4dfbd85617b81e4d9a6b@9netics.com> Date: Thu, 31 Dec 2015 11:33:52 +0100 Message-ID: From: David du Colombier <0intro@gmail.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a113521b2eccb8205282f30cb Subject: Re: [9fans] any updates on go for plan9/arm? Topicbox-Message-UUID: 7c230614-ead9-11e9-9d60-3106f5b1d025 --001a113521b2eccb8205282f30cb Content-Type: text/plain; charset=UTF-8 Richard Miller's work on the plan9/arm port is available here: http://9legacy.org/go/patch/go-arm.diff It has been tested successfully on Rasperry Pi 2 (ARMv7) with *ncpu=1. There is still a coherency issue that need to be fixed to be able to run reliably on multiple processors. -- David du Colombier --001a113521b2eccb8205282f30cb Content-Type: text/html; charset=UTF-8

Richard Miller's work on the plan9/arm port is available here:

http://9legacy.org/go/patch/go-arm.diff

It has been tested successfully on Rasperry Pi 2 (ARMv7) with *ncpu=1.

There is still a coherency issue that need to be fixed to be able to run reliably on multiple processors.

--
David du Colombier

--001a113521b2eccb8205282f30cb-- From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <327e2f1c17187c02a3cc24639321b9e2@proxima.alt.za> To: 9fans@9fans.net Date: Thu, 31 Dec 2015 12:40:20 +0200 From: lucio@proxima.alt.za In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] any updates on go for plan9/arm? Topicbox-Message-UUID: 7c4f3f18-ead9-11e9-9d60-3106f5b1d025 > http://9legacy.org/go/patch/go-arm.diff Thank you, David for the details. There are many rPi owners out there and some may be willing to contribute their efforts, it matters that they are well informed. Is the coherency problem documented anywhere? I appreciate I ought to know the answer, but I don't own a Pi and have not given this as much attention as I believe I ought to. Lucio. From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <9059cc13eb03b7b6aea900e0d87f08d4@hamnavoe.com> To: 9fans@9fans.net From: Richard Miller <9fans@hamnavoe.com> Date: Thu, 31 Dec 2015 11:03:14 +0000 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] any updates on go for plan9/arm? Topicbox-Message-UUID: 7c53a3c8-ead9-11e9-9d60-3106f5b1d025 > Richard Miller's work on the plan9/arm port is available here: > > http://9legacy.org/go/patch/go-arm.diff > > It has been tested successfully on Rasperry Pi 2 (ARMv7) with *ncpu=1. I think that's a diff against go1.5 -- and it runs on older rpi (ARMv6) too. In order to pass all the go test suite, a few small plan 9 patches are required as well. /n/sources/contrib/miller/go-plan9-arm.tar holds the latest snapshot. I haven't touched this for a while, so I'll see if it needs updating for the present state of Go. From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <9ed943cac2b126778cf7fbccc4d6d948@hamnavoe.com> To: 9fans@9fans.net From: Richard Miller <9fans@hamnavoe.com> Date: Thu, 31 Dec 2015 11:57:36 +0000 In-Reply-To: <327e2f1c17187c02a3cc24639321b9e2@proxima.alt.za> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] any updates on go for plan9/arm? Topicbox-Message-UUID: 7c57a11c-ead9-11e9-9d60-3106f5b1d025 > Is the coherency problem documented anywhere? I appreciate I ought to > know the answer, but I don't own a Pi and have not given this as much > attention as I believe I ought to. The kernel in /n/sources/contrib/miller/9/bcm supports multicore on the Raspberry Pi 2, but has an elusive "one last bug" which I suspect has to do with cache or page table coherency. The symptom is very infrequent memory corruption under heavy load, and the go test suite with *ncpu=4 occasionally triggers it. From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 31 Dec 2015 14:08:12 +0100 From: David du Colombier <0intro@gmail.com> To: 9fans@9fans.net Message-ID: <20151231140812.7289fd8e@neon.9fans.fr> In-Reply-To: <9059cc13eb03b7b6aea900e0d87f08d4@hamnavoe.com> References: <9059cc13eb03b7b6aea900e0d87f08d4@hamnavoe.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] any updates on go for plan9/arm? Topicbox-Message-UUID: 7c67e8a6-ead9-11e9-9d60-3106f5b1d025 I've just updated the patch so it should apply cleanly on Go 1.6. Richard, I think the following files have to be updated to match Go 1.6: - src/cmd/go/build.go (rebase to the current file) - src/runtime/os3_plan9.go (regSize =E2=86=92 sys.RegSize, ptrSize =E2=86=92 sys.PtrSize and go:nowritebarrier =E2=86=92 go:nowrite= barrierrec) - src/runtime/sys_plan9_386.s (m_errstr(BX) =E2=86=92 (m_mOS+mOS_errstr)(B= X)) --=20 David du Colombier From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 31 Dec 2015 14:20:59 +0100 From: David du Colombier <0intro@gmail.com> To: 9fans@9fans.net Message-ID: <20151231142059.39e96277@neon.9fans.fr> In-Reply-To: <20151231140812.7289fd8e@neon.9fans.fr> References: <9059cc13eb03b7b6aea900e0d87f08d4@hamnavoe.com> <20151231140812.7289fd8e@neon.9fans.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] any updates on go for plan9/arm? Topicbox-Message-UUID: 7c6b7962-ead9-11e9-9d60-3106f5b1d025 > I've just updated the patch so it should apply cleanly on Go 1.6. >=20 > Richard, I think the following files have to be updated > to match Go 1.6: >=20 > - src/cmd/go/build.go (rebase to the current file) > - src/runtime/os3_plan9.go (regSize =E2=86=92 sys.RegSize, > ptrSize =E2=86=92 sys.PtrSize and go:nowritebarrier =E2=86=92 go:nowri= tebarrierrec) > - src/runtime/sys_plan9_386.s (m_errstr(BX) =E2=86=92 (m_mOS+mOS_errstr)= (BX)) And move cas and casp1 functions from src/runtime/sys_plan9_arm.s to src/runtime/internal/atomic/sys_plan9_arm.s. --=20 David du Colombier From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <9ed943cac2b126778cf7fbccc4d6d948@hamnavoe.com> References: <327e2f1c17187c02a3cc24639321b9e2@proxima.alt.za> <9ed943cac2b126778cf7fbccc4d6d948@hamnavoe.com> Date: Thu, 31 Dec 2015 14:35:50 +0000 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7bfd091c3c1a8e0528329275 Subject: Re: [9fans] any updates on go for plan9/arm? Topicbox-Message-UUID: 7c6efd44-ead9-11e9-9d60-3106f5b1d025 --047d7bfd091c3c1a8e0528329275 Content-Type: text/plain; charset=UTF-8 On 31 December 2015 at 11:57, Richard Miller <9fans@hamnavoe.com> wrote: > Raspberry Pi 2, but has an elusive "one last bug" which I suspect has to > do with cache or page table coherency. > It's still got the explicit cache management code from the old bcm, which isn't right. There might be more. The hardware will provide full coherency. I've got some pi2 work to do so I'll work out the changes compared to what I use. --047d7bfd091c3c1a8e0528329275 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 31 December 2015 at 11:57, Richard Miller <9fans@hamnavoe.com>= wrote:
Raspberry Pi 2, but has an elusive "one= last bug" which I suspect has to
do with cache or page table coherency.=C2=A0

It= 's still got the explicit cache management code from the old bcm, which= isn't right. There might be more.
The = hardware will provide full coherency.
I'= ;ve got some pi2 work to do so I'll work out the changes compared to wh= at I use.
--047d7bfd091c3c1a8e0528329275-- From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <843332f610d2030454b2983e5c006fb5@proxima.alt.za> To: 9fans@9fans.net Date: Thu, 31 Dec 2015 18:36:01 +0200 From: lucio@proxima.alt.za In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] any updates on go for plan9/arm? Topicbox-Message-UUID: 7c7691e4-ead9-11e9-9d60-3106f5b1d025 > I've got some pi2 work to do so I'll work out the changes compared to what > I use. Thanks, Charles, Richard and David (in reverse order of appearance), for the effort. It is heart warming that there is still interest in Plan 9 and the curiously connected Go (in other words, that I'm not the only one attracted to the platform). I guess we'll need to wait for the critical mass or the killer app to re-launch Plan 9 into the stratosphere :-) In the meantime, if memory serves, there are no convenient builders for Plan9/arm and thus no likelihood that Go will be officially released for Plan9/arm until at least one builder is deployed. In my experience, David would be the best person to coordinate with, if builders can be made available. Lucio. From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1c7a412a3477b3723b8a4be62ee587e2@9netics.com> To: 9fans@9fans.net Date: Thu, 31 Dec 2015 11:03:52 -0800 From: Skip Tavakkolian <9nut@9netics.com> In-Reply-To: <843332f610d2030454b2983e5c006fb5@proxima.alt.za> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] any updates on go for plan9/arm? Topicbox-Message-UUID: 7c8db608-ead9-11e9-9d60-3106f5b1d025 > Thanks, Charles, Richard and David (in reverse order of appearance), > for the effort. It is heart warming that there is still interest in > Plan 9 and the curiously connected Go (in other words, that I'm not the > only one attracted to the platform). Let me add my thanks as well to Go Authors and all who have made Go on Plan 9 possible. Go really helps Plan 9 deal with the huge number of API's, subsystems and protocols (e.g. OAuth2, SQL databases, HTTP/2, etc). -Skip From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <1c7a412a3477b3723b8a4be62ee587e2@9netics.com> References: <843332f610d2030454b2983e5c006fb5@proxima.alt.za> <1c7a412a3477b3723b8a4be62ee587e2@9netics.com> Date: Fri, 1 Jan 2016 01:31:03 +0100 Message-ID: From: David du Colombier <0intro@gmail.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=089e012955f0e9114c05283ae2f8 Subject: Re: [9fans] any updates on go for plan9/arm? Topicbox-Message-UUID: 7c9a4b20-ead9-11e9-9d60-3106f5b1d025 --089e012955f0e9114c05283ae2f8 Content-Type: text/plain; charset=UTF-8 A plan9/arm builder has been already running for two months. -- David du Colombier --089e012955f0e9114c05283ae2f8 Content-Type: text/html; charset=UTF-8

A plan9/arm builder has been already running for two months.

--
David du Colombier

--089e012955f0e9114c05283ae2f8-- From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <2f180af50885a7dd76be62b11ffd5300@proxima.alt.za> To: 9fans@9fans.net Date: Fri, 1 Jan 2016 06:35:39 +0200 From: lucio@proxima.alt.za In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] any updates on go for plan9/arm? Topicbox-Message-UUID: 7c9e3c08-ead9-11e9-9d60-3106f5b1d025 > A plan9/arm builder has been already running for two months. I knew I'd have to qualify my statement :-) In your opinion, will Go for plan9/arm be ready for inclusion in 1.7? Is there any work that needs additional resources to make that possible? Lucio. From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <2f180af50885a7dd76be62b11ffd5300@proxima.alt.za> References: <2f180af50885a7dd76be62b11ffd5300@proxima.alt.za> From: minux Date: Thu, 31 Dec 2015 23:53:31 -0500 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a114a4386b1eab405283e8e14 Subject: Re: [9fans] any updates on go for plan9/arm? Topicbox-Message-UUID: 7ca79e9c-ead9-11e9-9d60-3106f5b1d025 --001a114a4386b1eab405283e8e14 Content-Type: text/plain; charset=UTF-8 I just went through the patch, aside from minor cosmetic changes, I think it's ready for inclusion into Go 1.7 if all.bash passes. The author just has to split it up into CLs and push to Gerrit for review. --001a114a4386b1eab405283e8e14 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I just went through the patch, = aside from minor cosmetic
changes, I think = it's ready for inclusion into Go 1.7 if
all.bash passes. The author just has to split it up into
CLs and push to Gerrit for review.
--001a114a4386b1eab405283e8e14-- From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@9fans.net Date: Fri, 1 Jan 2016 07:39:06 +0200 From: lucio@proxima.alt.za In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] any updates on go for plan9/arm? Topicbox-Message-UUID: 7cb06388-ead9-11e9-9d60-3106f5b1d025 > I just went through the patch, aside from minor cosmetic > changes, I think it's ready for inclusion into Go 1.7 if > all.bash passes. The author just has to split it up into > CLs and push to Gerrit for review. That is great, Minux. Thank you very much for taking the trouble. Maybe 2016 is going to be a good year for Plan 9. Happy new year to all 9fans! Lucio. From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: From: Conor Williams Date: Mon, 12 Feb 2018 06:08:07 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="001a113ecc84b7cb8e0564fdb3c9" Subject: Re: [9fans] any updates on go for plan9/arm? Topicbox-Message-UUID: cddde6c2-ead9-11e9-9d60-3106f5b1d025 --001a113ecc84b7cb8e0564fdb3c9 Content-Type: text/plain; charset="UTF-8" Happy neuo year bouz Kotw On Friday, January 1, 2016, wrote: > > I just went through the patch, aside from minor cosmetic > > changes, I think it's ready for inclusion into Go 1.7 if > > all.bash passes. The author just has to split it up into > > CLs and push to Gerrit for review. > > That is great, Minux. Thank you very much for taking the trouble. > > Maybe 2016 is going to be a good year for Plan 9. Happy new year to > all 9fans! > > Lucio. > > > --001a113ecc84b7cb8e0564fdb3c9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Happy neuo year bouz

Kotw

On Friday, January 1, = 2016, <lucio@proxima.alt.za= > wrote:
> I just went through the = patch, aside from minor cosmetic
> changes, I think it's ready for inclusion into Go 1.7 if
> all.bash passes. The author just has to split it up into
> CLs and push to Gerrit for review.

That is great, Minux.=C2=A0 Thank you very much for taking the trouble.

Maybe 2016 is going to be a good year for Plan 9.=C2=A0 Happy new year to all 9fans!

Lucio.


--001a113ecc84b7cb8e0564fdb3c9--