All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 10356] New: glibc 2.7 notes for eventfd(2)
Date: Sat, 29 Mar 2008 08:46:31 -0700 (PDT)	[thread overview]
Message-ID: <bug-10356-11311@http.bugzilla.kernel.org/> (raw)

http://bugzilla.kernel.org/show_bug.cgi?id=10356

           Summary: glibc 2.7 notes for eventfd(2)
           Product: Documentation
           Version: unspecified
     KernelVersion: n/a
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: man-pages
        AssignedTo: documentation_man-pages-ztI5WcYan/vQLgFONoPN62D2FQJk+8+b@public.gmane.org
        ReportedBy: mrsam-W1w4QoW4mIDgLSHwZvcCBg@public.gmane.org


I tested this, and it works:

--- /home/mrsam/src/man-pages/sources/manpages/man-pages-2.79/man2/eventfd.2   
2008-03-03 08:25:44.000000000 -0500
+++ ./eventfd.2 2008-03-29 11:42:24.000000000 -0400
@@ -204,8 +204,28 @@
 .SH VERSIONS
 .BR eventfd ()
 is available on Linux since kernel 2.6.22.
-Working support is provided in glibc since version 2.8.
+Working support is provided in glibc since version 2.8,
 .\" eventfd() is in glibc 2.7, but reportedly does not build
+but it's possible to create an event file descriptor with glibc 2.7 using
+.BR syscall (2):
+.RS
+.nf
+
+#include <sys/syscall.h>
+#include <unistd.h>
+
+...
+
+int efd=syscall(SYS_eventfd, 0, 0);
+
+.fi
+.RE
+Then use
+.BR read (2)
+and
+.BR write (2)
+with this file descriptor.
+This works as long as glibc 2.7 itself was built on kernel 2.6.22, or later.
 .SH CONFORMING TO
 .BR eventfd ()
 is Linux-specific.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2008-03-29 15:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-29 15:46 bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r [this message]
     [not found] ` <bug-10356-11311-V0hAGp6uBxO456/isadD/XN4h3HLQggn@public.gmane.org/>
2010-01-19 17:14   ` [Bug 10356] [PATCH]glibc 2.7 notes for eventfd(2) bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r

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=bug-10356-11311@http.bugzilla.kernel.org/ \
    --to=bugme-daemon-590eeb7gvniway/ihj7yzeb+6bgklq7r@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.