From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-devel@nongnu.org, "Victor Kamensky" <kamensky@cisco.com>
Cc: Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>,
Khem Raj <raj.khem@gmail.com>,
Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Aurelien Jarno <aurelien@aurel32.net>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [RFC PATCH 0/3] target/mips: Make the number of TLB entries a CPU property
Date: Tue, 13 Oct 2020 16:11:56 -0700 [thread overview]
Message-ID: <7b059e2f-b868-82b3-3d96-bd4e93d36368@linaro.org> (raw)
In-Reply-To: <20201013132535.3599453-1-f4bug@amsat.org>
On 10/13/20 6:25 AM, Philippe Mathieu-Daudé wrote:
> Yocto developers have expressed interest in running MIPS32
> CPU with custom number of TLB:
> https://lists.gnu.org/archive/html/qemu-devel/2020-10/msg03428.html
>
> Help them by making the number of TLB entries a CPU property,
> keeping our set of CPU definitions in sync with real hardware.
You mean keeping the 34kf model within qemu in sync, rather than creating a
nonsense model that doesn't exist.
Question: is this cpu parameter useful for anything else?
Because the ideal solution for a CI loop is to use one of the mips cpu models
that has the hw page table walker (CP0C3_PW). Having qemu being able to refill
the tlb itself is massively faster.
We do not currently implement a mips cpu that has the PW. When I downloaded
the document set in 2014, I only got the mips64-pra and neglected to get the
mips32-pra. So I don't actually know if the PW applies to mips32. I do know
that there's nothing in the kernel that ifdefs around it.
So:
(1) anyone know if the PW incompatible with mips32?
(2) if not, was there any mips32 hw built with PW
that we could model?
(3) if not, would a cpu parameter to force-enable PW
for any r2+ cpu be more useful that frobbing the
number of tlb entries?
r~
next prev parent reply other threads:[~2020-10-13 23:13 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 ` Richard Henderson [this message]
2020-10-14 2:22 ` [RFC PATCH 0/3] " 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
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=7b059e2f-b868-82b3-3d96-bd4e93d36368@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).