From: Sergey Fedorov <serge.fdrv@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Chaos Shu" <chaos.shun@live.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] 答复: Expansion Ratio Issue
Date: Thu, 05 Jun 2014 19:14:22 +0400 [thread overview]
Message-ID: <5390894E.1050902@gmail.com> (raw)
In-Reply-To: <CAFEAcA_kjoiWufgKD0x6R01tGsgD7bTm1HoXCo=h823mCd_O9w@mail.gmail.com>
On 05.06.2014 17:07, Peter Maydell wrote:
> Probably worth making sure you also test workloads that do different
> things in multiple processes (to catch performance issues from over
> frequent TB/TLB flushes, and so on).
Maybe "make -j<N>"?
Thanks,
Sergey
prev parent reply other threads:[~2014-06-05 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SNT149-DS20972BC8406328B03556C8FB240@phx.gbl>
[not found] ` <CAFEAcA8g5GLj3tjV8tAKC2ASMdGEg9gvKHSU17cExUrwdp1n6g@mail.gmail.com>
2014-06-03 17:13 ` [Qemu-devel] Expansion Ratio Issue Sergey Fedorov
2014-06-05 1:04 ` [Qemu-devel] 答复: " Chaos Shu
2014-06-05 8:02 ` Alex Bennée
2014-06-05 13:00 ` Sergey Fedorov
2014-06-05 13:07 ` Peter Maydell
2014-06-05 15:14 ` Sergey Fedorov [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=5390894E.1050902@gmail.com \
--to=serge.fdrv@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=chaos.shun@live.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 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.