Merge branch 'linus' into stackprotector

TAGS

vmlinux*

!vmlinux.lds.S

!vmlinux.lds.h

System.map

Module.markers

Module.symvers

    runs an instance of gdb against the vmlinux file which contains

    the symbols (not boot image such as bzImage, zImage, uImage...).

    In gdb the developer specifies the connection parameters and

    connects to kgdb.  Depending on which kgdb I/O modules exist in

    the kernel for a given architecture, it may be possible to debug

    the test machine's kernel with the development machine using a

    rs232 or ethernet connection.

    connects to kgdb.  The type of connection a developer makes with

    gdb depends on the availability of kgdb I/O modules compiled as

    builtin's or kernel modules in the test machine's kernel.

    </para>

  </chapter>

  <chapter id="CompilingAKernel">

  </para>

  <para>

  IMPORTANT NOTE: Using this option with kgdb over the console

  (kgdboc) or kgdb over ethernet (kgdboe) is not supported.

  (kgdboc) is not supported.

  </para>

  </sect1>

  </chapter>

    (gdb) target remote /dev/ttyS0

    </programlisting>

    <para>

    Example (kgdb to a terminal server):

    Example (kgdb to a terminal server on tcp port 2012):

    </para>

    <programlisting>

    % gdb ./vmlinux

    (gdb) target remote udp:192.168.2.2:6443

    </programlisting>

    <para>

    Example (kgdb over ethernet):

    </para>

    <programlisting>

    % gdb ./vmlinux

    (gdb) target remote udp:192.168.2.2:6443

    (gdb) target remote 192.168.2.2:2012

    </programlisting>

    <para>

    Once connected, you can debug a kernel the way you would debug an

now, but you can do this to mark internal company procedures or just

point out some special detail about the sign-off. 

If you are a subsystem or branch maintainer, sometimes you need to slightly

modify patches you receive in order to merge them, because the code is not

exactly the same in your tree and the submitters'. If you stick strictly to

rule (c), you should ask the submitter to rediff, but this is a totally

counter-productive waste of time and energy. Rule (b) allows you to adjust

the code, but then it is very impolite to change one submitter's code and

make him endorse your bugs. To solve this problem, it is recommended that

you add a line between the last Signed-off-by header and yours, indicating

the nature of your changes. While there is nothing mandatory about this, it

seems like prepending the description with your mail and/or name, all

enclosed in square brackets, is noticeable enough to make it obvious that

you are responsible for last-minute changes. Example :

	Signed-off-by: Random J Developer <random@developer.example.org>

	[lucky@maintainer.example.org: struct foo moved from foo.c to foo.h]

	Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>

This practise is particularly helpful if you maintain a stable branch and

want at the same time to credit the author, track changes, merge the fix,

and protect the submitter from complaints. Note that under no circumstances

can you change the author's identity (the From header), as it is the one

which appears in the changelog.

Special note to back-porters: It seems to be a common and useful practise

to insert an indication of the origin of a patch at the top of the commit

message (just after the subject line) to facilitate tracking. For instance,

here's what we see in 2.6-stable :

    Date:   Tue May 13 19:10:30 2008 +0000

        SCSI: libiscsi regression in 2.6.25: fix nop timer handling

        commit 4cf1043593db6a337f10e006c23c69e5fc93e722 upstream

And here's what appears in 2.4 :

    Date:   Tue May 13 22:12:27 2008 +0200

        wireless, airo: waitbusy() won't delay

        [backport of 2.6 commit b7acbdfbd1f277c1eb23f344f899cfa4cd0bf36a]

Whatever the format, this information provides a valuable help to people

tracking your trees, and to people trying to trouble-shoot bugs in your

tree.

13) When to use Acked-by: and Cc:

	* SA E200

	* SA E200i

	* SA E500

	* SA P212

	* SA P410

	* SA P410i

	* SA P411

	* SA P812

Detecting drive failures:

-------------------------

The following rules apply to each cpuset:

 - Its CPUs and Memory Nodes must be a subset of its parents.

 - It can only be marked exclusive if its parent is.

 - It can't be marked exclusive unless its parent is.

 - If its cpu or memory is exclusive, they may not overlap any sibling.

These rules, and the natural hierarchy of cpusets, enable efficient

flag, and if set, a call to a new routine cpuset_mem_spread_node()

returns the node to prefer for the allocation.

Similarly, setting 'memory_spread_cache' turns on the flag

Similarly, setting 'memory_spread_slab' turns on the flag

PF_SPREAD_SLAB, and appropriately marked slab caches will allocate

pages from the node returned by cpuset_mem_spread_node().

   2  : search cores in a package.

   3  : search cpus in a node [= system wide on non-NUMA system]

 ( 4  : search nodes in a chunk of node [on NUMA system] )

 ( 5~ : search system wide [on NUMA system])

 ( 5  : search system wide [on NUMA system] )

This file is per-cpuset and affect the sched domain where the cpuset

belongs to.  Therefore if the flag 'sched_load_balance' of a cpuset

In this directory you can find several files:

# ls

cpus  cpu_exclusive  mems  mem_exclusive mem_hardwall  tasks

cpu_exclusive  memory_migrate      mems                      tasks

cpus           memory_pressure     notify_on_release

mem_exclusive  memory_spread_page  sched_load_balance

mem_hardwall   memory_spread_slab  sched_relax_domain_level

Reading them will give you information about the state of this cpuset:

the CPUs and Memory Nodes it can use, the processes that are using