qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Laurent Desnogues <laurent.desnogues@gmail.com>,
	Steven Noonan <steven@uplinklabs.net>,
	Steven Noonan <snoonan@amazon.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH for-2.0] configure: add option to disable -fstack-protector flags
Date: Mon, 31 Mar 2014 21:50:12 +0100	[thread overview]
Message-ID: <CAFEAcA_8z+X=N6xKHMk2BTdiLA=samYNpBozf7gt096fwjXf2g@mail.gmail.com> (raw)
In-Reply-To: <1396023542-19667-1-git-send-email-pbonzini@redhat.com>

On 28 March 2014 16:19, Paolo Bonzini <pbonzini@redhat.com> wrote:
> From: Steven Noonan <steven@uplinklabs.net>
>
> The -fstack-protector flag family is useful for ensuring safety and for
> debugging, but has a performance impact. Here are some boot time comparisons of
> the various versions of -fstack-protector using qemu-system-arm on an x86_64
> host:

Applied to master, thanks.

-- PMM

  parent reply	other threads:[~2014-03-31 20:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 16:19 [Qemu-devel] [PATCH for-2.0] configure: add option to disable -fstack-protector flags Paolo Bonzini
2014-03-28 17:41 ` Laurent Desnogues
2014-03-28 17:51   ` Paolo Bonzini
2014-03-28 18:04     ` Noonan, Steven
2014-03-28 20:53       ` Brad Smith
2014-03-31 20:50 ` Peter Maydell [this message]
2014-04-08 20:37 ` Peter Maydell
2014-04-08 20:47   ` Noonan, Steven
2014-04-09  7:40     ` Peter Maydell
2014-04-09  9:29       ` Noonan, Steven
2014-04-09  9:34         ` Peter Maydell

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='CAFEAcA_8z+X=N6xKHMk2BTdiLA=samYNpBozf7gt096fwjXf2g@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=aliguori@amazon.com \
    --cc=laurent.desnogues@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=snoonan@amazon.com \
    --cc=steven@uplinklabs.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).