From: Peter Maydell <peter.maydell@linaro.org>
To: Brad Smith <brad@comstyle.com>
Cc: Kamil Rytarowski <n54@gmx.com>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] oslib-posix: Use MAP_STACK in qemu_alloc_stack() on OpenBSD
Date: Thu, 11 Oct 2018 10:36:34 +0100 [thread overview]
Message-ID: <CAFEAcA9rJZNeRJdjLU724qgr6PEyVE-8hOn_gk_uU+mYSxuxDw@mail.gmail.com> (raw)
In-Reply-To: <a67f0c2c-5a5b-7a78-141b-2e829304e72e@comstyle.com>
On 11 October 2018 at 00:55, Brad Smith <brad@comstyle.com> wrote:
> And from FreeBSD...
>
> MAP_STACK MAP_STACK implies MAP_ANON, and offset of 0. The fd
> argument must be -1 and prot must include at least
> PROT_READ and PROT_WRITE.
>
> This option creates a memory region that grows to at
> most len bytes in size, starting from the stack top
> and growing down. The stack top is the starting
> address returned by the call, plus len bytes. The
> bottom of the stack at maximum growth is the starting
> address returned by the call.
>
> Stacks created with MAP_STACK automatically grow.
> Guards prevent inadvertent use of the regions into
> which those stacks can grow without requiring mapping
> the whole stack in advance.
Hmm. That "automatically growing" part sounds like
behaviour we definitely do not want for our use case.
So we're going to need to make this OS-specific :-(
thanks
-- PMM
next prev parent reply other threads:[~2018-10-11 9:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 15:37 [Qemu-devel] [PATCH] oslib-posix: Use MAP_STACK in qemu_alloc_stack() on OpenBSD Brad Smith
2018-10-09 13:52 ` Kamil Rytarowski
2018-10-09 14:12 ` Peter Maydell
2018-10-09 15:04 ` Kamil Rytarowski
2018-10-10 23:55 ` Brad Smith
2018-10-11 9:36 ` Peter Maydell [this message]
2018-10-11 9:41 ` Kamil Rytarowski
2018-10-11 14:25 ` Brad Smith
2018-10-11 19:31 ` Kamil Rytarowski
2018-10-11 21:20 ` Brad Smith
2018-10-13 18:23 ` Kamil Rytarowski
2018-10-09 14:19 ` Brad Smith
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=CAFEAcA9rJZNeRJdjLU724qgr6PEyVE-8hOn_gk_uU+mYSxuxDw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=brad@comstyle.com \
--cc=n54@gmx.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).