On Sat, Oct 20, 2012 at 12:48 AM, telenn barz <telenn.barz@xxxxxxxxx> wrote:
Hello Arun,
Thanks for answering.On Fri, Oct 19, 2012 at 3:33 PM, Arun KS <getarunks@xxxxxxxxx> wrote:
On Fri, Oct 19, 2012 at 3:03 PM, telenn barz <telenn.barz@xxxxxxxxx> wrote:
Q: In the 4G/4G split case, I don't see why we have to necessarily flush the TLB when switching from user-space to kernel-space ? Why the TLB couldn't be shared across one user-space to kernel-space switch, and be flushed only every two switches ?
In 4G/4G split, kernel space(KS) and user space(US) both have 4GB address space. So there can be a same virtual address present in KS & US which corresponds to two different physical addressess.
When switching from US to KS or vice versa, the pointer to page table has to be changed in the MMU. So TLB which is just a cache for the page tables has to be flushed aswell.Yes you're right.
So considering the traditional 3G/1G split, another question is why the kernel restricts itself to a "window" of 128MB on high memory. Can we imagine rather that the kernel would simply allow itself to dynamically use some virtual pages of the 3G user-space part (while changing their access rights of course) ?
128MB of kernel linear address space is for mapping high mem pages. This is a temporary mapping, you have to unmap this 128MB to map another 128MB.
AFAIK you can change this configuration by changing your lowmem area, vmalloc area and device io memory area which are mapped to the kernel virtual space.
Thanks,
Arun
AFAIK you can change this configuration by changing your lowmem area, vmalloc area and device io memory area which are mapped to the kernel virtual space.
Thanks,
Arun
Thanks,
Telenn
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
