On Tue, Jun 28, 2016 at 10:12 PM, Yigal Korman wrote:
> On Wed, Jun 29, 2016 at 4:09 AM, Dan Williams
> wrote:
>>
>> On Tue, Jun 28, 2016 at 10:58 AM, H. Peter Anvin wrote:
>> > On 06/28/16 09:33, Dan Williams wrote:
>> >> On Tue,
On Tue, Jun 28, 2016 at 10:12 PM, Yigal Korman wrote:
> On Wed, Jun 29, 2016 at 4:09 AM, Dan Williams
> wrote:
>>
>> On Tue, Jun 28, 2016 at 10:58 AM, H. Peter Anvin wrote:
>> > On 06/28/16 09:33, Dan Williams wrote:
>> >> On Tue, Jun 28, 2016 at 1:31 AM, Yigal Korman wrote:
>> >>> Before
On Wed, Jun 29, 2016 at 4:09 AM, Dan Williams wrote:
>
> On Tue, Jun 28, 2016 at 10:58 AM, H. Peter Anvin wrote:
> > On 06/28/16 09:33, Dan Williams wrote:
> >> On Tue, Jun 28, 2016 at 1:31 AM, Yigal Korman wrote:
> >>> Before this
On Wed, Jun 29, 2016 at 4:09 AM, Dan Williams wrote:
>
> On Tue, Jun 28, 2016 at 10:58 AM, H. Peter Anvin wrote:
> > On 06/28/16 09:33, Dan Williams wrote:
> >> On Tue, Jun 28, 2016 at 1:31 AM, Yigal Korman wrote:
> >>> Before this patch, passing a range that is beyond the physical memory
> >>>
On Tue, Jun 28, 2016 at 10:58 AM, H. Peter Anvin wrote:
> On 06/28/16 09:33, Dan Williams wrote:
>> On Tue, Jun 28, 2016 at 1:31 AM, Yigal Korman wrote:
>>> Before this patch, passing a range that is beyond the physical memory
>>> range will succeed, the user
On Tue, Jun 28, 2016 at 10:58 AM, H. Peter Anvin wrote:
> On 06/28/16 09:33, Dan Williams wrote:
>> On Tue, Jun 28, 2016 at 1:31 AM, Yigal Korman wrote:
>>> Before this patch, passing a range that is beyond the physical memory
>>> range will succeed, the user will see a /dev/pmem0 and will be
On 06/28/16 09:33, Dan Williams wrote:
> On Tue, Jun 28, 2016 at 1:31 AM, Yigal Korman wrote:
>> Before this patch, passing a range that is beyond the physical memory
>> range will succeed, the user will see a /dev/pmem0 and will be able to
>> access it. Reads will always
On 06/28/16 09:33, Dan Williams wrote:
> On Tue, Jun 28, 2016 at 1:31 AM, Yigal Korman wrote:
>> Before this patch, passing a range that is beyond the physical memory
>> range will succeed, the user will see a /dev/pmem0 and will be able to
>> access it. Reads will always return 0 and writes will
On Tue, Jun 28, 2016 at 1:31 AM, Yigal Korman wrote:
> Before this patch, passing a range that is beyond the physical memory
> range will succeed, the user will see a /dev/pmem0 and will be able to
> access it. Reads will always return 0 and writes will be silently
> ignored.
On Tue, Jun 28, 2016 at 1:31 AM, Yigal Korman wrote:
> Before this patch, passing a range that is beyond the physical memory
> range will succeed, the user will see a /dev/pmem0 and will be able to
> access it. Reads will always return 0 and writes will be silently
> ignored.
>
> I've gotten more
10 matches
Mail list logo