From: Aneesh Kumar K.V
[ Upstream commit 4b99412ed6972cc77c1f16009e1d00323fcef9ab ]
The locking rules for walking partition scoped table is different from process
scoped table. Hence add a helper for secondary linux page table walk and also
add check whether we are holding the right locks
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Oliver O'Halloran
commit aaa229529244a1135b29353fefb001c430db79f0 upstream.
The current page table dumper scans the Linux page tables and coalesces mappings
with adjacent virtual addresses and
"Kirill A. Shutemov" writes:
> On Mon, May 11, 2015 at 11:56:01AM +0530, Aneesh Kumar K.V wrote:
>> Serialize against find_linux_pte_or_hugepte which does lock-less
>> lookup in page tables with local interrupts disabled. For huge pages
>> it casts pmd_t to pte_t. Since format of pte_t is differe
On Mon, May 11, 2015 at 11:56:01AM +0530, Aneesh Kumar K.V wrote:
> Serialize against find_linux_pte_or_hugepte which does lock-less
> lookup in page tables with local interrupts disabled. For huge pages
> it casts pmd_t to pte_t. Since format of pte_t is different from
> pmd_t we want to prevent t
; different code paths. So make sure we wait for the parallel
>> find_linux_pte_or_hugepage to finish.
>
> I'm not seeing here any description of the problem which is being
> fixed. Does the patch make the machine faster? Does the machine
> crash?
I sent v3 with updated commit message. Addi
Serialize against find_linux_pte_or_hugepte which does lock-less
lookup in page tables with local interrupts disabled. For huge pages
it casts pmd_t to pte_t. Since format of pte_t is different from
pmd_t we want to prevent transit from pmd pointing to page table
to pmd pointing to huge page (and b
On Thu, 7 May 2015 12:53:28 +0530 "Aneesh Kumar K.V"
wrote:
> Serialize against find_linux_pte_or_hugepte which does lock-less
> lookup in page tables with local interrupts disabled. For huge pages
> it casts pmd_t to pte_t. Since format of pte_t is different from
> pmd_t we want to prevent tra
Serialize against find_linux_pte_or_hugepte which does lock-less
lookup in page tables with local interrupts disabled. For huge pages
it casts pmd_t to pte_t. Since format of pte_t is different from
pmd_t we want to prevent transit from pmd pointing to page table
to pmd pointing to huge page (and b
On 09/03/2012 02:26 AM, Jiri Kosina wrote:
On Sun, 2 Sep 2012, Xin Tong wrote:
3. can two different processes have their CR3 being the same value
even though they have different first level page tables ?
Yes, if they are created by clone(CLONE_VM). In such case they share the
same mm_struct,
On Sun, 2 Sep 2012, Xin Tong wrote:
> >> 3. can two different processes have their CR3 being the same value
> >> even though they have different first level page tables ?
> >
> > Yes, if they are created by clone(CLONE_VM). In such case they share the
> > same mm_struct, and therefore mm_struct->p
On Sun, Sep 2, 2012 at 1:10 AM, Jiri Kosina wrote:
> On Sat, 1 Sep 2012, Xin Tong wrote:
>
>> When a process is created in Linux, corresponding page table is
>> implemented. In the current x86 linux, the page table is a multi-level
>> page table and CR3 points to the first level of the page table.
On Sat, 1 Sep 2012, Xin Tong wrote:
> When a process is created in Linux, corresponding page table is
> implemented. In the current x86 linux, the page table is a multi-level
> page table and CR3 points to the first level of the page table. I
> have 2 questions.
>
> 1. is the value in CR3 virtua
On Sat, Sep 1, 2012 at 1:01 PM, Shentino wrote:
> On Sat, Sep 1, 2012 at 12:30 PM, Xin Tong wrote:
>> When a process is created in Linux, corresponding page table is
>> implemented. In the current x86 linux, the page table is a multi-level
>> page table and CR3 points to the first level of the pa
On Sat, Sep 1, 2012 at 12:30 PM, Xin Tong wrote:
> When a process is created in Linux, corresponding page table is
> implemented. In the current x86 linux, the page table is a multi-level
> page table and CR3 points to the first level of the page table. I
> have 2 questions.
>
> 1. is the value i
When a process is created in Linux, corresponding page table is
implemented. In the current x86 linux, the page table is a multi-level
page table and CR3 points to the first level of the page table. I
have 2 questions.
1. is the value in CR3 virtual address or physical address ?
2. can the addres
15 matches
Mail list logo