All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, mreitz@redhat.com, pbonzini@redhat.com,
	mst@redhat.com, dgilbert@redhat.com, peter.maydell@linaro.org,
	eblake@redhat.com, Peter Lieven <pl@kamp.de>
Subject: [Qemu-devel] [PATCH 0/6] coroutine: mmap stack memory and stack size
Date: Thu, 30 Jun 2016 09:37:14 +0200	[thread overview]
Message-ID: <1467272240-32123-1-git-send-email-pl@kamp.de> (raw)

I decided to split this from the rest of the Qemu RSS usage series as
it contains the more or less non contentious patches.

I omitted the MAP_GROWSDOWN flag in mmap as we are not 100% sure which
side effects it has.

I kept the guard page which is now nicely makes the stacks visible in
smaps. The old version of the relevent patch lacked the MAP_FIXED flag
in the second call to mmap.

The last patch which reduces the stack size of coroutines to 64kB
may be omitted if its found to risky.

Peter Lieven (6):
  oslib-posix: add helpers for stack alloc and free
  coroutine: add a macro for the coroutine stack size
  coroutine-ucontext: use helper for allocating stack memory
  coroutine-sigaltstack: use helper for allocating stack memory
  oslib-posix: add a configure switch to debug stack usage
  coroutine: reduce stack size to 64kB

 configure                    | 15 ++++++++++++
 include/qemu/coroutine_int.h |  2 ++
 include/sysemu/os-posix.h    | 24 +++++++++++++++++++
 util/coroutine-sigaltstack.c |  7 +++---
 util/coroutine-ucontext.c    |  9 ++++----
 util/coroutine-win32.c       |  2 +-
 util/oslib-posix.c           | 55 ++++++++++++++++++++++++++++++++++++++++++++
 7 files changed, 104 insertions(+), 10 deletions(-)

-- 
1.9.1

             reply	other threads:[~2016-06-30  7:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30  7:37 Peter Lieven [this message]
2016-06-30  7:37 ` [Qemu-devel] [PATCH 1/6] oslib-posix: add helpers for stack alloc and free Peter Lieven
2016-07-01 20:12   ` Richard Henderson
2016-07-01 20:49     ` Richard Henderson
2016-07-04  6:18       ` Peter Lieven
2016-07-04 10:19         ` Paolo Bonzini
2016-07-04 10:25           ` Peter Lieven
2016-07-04 10:34             ` Paolo Bonzini
2016-07-04 10:35               ` Peter Lieven
2016-07-04 10:48                 ` Paolo Bonzini
2016-07-04  6:16     ` Peter Lieven
2016-06-30  7:37 ` [Qemu-devel] [PATCH 2/6] coroutine: add a macro for the coroutine stack size Peter Lieven
2016-07-01 20:50   ` Richard Henderson
2016-06-30  7:37 ` [Qemu-devel] [PATCH 3/6] coroutine-ucontext: use helper for allocating stack memory Peter Lieven
2016-07-01 20:52   ` Richard Henderson
2016-06-30  7:37 ` [Qemu-devel] [PATCH 4/6] coroutine-sigaltstack: " Peter Lieven
2016-07-01 20:53   ` Richard Henderson
2016-06-30  7:37 ` [Qemu-devel] [PATCH 5/6] oslib-posix: add a configure switch to debug stack usage Peter Lieven
2016-07-01 20:55   ` Richard Henderson
2016-06-30  7:37 ` [Qemu-devel] [PATCH 6/6] coroutine: reduce stack size to 64kB Peter Lieven
2016-07-01 21:13   ` Richard Henderson
2016-07-04  6:22     ` Peter Lieven
2016-07-04 10:20       ` Paolo Bonzini

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=1467272240-32123-1-git-send-email-pl@kamp.de \
    --to=pl@kamp.de \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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.