On 06/25/2015 12:33 AM, Daniel Vetter wrote:
>> In the specific case of bitfields it seems like it would be sufficient
>> > to mark the local variables as volatile? Or maybe just use open coded
>> > compiler barrier() functions instead, with accompanying documentation.
>> >
>> > Documentation/mem
On Wed, Jun 24, 2015 at 03:56:15PM -0700, Jesse Barnes wrote:
> On 06/22/2015 11:53 PM, Daniel Vetter wrote:
> > On Mon, Jun 22, 2015 at 02:19:51PM -0700, Jesse Barnes wrote:
> >> On 06/17/2015 08:10 AM, Daniel Vetter wrote:
> >>> On Wed, Jun 17, 2015 at 05:28:20PM +0300, Jani Nikula wrote:
>
On 06/22/2015 11:53 PM, Daniel Vetter wrote:
> On Mon, Jun 22, 2015 at 02:19:51PM -0700, Jesse Barnes wrote:
>> On 06/17/2015 08:10 AM, Daniel Vetter wrote:
>>> On Wed, Jun 17, 2015 at 05:28:20PM +0300, Jani Nikula wrote:
On Wed, 17 Jun 2015, Chris Wilson wrote:
> Here's an idea I want to
On Mon, Jun 22, 2015 at 02:19:51PM -0700, Jesse Barnes wrote:
> On 06/17/2015 08:10 AM, Daniel Vetter wrote:
> > On Wed, Jun 17, 2015 at 05:28:20PM +0300, Jani Nikula wrote:
> >> On Wed, 17 Jun 2015, Chris Wilson wrote:
> >>> Here's an idea I want to float to see if anyone has a better idea.
> >>
On 06/17/2015 08:10 AM, Daniel Vetter wrote:
> On Wed, Jun 17, 2015 at 05:28:20PM +0300, Jani Nikula wrote:
>> On Wed, 17 Jun 2015, Chris Wilson wrote:
>>> Here's an idea I want to float to see if anyone has a better idea.
>>
>> I'll give it some thought, but it pains me that things like this make
On Wed, Jun 17, 2015 at 05:28:20PM +0300, Jani Nikula wrote:
> On Wed, 17 Jun 2015, Chris Wilson wrote:
> > Here's an idea I want to float to see if anyone has a better idea.
>
> I'll give it some thought, but it pains me that things like this make it
> harder for source code cross referencers an
On Wed, 17 Jun 2015, Chris Wilson wrote:
> Here's an idea I want to float to see if anyone has a better idea.
I'll give it some thought, but it pains me that things like this make it
harder for source code cross referencers and even grep to find what you
you're looking for.
BR,
Jani.
> Daniel
Here's an idea I want to float to see if anyone has a better idea.
Daniel is very keen on using READ_ONCE/WRITE_ONCE/ACCESS_ONCE to
document where we play games with memory barriers instead outside of the
usual locks. However, that falls down given that we have a lot of
bitfields and the macros to
