All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Wiese <developlists@gmx.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] BeOS 5.0.3 network problems
Date: Fri, 19 Nov 2004 15:42:03 +0100	[thread overview]
Message-ID: <419E063B.6040508@gmx.de> (raw)
In-Reply-To: <20041119140550.1739.qmail@maboque.srv.clix.pt>

ruiapimenta@clix.pt wrote:

>Totally off-topic:
>What's the difference between "normal" and profiling?
>Forgive my ignorance...
>
>Regards,
>Rui
>  
>
If you run a program which is build with profiling enabled, the time is 
measured which was spend to execute different functions. This allows you 
to detect very time-consuming functions. As you may have noticed, BeOS 
in qEmu uses 100% of your host-cpu-time even if BeOS itself is idle (and 
uses HLT-instruction). With the use of a profiled-build I hope to 
identify the function which is "running wild".

       reply	other threads:[~2004-11-19 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20041119140550.1739.qmail@maboque.srv.clix.pt>
2004-11-19 14:42 ` Christian Wiese [this message]
     [not found] <20041119164742.23182.qmail@maboque.srv.clix.pt>
2004-11-19 17:05 ` [Qemu-devel] BeOS 5.0.3 network problems Christian Wiese
2004-11-19 12:22 ruiapimenta
2004-11-19 12:57 ` Christian Wiese

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=419E063B.6040508@gmx.de \
    --to=developlists@gmx.de \
    --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.