| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
reduce ABI disruptions when new cpu types and new PMC events are added
in the future.
- Support alternate spellings for PMC events. Derive the canonical
spelling of an event name from its enumeration name in 'enum pmc_event'.
- Provide a way for users to disambiguate between identically named events
supported by multiple classes of PMCs in a CPU.
- Change libpmc's machine-dependent event specifier parsing code to
better support CPUs containing two or more classes of PMC resources.
|
| |
|
|
|
|
| |
- Tweak -mdoc use.
|
| |
|
| |
|
|
|
|
| |
- Spell new PMC class names correctly.
|
|
|
|
| |
Intel Atom(tm), Core(tm) and Core2(tm) CPUs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Pass O_NOCTTY to posix_openpt(2). This makes the implementation work
consistently on implementations that make the PTY the controlling TTY
by default.
- Call unlockpt() before opening the slave device. POSIX mentions that
de slave device should only be opened after grantpt() and unlockpt()
have been called.
- Replace some redundant code by a label.
In theory we could remove a lot of code from openpty() on FreeBSD
-CURRENT, because grantpt(), unlockpt() and revoke() are not needed in
our implementation. We'd better keep them there. This makes the code
still work with older FreeBSD releases and even makes it work on other
non-BSD operating systems.
I've compiled openpty() on Linux. You only need to remove the revoke()
call, because revoke() on Linux always returns -1. Apart from that, it
seems to work like it should.
Reviewed by: jhb
|
|
|
|
|
| |
- Document an event that was missed out earlier.
- Sort event names alphabetically.
|
|
|
|
| |
- Sort event names.
|
| |
|
|
|
|
| |
- Correct misspellings of two event names.
|
|
|
|
| |
Requested by: Arun Sharma <arun at sharma-home dot net>
|
|
|
|
|
|
| |
Update referenced example to include unistd.h per manpage.
Update example to be more style(9)-ish, silence warnings and add
FreeBSD id to the source file.
|
|
|
|
| |
MFC after: 30 days
|
|
|
|
|
|
| |
time restore to disk.
MFC after: 30 days
|
|
|
|
|
| |
Submitted by: Pedro Giffuni
MFC after: 30 days
|
|
|
|
|
| |
Submitted by: Pedro Giffuni
MFC after: 30 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
last commit. Now it really can use a runtime-set cacheline size.
|
|
|
|
|
| |
supporting 64-bit CPUs, which often have 128-byte cache lines instead of the
standard 32.
|
| |
|
|
|
|
|
|
|
|
| |
control over the result of buildworld and installworld; this especially
helps packaging systems such as nanobsd
Reviewed by: various (posted to arch)
MFC after: 1 month
|
|
|
|
|
|
| |
remove it from this man page.
MFC after: 3 days
|
|
|
|
|
|
|
| |
into FBSD_1.1 section where they should be.
Pointed out by: kib, deischen
MFC after: 3 days
|
| |
|
| |
|
|
|
|
| |
Improve typography.
|
|
|
|
| |
which have a 64-bit integer type but don't provide standard C99 definitions.
|
|
|
|
| |
Submitted by: Joerg Sonnenberger
|
| |
|
| |
|
|
|
|
| |
the appropriate manual pages.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
a unitmask.
|
|
|
|
|
|
| |
Pointy hat goes to me.
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
| |
where critical. Some places still use ps_pread/ps_pwrite directly,
but only need changed when byte-order comes into the picture.
Also, change th_p in td_event_msg_t from a pointer type to
psaddr_t, so that events also work when psaddr_t is widened.
|
|
|
|
| |
rather than on platform.
|
|
|
|
| |
standard than the names are. Remove some trailing whitespace.
|
| |
|
|
|
|
| |
Of course, FreeBSD has both.
|
|
|
|
| |
(which always returns an error when invoked) needs its prototype.
|
|
|
|
|
|
| |
page size and using sysconf(3).
Suggested by: marcel
|
|
|
|
|
|
|
| |
the call never happens. This is necessary because malloc may be used
during exit handler processing.
Submitted by: davidxu
|
|
|
|
|
|
|
| |
allocated instead of waiting for the first request. This fixes an issue with
rpcbind's support for PMAPPROC_CALLIT.
Reviewed by: markm
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
review by secteam@ for the reasons mentioned below.
1) Rename /dev/urandom to /dev/random since urandom marked as
XXX Deprecated
alias in /sys/dev/random/randomdev.c
(this is our naming convention and no review by secteam@ required)
2) Set rs_stired flag after forced initialization to prevent
double stearing.
(this is already in OpenBSD, i.e. they don't have double stearing.
It means that this change matches their code path and no additional
secteam@ review required)
Submitted by: Thorsten Glaser <tg@mirbsd.de> (2)
|