All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe <s.priebe@profihost.ag>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] slow speed for virtio-scsi since qemu 2.2
Date: Mon, 16 Feb 2015 20:02:30 +0100	[thread overview]
Message-ID: <54E23EC6.4000000@profihost.ag> (raw)
In-Reply-To: <54E211DB.3020409@suse.de>


Am 16.02.2015 um 16:50 schrieb Andreas Färber:
> Am 16.02.2015 um 16:41 schrieb Stefan Priebe - Profihost AG:
>>> Am 16.02.2015 um 15:49 schrieb Paolo Bonzini <pbonzini@redhat.com>:
>>>
>>>
>>>
>>> On 16/02/2015 15:47, Stefan Priebe - Profihost AG wrote:
>>>>>>>>
>>>>>>>> Could it be that this is a results of compiling qemu with --enable-debug
>>>>>>>> to get debugging symbols?
>>>>>>
>>>>>> Yes.
>>>> *urg* my fault - sorry. Is there a way to get debugging symbols without
>>>> using enable-debug / getting slower performance?
>>>
>>> Yes, just do nothing ("--enable-debug-info" is the default;
>>> "--enable-debug" enables debug info _and_ turns off optimization).
>>
>> If I do not enable-debug dh_strip does not extract any debugging symbols.
>
> Maybe you forgot --disable-strip?

Thanks!

Stefan

>
> Regards,
> Andreas
>

  reply	other threads:[~2015-02-16 19:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15 18:46 [Qemu-devel] slow speed for virtio-scsi since qemu 2.2 Stefan Priebe
2015-02-16 11:06 ` Alexandre DERUMIER
2015-02-16 12:24 ` Paolo Bonzini
2015-02-16 14:43   ` Stefan Priebe - Profihost AG
2015-02-16 14:44     ` Paolo Bonzini
2015-02-16 14:47       ` Stefan Priebe - Profihost AG
2015-02-16 14:49         ` Paolo Bonzini
2015-02-16 15:41           ` Stefan Priebe - Profihost AG
2015-02-16 15:49             ` Paolo Bonzini
2015-02-16 19:02               ` Stefan Priebe
2015-02-16 15:50             ` Andreas Färber
2015-02-16 19:02               ` Stefan Priebe [this message]
2015-02-16 14:58         ` Andrey Korolyov
2015-02-16 15:38           ` Stefan Priebe - Profihost AG

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=54E23EC6.4000000@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=afaerber@suse.de \
    --cc=pbonzini@redhat.com \
    --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.