public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
	Arjan Koers <0h61vkll2ly8@xutrox.com>,
	kvm@vger.kernel.org
Subject: Re: [ANNOUNCE] qemu-kvm-0.13.0-rc1
Date: Fri, 10 Sep 2010 12:31:01 -0700	[thread overview]
Message-ID: <20100910193101.GB23988@sequoia.sous-sol.org> (raw)
In-Reply-To: <4C8A1ACD.6090903@redhat.com>

* Avi Kivity (avi@redhat.com) wrote:
>  On 09/09/2010 04:00 PM, Anthony Liguori wrote:
> >>It's perfectly reasonable to want to avoid building the tcg code
> >>if you aren't going to use it.
> >
> >Why?  It doesn't do any harm to have extra code.
> 
> It's half a megabyte of code.

And half a day to compile ;)

> Also, it's better not to have code
> snippets that call mprotect(PROT_EXEC) in your executable.

I agree, is there any reason not to enable compiling less into the binary?
There are folks interested in eliminating as much as possible to reduce
the attack surface and auditing requirements, for example.

thanks,
-chris

  reply	other threads:[~2010-09-10 19:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 16:29 [ANNOUNCE] qemu-kvm-0.13.0-rc1 Marcelo Tosatti
2010-09-08 20:05 ` Arjan Koers
2010-09-08 20:33   ` Anthony Liguori
2010-09-09  6:17     ` Avi Kivity
2010-09-09 13:00       ` Anthony Liguori
2010-09-10 11:47         ` Avi Kivity
2010-09-10 19:31           ` Chris Wright [this message]
2010-09-10 19:48             ` Anthony Liguori
2010-09-10 19:55               ` Chris Wright
2010-09-12  6:11               ` Avi Kivity
2010-09-12 15:31                 ` Anthony Liguori
2010-09-12 15:59                   ` Avi Kivity
2010-09-13 13:10                     ` Glauber Costa
2010-09-13 11:32                   ` Jan Kiszka

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=20100910193101.GB23988@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=0h61vkll2ly8@xutrox.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox