From: Gustavo Romero <gromero@linux.vnet.ibm.com>
To: David Gibson <david@gibson.dropbear.id.au>,
Richard Henderson <richard.henderson@linaro.org>
Cc: peter.maydell@linaro.org, Gustavo Romero <gromero@linux.ibm.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org, clg@kaod.org
Subject: Re: [PATCH v2] target/ppc: Integrate icount to purr, vtb, and tbu40
Date: Wed, 12 Aug 2020 23:42:34 -0300 [thread overview]
Message-ID: <5d05adf7-a6d0-7f15-5a69-9226a8b9646c@linux.vnet.ibm.com> (raw)
In-Reply-To: <20200813000321.GA17532@yekko.fritz.box>
On 8/12/20 9:03 PM, David Gibson wrote:
> On Wed, Aug 12, 2020 at 02:33:33PM -0700, Richard Henderson wrote:
>> On 8/11/20 8:32 AM, Gustavo Romero wrote:
>>> Currently if option '-icount auto' is passed to the QEMU TCG to enable
>>> counting instructions the VM crashes with the following error report when
>>> Linux runs on it:
>>>
>>> qemu-system-ppc64: Bad icount read
>>>
>>> This happens because read/write access to the SPRs PURR, VTB, and TBU40
>>> is not integrated to the icount framework.
>>>
>>> This commit fixes that issue by making the read/write access of these
>>> SPRs aware of icount framework, adding the proper gen_io_start() calls
>>> before calling the helpers to load/store these SPRs in TCG and ensuring
>>> that the associated TBs end immediately after, accordingly to what's in
>>> docs/devel/tcg-icount.rst.
>>>
>>> Signed-off-by: Gustavo Romero <gromero@linux.ibm.com>
>>> ---
>>> target/ppc/translate_init.inc.c | 30 ++++++++++++++++++++++++++++++
>>> 1 file changed, 30 insertions(+)
>>
>> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
>
> Applied to ppc-for-5.2, thanks.
Thanks Peter, Richard and David.
Best regards,
Gustavo
prev parent reply other threads:[~2020-08-13 2:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 15:32 [PATCH v2] target/ppc: Integrate icount to purr, vtb, and tbu40 Gustavo Romero
2020-08-12 21:33 ` Richard Henderson
2020-08-13 0:03 ` David Gibson
2020-08-13 2:42 ` Gustavo Romero [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=5d05adf7-a6d0-7f15-5a69-9226a8b9646c@linux.vnet.ibm.com \
--to=gromero@linux.vnet.ibm.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=gromero@linux.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=richard.henderson@linaro.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).