From: Richard Henderson <richard.henderson@linaro.org>
To: "Victor Kamensky (kamensky)" <kamensky@cisco.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Richard Henderson" <rth@twiddle.net>
Cc: Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>,
Khem Raj <raj.khem@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [RFC PATCH 0/3] target/mips: Make the number of TLB entries a CPU property
Date: Fri, 16 Oct 2020 10:19:00 -0700 [thread overview]
Message-ID: <570801b3-ce5a-682a-334d-73404e418f3d@linaro.org> (raw)
In-Reply-To: <BYAPR11MB30471A05FF44CF5F7C4C9A29CD020@BYAPR11MB3047.namprd11.prod.outlook.com>
On 10/15/20 11:56 AM, Victor Kamensky (kamensky) via wrote:
> Is possible to come back to 34Kf route, doing
> very small localized very well defined change
> of bumping TLBs number for model that we know
> works well for us?
Yes, thanks for testing.
I think we should also add a property to enable Config3.PM for any cpu, and see
how that gets on. But simply adjusting the number of tlb entries is a good
start, and is the only thing that will work for older kernels.
r~
prev parent reply other threads:[~2020-10-16 17:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 13:25 [RFC PATCH 0/3] target/mips: Make the number of TLB entries a CPU property Philippe Mathieu-Daudé
2020-10-13 13:25 ` [RFC PATCH 1/3] target/mips: Make cpu_mips_realize_env() propagate Error Philippe Mathieu-Daudé
2020-10-13 13:25 ` [RFC PATCH 2/3] target/mips: Store number of TLB entries in CPUMIPSState Philippe Mathieu-Daudé
2020-10-13 13:25 ` [RFC PATCH 3/3] target/mips: Make the number of TLB entries a CPU property Philippe Mathieu-Daudé
2020-10-14 10:20 ` Jiaxun Yang
2020-10-14 10:54 ` Philippe Mathieu-Daudé
2020-10-13 23:11 ` [RFC PATCH 0/3] " Richard Henderson
2020-10-14 2:22 ` Richard Henderson
2020-10-14 3:21 ` Victor Kamensky (kamensky) via
2020-10-14 7:26 ` Richard Purdie
2020-10-14 1:36 ` Victor Kamensky (kamensky)
2020-10-14 7:14 ` Richard Purdie
2020-10-14 14:53 ` Philippe Mathieu-Daudé
2020-10-14 20:20 ` Victor Kamensky (kamensky) via
2020-10-14 20:53 ` Khem Raj
2020-10-15 18:56 ` Victor Kamensky (kamensky) via
2020-10-16 17:19 ` Richard Henderson [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=570801b3-ce5a-682a-334d-73404e418f3d@linaro.org \
--to=richard.henderson@linaro.org \
--cc=aleksandar.qemu.devel@gmail.com \
--cc=aleksandar.rikalo@syrmia.com \
--cc=aurelien@aurel32.net \
--cc=f4bug@amsat.org \
--cc=kamensky@cisco.com \
--cc=qemu-devel@nongnu.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=rth@twiddle.net \
/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).