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
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
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
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
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
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
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
>
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
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
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
10 matches
Mail list logo