From: Matthew Wilcox <willy@infradead.org>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH] openrisc: Call destructor during __pte_free_tlb
Date: Sun, 17 Jun 2018 15:50:46 -0700 [thread overview]
Message-ID: <20180617225046.GB21805@bombadil.infradead.org> (raw)
In-Reply-To: <20180617221243.10126-1-shorne@gmail.com>
On Mon, Jun 18, 2018 at 07:12:42AM +0900, Stafford Horne wrote:
> During the __pte_free_tlb path openrisc fails to call the page
> destructor which would clear the new bits that were introduced.
> To fix this we are calling the destructor.
>
> It seem openrisc was the only architecture missing this, all other
> architectures either call the destructor like we are doing here or use
> pte_free.
It may be worth noting that failing to call the destructor was also
messing up the zone stats (and would be causing other problems if
you were using SPLIT_PTE_PTLOCKS).
At any rate, Acked-by: Matthew Wilcox <willy@infradead.org>
prev parent reply other threads:[~2018-06-17 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 22:12 [OpenRISC] [PATCH] openrisc: Call destructor during __pte_free_tlb Stafford Horne
2018-06-17 22:50 ` Matthew Wilcox [this message]
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=20180617225046.GB21805@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=openrisc@lists.librecores.org \
/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).