qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Brad Smith <brad@comstyle.com>
To: Kamil Rytarowski <n54@gmx.com>, Peter Maydell <peter.maydell@linaro.org>
Cc: 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:25:18 -0400	[thread overview]
Message-ID: <486f95ef-db10-e0f2-e9a8-dd3eff0d3200@comstyle.com> (raw)
In-Reply-To: <cae2d61f-c643-5be7-4200-fcafd2f92cc5@gmx.com>

On 10/11/2018 5:41 AM, Kamil Rytarowski wrote:

> On 11.10.2018 11:36, Peter Maydell wrote:
>> 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 :-(
>>
> I propose to restrict MAP_STACK it to OpenBSD (with a comment in the
> code). Once it will be needed by someone else will be able to enable it
> for other OSes.

I was going to propose doing something like that but you had replied 
before I did.
What sort of comment did you have in mind?

  reply	other threads:[~2018-10-11 14:25 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
2018-10-11  9:41           ` Kamil Rytarowski
2018-10-11 14:25             ` Brad Smith [this message]
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=486f95ef-db10-e0f2-e9a8-dd3eff0d3200@comstyle.com \
    --to=brad@comstyle.com \
    --cc=n54@gmx.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 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).