Scott Wood writes:
> On Wed, 2015-06-17 at 19:45 +1000, Michael Ellerman wrote:
>> On Wed, 2015-06-17 at 08:21 +0530, Aneesh Kumar K.V wrote:
>> > "Aneesh Kumar K.V" writes:
>> >
>> >
>> > Hi Scott,
>> >
>> > > Current swap encoding in pte can't support large pfns
>> > > above 4TB. Change the
On Wed, 2015-06-17 at 16:14 -0500, Scott Wood wrote:
> On Wed, 2015-06-17 at 19:45 +1000, Michael Ellerman wrote:
> > On Wed, 2015-06-17 at 08:21 +0530, Aneesh Kumar K.V wrote:
> > > "Aneesh Kumar K.V" writes:
> > >
> > >
> > > Hi Scott,
> > >
> > > > Current swap encoding in pte can't support
On Wed, 2015-06-17 at 19:45 +1000, Michael Ellerman wrote:
> On Wed, 2015-06-17 at 08:21 +0530, Aneesh Kumar K.V wrote:
> > "Aneesh Kumar K.V" writes:
> >
> >
> > Hi Scott,
> >
> > > Current swap encoding in pte can't support large pfns
> > > above 4TB. Change the swap encoding such that we put
On Wed, 2015-06-17 at 08:21 +0530, Aneesh Kumar K.V wrote:
> "Aneesh Kumar K.V" writes:
>
>
> Hi Scott,
>
> > Current swap encoding in pte can't support large pfns
> > above 4TB. Change the swap encoding such that we put
> > the swap type in the PTE bits. Also add build checks
> > to make sure
"Aneesh Kumar K.V" writes:
Hi Scott,
> Current swap encoding in pte can't support large pfns
> above 4TB. Change the swap encoding such that we put
> the swap type in the PTE bits. Also add build checks
> to make sure we don't overlap with HPTEFLAGS.
>
Can you please review this w.r.t 64bit bo
