On Wed, Jan 22, 2014 at 02:09:33PM +0100, Ingo Molnar wrote:
>
> * Peter Zijlstra wrote:
>
> > On Wed, Jan 22, 2014 at 01:09:17PM +0100, Ingo Molnar wrote:
> > >
> > > * Peter Zijlstra wrote:
> > >
> > > > On Tue, Jan 21, 2014 at 04:31:56PM -0800, Linus Torvalds wrote:
> > > > > And if
On Wed, Jan 22, 2014 at 02:09:33PM +0100, Ingo Molnar wrote:
* Peter Zijlstra pet...@infradead.org wrote:
On Wed, Jan 22, 2014 at 01:09:17PM +0100, Ingo Molnar wrote:
* Peter Zijlstra pet...@infradead.org wrote:
On Tue, Jan 21, 2014 at 04:31:56PM -0800, Linus Torvalds wrote:
* Peter Zijlstra wrote:
> On Wed, Jan 22, 2014 at 01:09:17PM +0100, Ingo Molnar wrote:
> >
> > * Peter Zijlstra wrote:
> >
> > > On Tue, Jan 21, 2014 at 04:31:56PM -0800, Linus Torvalds wrote:
> > > > And if somebody tries to do a "smp_store_release()" on a random
> > > > structure or union,
On Wed, Jan 22, 2014 at 01:09:17PM +0100, Ingo Molnar wrote:
>
> * Peter Zijlstra wrote:
>
> > On Tue, Jan 21, 2014 at 04:31:56PM -0800, Linus Torvalds wrote:
> > > And if somebody tries to do a "smp_store_release()" on a random
> > > structure or union, do we care? We're not some nanny state
* Peter Zijlstra wrote:
> On Tue, Jan 21, 2014 at 04:31:56PM -0800, Linus Torvalds wrote:
> > And if somebody tries to do a "smp_store_release()" on a random
> > structure or union, do we care? We're not some nanny state that wants
> > to give nice warnings for insane code.
>
> Hurm, and here
On Tue, Jan 21, 2014 at 04:31:56PM -0800, Linus Torvalds wrote:
> And if somebody tries to do a "smp_store_release()" on a random
> structure or union, do we care? We're not some nanny state that wants
> to give nice warnings for insane code.
Hurm, and here I thought warning on insane code was a
On Tue, Jan 21, 2014 at 04:31:56PM -0800, Linus Torvalds wrote:
And if somebody tries to do a smp_store_release() on a random
structure or union, do we care? We're not some nanny state that wants
to give nice warnings for insane code.
Hurm, and here I thought warning on insane code was a good
* Peter Zijlstra pet...@infradead.org wrote:
On Tue, Jan 21, 2014 at 04:31:56PM -0800, Linus Torvalds wrote:
And if somebody tries to do a smp_store_release() on a random
structure or union, do we care? We're not some nanny state that wants
to give nice warnings for insane code.
Hurm,
On Wed, Jan 22, 2014 at 01:09:17PM +0100, Ingo Molnar wrote:
* Peter Zijlstra pet...@infradead.org wrote:
On Tue, Jan 21, 2014 at 04:31:56PM -0800, Linus Torvalds wrote:
And if somebody tries to do a smp_store_release() on a random
structure or union, do we care? We're not some nanny
* Peter Zijlstra pet...@infradead.org wrote:
On Wed, Jan 22, 2014 at 01:09:17PM +0100, Ingo Molnar wrote:
* Peter Zijlstra pet...@infradead.org wrote:
On Tue, Jan 21, 2014 at 04:31:56PM -0800, Linus Torvalds wrote:
And if somebody tries to do a smp_store_release() on a random
On 01/21/2014 07:31 PM, Linus Torvalds wrote:
On Tue, Jan 21, 2014 at 8:09 AM, Waiman Long wrote:
include/linux/compiler.h:
#ifndef __native_word
# ifdef __arch_native_word(t)
# define __native_word(t) __arch_native_word(t)
# else
# define __native_word(t) (sizeof(t) == sizeof(int) ||
On Tue, Jan 21, 2014 at 8:09 AM, Waiman Long wrote:
>
> include/linux/compiler.h:
>
> #ifndef __native_word
> # ifdef __arch_native_word(t)
> # define __native_word(t) __arch_native_word(t)
> # else
> # define __native_word(t) (sizeof(t) == sizeof(int) || sizeof(t) ==
> siizeof(long))
> #
On 01/21/2014 10:39 AM, Peter Zijlstra wrote:
On Tue, Jan 21, 2014 at 10:36:48AM -0500, Waiman Long wrote:
On 01/20/2014 10:03 AM, Peter Zijlstra wrote:
On Tue, Jan 14, 2014 at 11:44:05PM -0500, Waiman Long wrote:
The generic __native_word() macro defined in include/linux/compiler.h
only
On Tue, Jan 21, 2014 at 10:36:48AM -0500, Waiman Long wrote:
> On 01/20/2014 10:03 AM, Peter Zijlstra wrote:
> >On Tue, Jan 14, 2014 at 11:44:05PM -0500, Waiman Long wrote:
> >>The generic __native_word() macro defined in include/linux/compiler.h
> >>only allows "int" and "long" data types to be
On 01/20/2014 10:03 AM, Peter Zijlstra wrote:
On Tue, Jan 14, 2014 at 11:44:05PM -0500, Waiman Long wrote:
The generic __native_word() macro defined in include/linux/compiler.h
only allows "int" and "long" data types to be treated as native and
atomic. The x86 architecture, however, allow the
On 01/20/2014 10:03 AM, Peter Zijlstra wrote:
On Tue, Jan 14, 2014 at 11:44:05PM -0500, Waiman Long wrote:
The generic __native_word() macro defined in include/linux/compiler.h
only allows int and long data types to be treated as native and
atomic. The x86 architecture, however, allow the use
On Tue, Jan 21, 2014 at 10:36:48AM -0500, Waiman Long wrote:
On 01/20/2014 10:03 AM, Peter Zijlstra wrote:
On Tue, Jan 14, 2014 at 11:44:05PM -0500, Waiman Long wrote:
The generic __native_word() macro defined in include/linux/compiler.h
only allows int and long data types to be treated as
On 01/21/2014 10:39 AM, Peter Zijlstra wrote:
On Tue, Jan 21, 2014 at 10:36:48AM -0500, Waiman Long wrote:
On 01/20/2014 10:03 AM, Peter Zijlstra wrote:
On Tue, Jan 14, 2014 at 11:44:05PM -0500, Waiman Long wrote:
The generic __native_word() macro defined in include/linux/compiler.h
only
On Tue, Jan 21, 2014 at 8:09 AM, Waiman Long waiman.l...@hp.com wrote:
include/linux/compiler.h:
#ifndef __native_word
# ifdef __arch_native_word(t)
# define __native_word(t) __arch_native_word(t)
# else
# define __native_word(t) (sizeof(t) == sizeof(int) || sizeof(t) ==
On 01/21/2014 07:31 PM, Linus Torvalds wrote:
On Tue, Jan 21, 2014 at 8:09 AM, Waiman Longwaiman.l...@hp.com wrote:
include/linux/compiler.h:
#ifndef __native_word
# ifdef __arch_native_word(t)
# define __native_word(t) __arch_native_word(t)
# else
# define __native_word(t) (sizeof(t)
On Tue, Jan 14, 2014 at 11:44:05PM -0500, Waiman Long wrote:
> The generic __native_word() macro defined in include/linux/compiler.h
> only allows "int" and "long" data types to be treated as native and
> atomic. The x86 architecture, however, allow the use of char and short
> data types as atomic
On Tue, Jan 14, 2014 at 11:44:05PM -0500, Waiman Long wrote:
The generic __native_word() macro defined in include/linux/compiler.h
only allows int and long data types to be treated as native and
atomic. The x86 architecture, however, allow the use of char and short
data types as atomic as
The generic __native_word() macro defined in include/linux/compiler.h
only allows "int" and "long" data types to be treated as native and
atomic. The x86 architecture, however, allow the use of char and short
data types as atomic as well.
This patch extends the data type allowed in the
The generic __native_word() macro defined in include/linux/compiler.h
only allows int and long data types to be treated as native and
atomic. The x86 architecture, however, allow the use of char and short
data types as atomic as well.
This patch extends the data type allowed in the
24 matches
Mail list logo
