From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: linux-mm@kvack.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH 1/2] mm: add architecture primitives for software dirty bit clearing
Date: Mon, 21 Sep 2015 22:48:54 +0300 [thread overview]
Message-ID: <20150921194854.GD3181@uranus> (raw)
In-Reply-To: <1442848940-22108-2-git-send-email-schwidefsky@de.ibm.com>
On Mon, Sep 21, 2015 at 05:22:19PM +0200, Martin Schwidefsky wrote:
> There are primitives to create and query the software dirty bits
> in a pte or pmd. But the clearing of the software dirty bits is done
> in common code with x86 specific page table functions.
>
> Add the missing architecture primitives to clear the software dirty
> bits to allow the feature to be used on non-x86 systems, e.g. the
> s390 architecture.
>
> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Looks good to me. Thank you, Martin!
(I cant ack s390 part 'casuse I simply not familiar
with the architecture).
Acked-by: Cyrill Gorcunov <gorcunov@openvz.org>
--
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-09-21 19:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 15:22 [PATCH 0/2] mm: soft-dirty bits for s390 Martin Schwidefsky
2015-09-21 15:22 ` [PATCH 1/2] mm: add architecture primitives for software dirty bit clearing Martin Schwidefsky
2015-09-21 19:48 ` Cyrill Gorcunov [this message]
2015-09-22 7:35 ` Martin Schwidefsky
2015-09-22 9:09 ` Cyrill Gorcunov
2015-09-22 10:30 ` Martin Schwidefsky
2015-09-21 15:22 ` [PATCH 2/2] s390/mm: implement soft-dirty bits for user memory change tracking Martin Schwidefsky
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=20150921194854.GD3181@uranus \
--to=gorcunov@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=schwidefsky@de.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).