Grokbase › Groups › Go › golang-dev › February 2016
FAQ
Hello. Our 1.6-level port has been updated to the release level on our
github repo, so we are anxious to begin contributing our port for Linux on
System Z to the 1.7 stream. We have the builder machine ready to go. The
machine that we have is a z13 VM running SLES 12.1. It has 2 vCPUs, 2GB of
RAM, 500MB of swap, and 42GB of disk (on top of the boot file system)
mounted under /data, which is where I have placed a bootstrap Go compiler
for z and the build bot code (they call it "buildlet"). The system has
Docker installed. The machine has one user account named "linux1" and is
accessed only via a SSH key (no password). linux1 has sudo access so it can
do whatever it wants, e.g. create new users for ourselves and community
leaders.

We'd appreciate a little help getting started. First of all, some advice on
structuring our CLs. Also, Russ or Brad, can we send you the ssh key?
Thanks for your advice.
...Bill

--
You received this message because you are subscribed to the Google Groups "golang-dev" 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.

Search Discussions

  • Minux at Feb 24, 2016 at 1:18 am ⇧

    On Mon, Feb 22, 2016 at 3:58 PM, Bill O'Farrell wrote:

    Hello. Our 1.6-level port has been updated to the release level on our
    github repo, so we are anxious to begin contributing our port for Linux on
    System Z to the 1.7 stream. We have the builder machine ready to go. The
    machine that we have is a z13 VM running SLES 12.1. It has 2 vCPUs, 2GB of
    RAM, 500MB of swap, and 42GB of disk (on top of the boot file system)
    mounted under /data, which is where I have placed a bootstrap Go compiler
    for z and the build bot code (they call it "buildlet"). The system has
    Docker installed. The machine has one user account named "linux1" and is
    accessed only via a SSH key (no password). linux1 has sudo access so it can
    do whatever it wants, e.g. create new users for ourselves and community
    leaders.

    We'd appreciate a little help getting started. First of all, some advice
    on structuring our CLs. Also, Russ or Brad, can we send you the ssh key?
    I suggest follow the structure of the mips64 port in the last cycle.
    https://go-review.googlesource.com/#/q/status:merged+project:go+branch:master+topic:mips64

    Basically, first divide the changes into separate CLs for each changed
    package. Within
    each changed package, use separate CLs for manually written files and
    automatically
    generated files (syscall/z*.go).

    If there are changes to the portable part of a package (this mostly applies
    to the runtime
    package), then separate out the changes to the portable part too. (see the
    runtime CLs
    for the linux/mips64 port)

    --
    You received this message because you are subscribed to the Google Groups "golang-dev" 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.
  • Cherry at Feb 24, 2016 at 2:57 am ⇧
    On Tue, Feb 23, 2016 at 8:18 PM, minux wrote:
    On Mon, Feb 22, 2016 at 3:58 PM, Bill O'Farrell wrote:

    Hello. Our 1.6-level port has been updated to the release level on our
    github repo, so we are anxious to begin contributing our port for Linux on
    System Z to the 1.7 stream. We have the builder machine ready to go. The
    machine that we have is a z13 VM running SLES 12.1. It has 2 vCPUs, 2GB of
    RAM, 500MB of swap, and 42GB of disk (on top of the boot file system)
    mounted under /data, which is where I have placed a bootstrap Go compiler
    for z and the build bot code (they call it "buildlet"). The system has
    Docker installed. The machine has one user account named "linux1" and is
    accessed only via a SSH key (no password). linux1 has sudo access so it can
    do whatever it wants, e.g. create new users for ourselves and community
    leaders.

    We'd appreciate a little help getting started. First of all, some advice
    on structuring our CLs. Also, Russ or Brad, can we send you the ssh key?
    I suggest follow the structure of the mips64 port in the last cycle.

    https://go-review.googlesource.com/#/q/status:merged+project:go+branch:master+topic:mips64
    There was a problem with that CL sequence. We need to update cmd/dist
    whenever a dependency is added to cmd/*, instead of doing it all at the end.

    --
    You received this message because you are subscribed to the Google Groups "golang-dev" 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.
  • Brad Fitzpatrick at Feb 26, 2016 at 8:18 pm ⇧
    I am:

    ssh-ed25519
    AAAAC3NzaC1lZDI1NTE5AAAAIBc8FQIyzPuAFtyTmCZFpRb6YSU0qHcuq7Ms96utYfX+
    bradfitz



    On Mon, Feb 22, 2016 at 12:58 PM, Bill O'Farrell wrote:

    Hello. Our 1.6-level port has been updated to the release level on our
    github repo, so we are anxious to begin contributing our port for Linux on
    System Z to the 1.7 stream. We have the builder machine ready to go. The
    machine that we have is a z13 VM running SLES 12.1. It has 2 vCPUs, 2GB of
    RAM, 500MB of swap, and 42GB of disk (on top of the boot file system)
    mounted under /data, which is where I have placed a bootstrap Go compiler
    for z and the build bot code (they call it "buildlet"). The system has
    Docker installed. The machine has one user account named "linux1" and is
    accessed only via a SSH key (no password). linux1 has sudo access so it can
    do whatever it wants, e.g. create new users for ourselves and community
    leaders.

    We'd appreciate a little help getting started. First of all, some advice
    on structuring our CLs. Also, Russ or Brad, can we send you the ssh key?
    Thanks for your advice.
    ...Bill

    --
    You received this message because you are subscribed to the Google Groups
    "golang-dev" 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-dev" 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.
  • Munday at Mar 21, 2016 at 4:14 am ⇧
    Hello,

    I have just sent the core set of CLs for the s390x port:

    https://go-review.googlesource.com/20872 cmd/dist: add "s390x" to okgoarch
    and cgoEnabled
    https://go-review.googlesource.com/20932 cmd/dist: enable -shared and
    external linking tests on s390x
    https://go-review.googlesource.com/20934 cmd/asm: add s390x support
    https://go-review.googlesource.com/20935 cmd/api: add s390x support
    https://go-review.googlesource.com/20873 cmd/compile/internal/s390x: add
    s390x support
    https://go-review.googlesource.com/20874 debug: add s390x support
    https://go-review.googlesource.com/20875 cmd/compile/internal/gc: add s390x
    support
    https://go-review.googlesource.com/20876 cmd/go: add s390x support
    https://go-review.googlesource.com/20877 internal/syscall/unix: add
    randomTrap const for s390x
    https://go-review.googlesource.com/20878 cmd/link/internal/ld: add s390x
    support
    https://go-review.googlesource.com/20879 cmd/link/internal/s390x: add s390x
    support
    https://go-review.googlesource.com/20936 math: add functions and stubs for
    s390x
    https://go-review.googlesource.com/20937 math/big: add s390x function
    implementations
    https://go-review.googlesource.com/20940 misc/cgo/test: add RewindAndSetgid
    implementation for s390x
    https://go-review.googlesource.com/20941 cmd/internal/obj: add support for
    s390x
    https://go-review.googlesource.com/20942 cmd/internal/obj/s390x: add s390x
    support
    https://go-review.googlesource.com/20943 cmd/internal/objfile: add s390x
    support
    https://go-review.googlesource.com/20944 reflect: add s390x support
    https://go-review.googlesource.com/20945 runtime: add s390x support
    (modified files only)
    https://go-review.googlesource.com/20946 runtime: add s390x support (new
    files only)
    https://go-review.googlesource.com/20938 runtime/internal/atomic: add s390x
    atomic operations
    https://go-review.googlesource.com/20939 runtime/internal/sys: add s390x
    support
    https://go-review.googlesource.com/20950 runtime/cgo: add s390x support
    https://go-review.googlesource.com/20947 sync/atomic: add s390x
    implementations of atomic functions
    https://go-review.googlesource.com/20948 syscall: add s390x support
    https://go-review.googlesource.com/20949 syscall: add autogenerated files
    for s390x
    https://go-review.googlesource.com/20960 syscall: change clone argument
    order on s390x
    https://go-review.googlesource.com/20961 syscall: add PtraceRegs struct for
    s390x
    https://go-review.googlesource.com/20962 test/fixedbugs: add s390x case to
    issue11656
    https://go-review.googlesource.com/20963 test: skip nilptr3 test on s390x

    I have tried to structure them so that they can be applied individually
    without breaking other architecture builds (as long as each ones
    dependencies have already been committed of course).

    Some of the commit messages are a bit light on detail, I'll try and flesh
    them out depending on what comes out of the code reviews.

    Thank you all so much for all your help!

    Michael


    On Friday, February 26, 2016 at 3:18:12 PM UTC-5, Brad Fitzpatrick wrote:

    I am:

    ssh-ed25519
    AAAAC3NzaC1lZDI1NTE5AAAAIBc8FQIyzPuAFtyTmCZFpRb6YSU0qHcuq7Ms96utYfX+
    bradfitz




    On Mon, Feb 22, 2016 at 12:58 PM, Bill O'Farrell <[email protected]
    <javascript:>> wrote:
    Hello. Our 1.6-level port has been updated to the release level on our
    github repo, so we are anxious to begin contributing our port for Linux on
    System Z to the 1.7 stream. We have the builder machine ready to go. The
    machine that we have is a z13 VM running SLES 12.1. It has 2 vCPUs, 2GB of
    RAM, 500MB of swap, and 42GB of disk (on top of the boot file system)
    mounted under /data, which is where I have placed a bootstrap Go compiler
    for z and the build bot code (they call it "buildlet"). The system has
    Docker installed. The machine has one user account named "linux1" and is
    accessed only via a SSH key (no password). linux1 has sudo access so it can
    do whatever it wants, e.g. create new users for ourselves and community
    leaders.

    We'd appreciate a little help getting started. First of all, some advice
    on structuring our CLs. Also, Russ or Brad, can we send you the ssh key?
    Thanks for your advice.
    ...Bill

    --
    You received this message because you are subscribed to the Google Groups
    "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to [email protected] <javascript:>.
    For more options, visit https://groups.google.com/d/optout.
    --
    You received this message because you are subscribed to the Google Groups "golang-dev" 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.
  • Minux at Mar 21, 2016 at 4:18 am ⇧

    On Mon, Mar 21, 2016 at 12:14 AM, wrote:

    Hello,

    I have just sent the core set of CLs for the s390x port:

    https://go-review.googlesource.com/20872 cmd/dist: add "s390x" to
    okgoarch and cgoEnabled
    https://go-review.googlesource.com/20932 cmd/dist: enable -shared and
    external linking tests on s390x
    https://go-review.googlesource.com/20934 cmd/asm: add s390x support
    https://go-review.googlesource.com/20935 cmd/api: add s390x support
    https://go-review.googlesource.com/20873 cmd/compile/internal/s390x: add
    s390x support
    https://go-review.googlesource.com/20874 debug: add s390x support
    https://go-review.googlesource.com/20875 cmd/compile/internal/gc: add
    s390x support
    https://go-review.googlesource.com/20876 cmd/go: add s390x support
    https://go-review.googlesource.com/20877 internal/syscall/unix: add
    randomTrap const for s390x
    https://go-review.googlesource.com/20878 cmd/link/internal/ld: add s390x
    support
    https://go-review.googlesource.com/20879 cmd/link/internal/s390x: add
    s390x support
    https://go-review.googlesource.com/20936 math: add functions and stubs
    for s390x
    https://go-review.googlesource.com/20937 math/big: add s390x function
    implementations
    https://go-review.googlesource.com/20940 misc/cgo/test: add
    RewindAndSetgid implementation for s390x
    https://go-review.googlesource.com/20941 cmd/internal/obj: add support
    for s390x
    https://go-review.googlesource.com/20942 cmd/internal/obj/s390x: add
    s390x support
    https://go-review.googlesource.com/20943 cmd/internal/objfile: add s390x
    support
    https://go-review.googlesource.com/20944 reflect: add s390x support
    https://go-review.googlesource.com/20945 runtime: add s390x support
    (modified files only)
    https://go-review.googlesource.com/20946 runtime: add s390x support (new
    files only)
    https://go-review.googlesource.com/20938 runtime/internal/atomic: add
    s390x atomic operations
    https://go-review.googlesource.com/20939 runtime/internal/sys: add s390x
    support
    https://go-review.googlesource.com/20950 runtime/cgo: add s390x support
    https://go-review.googlesource.com/20947 sync/atomic: add s390x
    implementations of atomic functions
    https://go-review.googlesource.com/20948 syscall: add s390x support
    https://go-review.googlesource.com/20949 syscall: add autogenerated files
    for s390x
    https://go-review.googlesource.com/20960 syscall: change clone argument
    order on s390x
    https://go-review.googlesource.com/20961 syscall: add PtraceRegs struct
    for s390x
    https://go-review.googlesource.com/20962 test/fixedbugs: add s390x case
    to issue11656
    https://go-review.googlesource.com/20963 test: skip nilptr3 test on s390x

    I have tried to structure them so that they can be applied individually
    without breaking other architecture builds (as long as each ones
    dependencies have already been committed of course).
    Could you please at least make the dependency clear by stacking dependent
    CLs on their dependencies CLs as a CL series. (A CL series is basically
    multiple
    CL commits on the same branch and they can be pushed together to gerrit.)

    --
    You received this message because you are subscribed to the Google Groups "golang-dev" 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.
  • Brad Fitzpatrick at Mar 21, 2016 at 4:47 am ⇧
    If that's too onerous, though, don't worry about it.

    We'll try to get these reviewed and submitted soon. As long as they don't
    break other builders I don't really care about the order.
    On Mar 21, 2016 3:18 PM, "minux" wrote:


    On Mon, Mar 21, 2016 at 12:14 AM, wrote:

    Hello,

    I have just sent the core set of CLs for the s390x port:

    https://go-review.googlesource.com/20872 cmd/dist: add "s390x" to
    okgoarch and cgoEnabled
    https://go-review.googlesource.com/20932 cmd/dist: enable -shared and
    external linking tests on s390x
    https://go-review.googlesource.com/20934 cmd/asm: add s390x support
    https://go-review.googlesource.com/20935 cmd/api: add s390x support
    https://go-review.googlesource.com/20873 cmd/compile/internal/s390x: add
    s390x support
    https://go-review.googlesource.com/20874 debug: add s390x support
    https://go-review.googlesource.com/20875 cmd/compile/internal/gc: add
    s390x support
    https://go-review.googlesource.com/20876 cmd/go: add s390x support
    https://go-review.googlesource.com/20877 internal/syscall/unix: add
    randomTrap const for s390x
    https://go-review.googlesource.com/20878 cmd/link/internal/ld: add s390x
    support
    https://go-review.googlesource.com/20879 cmd/link/internal/s390x: add
    s390x support
    https://go-review.googlesource.com/20936 math: add functions and stubs
    for s390x
    https://go-review.googlesource.com/20937 math/big: add s390x function
    implementations
    https://go-review.googlesource.com/20940 misc/cgo/test: add
    RewindAndSetgid implementation for s390x
    https://go-review.googlesource.com/20941 cmd/internal/obj: add support
    for s390x
    https://go-review.googlesource.com/20942 cmd/internal/obj/s390x: add
    s390x support
    https://go-review.googlesource.com/20943 cmd/internal/objfile: add s390x
    support
    https://go-review.googlesource.com/20944 reflect: add s390x support
    https://go-review.googlesource.com/20945 runtime: add s390x support
    (modified files only)
    https://go-review.googlesource.com/20946 runtime: add s390x support (new
    files only)
    https://go-review.googlesource.com/20938 runtime/internal/atomic: add
    s390x atomic operations
    https://go-review.googlesource.com/20939 runtime/internal/sys: add s390x
    support
    https://go-review.googlesource.com/20950 runtime/cgo: add s390x support
    https://go-review.googlesource.com/20947 sync/atomic: add s390x
    implementations of atomic functions
    https://go-review.googlesource.com/20948 syscall: add s390x support
    https://go-review.googlesource.com/20949 syscall: add autogenerated
    files for s390x
    https://go-review.googlesource.com/20960 syscall: change clone argument
    order on s390x
    https://go-review.googlesource.com/20961 syscall: add PtraceRegs struct
    for s390x
    https://go-review.googlesource.com/20962 test/fixedbugs: add s390x case
    to issue11656
    https://go-review.googlesource.com/20963 test: skip nilptr3 test on s390x

    I have tried to structure them so that they can be applied individually
    without breaking other architecture builds (as long as each ones
    dependencies have already been committed of course).
    Could you please at least make the dependency clear by stacking dependent
    CLs on their dependencies CLs as a CL series. (A CL series is basically
    multiple
    CL commits on the same branch and they can be pushed together to gerrit.)

    --
    You received this message because you are subscribed to the Google Groups
    "golang-dev" 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-dev" 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.
  • Michael Munday at Mar 21, 2016 at 4:57 am ⇧
    Minux has posted some instructions in one of the CLs (thanks Minux!). I'll
    give it a go, it sounds like it will make things a little easier for me to
    manage too.



    From: Brad Fitzpatrick <[email protected]>
    To: Shenghou Ma <[email protected]>
    Cc: Michael Munday/Toronto/[email protected], "Bill O'Farrell"
                 <[email protected]>, golang-dev
                 <[email protected]>
    Date: 03/21/2016 12:47 AM
    Subject: Re: [golang-dev] Port of go to Linux on Z
    Sent by: [email protected]



    If that's too onerous, though, don't worry about it.


    We'll try to get these reviewed and submitted soon. As long as they don't
    break other builders I don't really care about the order.


    On Mar 21, 2016 3:18 PM, "minux" wrote:


       On Mon, Mar 21, 2016 at 12:14 AM, wrote:
        Hello,

        I have just sent the core set of CLs for the s390x port:

        https://go-review.googlesource.com/20872 cmd/dist: add "s390x" to
        okgoarch and cgoEnabled
        https://go-review.googlesource.com/20932 cmd/dist: enable -shared and
        external linking tests on s390x
        https://go-review.googlesource.com/20934 cmd/asm: add s390x support
        https://go-review.googlesource.com/20935 cmd/api: add s390x support
        https://go-review.googlesource.com/20873 cmd/compile/internal/s390x: add
        s390x support
        https://go-review.googlesource.com/20874 debug: add s390x support
        https://go-review.googlesource.com/20875 cmd/compile/internal/gc: add
        s390x support
        https://go-review.googlesource.com/20876 cmd/go: add s390x support
        https://go-review.googlesource.com/20877 internal/syscall/unix: add
        randomTrap const for s390x
        https://go-review.googlesource.com/20878 cmd/link/internal/ld: add s390x
        support
        https://go-review.googlesource.com/20879 cmd/link/internal/s390x: add
        s390x support
        https://go-review.googlesource.com/20936 math: add functions and stubs
        for s390x
        https://go-review.googlesource.com/20937 math/big: add s390x function
        implementations
        https://go-review.googlesource.com/20940 misc/cgo/test: add
        RewindAndSetgid implementation for s390x
        https://go-review.googlesource.com/20941 cmd/internal/obj: add support
        for s390x
        https://go-review.googlesource.com/20942 cmd/internal/obj/s390x: add
        s390x support
        https://go-review.googlesource.com/20943 cmd/internal/objfile: add s390x
        support
        https://go-review.googlesource.com/20944 reflect: add s390x support
        https://go-review.googlesource.com/20945 runtime: add s390x support
        (modified files only)
        https://go-review.googlesource.com/20946 runtime: add s390x support (new
        files only)
        https://go-review.googlesource.com/20938 runtime/internal/atomic: add
        s390x atomic operations
        https://go-review.googlesource.com/20939 runtime/internal/sys: add s390x
        support
        https://go-review.googlesource.com/20950 runtime/cgo: add s390x support
        https://go-review.googlesource.com/20947 sync/atomic: add s390x
        implementations of atomic functions
        https://go-review.googlesource.com/20948 syscall: add s390x support
        https://go-review.googlesource.com/20949 syscall: add autogenerated
        files for s390x
        https://go-review.googlesource.com/20960 syscall: change clone argument
        order on s390x
        https://go-review.googlesource.com/20961 syscall: add PtraceRegs struct
        for s390x
        https://go-review.googlesource.com/20962 test/fixedbugs: add s390x case
        to issue11656
        https://go-review.googlesource.com/20963 test: skip nilptr3 test on
        s390x

        I have tried to structure them so that they can be applied individually
        without breaking other architecture builds (as long as each ones
        dependencies have already been committed of course).

       Could you please at least make the dependency clear by stacking dependent
       CLs on their dependencies CLs as a CL series. (A CL series is basically
       multiple
       CL commits on the same branch and they can be pushed together to gerrit.)
       --
       You received this message because you are subscribed to the Google Groups
       "golang-dev" 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 a topic in the
    Google Groups "golang-dev" group.
    To unsubscribe from this topic, visit
    https://groups.google.com/d/topic/golang-dev/T1TwiiVZj_Q/unsubscribe.
    To unsubscribe from this group and all its topics, 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-dev" 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.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupgolang-dev @
categoriesgo
postedFeb 22, '16 at 8:58p
activeMar 21, '16 at 4:57a
posts8
users5
websitegolang.org

5 users in discussion

Michael Munday: 2 posts Minux: 2 posts Brad Fitzpatrick: 2 posts Cherry: 1 post Bill O'Farrell: 1 post

Content

People

Support

Translate

site design / logo © 2023 Grokbase