From: Paolo Bonzini <pbonzini@redhat.com>
To: "Peter Maydell" <peter.maydell@linaro.org>,
"Emilio G. Cota" <cota@braap.org>,
"Pranith Kumar" <bobby.prani@gmail.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
"Richard Henderson" <rth@twiddle.net>,
"Alessandro Di Federico" <ale+qemu@clearmind.me>
Subject: Re: [Qemu-devel] GSoC 2017 Proposal: TCG performance enhancements
Date: Wed, 7 Jun 2017 15:35:33 +0200 [thread overview]
Message-ID: <000023f1-57a6-b211-d9d1-87b8f39326d5@redhat.com> (raw)
In-Reply-To: <CAFEAcA8RBMtfS+5GP=cGeAdV+zgGRg5OPEAu_PY+_hEPcWaJqw@mail.gmail.com>
On 07/06/2017 14:07, Peter Maydell wrote:
>> My understanding was that adding a public instrumentation interface would add
>> too much code maintenance overhead for a feature that is not in QEMU's core
>> target.
> Well, it depends what you define as our core target :-)
> I think we get quite a lot of users that want some useful ability
> to see what their guest code is doing, and these days (when
> dev board hardware is often very cheap and easily available)
and virtualization is too...
> I think that's a lot of the value that emulation can bring to
> the table. Obviously we would want to try to do it in a way
> that is low-runtime-overhead and is easy to get right for
> people adding/maintaining cpu target frontend code...
Indeed. I even sometimes use TCG -d in_asm,exec,int for KVM unit tests,
because it's easier to debug them that way :) so introspection ability
is welcome.
Related to this is also Alessandro's work to librarify TCG (he has a
TCG->LLVM backend for example).
next prev parent reply other threads:[~2017-06-07 13:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-25 16:52 [Qemu-devel] GSoC 2017 Proposal: TCG performance enhancements Pranith Kumar
2017-03-27 10:57 ` Richard Henderson
2017-03-27 13:22 ` Alex Bennée
2017-03-28 3:03 ` Pranith Kumar
2017-03-28 3:09 ` Pranith Kumar
2017-03-28 10:03 ` Stefan Hajnoczi
2017-06-02 23:39 ` [Qemu-devel] [PATCH] tcg: allocate TB structs before the corresponding translated code Emilio G. Cota
2017-06-04 17:47 ` Richard Henderson
2017-03-27 11:32 ` [Qemu-devel] GSoC 2017 Proposal: TCG performance enhancements Paolo Bonzini
2017-03-28 3:07 ` Pranith Kumar
2017-03-27 15:54 ` Stefan Hajnoczi
2017-03-27 17:13 ` Pranith Kumar
2017-06-06 17:13 ` Emilio G. Cota
2017-06-07 10:15 ` Alex Bennée
2017-06-07 11:12 ` Lluís Vilanova
2017-06-07 12:07 ` Peter Maydell
2017-06-07 13:35 ` Paolo Bonzini [this message]
2017-06-07 15:52 ` Lluís Vilanova
2017-06-07 16:09 ` Alex Bennée
2017-06-07 17:07 ` Paolo Bonzini
2017-06-07 15:45 ` Lluís Vilanova
2017-06-07 16:17 ` Peter Maydell
2017-06-07 22:49 ` Emilio G. Cota
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=000023f1-57a6-b211-d9d1-87b8f39326d5@redhat.com \
--to=pbonzini@redhat.com \
--cc=ale+qemu@clearmind.me \
--cc=alex.bennee@linaro.org \
--cc=bobby.prani@gmail.com \
--cc=cota@braap.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).