From: Christoph Egger <Christoph.Egger@amd.com>
To: Christoph Hellwig <hch@lst.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [5778] Use MAP_ANON also for FreeBSD (Juergen Lock)
Date: Mon, 24 Nov 2008 13:54:36 +0200 [thread overview]
Message-ID: <200811241254.37072.Christoph.Egger@amd.com> (raw)
In-Reply-To: <20081124110745.GA30446@lst.de>
On Monday 24 November 2008 12:07:45 Christoph Hellwig wrote:
> On Mon, Nov 24, 2008 at 12:44:21PM +0200, Christoph Egger wrote:
> > On Sunday 23 November 2008 10:10:06 Christoph Hellwig wrote:
> > > On Sat, Nov 22, 2008 at 08:43:01PM +0000, Blue Swirl wrote:
> > > > -#ifdef __OpenBSD__ /* no need (?) for a dummy file on OpenBSD */
> > > > +/* no need (?) for a dummy file on OpenBSD/FreeBSD */
> > > > +#if defined(__OpenBSD__) || defined(__FreeBSD__)
> > >
> > > The same is true for Linux, btw.
> >
> > and NetBSD, too. and Solaris, too.
> >
> > Actually, this is POSIX.
>
> MAP_ANON/MAP_ANONYMOUS are not in Posix.
MAP_ANONYMOUS is GNU, MAP_ANON is Unix at least.
Christoph
--
AMD Saxony, Dresden, Germany
Operating System Research Center
Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
Dr. Hans-R. Deppe, Thomas McCoy
next prev parent reply other threads:[~2008-11-24 16:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 20:43 [Qemu-devel] [5778] Use MAP_ANON also for FreeBSD (Juergen Lock) Blue Swirl
2008-11-23 9:10 ` Christoph Hellwig
2008-11-24 10:44 ` Christoph Egger
2008-11-24 11:07 ` Christoph Hellwig
2008-11-24 11:54 ` Christoph Egger [this message]
2008-11-23 10:03 ` Jamie Lokier
2008-11-23 12:00 ` Christoph Hellwig
2008-11-23 12:41 ` Jamie Lokier
2008-11-24 9:35 ` Christoph Egger
2008-11-24 17:40 ` M. Warner Losh
2008-11-25 10:19 ` Christoph Egger
2008-11-28 20:02 ` Stuart Brady
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=200811241254.37072.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=hch@lst.de \
--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.