Message-ID: <4f35f41c143b02b6b815e7eb527ca3acd8b4aabe.camel@redhat.com>
Subject: Re: [RFC PATCH 0/6] Deduplicating RISCV cmpxchg.h macros
From:   Leonardo =?ISO-8859-1?Q?Br=E1s?= <leobras@redhat.com>
To:     Conor Dooley <conor@kernel.org>
Cc:     Paul Walmsley <paul.walmsley@sifive.com>,
        Palmer Dabbelt <palmer@dabbelt.com>,
        Albert Ou <aou@eecs.berkeley.edu>, Guo Ren <guoren@kernel.org>,
        linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Date:   Tue, 21 Mar 2023 03:30:35 -0300
In-Reply-To: <8f698f49-135a-4263-8471-96f406919cb1@spud>
References: <20230318080059.1109286-1-leobras@redhat.com>
         <8f698f49-135a-4263-8471-96f406919cb1@spud>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.46.4 
MIME-Version: 1.0
Precedence: bulk

Hello Conor, thanks for the feedback!


On Sun, 2023-03-19 at 20:35 +0000, Conor Dooley wrote:
> On Sat, Mar 18, 2023 at 05:00:54AM -0300, Leonardo Bras wrote:
> > While studying riscv's cmpxchg.h file, I got really interested in=20
> > understanding how RISCV asm implemented the different versions of=20
> > {cmp,}xchg.
> >=20
> > When I understood the pattern, it made sense for me to remove the=20
> > duplications and create macros to make it easier to understand what exa=
ctly=20
> > changes between the versions: Instruction sufixes & barriers.
> >=20
> > I split those changes in 3 levels for each cmpxchg and xchg, resulting =
a=20
> > total of 6 patches. I did this so it becomes easier to review and remov=
e=20
> > the last levels if desired, but I have no issue squashing them if it's=
=20
> > better.
> >=20
> > Please provide comments.
> >=20
> > Thanks!
> > Leo
> >=20
> > Leonardo Bras (6):
> >   riscv/cmpxchg: Deduplicate cmpxchg() asm functions
> >   riscv/cmpxchg: Deduplicate cmpxchg() macros
> >   riscv/cmpxchg: Deduplicate arch_cmpxchg() macros
>=20
> >   riscv/cmpxchg: Deduplicate xchg() asm functions
>=20
> FWIW, this patch seems to break the build pretty badly:
> https://patchwork.kernel.org/project/linux-riscv/patch/20230318080059.110=
9286-5-leobras@redhat.com/

Thanks for pointing out!

It was an intermediary error:
Sufix for amoswap on acquire version was "d.aqrl" instead of the
correct".d.aqrl", and that caused the fail.

I did not notice anything because the next commit made it more general, and=
 thus
removed this line of code. I will send a v2-RFC shortly.

I see that patch 4/6 has 5 fails, but on each one of them I can see:
"I: build output in /ci/workspace/[...]", or
""I: build output in /tmp/[...]".

I could not find any reference to where this is saved, though.
Could you point where can I find the error output, just for the sake of fur=
ther
debugging?

>=20
> Patches 1 & 5 also add quite a lot of sparse issues (like 1000), but I
> think that may be more of an artifact of the testing process as opposed
> to something caused by this patchset.

For those I can see the build output diffs. Both added error lines to
conchuod/build_rv64_gcc_allmodconfig.
I tried to mimic this with [make allmodconfig + gcc build with
CROSS_COMPILE=3Driscv64-linux-gnu- ] but I could not get any error in any p=
atch.

For patch 1/6 it removes as much error lines (-) as it adds (+), and the er=
ror
messages are mostly the same, apart for an line number.

For patch 5/6 it actually adds many more lines, but tracking (some of) the
errors gave me no idea why.

>=20
> Cheers,
> Conor.

Thanks a lot!
Leo