Re: [RESEND PATCH] x86/mm: only allow memmap=XX!YY over existing RAM

2016-06-29 Thread Dan Williams
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,

Re: [RESEND PATCH] x86/mm: only allow memmap=XX!YY over existing RAM

2016-06-29 Thread Dan Williams
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

Re: [RESEND PATCH] x86/mm: only allow memmap=XX!YY over existing RAM

2016-06-28 Thread Yigal Korman
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

Re: [RESEND PATCH] x86/mm: only allow memmap=XX!YY over existing RAM

2016-06-28 Thread Yigal Korman
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 > >>>

Re: [RESEND PATCH] x86/mm: only allow memmap=XX!YY over existing RAM

2016-06-28 Thread Dan Williams
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

Re: [RESEND PATCH] x86/mm: only allow memmap=XX!YY over existing RAM

2016-06-28 Thread Dan Williams
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

Re: [RESEND PATCH] x86/mm: only allow memmap=XX!YY over existing RAM

2016-06-28 Thread H. Peter Anvin
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

Re: [RESEND PATCH] x86/mm: only allow memmap=XX!YY over existing RAM

2016-06-28 Thread H. Peter Anvin
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

Re: [RESEND PATCH] x86/mm: only allow memmap=XX!YY over existing RAM

2016-06-28 Thread Dan Williams
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.

Re: [RESEND PATCH] x86/mm: only allow memmap=XX!YY over existing RAM

2016-06-28 Thread Dan Williams
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