From: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
To: Howard Spoelstra <hsp.cat7@gmail.com>
Cc: qemu-ppc <qemu-ppc@nongnu.org>,
Richard Henderson <richard.henderson@linaro.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH 0/4] target/ppc: Use probe_access
Date: Thu, 30 Jan 2020 17:07:17 +0100 [thread overview]
Message-ID: <CAL1e-=iG_s-hcAChaoKa8BF7e4EZ6eQR=QgUwOAAPQmEJBbu7Q@mail.gmail.com> (raw)
In-Reply-To: <CABLmASHGOGsDYo-jmqs2XCTvGbw80x1OAghx1AVTCOz2WMFKxw@mail.gmail.com>
On Thu, Jan 30, 2020 at 4:09 PM Howard Spoelstra <hsp.cat7@gmail.com> wrote:
>
> As this patch set solved the performance issue and even led to the highest scores I ever saw on the benchmark tool I used, let me add a:
>
This makes my question to Richard more important:
Are other targets exposed to performance degradation, and why?
> Tested-by: Howard Spoelstra <hsp.cat7@gmail.com>
>
> On Thu, Jan 30, 2020 at 12:50 AM Richard Henderson <richard.henderson@linaro.org> wrote:
>>
>> The first two address the performance regression noticed
>> by Howard Spoelstra. The last two are just something I
>> noticed at the same time.
>>
>>
>> r~
>>
>>
>> Richard Henderson (4):
>> target/ppc: Use probe_access for LSW, STSW
>> target/ppc: Use probe_access for LMW, STMW
>> target/ppc: Remove redundant mask in DCBZ
>> target/ppc: Use probe_write for DCBZ
>>
>> target/ppc/mem_helper.c | 197 +++++++++++++++++++++++++++++++++-------
>> 1 file changed, 162 insertions(+), 35 deletions(-)
>>
>> --
>> 2.20.1
>>
next prev parent reply other threads:[~2020-01-30 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 23:50 [PATCH 0/4] target/ppc: Use probe_access Richard Henderson
2020-01-29 23:50 ` [PATCH 1/4] target/ppc: Use probe_access for LSW, STSW Richard Henderson
2020-01-29 23:50 ` [PATCH 2/4] target/ppc: Use probe_access for LMW, STMW Richard Henderson
2020-01-29 23:50 ` [PATCH 3/4] target/ppc: Remove redundant mask in DCBZ Richard Henderson
2020-01-29 23:50 ` [PATCH 4/4] target/ppc: Use probe_write for DCBZ Richard Henderson
2020-01-30 1:35 ` [PATCH 0/4] target/ppc: Use probe_access Aleksandar Markovic
2020-01-30 16:09 ` Richard Henderson
2020-01-30 16:42 ` Aleksandar Markovic
2020-01-30 7:08 ` Howard Spoelstra
2020-01-30 15:09 ` Howard Spoelstra
2020-01-30 16:07 ` Aleksandar Markovic [this message]
2020-01-30 23:54 ` David Gibson
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='CAL1e-=iG_s-hcAChaoKa8BF7e4EZ6eQR=QgUwOAAPQmEJBbu7Q@mail.gmail.com' \
--to=aleksandar.m.mail@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=hsp.cat7@gmail.com \
--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).