From: Andrew Morton <akpm@linux-foundation.org>
To: Bibo Mao <maobibo@loongson.cn>
Cc: "Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"Huacai Chen" <chenhc@lemote.com>,
"Paul Burton" <paulburton@kernel.org>,
"Dmitry Korotin" <dkorotin@wavecomp.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Stafford Horne" <shorne@gmail.com>,
"Steven Price" <steven.price@arm.com>,
"Anshuman Khandual" <anshuman.khandual@arm.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
"Mike Rapoport" <rppt@linux.ibm.com>,
"Sergei Shtylyov" <sergei.shtylyov@cogentembedded.com>,
"Maciej W. Rozycki" <macro@wdc.com>,
linux-mm@kvack.org, "David Hildenbrand" <david@redhat.com>
Subject: Re: [PATCH v6 1/4] MIPS: Do not flush tlb page when updating PTE entry
Date: Mon, 25 May 2020 14:42:41 -0700 [thread overview]
Message-ID: <20200525144241.f0e55183a846607cdbb0d819@linux-foundation.org> (raw)
In-Reply-To: <1590375160-6997-1-git-send-email-maobibo@loongson.cn>
On Mon, 25 May 2020 10:52:37 +0800 Bibo Mao <maobibo@loongson.cn> wrote:
> It is not necessary to flush tlb page on all CPUs if suitable PTE
> entry exists already during page fault handling, just updating
> TLB is fine.
>
> Here redefine flush_tlb_fix_spurious_fault as empty on MIPS system.
>
> ...
>
> --- a/arch/mips/include/asm/pgtable.h
> +++ b/arch/mips/include/asm/pgtable.h
> @@ -478,6 +478,8 @@ static inline pgprot_t pgprot_writecombine(pgprot_t _prot)
> return __pgprot(prot);
> }
>
> +#define flush_tlb_fix_spurious_fault(vma, address) do { } while (0)
> +
static inline C would be preferred, if that works. For a number of reasons:
- looks nicer
- more likely to get a code comment (for some reason)
- adds typechecking. So right now a MIPS developer could do
struct wibble a;
struct wobble b;
flush_tlb_fix_spurious_fault(&a, &b);
and there would be no compiler warning. Then the code gets merged
upstream and in come the embarrassing emails!
- avoids unused-var warnings
foo()
{
struct address_space a;
struct vm_area_struct v;
flush_tlb_fix_spurious_fault(&v, &a);
}
will generate unused-variable warnings if
flush_tlb_fix_spurious_fault() is a macro. Making
flush_tlb_fix_spurious_fault() inlined C prevents this.
next prev parent reply other threads:[~2020-05-25 21:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 2:52 [PATCH v6 1/4] MIPS: Do not flush tlb page when updating PTE entry Bibo Mao
2020-05-25 2:52 ` [PATCH v6 2/4] mm/memory.c: Update local TLB if PTE entry exists Bibo Mao
2020-05-25 21:43 ` Andrew Morton
2020-05-25 2:52 ` [PATCH v6 3/4] mm/memory.c: Add memory read privilege on page fault handling Bibo Mao
2020-05-25 21:44 ` Andrew Morton
2020-05-27 1:05 ` maobibo
2020-05-27 7:10 ` Thomas Bogendoerfer
2020-05-25 2:52 ` [PATCH v6 4/4] MIPS: mm: add page valid judgement in function pte_modify Bibo Mao
2020-05-25 8:12 ` [PATCH v6 1/4] MIPS: Do not flush tlb page when updating PTE entry Sergei Shtylyov
2020-05-25 8:31 ` Sergei Shtylyov
2020-05-27 1:07 ` maobibo
2020-05-25 21:42 ` Andrew Morton [this message]
2020-05-27 1:06 ` maobibo
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=20200525144241.f0e55183a846607cdbb0d819@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=chenhc@lemote.com \
--cc=david@redhat.com \
--cc=dkorotin@wavecomp.com \
--cc=f4bug@amsat.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=macro@wdc.com \
--cc=maobibo@loongson.cn \
--cc=paulburton@kernel.org \
--cc=rppt@linux.ibm.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=shorne@gmail.com \
--cc=steven.price@arm.com \
--cc=tsbogend@alpha.franken.de \
/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).