[PATCH 13/19] x86, mpx: Add temporary variable to reduce masking

2015-06-07 Thread Dave Hansen
From: Dave Hansen When we allocate a bounds table, we call mmap(), then add a "valid" bit to the value before storing it in to the bounds directory. If we fail along the way, we go and mask that valid bit _back_ out. That seems a little silly, and this makes it much more clear when we have a

[PATCH 13/19] x86, mpx: Add temporary variable to reduce masking

2015-06-07 Thread Dave Hansen
From: Dave Hansen dave.han...@linux.intel.com When we allocate a bounds table, we call mmap(), then add a valid bit to the value before storing it in to the bounds directory. If we fail along the way, we go and mask that valid bit _back_ out. That seems a little silly, and this makes it much

[PATCH 13/19] x86, mpx: Add temporary variable to reduce masking

2015-05-27 Thread Dave Hansen
From: Dave Hansen When we allocate a bounds table, we call mmap(), then add a "valid" bit to the value before storing it in to the bounds directory. If we fail along the way, we go and mask that valid bit _back_ out. That seems a little silly, and this makes it much more clear when we have a

[PATCH 13/19] x86, mpx: Add temporary variable to reduce masking

2015-05-27 Thread Dave Hansen
From: Dave Hansen dave.han...@linux.intel.com When we allocate a bounds table, we call mmap(), then add a valid bit to the value before storing it in to the bounds directory. If we fail along the way, we go and mask that valid bit _back_ out. That seems a little silly, and this makes it much

[PATCH 13/19] x86, mpx: Add temporary variable to reduce masking

2015-05-19 Thread Dave Hansen
From: Dave Hansen When we allocate a bounds table, we call mmap(), then add a "valid" bit to the value before storing it in to the bounds directory. If we fail along the way, we go and mask that valid bit _back_ out. That seems a little silly, and this makes it much more clear when we have a

[PATCH 13/19] x86, mpx: Add temporary variable to reduce masking

2015-05-19 Thread Dave Hansen
From: Dave Hansen dave.han...@linux.intel.com When we allocate a bounds table, we call mmap(), then add a valid bit to the value before storing it in to the bounds directory. If we fail along the way, we go and mask that valid bit _back_ out. That seems a little silly, and this makes it much

Re: [PATCH 13/19] x86, mpx: Add temporary variable to reduce masking

2015-05-18 Thread Thomas Gleixner
On Fri, 8 May 2015, Dave Hansen wrote: > When we allocate a bounds table, we call mmap(), then add a > "valid" bit to the value before storing it in to the bounds > directory. > > If we fail along the way, we go and mask that valid bit > _back_ out. That seems a little silly, and this makes it >

Re: [PATCH 13/19] x86, mpx: Add temporary variable to reduce masking

2015-05-18 Thread Thomas Gleixner
On Fri, 8 May 2015, Dave Hansen wrote: When we allocate a bounds table, we call mmap(), then add a valid bit to the value before storing it in to the bounds directory. If we fail along the way, we go and mask that valid bit _back_ out. That seems a little silly, and this makes it much

[PATCH 13/19] x86, mpx: Add temporary variable to reduce masking

2015-05-08 Thread Dave Hansen
From: Dave Hansen When we allocate a bounds table, we call mmap(), then add a "valid" bit to the value before storing it in to the bounds directory. If we fail along the way, we go and mask that valid bit _back_ out. That seems a little silly, and this makes it much more clear when we have a

[PATCH 13/19] x86, mpx: Add temporary variable to reduce masking

2015-05-08 Thread Dave Hansen
From: Dave Hansen dave.han...@linux.intel.com When we allocate a bounds table, we call mmap(), then add a valid bit to the value before storing it in to the bounds directory. If we fail along the way, we go and mask that valid bit _back_ out. That seems a little silly, and this makes it much