From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40005) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W1P5h-00009v-Nm for qemu-devel@nongnu.org; Thu, 09 Jan 2014 18:32:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W1P5b-0000bq-Pc for qemu-devel@nongnu.org; Thu, 09 Jan 2014 18:32:45 -0500 Received: from smtp-fw-9102.amazon.com ([207.171.184.29]:31600) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W1P5b-0000bV-JR for qemu-devel@nongnu.org; Thu, 09 Jan 2014 18:32:39 -0500 Date: Thu, 9 Jan 2014 15:31:43 -0800 From: "Noonan, Steven" Message-ID: <20140109233142.GB11226@amazon.com> References: <1389304508-10100-1-git-send-email-steven@uplinklabs.net> <52CF2561.7050105@redhat.com> <52CF2E2F.4060005@comstyle.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline In-Reply-To: <52CF2E2F.4060005@comstyle.com> Subject: Re: [Qemu-devel] [PATCH 1/3] configure: add option to disable -fstack-protector flags List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Brad Smith Cc: Paolo Bonzini , Steven Noonan , qemu-devel@nongnu.org, Anthony Liguori On Thu, Jan 09, 2014 at 06:18:07PM -0500, Brad Smith wrote: > On 09/01/14 5:40 PM, Paolo Bonzini wrote: > >Il 09/01/2014 22:55, Steven Noonan ha scritto: > >>From: Steven Noonan > >> > >>The -fstack-protector flag family is useful for ensuring safety and for > >>debugging, but has a performance impact. Here's a boot time comparison between > >>a QEMU build of qemu-system-arm with and without the -fstack-protector-all > >>flag: > >> > >> # WITHOUT -fstack-protector-all > >> [root@localhost ~]# systemd-analyze > >> Startup finished in 1.744s (kernel) + 11.345s (initrd) + 47.164s (userspace) = 1min 255ms > >> > >> # WITH -fstack-protector-all > >> [root@localhost ~]# systemd-analyze > >> Startup finished in 1.843s (kernel) + 12.262s (initrd) + 1min 3.480s (userspace) = 1min 17.587s > > > >Can you try -fstack-protector-strong? > > > >Probably the right thing to do is to pick in order > >-fstack-protector-strong, -fstack-protector, and nothing. > > +1 > I think there should still be an option to turn it off, but I agree that there are probably better flags than -fstack-protector-all. I'll try those out and post an update here probably later this evening.