On Tue, 14 Mar 2017, Chris Metcalf wrote:
> On 3/14/2017 12:12 PM, Till Smejkal wrote:
> > On Mon, 13 Mar 2017, Andy Lutomirski wrote:
> > > On Mon, Mar 13, 2017 at 7:07 PM, Till Smejkal
> > > wrote:
> > > > On Mon, 13 Mar 2017, Andy Lutomirski wrote:
> > > > > This
On Mon, 13 Mar 2017, Andy Lutomirski wrote:
> On Mon, Mar 13, 2017 at 7:07 PM, Till Smejkal
> wrote:
> > On Mon, 13 Mar 2017, Andy Lutomirski wrote:
> >> This sounds rather complicated. Getting TLB flushing right seems
> >> tricky. Why not just map the same thing
On 3/14/2017 12:12 PM, Till Smejkal wrote:
On Mon, 13 Mar 2017, Andy Lutomirski wrote:
On Mon, Mar 13, 2017 at 7:07 PM, Till Smejkal
wrote:
On Mon, 13 Mar 2017, Andy Lutomirski wrote:
This sounds rather complicated. Getting TLB flushing right seems
tricky. Why
On Tue, 14 Mar 2017, David Laight wrote:
> From: Linuxppc-dev Till Smejkal
> > Sent: 13 March 2017 22:14
> > The only way until now to create a new memory map was via the exported
> > function 'mm_alloc'. Unfortunately, this function not only allocates a new
> > memory map, but also completely
From: Linuxppc-dev Till Smejkal
> Sent: 13 March 2017 22:14
> The only way until now to create a new memory map was via the exported
> function 'mm_alloc'. Unfortunately, this function not only allocates a new
> memory map, but also completely initializes it. However, with the
> introduction of
On Mon, Mar 13, 2017 at 7:07 PM, Till Smejkal
wrote:
> On Mon, 13 Mar 2017, Andy Lutomirski wrote:
>> This sounds rather complicated. Getting TLB flushing right seems
>> tricky. Why not just map the same thing into multiple mms?
>
> This is exactly what happens at
On Mon, 13 Mar 2017, Andy Lutomirski wrote:
> On Mon, Mar 13, 2017 at 3:14 PM, Till Smejkal
> wrote:
> > This patchset extends the kernel memory management subsystem with a new
> > type of address spaces (called VAS) which can be created and destroyed
> >