All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Guy Martin <gmsoft@tuxicoman.be>
Cc: linux-parisc@vger.kernel.org
Subject: Re: [RFC PATCHv2] 64bit LWS CAS
Date: Tue, 26 Aug 2014 22:11:43 +0200	[thread overview]
Message-ID: <53FCE9FF.1080704@gmx.de> (raw)
In-Reply-To: <f4954acbf0d2c11646341cb93efdd247@tuxicoman.be>

Hi Guy,

should we try to do a last round of cleanup of this patch, since
I would like to include it in the next push to Linus...

On 07/30/2014 11:17 AM, Guy Martin wrote:
>>> Regading the GCC counterpart of the implementation, I'm not sure about
>>> the way to proceed.
>>>
>>> Should I try to detect the presence of the new LWS and use it for all
>>> CAS operations at init time ?
>>
>> I leave this up to Dave & Carlos to answer.

I think it's OK to stay using the existing 32bit implementation for 32bit CAS,
and just use the new one for 8/16/64 bit CAS.
And maybe: If the LWS fails, just crash the application.

>> Should we maybe drop the whole ENABLE_LWS_DEBUG thing? Was it ever used/enabled?
>
> Indeed, I have not tested it and I dropped it in this new patch.

Good.
In comments at the top still include info about the debug case:
-> "If debugging is DISabled:..."

>>> I guess that using the new LWS unconditionally for all CAS operations
>>> isn't an option since it will break for newer gcc on old kernels.
>>
>> Up to now we only had the 32bit CAS working correctly, so we shouldn't care much
>> about the other CAS anyway.
>> And if we get it backported into all relevant kernels before we change gcc
>> I would prefer this hard break...

I'm still thinking this is the right way.

Your patch had some whitespace errors too.
Please run it through the scripts/checkpatch tool in the kernel tree.

If you like I can take care of the suggested changes and send a revised patch for you?
Just let me know.

Helge

  parent reply	other threads:[~2014-08-26 20:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29 19:13 [RFC PATCHv2] 64bit LWS CAS Guy Martin
2014-07-29 21:24 ` Helge Deller
2014-07-30  9:17   ` Guy Martin
2014-07-30  9:45     ` Guy Martin
2014-08-26 20:11     ` Helge Deller [this message]
2014-08-27  8:35       ` Guy Martin

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=53FCE9FF.1080704@gmx.de \
    --to=deller@gmx.de \
    --cc=gmsoft@tuxicoman.be \
    --cc=linux-parisc@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.