From: "Christoph Egger" <Christoph.Egger@amd.com>
To: Vincent Hanquez <vincent@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] libxc portability fixes
Date: Wed, 19 Sep 2007 17:04:35 +0200 [thread overview]
Message-ID: <200709191704.35189.Christoph.Egger@amd.com> (raw)
In-Reply-To: <20070919144949.GA7154@snarc.org>
On Wednesday 19 September 2007 16:49:49 Vincent Hanquez wrote:
> On Wed, Sep 19, 2007 at 04:32:59PM +0200, Christoph Egger wrote:
> > MAP_ANONYMOUS is the proprietary thing.
>
> which "proprietary thing" ?
>
> > The glibc people
> > should know that and should deprecate MAP_ANONYMOUS instead.
>
> solaris has deprecated MAP_ANON as well.
Oh, SystemV Unix has MAP_ANONYMOUS?
BSD-Unix only has MAP_ANON.
> > They should also document that the fd argument must be
> > -1 when MAP_ANON is specified to match the Unix behaviour.
>
> ----------
> MAP_ANONYMOUS
>
> The mapping is not backed by any file; its contents are initial‐
> ized to zero. The fd and offset arguments are ignored; however,
> some implementations require fd to be -1 if MAP_ANONYMOUS (or
> MAP_ANON) is specified, and portable applications should ensure
> this. The use of MAP_ANONYMOUS in conjunction with MAP_SHARED
> is only supported on Linux since kernel 2.4.
> ----------
>
> what are you missing from this ?
My linux mmap manpage says:
---------------------------
MAP_ANONYMOUS
The mapping is not backed by any file; the fd and offset argu-
ments are ignored. The use of this flag in conjunction with
MAP_SHARED is only supported on Linux since kernel 2.4.
MAP_ANON
Alias for MAP_ANONYMOUS. Deprecated.
---------------------------
My bsd mmap manpage says:
-------------------------------
MAP_ANON Map anonymous memory not associated with any specific
file. The file descriptor is not used for creating
MAP_ANON regions, and must be specified as -1. The
mapped memory will be zero filled.
-------------------------------
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:[~2007-09-19 15:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 13:19 [PATCH] libxc portability fixes Christoph Egger
2007-09-19 14:25 ` Vincent Hanquez
2007-09-19 14:32 ` Christoph Egger
2007-09-19 14:49 ` Vincent Hanquez
2007-09-19 15:04 ` Christoph Egger [this message]
2007-09-19 15:41 ` Vincent Hanquez
2007-09-19 16:44 ` Keir Fraser
2007-09-19 22:21 ` John Levon
2007-09-20 12:30 ` Vincent Hanquez
2007-09-20 16:41 ` John Levon
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=200709191704.35189.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=vincent@xensource.com \
--cc=xen-devel@lists.xensource.com \
/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.