From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Laurent Dufour <ldufour@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
xemul@parallels.com, linuxppc-dev@lists.ozlabs.org,
mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org,
criu@openvz.org
Subject: Re: [PATCH 0/3] mm/powerpc: enabling memory soft dirty tracking
Date: Sat, 17 Oct 2015 17:37:44 +0530 [thread overview]
Message-ID: <87io65itpr.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20151016141129.8b014c6d882c475fafe577a9@linux-foundation.org>
Andrew Morton <akpm@linux-foundation.org> writes:
> On Fri, 16 Oct 2015 14:07:05 +0200 Laurent Dufour <ldufour@linux.vnet.ibm.com> wrote:
>
>> This series is enabling the software memory dirty tracking in the
>> kernel for powerpc. This is the follow up of the commit 0f8975ec4db2
>> ("mm: soft-dirty bits for user memory changes tracking") which
>> introduced this feature in the mm code.
>>
>> The first patch is fixing an issue in the code clearing the soft dirty
>> bit. The PTE were not cleared before being modified, leading to hang
>> on ppc64.
>>
>> The second patch is fixing a build issue when the transparent huge
>> page is not enabled.
>>
>> The third patch is introducing the soft dirty tracking in the powerpc
>> architecture code.
>
> I grabbed these patches, but they're more a ppc thing than a core
> kernel thing. I can merge them into 4.3 with suitable acks or drop
> them if they turn up in the powerpc tree. Or something else?
patch 1 and patch 2 are fixes for generic code. That can go via -mm
tree. The ppc64 bits should go via linux-powerpc tree. We have changes
in this area pending to be merged upstream and patch 3 will result
in conflicts.
-aneesh
WARNING: multiple messages have this Message-ID (diff)
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Laurent Dufour <ldufour@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
xemul@parallels.com, linuxppc-dev@lists.ozlabs.org,
mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org,
criu@openvz.org
Subject: Re: [PATCH 0/3] mm/powerpc: enabling memory soft dirty tracking
Date: Sat, 17 Oct 2015 17:37:44 +0530 [thread overview]
Message-ID: <87io65itpr.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20151016141129.8b014c6d882c475fafe577a9@linux-foundation.org>
Andrew Morton <akpm@linux-foundation.org> writes:
> On Fri, 16 Oct 2015 14:07:05 +0200 Laurent Dufour <ldufour@linux.vnet.ibm.com> wrote:
>
>> This series is enabling the software memory dirty tracking in the
>> kernel for powerpc. This is the follow up of the commit 0f8975ec4db2
>> ("mm: soft-dirty bits for user memory changes tracking") which
>> introduced this feature in the mm code.
>>
>> The first patch is fixing an issue in the code clearing the soft dirty
>> bit. The PTE were not cleared before being modified, leading to hang
>> on ppc64.
>>
>> The second patch is fixing a build issue when the transparent huge
>> page is not enabled.
>>
>> The third patch is introducing the soft dirty tracking in the powerpc
>> architecture code.
>
> I grabbed these patches, but they're more a ppc thing than a core
> kernel thing. I can merge them into 4.3 with suitable acks or drop
> them if they turn up in the powerpc tree. Or something else?
patch 1 and patch 2 are fixes for generic code. That can go via -mm
tree. The ppc64 bits should go via linux-powerpc tree. We have changes
in this area pending to be merged upstream and patch 3 will result
in conflicts.
-aneesh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-10-17 12:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 12:07 [PATCH 0/3] mm/powerpc: enabling memory soft dirty tracking Laurent Dufour
2015-10-16 12:07 ` Laurent Dufour
2015-10-16 12:07 ` [PATCH 1/3] mm: clearing pte in clear_soft_dirty() Laurent Dufour
2015-10-16 12:07 ` Laurent Dufour
2015-10-16 15:00 ` Benjamin Herrenschmidt
2015-10-16 15:00 ` Benjamin Herrenschmidt
2015-10-17 12:12 ` Aneesh Kumar K.V
2015-10-17 12:12 ` Aneesh Kumar K.V
2015-10-16 12:07 ` [PATCH 2/3] mm: clear_soft_dirty_pmd requires THP Laurent Dufour
2015-10-16 12:07 ` Laurent Dufour
2015-10-17 12:14 ` Aneesh Kumar K.V
2015-10-17 12:14 ` Aneesh Kumar K.V
2015-10-16 12:07 ` [PATCH 3/3] powerpc/mm: Add page soft dirty tracking Laurent Dufour
2015-10-16 12:07 ` Laurent Dufour
2015-10-17 12:19 ` Aneesh Kumar K.V
2015-10-17 12:19 ` Aneesh Kumar K.V
2015-10-17 13:24 ` Benjamin Herrenschmidt
2015-10-17 13:24 ` Benjamin Herrenschmidt
2015-10-16 21:11 ` [PATCH 0/3] mm/powerpc: enabling memory " Andrew Morton
2015-10-16 21:11 ` Andrew Morton
2015-10-17 2:15 ` Benjamin Herrenschmidt
2015-10-17 2:15 ` Benjamin Herrenschmidt
2015-10-17 12:07 ` Aneesh Kumar K.V [this message]
2015-10-17 12:07 ` Aneesh Kumar K.V
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87io65itpr.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=criu@openvz.org \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=xemul@parallels.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.