All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rayson Ho <rho@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kvm@vger.kernel.org, systemtap@sources.redhat.com,
	       Prerna Saxena <prerna@linux.vnet.ibm.com>
Subject: Re: Tracing KVM with Systemtap
Date: Wed, 22 Sep 2010 08:42:37 -0400	[thread overview]
Message-ID: <1285159357.6879.31.camel@computer> (raw)
In-Reply-To: <AANLkTi=Sy3qJxXADiSyt+sBK7cP9p=0cnFj6-V_RCSPT@mail.gmail.com>

On Wed, 2010-09-22 at 13:33 +0100, Stefan Hajnoczi wrote:
> KVM does not generate code.  Almost all the "emulation" code in the
> source tree is part of the Tiny Code Generator (TCG) used when KVM is
> not enabled (e.g. to emulate an ARM board on an x86-64 host).

Thanks, that's what I thought too. Otherwise it would be really slow to
run KVM :)

But if KVM is not used, and QEMU host & guest are running on the same
architecture, is TCG off? (Hmm, I guess I can find that answer myself by
reading the code).

Stefan, are you accepting patches? If so, I will create a patch with the
Systemtap framework & other probes.

Rayson



> 
> If you follow the life-cycle in vl.c it will take you through cpus.c
> and into kvm-all.c:kvm_cpu_exec().  Note that the details differ
> slightly between qemu.git and qemu-kvm.git, and I have described
> qemu.git.
> 
> Stefan
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-09-22 12:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 13:20 Tracing KVM with Systemtap Rayson Ho
2010-09-08 14:08 ` Stefan Hajnoczi
2010-09-20 13:19   ` Rayson Ho
2010-09-20 13:36     ` Stefan Hajnoczi
2010-09-21 12:58       ` Rayson Ho
2010-09-21 13:33         ` Stefan Hajnoczi
2010-09-22 12:11           ` Rayson Ho
2010-09-22 12:33             ` Stefan Hajnoczi
2010-09-22 12:42               ` Rayson Ho [this message]
2010-09-22 13:39                 ` Stefan Hajnoczi
     [not found]                   ` <1290019040.2454.3.camel@computer>
     [not found]                     ` <AANLkTi=sf_v_SxLR1vNB7JwqU-KUcM2QVmYLn9MJyds4@mail.gmail.com>
     [not found]                       ` <1290626577.7673.2.camel@computer>
     [not found]                         ` <AANLkTikta_R78LFf9_=OH1U3+HXSz0xepOWmYR8QV=qD@mail.gmail.com>
2011-02-09 19:27                           ` [Qemu-devel] QEMU network probes Rayson Ho
2011-02-10 11:12                             ` Stefan Hajnoczi

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=1285159357.6879.31.camel@computer \
    --to=rho@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=prerna@linux.vnet.ibm.com \
    --cc=stefanha@gmail.com \
    --cc=systemtap@sources.redhat.com \
    /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.