Jim Warner 02508b3d76 top: use CPU_ZEROTICS to embrace the Nehalem logic
The recently added logic dealing with "missing" tics
is mutually exclusive with logic associated with a
define called CPU_ZEROTICS.

This commit expands the use of that define to exclude
such Nehalem logic as appropriate.

It also extends programmer notes in top.h to include
an attribution for initiating the topic of potential
Nehalem type % CPU distortions, acknowledging:
  Jaromir Capik, <jcapik@redhat.com>

References
commit ce1410a51a624a91816fcc8c232c8a4d60b09638
commit 9e7dd43ab7b2e68177cefd49b3c07311ea79bc1a
commit a9041a5526eddc631b94bac86c09a47e60a3b4e1
2012-02-12 21:52:23 +11:00
2012-01-08 21:57:35 +01:00
2012-01-24 08:55:05 +01:00
2012-01-08 23:02:17 +01:00
2012-01-24 08:55:05 +01:00
2012-01-08 23:02:17 +01:00
2012-01-13 22:42:38 +01:00
2012-01-08 23:02:17 +01:00
2002-09-27 13:26:07 +00:00
2002-02-01 22:47:29 +00:00
2011-12-20 17:17:03 +01:00
2011-12-20 17:30:53 +01:00
2012-01-09 21:40:53 +11:00
2002-02-01 22:47:29 +00:00
2012-02-05 20:44:39 +01:00
2011-06-04 20:50:12 +02:00
2011-12-20 17:30:53 +01:00
2002-02-01 22:47:29 +00:00
2012-01-13 23:59:26 +11:00
2012-01-21 23:29:02 +01:00
2012-01-03 18:48:43 +11:00
w.1
2011-12-20 17:17:01 +01:00
2012-01-21 16:41:31 +01:00
2012-02-05 20:48:33 +01:00

COMPATIBILITY

    This code is intended for use with Linux 2.2.xx, 2.4.xx,
    2.6.xx, and hopefully all future kernels. You should be
    running a system with libc 6, but libc 5 might work too.

INSTALLATION

    make
    make install

    Only the second ("make install") is needed if you just
    want to build and install procps-ng in the normal way.

    If you wish to test before installing, use the scripts
    named t, v, and p to ensure that the correct libproc
    (the new one) is used during your testing.

    You may set SKIP to avoid building or installing things.
    For example:

    make SKIP='/bin/kill /usr/share/man/man1/kill.1' install

    Use SHARED=0 to build procps-ng without shared libraries.
    This may be useful for installing in your home directory.

    make SHARED=0 DESTDIR=$HOME install

    Suppose you wanted to install stuff in strange places.
    You might do something like this:

    make usr/bin=/tmp/Q/i/ DESTDIR=/tmp/Q install="install -D" ldconfig=echo install

    If cross-compiling, you might need to set lib64 to
    either "lib" or "lib64". You might need to set m64 to
    -m64, -m32, or nothing at all. Some examples:

    make lib64=lib m64=-m32      # for a bi-arch gcc
    make lib64=lib64 CC=x86_64-gcc
    make lib64=lib CC=alpha-gcc

PACKAGING

    If you are a downstream maintainer (packager) for a Linux distribution,
    please avoid causing troubles. This section applies to you.

    Send patches in regularly. Many patches made by vendors have been buggy,
    some quite severely so. Sending in a patch will at least get it reviewed,
    if not included. There is a procps-ng test suite that must be passed.
    Forward all bug reports. If your bug database is public and busy enough
    to bother with, please make this known. Follow Debian's lead in making
    the bug database easy to comment on via email w/o need for an account.

    Do not change the user interface. Many of the programs are intended to be
    compatible with Solaris, FreeBSD, AIX, IRIX, Tru64, and the UNIX standard.
    Your nice new command options WILL BE BROKEN as needed to ensure that
    procps-ng remains compatible with the rest of the world. Sysadmins hate to
    deal with incompatible behavior. If you need a new option, ask for it.

    For normal packages, ensure that you do not add debugging flags
    to the CFLAGS variable. If debugging flags are present, the Makefile
    will avoid adding several optimizations that would interfere with gdb.

    There should be no need to modify the Makefile. You can set variables
    on the "make" command line or use "make -e" to pass variables from
    the environment.

BUG REPORTS

    Email to procps@freelists.org.
Description
Command line and full screen utilities for browsing procfs, a "pseudo" file system dynamically generated by Linux to provide information about the status of entries in its process table.
Readme 15 MiB
Languages
C 97.2%
Makefile 1%
Shell 0.9%
M4 0.9%