[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170628212500.GN6973@jhogan-linux.le.imgtec.org>
Date: Wed, 28 Jun 2017 22:25:00 +0100
From: James Hogan <james.hogan@...tec.com>
To: Palmer Dabbelt <palmer@...belt.com>
CC: <peterz@...radead.org>, <mingo@...hat.com>, <mcgrof@...nel.org>,
<viro@...iv.linux.org.uk>, <sfr@...b.auug.org.au>,
<nicolas.dichtel@...nd.com>, <rmk+kernel@...linux.org.uk>,
<msalter@...hat.com>, <tklauser@...tanz.ch>, <will.deacon@....com>,
<paul.gortmaker@...driver.com>, <linux@...ck-us.net>,
<linux-kernel@...r.kernel.org>, <linux-arch@...r.kernel.org>,
<albert@...ive.com>
Subject: Re: [PATCH 9/9] RISC-V: Build Infastructure
Hi Palmer,
On Wed, Jun 28, 2017 at 11:55:38AM -0700, Palmer Dabbelt wrote:
> + select SYSRISCV_ATOMIC if !ISA_A
...
> +config SYSRISCV_ATOMIC
> + bool "Include support for atomic operation syscalls"
> + default !ISA_A
> + help
> + If atomic memory instructions are present, i.e.,
> + CONFIG_ISA_A, this includes support for the syscall that
> + provides atomic accesses. This is only useful to run
> + binaries that require atomic access but were compiled with
> + -mno-atomic.
> +
> + If CONFIG_ISA_A is unset, this option is mandatory.
> +
> + If you don't know what to do here, say N.
Can this be removed now that you mentioned the atomics syscall being
mandatory? I can't find any other references to it.
Cheers
James
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists