qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jan-Simon Möller" <dl9pf@gmx.de>
To: Laurent Desnogues <laurent.desnogues@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Patch] Make usermode stacksize (-s) configurable at compile-time
Date: Sun, 25 Oct 2009 18:41:24 +0100	[thread overview]
Message-ID: <200910251841.25045.dl9pf@gmx.de> (raw)
In-Reply-To: <761ea48b0910250854g2aa96a49w65eb5ede77c38f51@mail.gmail.com>

Am Sonntag 25 Oktober 2009 16:54:16 schrieb Laurent Desnogues:
> Wouldn't it be better to set this earlier only if target_user_only
> is set to yes and use cflags?
> 
> Something like this:
> 
> if test "$target_user_only" = "yes" -a "$user_mode_stacksize" != ""; then
>   cflags="-DUSER_MODE_STACKSIZE $cflags"
> fi
> 
> just after the test for pie (line 2478) for instance.
Done. 
> The informative echo should go with the others (line 1853).
Its not clear at this stage, if its "default" or the cmdline value, 
as $target_user_only isn't evaluated until line 2171 .

I'd leave therefore the echo in line 2491.
> 
>
> I'd prefer:
> 
> #ifndef USER_MODE_STACKSIZE
> #define x86_stack_size (512 * 1024)
> #endif
> unsigned long x86_stack_size = USER_MODE_STACKSIZE;
> 
You mean probably?
#ifndef USER_MODE_STACKSIZE
#define USER_MODE_STACKSIZE (512 * 1024)
#endif
unsigned long x86_stack_size = USER_MODE_STACKSIZE;

Done.

Patch will follow in next mail as reply.

Tnx and have phun !

Jan-Simon

  reply	other threads:[~2009-10-25 17:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-25 15:22 [Qemu-devel] [Patch] Make usermode stacksize (-s) configurable at compile-time Jan-Simon Möller
2009-10-25 15:54 ` Laurent Desnogues
2009-10-25 17:41   ` Jan-Simon Möller [this message]
2009-10-25 17:49     ` Jan-Simon Möller
2009-10-25 21:09       ` [Qemu-devel] " Juan Quintela
2009-10-26 11:37         ` Jan-Simon Möller
2009-10-26  0:53       ` [Qemu-devel] " Jamie Lokier
2009-10-26 12:25       ` Riku Voipio
2009-10-27 19:56         ` Jan-Simon Möller

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=200910251841.25045.dl9pf@gmx.de \
    --to=dl9pf@gmx.de \
    --cc=laurent.desnogues@gmail.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 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).