From: James Hogan <james.hogan@imgtec.com> To: Ralf Baechle <ralf@linux-mips.org> Cc: Manuel Lauss <manuel.lauss@gmail.com>, James Hogan <james.hogan@imgtec.com>, Leonid Yegoshin <leonid.yegoshin@imgtec.com>, <linux-mips@linux-mips.org> Subject: [PATCH 0/2] MIPS: I6400: Avoid dcache flushes Date: Fri, 22 Jan 2016 10:58:24 +0000 [thread overview] Message-ID: <1453460306-8505-1-git-send-email-james.hogan@imgtec.com> (raw) These patches allow I6400 core to avoid dcache flushes when making recently modified data available to icache. I6400 effectively can fill icache from dirty dcache contents, which means cpu_has_ic_fills_f_dc can evaluate to true (see patch 2). However there are a couple of bugs in the cache handling when cpu_has_ic_fills_f_dc, which need fixing first (see patch 1). That the CPU fills icache from dcache does not imply that the icache is coherent with dcache. Stale lines still need flushing from the icache, even if lines in the dcache don't need writing back first. James Hogan (2): MIPS: c-r4k: Sync icache when it fills from dcache MIPS: I6400: Icache fills from dcache arch/mips/mm/c-r4k.c | 12 ++++++++++-- arch/mips/mm/init.c | 2 +- 2 files changed, 11 insertions(+), 3 deletions(-) Cc: Ralf Baechle <ralf@linux-mips.org> Cc: Leonid Yegoshin <leonid.yegoshin@imgtec.com> Cc: Manuel Lauss <manuel.lauss@gmail.com> Cc: linux-mips@linux-mips.org -- 2.4.10
WARNING: multiple messages have this Message-ID (diff)
From: James Hogan <james.hogan@imgtec.com> To: Ralf Baechle <ralf@linux-mips.org> Cc: Manuel Lauss <manuel.lauss@gmail.com>, James Hogan <james.hogan@imgtec.com>, Leonid Yegoshin <leonid.yegoshin@imgtec.com>, linux-mips@linux-mips.org Subject: [PATCH 0/2] MIPS: I6400: Avoid dcache flushes Date: Fri, 22 Jan 2016 10:58:24 +0000 [thread overview] Message-ID: <1453460306-8505-1-git-send-email-james.hogan@imgtec.com> (raw) Message-ID: <20160122105824.Zqr3qe-eyK6cL1Fur0KO5UC2QsbIrUes75Yvmm9Agcg@z> (raw) These patches allow I6400 core to avoid dcache flushes when making recently modified data available to icache. I6400 effectively can fill icache from dirty dcache contents, which means cpu_has_ic_fills_f_dc can evaluate to true (see patch 2). However there are a couple of bugs in the cache handling when cpu_has_ic_fills_f_dc, which need fixing first (see patch 1). That the CPU fills icache from dcache does not imply that the icache is coherent with dcache. Stale lines still need flushing from the icache, even if lines in the dcache don't need writing back first. James Hogan (2): MIPS: c-r4k: Sync icache when it fills from dcache MIPS: I6400: Icache fills from dcache arch/mips/mm/c-r4k.c | 12 ++++++++++-- arch/mips/mm/init.c | 2 +- 2 files changed, 11 insertions(+), 3 deletions(-) Cc: Ralf Baechle <ralf@linux-mips.org> Cc: Leonid Yegoshin <leonid.yegoshin@imgtec.com> Cc: Manuel Lauss <manuel.lauss@gmail.com> Cc: linux-mips@linux-mips.org -- 2.4.10
next reply other threads:[~2016-01-22 10:58 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-01-22 10:58 James Hogan [this message] 2016-01-22 10:58 ` [PATCH 0/2] MIPS: I6400: Avoid dcache flushes James Hogan 2016-01-22 10:58 ` [PATCH 1/2] MIPS: c-r4k: Sync icache when it fills from dcache James Hogan 2016-01-22 10:58 ` James Hogan 2016-01-22 12:06 ` Manuel Lauss 2016-01-22 12:19 ` James Hogan 2016-01-22 13:05 ` Joshua Kinard 2016-01-22 13:54 ` James Hogan 2016-01-22 14:03 ` Ralf Baechle 2016-01-22 14:30 ` Manuel Lauss 2016-01-22 15:02 ` James Hogan 2016-01-22 15:55 ` Manuel Lauss 2016-01-22 10:58 ` [PATCH 2/2] MIPS: I6400: Icache " James Hogan 2016-01-22 10:58 ` James Hogan
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=1453460306-8505-1-git-send-email-james.hogan@imgtec.com \ --to=james.hogan@imgtec.com \ --cc=leonid.yegoshin@imgtec.com \ --cc=linux-mips@linux-mips.org \ --cc=manuel.lauss@gmail.com \ --cc=ralf@linux-mips.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: linkBe 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.