Skip to content

K
Kernel

openeuler / Kernel
接近 2 年 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
提交 d9b2002c 编写于 作者: I Ingo Molnar
浏览文件
操作

Merge branch 'perf/urgent' into perf/core 

Merge reason: Upcoming patch is dependent on a fix in perf/urgent.
Signed-off-by: NIngo Molnar <mingo@elte.hu>
上级 c3b32fcb 906010b2
展开全部 隐藏空白更改
内联 并排
Showing with 35304 addition and 14942 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
Documentation/ABI/stable/sysfs-class-backlight 0 → 100644
浏览文件 @ d9b2002c
What: /sys/class/backlight/<backlight>/bl_power
Date: April 2005
KernelVersion: 2.6.12
Contact: Richard Purdie <rpurdie@rpsys.net>
Description:
Control BACKLIGHT power, values are FB_BLANK_* from fb.h
- FB_BLANK_UNBLANK (0) : power on.
- FB_BLANK_POWERDOWN (4) : power off
Users: HAL
What: /sys/class/backlight/<backlight>/brightness
Date: April 2005
KernelVersion: 2.6.12
Contact: Richard Purdie <rpurdie@rpsys.net>
Description:
Control the brightness for this <backlight>. Values
are between 0 and max_brightness. This file will also
show the brightness level stored in the driver, which
may not be the actual brightness (see actual_brightness).
Users: HAL
What: /sys/class/backlight/<backlight>/actual_brightness
Date: March 2006
KernelVersion: 2.6.17
Contact: Richard Purdie <rpurdie@rpsys.net>
Description:
Show the actual brightness by querying the hardware.
Users: HAL
What: /sys/class/backlight/<backlight>/max_brightness
Date: April 2005
KernelVersion: 2.6.12
Contact: Richard Purdie <rpurdie@rpsys.net>
Description:
Maximum brightness for <backlight>.
Users: HAL
Documentation/ABI/testing/sysfs-class-lcd 0 → 100644
浏览文件 @ d9b2002c
What: /sys/class/lcd/<lcd>/lcd_power
Date: April 2005
KernelVersion: 2.6.12
Contact: Richard Purdie <rpurdie@rpsys.net>
Description:
Control LCD power, values are FB_BLANK_* from fb.h
- FB_BLANK_UNBLANK (0) : power on.
- FB_BLANK_POWERDOWN (4) : power off
What: /sys/class/lcd/<lcd>/contrast
Date: April 2005
KernelVersion: 2.6.12
Contact: Richard Purdie <rpurdie@rpsys.net>
Description:
Current contrast of this LCD device. Value is between 0 and
/sys/class/lcd/<lcd>/max_contrast.
What: /sys/class/lcd/<lcd>/max_contrast
Date: April 2005
KernelVersion: 2.6.12
Contact: Richard Purdie <rpurdie@rpsys.net>
Description:
Maximum contrast for this LCD device.
Documentation/ABI/testing/sysfs-class-led 0 → 100644
浏览文件 @ d9b2002c
What: /sys/class/leds/<led>/brightness
Date: March 2006
KernelVersion: 2.6.17
Contact: Richard Purdie <rpurdie@rpsys.net>
Description:
Set the brightness of the LED. Most LEDs don't
have hardware brightness support so will just be turned on for
non-zero brightness settings. The value is between 0 and
/sys/class/leds/<led>/max_brightness.
What: /sys/class/leds/<led>/max_brightness
Date: March 2006
KernelVersion: 2.6.17
Contact: Richard Purdie <rpurdie@rpsys.net>
Description:
Maximum brightness level for this led, default is 255 (LED_FULL).
What: /sys/class/leds/<led>/trigger
Date: March 2006
KernelVersion: 2.6.17
Contact: Richard Purdie <rpurdie@rpsys.net>
Description:
Set the trigger for this LED. A trigger is a kernel based source
of led events.
You can change triggers in a similar manner to the way an IO
scheduler is chosen. Trigger specific parameters can appear in
/sys/class/leds/<led> once a given trigger is selected.
Documentation/ABI/testing/sysfs-gpio
浏览文件 @ d9b2002c
......@@ -19,6 +19,7 @@ Description:
/gpioN ... for each exported GPIO #N
/value ... always readable, writes fail for input GPIOs
/direction ... r/w as: in, out (default low); write: high, low
/edge ... r/w as: none, falling, rising, both
/gpiochipN ... for each gpiochip; #N is its first GPIO
/base ... (r/o) same as N
/label ... (r/o) descriptive, not necessarily unique
......
Documentation/ABI/testing/sysfs-platform-asus-laptop 0 → 100644
浏览文件 @ d9b2002c
What: /sys/devices/platform/asus-laptop/display
Date: January 2007
KernelVersion: 2.6.20
Contact: "Corentin Chary" <corentincj@iksaif.net>
Description:
This file allows display switching. The value
is composed by 4 bits and defined as follow:
4321
|||`- LCD
||`-- CRT
|`--- TV
`---- DVI
Ex: - 0 (0000b) means no display
- 3 (0011b) CRT+LCD.
What: /sys/devices/platform/asus-laptop/gps
Date: January 2007
KernelVersion: 2.6.20
Contact: "Corentin Chary" <corentincj@iksaif.net>
Description:
Control the gps device. 1 means on, 0 means off.
Users: Lapsus
What: /sys/devices/platform/asus-laptop/ledd
Date: January 2007
KernelVersion: 2.6.20
Contact: "Corentin Chary" <corentincj@iksaif.net>
Description:
Some models like the W1N have a LED display that can be
used to display several informations.
To control the LED display, use the following :
echo 0x0T000DDD > /sys/devices/platform/asus-laptop/
where T control the 3 letters display, and DDD the 3 digits display.
The DDD table can be found in Documentation/laptops/asus-laptop.txt
What: /sys/devices/platform/asus-laptop/bluetooth
Date: January 2007
KernelVersion: 2.6.20
Contact: "Corentin Chary" <corentincj@iksaif.net>
Description:
Control the bluetooth device. 1 means on, 0 means off.
This may control the led, the device or both.
Users: Lapsus
What: /sys/devices/platform/asus-laptop/wlan
Date: January 2007
KernelVersion: 2.6.20
Contact: "Corentin Chary" <corentincj@iksaif.net>
Description:
Control the bluetooth device. 1 means on, 0 means off.
This may control the led, the device or both.
Users: Lapsus
Documentation/ABI/testing/sysfs-platform-eeepc-laptop 0 → 100644
浏览文件 @ d9b2002c
What: /sys/devices/platform/eeepc-laptop/disp
Date: May 2008
KernelVersion: 2.6.26
Contact: "Corentin Chary" <corentincj@iksaif.net>
Description:
This file allows display switching.
- 1 = LCD
- 2 = CRT
- 3 = LCD+CRT
If you run X11, you should use xrandr instead.
What: /sys/devices/platform/eeepc-laptop/camera
Date: May 2008
KernelVersion: 2.6.26
Contact: "Corentin Chary" <corentincj@iksaif.net>
Description:
Control the camera. 1 means on, 0 means off.
What: /sys/devices/platform/eeepc-laptop/cardr
Date: May 2008
KernelVersion: 2.6.26
Contact: "Corentin Chary" <corentincj@iksaif.net>
Description:
Control the card reader. 1 means on, 0 means off.
What: /sys/devices/platform/eeepc-laptop/cpufv
Date: Jun 2009
KernelVersion: 2.6.31
Contact: "Corentin Chary" <corentincj@iksaif.net>
Description:
Change CPU clock configuration.
On the Eee PC 1000H there are three available clock configuration:
* 0 -> Super Performance Mode
* 1 -> High Performance Mode
* 2 -> Power Saving Mode
On Eee PC 701 there is only 2 available clock configurations.
Available configuration are listed in available_cpufv file.
Reading this file will show the raw hexadecimal value which
is defined as follow:
| 8 bit | 8 bit |
| `---- Current mode
`------------ Availables modes
For example, 0x301 means: mode 1 selected, 3 available modes.
What: /sys/devices/platform/eeepc-laptop/available_cpufv
Date: Jun 2009
KernelVersion: 2.6.31
Contact: "Corentin Chary" <corentincj@iksaif.net>
Description:
List available cpufv modes.
Documentation/DocBook/mtdnand.tmpl
浏览文件 @ d9b2002c
......@@ -568,7 +568,7 @@ static void board_select_chip (struct mtd_info *mtd, int chip)
<para>
The blocks in which the tables are stored are procteted against
accidental access by marking them bad in the memory bad block
table. The bad block table managment functions are allowed
table. The bad block table management functions are allowed
to circumvernt this protection.
</para>
<para>
......
Documentation/DocBook/scsi.tmpl
浏览文件 @ d9b2002c
......@@ -317,7 +317,7 @@
<para>
The SAS transport class contains common code to deal with SAS HBAs,
an aproximated representation of SAS topologies in the driver model,
and various sysfs attributes to expose these topologies and managment
and various sysfs attributes to expose these topologies and management
interfaces to userspace.
</para>
<para>
......
Documentation/Intel-IOMMU.txt
浏览文件 @ d9b2002c
......@@ -56,11 +56,7 @@ Graphics Problems?
------------------
If you encounter issues with graphics devices, you can try adding
option intel_iommu=igfx_off to turn off the integrated graphics engine.
If it happens to be a PCI device included in the INCLUDE_ALL Engine,
then try enabling CONFIG_DMAR_GFX_WA to setup a 1-1 map. We hear
graphics drivers may be in process of using DMA api's in the near
future and at that time this option can be yanked out.
If this fixes anything, please ensure you file a bug reporting the problem.
Some exceptions to IOVA
-----------------------
......
Documentation/SubmittingPatches
浏览文件 @ d9b2002c
......@@ -183,7 +183,7 @@ the MAN-PAGES maintainer (as listed in the MAINTAINERS file)
a man-pages patch, or at least a notification of the change,
so that some information makes its way into the manual pages.
Even if the maintainer did not respond in step #4, make sure to ALWAYS
Even if the maintainer did not respond in step #5, make sure to ALWAYS
copy the maintainer when you change their code.
For small patches you may want to CC the Trivial Patch Monkey
......
Documentation/accounting/getdelays.c
浏览文件 @ d9b2002c
......@@ -116,7 +116,7 @@ static int create_nl_socket(int protocol)
}
int send_cmd(int sd, __u16 nlmsg_type, __u32 nlmsg_pid,
static int send_cmd(int sd, __u16 nlmsg_type, __u32 nlmsg_pid,
__u8 genl_cmd, __u16 nla_type,
void *nla_data, int nla_len)
{
......@@ -160,7 +160,7 @@ int send_cmd(int sd, __u16 nlmsg_type, __u32 nlmsg_pid,
* Probe the controller in genetlink to find the family id
* for the TASKSTATS family
*/
int get_family_id(int sd)
static int get_family_id(int sd)
{
struct {
struct nlmsghdr n;
......@@ -190,7 +190,7 @@ int get_family_id(int sd)
return id;
}
void print_delayacct(struct taskstats *t)
static void print_delayacct(struct taskstats *t)
{
printf("\n\nCPU %15s%15s%15s%15s\n"
" %15llu%15llu%15llu%15llu\n"
......@@ -216,7 +216,7 @@ void print_delayacct(struct taskstats *t)
(unsigned long long)t->freepages_delay_total);
}
void task_context_switch_counts(struct taskstats *t)
static void task_context_switch_counts(struct taskstats *t)
{
printf("\n\nTask %15s%15s\n"
" %15llu%15llu\n",
......@@ -224,7 +224,7 @@ void task_context_switch_counts(struct taskstats *t)
(unsigned long long)t->nvcsw, (unsigned long long)t->nivcsw);
}
void print_cgroupstats(struct cgroupstats *c)
static void print_cgroupstats(struct cgroupstats *c)
{
printf("sleeping %llu, blocked %llu, running %llu, stopped %llu, "
"uninterruptible %llu\n", (unsigned long long)c->nr_sleeping,
......@@ -235,7 +235,7 @@ void print_cgroupstats(struct cgroupstats *c)
}
void print_ioacct(struct taskstats *t)
static void print_ioacct(struct taskstats *t)
{
printf("%s: read=%llu, write=%llu, cancelled_write=%llu\n",
t->ac_comm,
......
Documentation/arm/tcm.txt 0 → 100644
浏览文件 @ d9b2002c
ARM TCM (Tightly-Coupled Memory) handling in Linux
----
Written by Linus Walleij <linus.walleij@stericsson.com>
Some ARM SoC:s have a so-called TCM (Tightly-Coupled Memory).
This is usually just a few (4-64) KiB of RAM inside the ARM
processor.
Due to being embedded inside the CPU The TCM has a
Harvard-architecture, so there is an ITCM (instruction TCM)
and a DTCM (data TCM). The DTCM can not contain any
instructions, but the ITCM can actually contain data.
The size of DTCM or ITCM is minimum 4KiB so the typical
minimum configuration is 4KiB ITCM and 4KiB DTCM.
ARM CPU:s have special registers to read out status, physical
location and size of TCM memories. arch/arm/include/asm/cputype.h
defines a CPUID_TCM register that you can read out from the
system control coprocessor. Documentation from ARM can be found
at http://infocenter.arm.com, search for "TCM Status Register"
to see documents for all CPUs. Reading this register you can
determine if ITCM (bit 0) and/or DTCM (bit 16) is present in the
machine.
There is further a TCM region register (search for "TCM Region
Registers" at the ARM site) that can report and modify the location
size of TCM memories at runtime. This is used to read out and modify
TCM location and size. Notice that this is not a MMU table: you
actually move the physical location of the TCM around. At the
place you put it, it will mask any underlying RAM from the
CPU so it is usually wise not to overlap any physical RAM with
the TCM. The TCM memory exists totally outside the MMU and will
override any MMU mappings.
Code executing inside the ITCM does not "see" any MMU mappings
and e.g. register accesses must be made to physical addresses.
TCM is used for a few things:
- FIQ and other interrupt handlers that need deterministic
timing and cannot wait for cache misses.
- Idle loops where all external RAM is set to self-refresh
retention mode, so only on-chip RAM is accessible by
the CPU and then we hang inside ITCM waiting for an
interrupt.
- Other operations which implies shutting off or reconfiguring
the external RAM controller.
There is an interface for using TCM on the ARM architecture
in <asm/tcm.h>. Using this interface it is possible to:
- Define the physical address and size of ITCM and DTCM.
- Tag functions to be compiled into ITCM.
- Tag data and constants to be allocated to DTCM and ITCM.
- Have the remaining TCM RAM added to a special
allocation pool with gen_pool_create() and gen_pool_add()
and provice tcm_alloc() and tcm_free() for this
memory. Such a heap is great for things like saving
device state when shutting off device power domains.
A machine that has TCM memory shall select HAVE_TCM in
arch/arm/Kconfig for itself, and then the
rest of the functionality will depend on the physical
location and size of ITCM and DTCM to be defined in
mach/memory.h for the machine. Code that needs to use
TCM shall #include <asm/tcm.h> If the TCM is not located
at the place given in memory.h it will be moved using
the TCM Region registers.
Functions to go into itcm can be tagged like this:
int __tcmfunc foo(int bar);
Variables to go into dtcm can be tagged like this:
int __tcmdata foo;
Constants can be tagged like this:
int __tcmconst foo;
To put assembler into TCM just use
.section ".tcm.text" or .section ".tcm.data"
respectively.
Example code:
#include <asm/tcm.h>
/* Uninitialized data */
static u32 __tcmdata tcmvar;
/* Initialized data */
static u32 __tcmdata tcmassigned = 0x2BADBABEU;
/* Constant */
static const u32 __tcmconst tcmconst = 0xCAFEBABEU;
static void __tcmlocalfunc tcm_to_tcm(void)
{
int i;
for (i = 0; i < 100; i++)
tcmvar ++;
}
static void __tcmfunc hello_tcm(void)
{
/* Some abstract code that runs in ITCM */
int i;
for (i = 0; i < 100; i++) {
tcmvar ++;
}
tcm_to_tcm();
}
static void __init test_tcm(void)
{
u32 *tcmem;
int i;
hello_tcm();
printk("Hello TCM executed from ITCM RAM\n");
printk("TCM variable from testrun: %u @ %p\n", tcmvar, &tcmvar);
tcmvar = 0xDEADBEEFU;
printk("TCM variable: 0x%x @ %p\n", tcmvar, &tcmvar);
printk("TCM assigned variable: 0x%x @ %p\n", tcmassigned, &tcmassigned);
printk("TCM constant: 0x%x @ %p\n", tcmconst, &tcmconst);
/* Allocate some TCM memory from the pool */
tcmem = tcm_alloc(20);
if (tcmem) {
printk("TCM Allocated 20 bytes of TCM @ %p\n", tcmem);
tcmem[0] = 0xDEADBEEFU;
tcmem[1] = 0x2BADBABEU;
tcmem[2] = 0xCAFEBABEU;
tcmem[3] = 0xDEADBEEFU;
tcmem[4] = 0x2BADBABEU;
for (i = 0; i < 5; i++)
printk("TCM tcmem[%d] = %08x\n", i, tcmem[i]);
tcm_free(tcmem, 20);
}
}
Documentation/auxdisplay/cfag12864b-example.c
浏览文件 @ d9b2002c
......@@ -62,7 +62,7 @@ unsigned char cfag12864b_buffer[CFAG12864B_SIZE];
* Unable to open: return = -1
* Unable to mmap: return = -2
*/
int cfag12864b_init(char *path)
static int cfag12864b_init(char *path)
{
cfag12864b_fd = open(path, O_RDWR);
if (cfag12864b_fd == -1)
......@@ -81,7 +81,7 @@ int cfag12864b_init(char *path)
/*
* exit a cfag12864b framebuffer device
*/
void cfag12864b_exit(void)
static void cfag12864b_exit(void)
{
munmap(cfag12864b_mem, CFAG12864B_SIZE);
close(cfag12864b_fd);
......@@ -90,7 +90,7 @@ void cfag12864b_exit(void)
/*
* set (x, y) pixel
*/
void cfag12864b_set(unsigned char x, unsigned char y)
static void cfag12864b_set(unsigned char x, unsigned char y)
{
if (CFAG12864B_CHECK(x, y))
cfag12864b_buffer[CFAG12864B_ADDRESS(x, y)] |=
......@@ -100,7 +100,7 @@ void cfag12864b_set(unsigned char x, unsigned char y)
/*
* unset (x, y) pixel
*/
void cfag12864b_unset(unsigned char x, unsigned char y)
static void cfag12864b_unset(unsigned char x, unsigned char y)
{
if (CFAG12864B_CHECK(x, y))
cfag12864b_buffer[CFAG12864B_ADDRESS(x, y)] &=
......@@ -113,7 +113,7 @@ void cfag12864b_unset(unsigned char x, unsigned char y)
* Pixel off: return = 0
* Pixel on: return = 1
*/
unsigned char cfag12864b_isset(unsigned char x, unsigned char y)
static unsigned char cfag12864b_isset(unsigned char x, unsigned char y)
{
if (CFAG12864B_CHECK(x, y))
if (cfag12864b_buffer[CFAG12864B_ADDRESS(x, y)] &
......@@ -126,7 +126,7 @@ unsigned char cfag12864b_isset(unsigned char x, unsigned char y)
/*
* not (x, y) pixel
*/
void cfag12864b_not(unsigned char x, unsigned char y)
static void cfag12864b_not(unsigned char x, unsigned char y)
{
if (cfag12864b_isset(x, y))
cfag12864b_unset(x, y);
......@@ -137,7 +137,7 @@ void cfag12864b_not(unsigned char x, unsigned char y)
/*
* fill (set all pixels)
*/
void cfag12864b_fill(void)
static void cfag12864b_fill(void)
{
unsigned short i;
......@@ -148,7 +148,7 @@ void cfag12864b_fill(void)
/*
* clear (unset all pixels)
*/
void cfag12864b_clear(void)
static void cfag12864b_clear(void)
{
unsigned short i;
......@@ -162,7 +162,7 @@ void cfag12864b_clear(void)
* Pixel off: src[i] = 0
* Pixel on: src[i] > 0
*/
void cfag12864b_format(unsigned char * matrix)
static void cfag12864b_format(unsigned char * matrix)
{
unsigned char i, j, n;
......@@ -182,7 +182,7 @@ void cfag12864b_format(unsigned char * matrix)
/*
* blit buffer to lcd
*/
void cfag12864b_blit(void)
static void cfag12864b_blit(void)
{
memcpy(cfag12864b_mem, cfag12864b_buffer, CFAG12864B_SIZE);
}
......@@ -194,11 +194,10 @@ void cfag12864b_blit(void)
*/
#include <stdio.h>
#include <string.h>
#define EXAMPLES 6
void example(unsigned char n)
static void example(unsigned char n)
{
unsigned short i, j;
unsigned char matrix[CFAG12864B_WIDTH * CFAG12864B_HEIGHT];
......
Documentation/cgroups/cgroups.txt
浏览文件 @ d9b2002c
......@@ -408,6 +408,26 @@ You can attach the current shell task by echoing 0:
# echo 0 > tasks
2.3 Mounting hierarchies by name
--------------------------------
Passing the name=<x> option when mounting a cgroups hierarchy
associates the given name with the hierarchy. This can be used when
mounting a pre-existing hierarchy, in order to refer to it by name
rather than by its set of active subsystems. Each hierarchy is either
nameless, or has a unique name.
The name should match [\w.-]+
When passing a name=<x> option for a new hierarchy, you need to
specify subsystems manually; the legacy behaviour of mounting all
subsystems when none are explicitly specified is not supported when
you give a subsystem a name.
The name of the subsystem appears as part of the hierarchy description
in /proc/mounts and /proc/<pid>/cgroups.
3. Kernel API
=============
......@@ -501,7 +521,7 @@ rmdir() will fail with it. From this behavior, pre_destroy() can be
called multiple times against a cgroup.
int can_attach(struct cgroup_subsys *ss, struct cgroup *cgrp,
struct task_struct *task)
struct task_struct *task, bool threadgroup)
(cgroup_mutex held by caller)
Called prior to moving a task into a cgroup; if the subsystem
......@@ -509,14 +529,20 @@ returns an error, this will abort the attach operation. If a NULL
task is passed, then a successful result indicates that *any*
unspecified task can be moved into the cgroup. Note that this isn't
called on a fork. If this method returns 0 (success) then this should
remain valid while the caller holds cgroup_mutex.
remain valid while the caller holds cgroup_mutex. If threadgroup is
true, then a successful result indicates that all threads in the given
thread's threadgroup can be moved together.
void attach(struct cgroup_subsys *ss, struct cgroup *cgrp,
struct cgroup *old_cgrp, struct task_struct *task)
struct cgroup *old_cgrp, struct task_struct *task,
bool threadgroup)
(cgroup_mutex held by caller)
Called after the task has been attached to the cgroup, to allow any
post-attachment activity that requires memory allocations or blocking.
If threadgroup is true, the subsystem should take care of all threads
in the specified thread's threadgroup. Currently does not support any
subsystem that might need the old_cgrp for every thread in the group.
void fork(struct cgroup_subsy *ss, struct task_struct *task)
......
Documentation/cgroups/memory.txt
浏览文件 @ d9b2002c
......@@ -179,6 +179,9 @@ The reclaim algorithm has not been modified for cgroups, except that
pages that are selected for reclaiming come from the per cgroup LRU
list.
NOTE: Reclaim does not work for the root cgroup, since we cannot set any
limits on the root cgroup.
2. Locking
The memory controller uses the following hierarchy
......@@ -210,6 +213,7 @@ We can alter the memory limit:
NOTE: We can use a suffix (k, K, m, M, g or G) to indicate values in kilo,
mega or gigabytes.
NOTE: We can write "-1" to reset the *.limit_in_bytes(unlimited).
NOTE: We cannot set limits on the root cgroup any more.
# cat /cgroups/0/memory.limit_in_bytes
4194304
......@@ -375,7 +379,42 @@ cgroups created below it.
NOTE2: This feature can be enabled/disabled per subtree.
7. TODO
7. Soft limits
Soft limits allow for greater sharing of memory. The idea behind soft limits
is to allow control groups to use as much of the memory as needed, provided
a. There is no memory contention
b. They do not exceed their hard limit
When the system detects memory contention or low memory control groups
are pushed back to their soft limits. If the soft limit of each control
group is very high, they are pushed back as much as possible to make
sure that one control group does not starve the others of memory.
Please note that soft limits is a best effort feature, it comes with
no guarantees, but it does its best to make sure that when memory is
heavily contended for, memory is allocated based on the soft limit
hints/setup. Currently soft limit based reclaim is setup such that
it gets invoked from balance_pgdat (kswapd).
7.1 Interface
Soft limits can be setup by using the following commands (in this example we
assume a soft limit of 256 megabytes)
# echo 256M > memory.soft_limit_in_bytes
If we want to change this to 1G, we can at any time use
# echo 1G > memory.soft_limit_in_bytes
NOTE1: Soft limits take effect over a long period of time, since they involve
reclaiming memory for balancing between memory cgroups
NOTE2: It is recommended to set the soft limit always below the hard limit,
otherwise the hard limit will take precedence.
8. TODO
1. Add support for accounting huge pages (as a separate controller)
2. Make per-cgroup scanner reclaim not-shared pages first
......
Documentation/crypto/async-tx-api.txt
浏览文件 @ d9b2002c
......@@ -54,20 +54,23 @@ features surfaced as a result:
3.1 General format of the API:
struct dma_async_tx_descriptor *
async_<operation>(<op specific parameters>,
enum async_tx_flags flags,
struct dma_async_tx_descriptor *dependency,
dma_async_tx_callback callback_routine,
void *callback_parameter);
async_<operation>(<op specific parameters>, struct async_submit ctl *submit)
3.2 Supported operations:
memcpy - memory copy between a source and a destination buffer
memset - fill a destination buffer with a byte value
xor - xor a series of source buffers and write the result to a
destination buffer
xor_zero_sum - xor a series of source buffers and set a flag if the
result is zero. The implementation attempts to prevent
writes to memory
memcpy - memory copy between a source and a destination buffer
memset - fill a destination buffer with a byte value
xor - xor a series of source buffers and write the result to a
destination buffer
xor_val - xor a series of source buffers and set a flag if the
result is zero. The implementation attempts to prevent
writes to memory
pq - generate the p+q (raid6 syndrome) from a series of source buffers
pq_val - validate that a p and or q buffer are in sync with a given series of
sources
datap - (raid6_datap_recov) recover a raid6 data block and the p block
from the given sources
2data - (raid6_2data_recov) recover 2 raid6 data blocks from the given
sources
3.3 Descriptor management:
The return value is non-NULL and points to a 'descriptor' when the operation
......@@ -80,8 +83,8 @@ acknowledged by the application before the offload engine driver is allowed to
recycle (or free) the descriptor. A descriptor can be acked by one of the
following methods:
1/ setting the ASYNC_TX_ACK flag if no child operations are to be submitted
2/ setting the ASYNC_TX_DEP_ACK flag to acknowledge the parent
descriptor of a new operation.
2/ submitting an unacknowledged descriptor as a dependency to another
async_tx call will implicitly set the acknowledged state.
3/ calling async_tx_ack() on the descriptor.
3.4 When does the operation execute?
......@@ -119,30 +122,42 @@ of an operation.
Perform a xor->copy->xor operation where each operation depends on the
result from the previous operation:
void complete_xor_copy_xor(void *param)
void callback(void *param)
{
printk("complete\n");
struct completion *cmp = param;
complete(cmp);
}
int run_xor_copy_xor(struct page **xor_srcs,
int xor_src_cnt,
struct page *xor_dest,
size_t xor_len,
struct page *copy_src,
struct page *copy_dest,
size_t copy_len)
void run_xor_copy_xor(struct page **xor_srcs,
int xor_src_cnt,
struct page *xor_dest,
size_t xor_len,
struct page *copy_src,
struct page *copy_dest,
size_t copy_len)
{
struct dma_async_tx_descriptor *tx;
addr_conv_t addr_conv[xor_src_cnt];
struct async_submit_ctl submit;
addr_conv_t addr_conv[NDISKS];
struct completion cmp;
init_async_submit(&submit, ASYNC_TX_XOR_DROP_DST, NULL, NULL, NULL,
addr_conv);
tx = async_xor(xor_dest, xor_srcs, 0, xor_src_cnt, xor_len, &submit)
tx = async_xor(xor_dest, xor_srcs, 0, xor_src_cnt, xor_len,
ASYNC_TX_XOR_DROP_DST, NULL, NULL, NULL);
tx = async_memcpy(copy_dest, copy_src, 0, 0, copy_len,
ASYNC_TX_DEP_ACK, tx, NULL, NULL);
tx = async_xor(xor_dest, xor_srcs, 0, xor_src_cnt, xor_len,
ASYNC_TX_XOR_DROP_DST | ASYNC_TX_DEP_ACK | ASYNC_TX_ACK,
tx, complete_xor_copy_xor, NULL);
submit->depend_tx = tx;
tx = async_memcpy(copy_dest, copy_src, 0, 0, copy_len, &submit);
init_completion(&cmp);
init_async_submit(&submit, ASYNC_TX_XOR_DROP_DST | ASYNC_TX_ACK, tx,
callback, &cmp, addr_conv);
tx = async_xor(xor_dest, xor_srcs, 0, xor_src_cnt, xor_len, &submit);
async_tx_issue_pending_all();
wait_for_completion(&cmp);
}
See include/linux/async_tx.h for more information on the flags. See the
......
Documentation/fb/ep93xx-fb.txt 0 → 100644
浏览文件 @ d9b2002c
================================
Driver for EP93xx LCD controller
================================
The EP93xx LCD controller can drive both standard desktop monitors and
embedded LCD displays. If you have a standard desktop monitor then you
can use the standard Linux video mode database. In your board file:
static struct ep93xxfb_mach_info some_board_fb_info = {
.num_modes = EP93XXFB_USE_MODEDB,
.bpp = 16,
};
If you have an embedded LCD display then you need to define a video
mode for it as follows:
static struct fb_videomode some_board_video_modes[] = {
{
.name = "some_lcd_name",
/* Pixel clock, porches, etc */
},
};
Note that the pixel clock value is in pico-seconds. You can use the
KHZ2PICOS macro to convert the pixel clock value. Most other values
are in pixel clocks. See Documentation/fb/framebuffer.txt for further
details.
The ep93xxfb_mach_info structure for your board should look like the
following:
static struct ep93xxfb_mach_info some_board_fb_info = {
.num_modes = ARRAY_SIZE(some_board_video_modes),
.modes = some_board_video_modes,
.default_mode = &some_board_video_modes[0],
.bpp = 16,
};
The framebuffer device can be registered by adding the following to
your board initialisation function:
ep93xx_register_fb(&some_board_fb_info);
=====================
Video Attribute Flags
=====================
The ep93xxfb_mach_info structure has a flags field which can be used
to configure the controller. The video attributes flags are fully
documented in section 7 of the EP93xx users' guide. The following
flags are available:
EP93XXFB_PCLK_FALLING Clock data on the falling edge of the
pixel clock. The default is to clock
data on the rising edge.
EP93XXFB_SYNC_BLANK_HIGH Blank signal is active high. By
default the blank signal is active low.
EP93XXFB_SYNC_HORIZ_HIGH Horizontal sync is active high. By
default the horizontal sync is active low.
EP93XXFB_SYNC_VERT_HIGH Vertical sync is active high. By
default the vertical sync is active high.
The physical address of the framebuffer can be controlled using the
following flags:
EP93XXFB_USE_SDCSN0 Use SDCSn[0] for the framebuffer. This
is the default setting.
EP93XXFB_USE_SDCSN1 Use SDCSn[1] for the framebuffer.
EP93XXFB_USE_SDCSN2 Use SDCSn[2] for the framebuffer.
EP93XXFB_USE_SDCSN3 Use SDCSn[3] for the framebuffer.
==================
Platform callbacks
==================
The EP93xx framebuffer driver supports three optional platform
callbacks: setup, teardown and blank. The setup and teardown functions
are called when the framebuffer driver is installed and removed
respectively. The blank function is called whenever the display is
blanked or unblanked.
The setup and teardown devices pass the platform_device structure as
an argument. The fb_info and ep93xxfb_mach_info structures can be
obtained as follows:
static int some_board_fb_setup(struct platform_device *pdev)
{
struct ep93xxfb_mach_info *mach_info = pdev->dev.platform_data;
struct fb_info *fb_info = platform_get_drvdata(pdev);
/* Board specific framebuffer setup */
}
======================
Setting the video mode
======================
The video mode is set using the following syntax:
video=XRESxYRES[-BPP][@REFRESH]
If the EP93xx video driver is built-in then the video mode is set on
the Linux kernel command line, for example:
video=ep93xx-fb:800x600-16@60
If the EP93xx video driver is built as a module then the video mode is
set when the module is installed:
modprobe ep93xx-fb video=320x240
==============
Screenpage bug
==============
At least on the EP9315 there is a silicon bug which causes bit 27 of
the VIDSCRNPAGE (framebuffer physical offset) to be tied low. There is
an unofficial errata for this bug at:
http://marc.info/?l=linux-arm-kernel&m=110061245502000&w=2
By default the EP93xx framebuffer driver checks if the allocated physical
address has bit 27 set. If it does, then the memory is freed and an
error is returned. The check can be disabled by adding the following
option when loading the driver:
ep93xx-fb.check_screenpage_bug=0
In some cases it may be possible to reconfigure your SDRAM layout to
avoid this bug. See section 13 of the EP93xx users' guide for details.
Documentation/fb/matroxfb.txt
浏览文件 @ d9b2002c
......@@ -186,9 +186,7 @@ noinverse - show true colors on screen. It is default.
dev:X - bind driver to device X. Driver numbers device from 0 up to N,
where device 0 is first `known' device found, 1 second and so on.
lspci lists devices in this order.
Default is `every' known device for driver with multihead support
and first working device (usually dev:0) for driver without
multihead support.
Default is `every' known device.
nohwcursor - disables hardware cursor (use software cursor instead).
hwcursor - enables hardware cursor. It is default. If you are using
non-accelerated mode (`noaccel' or `fbset -accel false'), software
......
Documentation/feature-removal-schedule.txt
浏览文件 @ d9b2002c
......@@ -354,14 +354,6 @@ Who: Krzysztof Piotr Oledzki <ole@ans.pl>
---------------------------
What: fscher and fscpos drivers
When: June 2009
Why: Deprecated by the new fschmd driver.
Who: Hans de Goede <hdegoede@redhat.com>
Jean Delvare <khali@linux-fr.org>
---------------------------
What: sysfs ui for changing p4-clockmod parameters
When: September 2009
Why: See commits 129f8ae9b1b5be94517da76009ea956e89104ce8 and
......
Documentation/filesystems/9p.txt
浏览文件 @ d9b2002c
......@@ -18,11 +18,11 @@ the 9p client is available in the form of a USENIX paper:
Other applications are described in the following papers:
* XCPU & Clustering
http://www.xcpu.org/xcpu-talk.pdf
http://xcpu.org/papers/xcpu-talk.pdf
* KVMFS: control file system for KVM
http://www.xcpu.org/kvmfs.pdf
* CellFS: A New ProgrammingModel for the Cell BE
http://www.xcpu.org/cellfs-talk.pdf
http://xcpu.org/papers/kvmfs.pdf
* CellFS: A New Programming Model for the Cell BE
http://xcpu.org/papers/cellfs-talk.pdf
* PROSE I/O: Using 9p to enable Application Partitions
http://plan9.escet.urjc.es/iwp9/cready/PROSE_iwp9_2006.pdf
......@@ -48,6 +48,7 @@ OPTIONS
(see rfdno and wfdno)
virtio - connect to the next virtio channel available
(from lguest or KVM with trans_virtio module)
rdma - connect to a specified RDMA channel
uname=name user name to attempt mount as on the remote server. The
server may override or ignore this value. Certain user
......@@ -59,16 +60,22 @@ OPTIONS
cache=mode specifies a caching policy. By default, no caches are used.
loose = no attempts are made at consistency,
intended for exclusive, read-only mounts
fscache = use FS-Cache for a persistent, read-only
cache backend.
debug=n specifies debug level. The debug level is a bitmask.
0x01 = display verbose error messages
0x02 = developer debug (DEBUG_CURRENT)
0x04 = display 9p trace
0x08 = display VFS trace
0x10 = display Marshalling debug
0x20 = display RPC debug
0x40 = display transport debug
0x80 = display allocation debug
0x01 = display verbose error messages
0x02 = developer debug (DEBUG_CURRENT)
0x04 = display 9p trace
0x08 = display VFS trace
0x10 = display Marshalling debug
0x20 = display RPC debug
0x40 = display transport debug
0x80 = display allocation debug
0x100 = display protocol message debug
0x200 = display Fid debug
0x400 = display packet debug
0x800 = display fscache tracing debug
rfdno=n the file descriptor for reading with trans=fd
......@@ -100,6 +107,10 @@ OPTIONS
any = v9fs does single attach and performs all
operations as one user
cachetag cache tag to use the specified persistent cache.
cache tags for existing cache sessions can be listed at
/sys/fs/9p/caches. (applies only to cache=fscache)
RESOURCES
=========
......@@ -118,7 +129,7 @@ and export.
A Linux version of the 9p server is now maintained under the npfs project
on sourceforge (http://sourceforge.net/projects/npfs). The currently
maintained version is the single-threaded version of the server (named spfs)
available from the same CVS repository.
available from the same SVN repository.
There are user and developer mailing lists available through the v9fs project
on sourceforge (http://sourceforge.net/projects/v9fs).
......@@ -126,7 +137,8 @@ on sourceforge (http://sourceforge.net/projects/v9fs).
A stand-alone version of the module (which should build for any 2.6 kernel)
is available via (http://github.com/ericvh/9p-sac/tree/master)
News and other information is maintained on SWiK (http://swik.net/v9fs).
News and other information is maintained on SWiK (http://swik.net/v9fs)
and the Wiki (http://sf.net/apps/mediawiki/v9fs/index.php).
Bug reports may be issued through the kernel.org bugzilla
(http://bugzilla.kernel.org)
......
Documentation/filesystems/ncpfs.txt
浏览文件 @ d9b2002c
......@@ -7,6 +7,6 @@ ftp.gwdg.de/pub/linux/misc/ncpfs, but sunsite and its many mirrors
will have it as well.
Related products are linware and mars_nwe, which will give Linux partial
NetWare server functionality. Linware's home site is
klokan.sh.cvut.cz/pub/linux/linware; mars_nwe can be found on
ftp.gwdg.de/pub/linux/misc/ncpfs.
NetWare server functionality.
mars_nwe can be found on ftp.gwdg.de/pub/linux/misc/ncpfs.
Documentation/filesystems/nfs41-server.txt
浏览文件 @ d9b2002c
......@@ -11,6 +11,11 @@ the /proc/fs/nfsd/versions control file. Note that to write this
control file, the nfsd service must be taken down. Use your user-mode
nfs-utils to set this up; see rpc.nfsd(8)
(Warning: older servers will interpret "+4.1" and "-4.1" as "+4" and
"-4", respectively. Therefore, code meant to work on both new and old
kernels must turn 4.1 on or off *before* turning support for version 4
on or off; rpc.nfsd does this correctly.)
The NFSv4 minorversion 1 (NFSv4.1) implementation in nfsd is based
on the latest NFSv4.1 Internet Draft:
http://tools.ietf.org/html/draft-ietf-nfsv4-minorversion1-29
......@@ -25,6 +30,49 @@ are still under development out of tree.
See http://wiki.linux-nfs.org/wiki/index.php/PNFS_prototype_design
for more information.
The current implementation is intended for developers only: while it
does support ordinary file operations on clients we have tested against
(including the linux client), it is incomplete in ways which may limit
features unexpectedly, cause known bugs in rare cases, or cause
interoperability problems with future clients. Known issues:
- gss support is questionable: currently mounts with kerberos
from a linux client are possible, but we aren't really
conformant with the spec (for example, we don't use kerberos
on the backchannel correctly).
- no trunking support: no clients currently take advantage of
trunking, but this is a mandatory failure, and its use is
recommended to clients in a number of places. (E.g. to ensure
timely renewal in case an existing connection's retry timeouts
have gotten too long; see section 8.3 of the draft.)
Therefore, lack of this feature may cause future clients to
fail.
- Incomplete backchannel support: incomplete backchannel gss
support and no support for BACKCHANNEL_CTL mean that
callbacks (hence delegations and layouts) may not be
available and clients confused by the incomplete
implementation may fail.
- Server reboot recovery is unsupported; if the server reboots,
clients may fail.
- We do not support SSV, which provides security for shared
client-server state (thus preventing unauthorized tampering
with locks and opens, for example). It is mandatory for
servers to support this, though no clients use it yet.
- Mandatory operations which we do not support, such as
DESTROY_CLIENTID, FREE_STATEID, SECINFO_NO_NAME, and
TEST_STATEID, are not currently used by clients, but will be
(and the spec recommends their uses in common cases), and
clients should not be expected to know how to recover from the
case where they are not supported. This will eventually cause
interoperability failures.
In addition, some limitations are inherited from the current NFSv4
implementation:
- Incomplete delegation enforcement: if a file is renamed or
unlinked, a client holding a delegation may continue to
indefinitely allow opens of the file under the old name.
The table below, taken from the NFSv4.1 document, lists
the operations that are mandatory to implement (REQ), optional
(OPT), and NFSv4.0 operations that are required not to implement (MNI)
......@@ -142,6 +190,12 @@ NS*| CB_WANTS_CANCELLED | OPT | FDELG, | Section 20.10 |
Implementation notes:
DELEGPURGE:
* mandatory only for servers that support CLAIM_DELEGATE_PREV and/or
CLAIM_DELEG_PREV_FH (which allows clients to keep delegations that
persist across client reboots). Thus we need not implement this for
now.
EXCHANGE_ID:
* only SP4_NONE state protection supported
* implementation ids are ignored
......
Documentation/filesystems/nfsroot.txt
浏览文件 @ d9b2002c
......@@ -105,7 +105,7 @@ ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>
the client address and this parameter is NOT empty only
replies from the specified server are accepted.
Only required for for NFS root. That is autoconfiguration
Only required for NFS root. That is autoconfiguration
will not be triggered if it is missing and NFS root is not
in operation.
......
Documentation/filesystems/proc.txt
浏览文件 @ d9b2002c
......@@ -176,6 +176,7 @@ read the file /proc/PID/status:
CapBnd: ffffffffffffffff
voluntary_ctxt_switches: 0
nonvoluntary_ctxt_switches: 1
Stack usage: 12 kB
This shows you nearly the same information you would get if you viewed it with
the ps command. In fact, ps uses the proc file system to obtain its
......@@ -229,6 +230,7 @@ Table 1-2: Contents of the statm files (as of 2.6.30-rc7)
Mems_allowed_list Same as previous, but in "list format"
voluntary_ctxt_switches number of voluntary context switches
nonvoluntary_ctxt_switches number of non voluntary context switches
Stack usage: stack usage high water mark (round up to page size)
..............................................................................
Table 1-3: Contents of the statm files (as of 2.6.8-rc3)
......@@ -307,7 +309,7 @@ address perms offset dev inode pathname
08049000-0804a000 rw-p 00001000 03:00 8312 /opt/test
0804a000-0806b000 rw-p 00000000 00:00 0 [heap]
a7cb1000-a7cb2000 ---p 00000000 00:00 0
a7cb2000-a7eb2000 rw-p 00000000 00:00 0
a7cb2000-a7eb2000 rw-p 00000000 00:00 0 [threadstack:001ff4b4]
a7eb2000-a7eb3000 ---p 00000000 00:00 0
a7eb3000-a7ed5000 rw-p 00000000 00:00 0
a7ed5000-a8008000 r-xp 00000000 03:00 4222 /lib/libc.so.6
......@@ -343,6 +345,7 @@ is not associated with a file:
[stack] = the stack of the main process
[vdso] = the "virtual dynamic shared object",
the kernel system call handler
[threadstack:xxxxxxxx] = the stack of the thread, xxxxxxxx is the stack size
or if empty, the mapping is anonymous.
......@@ -375,6 +378,19 @@ of memory currently marked as referenced or accessed.
This file is only present if the CONFIG_MMU kernel configuration option is
enabled.
The /proc/PID/clear_refs is used to reset the PG_Referenced and ACCESSED/YOUNG
bits on both physical and virtual pages associated with a process.
To clear the bits for all the pages associated with the process
> echo 1 > /proc/PID/clear_refs
To clear the bits for the anonymous pages associated with the process
> echo 2 > /proc/PID/clear_refs
To clear the bits for the file mapped pages associated with the process
> echo 3 > /proc/PID/clear_refs
Any other value written to /proc/PID/clear_refs will have no effect.
1.2 Kernel data
---------------
......@@ -1032,9 +1048,9 @@ Various pieces of information about kernel activity are available in the
since the system first booted. For a quick look, simply cat the file:
> cat /proc/stat
cpu 2255 34 2290 22625563 6290 127 456 0
cpu0 1132 34 1441 11311718 3675 127 438 0
cpu1 1123 0 849 11313845 2614 0 18 0
cpu 2255 34 2290 22625563 6290 127 456 0 0
cpu0 1132 34 1441 11311718 3675 127 438 0 0
cpu1 1123 0 849 11313845 2614 0 18 0 0
intr 114930548 113199788 3 0 5 263 0 4 [... lots more numbers ...]
ctxt 1990473
btime 1062191376
......@@ -1056,6 +1072,7 @@ second). The meanings of the columns are as follows, from left to right:
- irq: servicing interrupts
- softirq: servicing softirqs
- steal: involuntary wait
- guest: running a guest
The "intr" line gives counts of interrupts serviced since boot time, for each
of the possible system interrupts. The first column is the total of all
......@@ -1191,7 +1208,7 @@ The following heuristics are then applied:
* if the task was reniced, its score doubles
* superuser or direct hardware access tasks (CAP_SYS_ADMIN, CAP_SYS_RESOURCE
or CAP_SYS_RAWIO) have their score divided by 4
* if oom condition happened in one cpuset and checked task does not belong
* if oom condition happened in one cpuset and checked process does not belong
to it, its score is divided by 8
* the resulting score is multiplied by two to the power of oom_adj, i.e.
points <<= oom_adj when it is positive and
......
Documentation/filesystems/sharedsubtree.txt
浏览文件 @ d9b2002c
......@@ -4,7 +4,7 @@ Shared Subtrees
Contents:
1) Overview
2) Features
3) smount command
3) Setting mount states
4) Use-case
5) Detailed semantics
6) Quiz
......@@ -41,14 +41,14 @@ replicas continue to be exactly same.
Here is an example:
Lets say /mnt has a mount that is shared.
Let's say /mnt has a mount that is shared.
mount --make-shared /mnt
note: mount command does not yet support the --make-shared flag.
I have included a small C program which does the same by executing
'smount /mnt shared'
Note: mount(8) command now supports the --make-shared flag,
so the sample 'smount' program is no longer needed and has been
removed.
#mount --bind /mnt /tmp
# mount --bind /mnt /tmp
The above command replicates the mount at /mnt to the mountpoint /tmp
and the contents of both the mounts remain identical.
......@@ -58,8 +58,8 @@ replicas continue to be exactly same.
#ls /tmp
a b c
Now lets say we mount a device at /tmp/a
#mount /dev/sd0 /tmp/a
Now let's say we mount a device at /tmp/a
# mount /dev/sd0 /tmp/a
#ls /tmp/a
t1 t2 t2
......@@ -80,21 +80,20 @@ replicas continue to be exactly same.
Here is an example:
Lets say /mnt has a mount which is shared.
#mount --make-shared /mnt
Let's say /mnt has a mount which is shared.
# mount --make-shared /mnt
Lets bind mount /mnt to /tmp
#mount --bind /mnt /tmp
Let's bind mount /mnt to /tmp
# mount --bind /mnt /tmp
the new mount at /tmp becomes a shared mount and it is a replica of
the mount at /mnt.
Now lets make the mount at /tmp; a slave of /mnt
#mount --make-slave /tmp
[or smount /tmp slave]
Now let's make the mount at /tmp; a slave of /mnt
# mount --make-slave /tmp
lets mount /dev/sd0 on /mnt/a
#mount /dev/sd0 /mnt/a
let's mount /dev/sd0 on /mnt/a
# mount /dev/sd0 /mnt/a
#ls /mnt/a
t1 t2 t3
......@@ -104,9 +103,9 @@ replicas continue to be exactly same.
Note the mount event has propagated to the mount at /tmp
However lets see what happens if we mount something on the mount at /tmp
However let's see what happens if we mount something on the mount at /tmp
#mount /dev/sd1 /tmp/b
# mount /dev/sd1 /tmp/b
#ls /tmp/b
s1 s2 s3
......@@ -124,12 +123,11 @@ replicas continue to be exactly same.
2d) A unbindable mount is a unbindable private mount
lets say we have a mount at /mnt and we make is unbindable
let's say we have a mount at /mnt and we make is unbindable
#mount --make-unbindable /mnt
[ smount /mnt unbindable ]
# mount --make-unbindable /mnt
Lets try to bind mount this mount somewhere else.
Let's try to bind mount this mount somewhere else.
# mount --bind /mnt /tmp
mount: wrong fs type, bad option, bad superblock on /mnt,
or too many mounted file systems
......@@ -137,149 +135,15 @@ replicas continue to be exactly same.
Binding a unbindable mount is a invalid operation.
3) smount command
3) Setting mount states
Currently the mount command is not aware of shared subtree features.
Work is in progress to add the support in mount ( util-linux package ).
Till then use the following program.
The mount command (util-linux package) can be used to set mount
states:
------------------------------------------------------------------------
//
//this code was developed my Miklos Szeredi <miklos@szeredi.hu>
//and modified by Ram Pai <linuxram@us.ibm.com>
// sample usage:
// smount /tmp shared
//
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <string.h>
#include <sys/mount.h>
#include <sys/fsuid.h>
#ifndef MS_REC
#define MS_REC 0x4000 /* 16384: Recursive loopback */
#endif
#ifndef MS_SHARED
#define MS_SHARED 1<<20 /* Shared */
#endif
#ifndef MS_PRIVATE
#define MS_PRIVATE 1<<18 /* Private */
#endif
#ifndef MS_SLAVE
#define MS_SLAVE 1<<19 /* Slave */
#endif
#ifndef MS_UNBINDABLE
#define MS_UNBINDABLE 1<<17 /* Unbindable */
#endif
int main(int argc, char *argv[])
{
int type;
if(argc != 3) {
fprintf(stderr, "usage: %s dir "
"<rshared|rslave|rprivate|runbindable|shared|slave"
"|private|unbindable>\n" , argv[0]);
return 1;
}
fprintf(stdout, "%s %s %s\n", argv[0], argv[1], argv[2]);
if (strcmp(argv[2],"rshared")==0)
type=(MS_SHARED|MS_REC);
else if (strcmp(argv[2],"rslave")==0)
type=(MS_SLAVE|MS_REC);
else if (strcmp(argv[2],"rprivate")==0)
type=(MS_PRIVATE|MS_REC);
else if (strcmp(argv[2],"runbindable")==0)
type=(MS_UNBINDABLE|MS_REC);
else if (strcmp(argv[2],"shared")==0)
type=MS_SHARED;
else if (strcmp(argv[2],"slave")==0)
type=MS_SLAVE;
else if (strcmp(argv[2],"private")==0)
type=MS_PRIVATE;
else if (strcmp(argv[2],"unbindable")==0)
type=MS_UNBINDABLE;
else {
fprintf(stderr, "invalid operation: %s\n", argv[2]);
return 1;
}
setfsuid(getuid());
if(mount("", argv[1], "dontcare", type, "") == -1) {
perror("mount");
return 1;
}
return 0;
}
-----------------------------------------------------------------------
Copy the above code snippet into smount.c
gcc -o smount smount.c
(i) To mark all the mounts under /mnt as shared execute the following
command:
smount /mnt rshared
the corresponding syntax planned for mount command is
mount --make-rshared /mnt
just to mark a mount /mnt as shared, execute the following
command:
smount /mnt shared
the corresponding syntax planned for mount command is
mount --make-shared /mnt
(ii) To mark all the shared mounts under /mnt as slave execute the
following
command:
smount /mnt rslave
the corresponding syntax planned for mount command is
mount --make-rslave /mnt
just to mark a mount /mnt as slave, execute the following
command:
smount /mnt slave
the corresponding syntax planned for mount command is
mount --make-slave /mnt
(iii) To mark all the mounts under /mnt as private execute the
following command:
smount /mnt rprivate
the corresponding syntax planned for mount command is
mount --make-rprivate /mnt
just to mark a mount /mnt as private, execute the following
command:
smount /mnt private
the corresponding syntax planned for mount command is
mount --make-private /mnt
NOTE: by default all the mounts are created as private. But if
you want to change some shared/slave/unbindable mount as
private at a later point in time, this command can help.
(iv) To mark all the mounts under /mnt as unbindable execute the
following
command:
smount /mnt runbindable
the corresponding syntax planned for mount command is
mount --make-runbindable /mnt
just to mark a mount /mnt as unbindable, execute the following
command:
smount /mnt unbindable
the corresponding syntax planned for mount command is
mount --make-unbindable /mnt
mount --make-shared mountpoint
mount --make-slave mountpoint
mount --make-private mountpoint
mount --make-unbindable mountpoint
4) Use cases
......@@ -350,7 +214,7 @@ replicas continue to be exactly same.
mount --rbind / /view/v3
mount --rbind / /view/v4
and if /usr has a versioning filesystem mounted, than that
and if /usr has a versioning filesystem mounted, then that
mount appears at /view/v1/usr, /view/v2/usr, /view/v3/usr and
/view/v4/usr too
......@@ -390,7 +254,7 @@ replicas continue to be exactly same.
For example:
mount --make-shared /mnt
mount --bin /mnt /tmp
mount --bind /mnt /tmp
The mount at /mnt and that at /tmp are both shared and belong
to the same peer group. Anything mounted or unmounted under
......@@ -558,7 +422,7 @@ replicas continue to be exactly same.
then the subtree under the unbindable mount is pruned in the new
location.
eg: lets say we have the following mount tree.
eg: let's say we have the following mount tree.
A
/ \
......@@ -566,7 +430,7 @@ replicas continue to be exactly same.
/ \ / \
D E F G
Lets say all the mount except the mount C in the tree are
Let's say all the mount except the mount C in the tree are
of a type other than unbindable.
If this tree is rbound to say Z
......@@ -683,13 +547,13 @@ replicas continue to be exactly same.
'b' on mounts that receive propagation from mount 'B' and does not have
sub-mounts within them are unmounted.
Example: Lets say 'B1', 'B2', 'B3' are shared mounts that propagate to
Example: Let's say 'B1', 'B2', 'B3' are shared mounts that propagate to
each other.
lets say 'A1', 'A2', 'A3' are first mounted at dentry 'b' on mount
let's say 'A1', 'A2', 'A3' are first mounted at dentry 'b' on mount
'B1', 'B2' and 'B3' respectively.
lets say 'C1', 'C2', 'C3' are next mounted at the same dentry 'b' on
let's say 'C1', 'C2', 'C3' are next mounted at the same dentry 'b' on
mount 'B1', 'B2' and 'B3' respectively.
if 'C1' is unmounted, all the mounts that are most-recently-mounted on
......@@ -710,7 +574,7 @@ replicas continue to be exactly same.
A cloned namespace contains all the mounts as that of the parent
namespace.
Lets say 'A' and 'B' are the corresponding mounts in the parent and the
Let's say 'A' and 'B' are the corresponding mounts in the parent and the
child namespace.
If 'A' is shared, then 'B' is also shared and 'A' and 'B' propagate to
......@@ -759,11 +623,11 @@ replicas continue to be exactly same.
mount --make-slave /mnt
At this point we have the first mount at /tmp and
its root dentry is 1. Lets call this mount 'A'
its root dentry is 1. Let's call this mount 'A'
And then we have a second mount at /tmp1 with root
dentry 2. Lets call this mount 'B'
dentry 2. Let's call this mount 'B'
Next we have a third mount at /mnt with root dentry
mnt. Lets call this mount 'C'
mnt. Let's call this mount 'C'
'B' is the slave of 'A' and 'C' is a slave of 'B'
A -> B -> C
......@@ -794,7 +658,7 @@ replicas continue to be exactly same.
Q3 Why is unbindable mount needed?
Lets say we want to replicate the mount tree at multiple
Let's say we want to replicate the mount tree at multiple
locations within the same subtree.
if one rbind mounts a tree within the same subtree 'n' times
......@@ -803,7 +667,7 @@ replicas continue to be exactly same.
mounts. Here is a example.
step 1:
lets say the root tree has just two directories with
let's say the root tree has just two directories with
one vfsmount.
root
/ \
......@@ -875,7 +739,7 @@ replicas continue to be exactly same.
Unclonable mounts come in handy here.
step 1:
lets say the root tree has just two directories with
let's say the root tree has just two directories with
one vfsmount.
root
/ \
......
Documentation/filesystems/vfs.txt
浏览文件 @ d9b2002c
......@@ -536,6 +536,7 @@ struct address_space_operations {
/* migrate the contents of a page to the specified target */
int (*migratepage) (struct page *, struct page *);
int (*launder_page) (struct page *);
int (*error_remove_page) (struct mapping *mapping, struct page *page);
};
writepage: called by the VM to write a dirty page to backing store.
......@@ -694,6 +695,12 @@ struct address_space_operations {
prevent redirtying the page, it is kept locked during the whole
operation.
error_remove_page: normally set to generic_error_remove_page if truncation
is ok for this address space. Used for memory failure handling.
Setting this implies you deal with pages going away under you,
unless you have them locked or reference counts increased.
The File Object
===============
......
Documentation/gcov.txt
浏览文件 @ d9b2002c
......@@ -47,7 +47,7 @@ Possible uses:
Configure the kernel with:
CONFIG_DEBUGFS=y
CONFIG_DEBUG_FS=y
CONFIG_GCOV_KERNEL=y
and to get coverage data for the entire kernel:
......
Documentation/gpio.txt
浏览文件 @ d9b2002c
......@@ -524,6 +524,13 @@ and have the following read/write attributes:
is configured as an output, this value may be written;
any nonzero value is treated as high.
"edge" ... reads as either "none", "rising", "falling", or
"both". Write these strings to select the signal edge(s)
that will make poll(2) on the "value" file return.
This file exists only if the pin can be configured as an
interrupt generating input pin.
GPIO controllers have paths like /sys/class/gpio/chipchip42/ (for the
controller implementing GPIOs starting at #42) and have the following
read-only attributes:
......@@ -555,6 +562,11 @@ requested using gpio_request():
/* reverse gpio_export() */
void gpio_unexport();
/* create a sysfs link to an exported GPIO node */
int gpio_export_link(struct device *dev, const char *name,
unsigned gpio)
After a kernel driver requests a GPIO, it may only be made available in
the sysfs interface by gpio_export(). The driver can control whether the
signal direction may change. This helps drivers prevent userspace code
......@@ -563,3 +575,8 @@ from accidentally clobbering important system state.
This explicit exporting can help with debugging (by making some kinds
of experiments easier), or can provide an always-there interface that's
suitable for documenting as part of a board support package.
After the GPIO has been exported, gpio_export_link() allows creating
symlinks from elsewhere in sysfs to the GPIO sysfs node. Drivers can
use this to provide the interface under their own device in sysfs with
a descriptive name.
Documentation/hwmon/acpi_power_meter 0 → 100644
浏览文件 @ d9b2002c
Kernel driver power_meter
=========================
This driver talks to ACPI 4.0 power meters.
Supported systems:
* Any recent system with ACPI 4.0.
Prefix: 'power_meter'
Datasheet: http://acpi.info/, section 10.4.
Author: Darrick J. Wong
Description
-----------
This driver implements sensor reading support for the power meters exposed in
the ACPI 4.0 spec (Chapter 10.4). These devices have a simple set of
features--a power meter that returns average power use over a configurable
interval, an optional capping mechanism, and a couple of trip points. The
sysfs interface conforms with the specification outlined in the "Power" section
of Documentation/hwmon/sysfs-interface.
Special Features
----------------
The power[1-*]_is_battery knob indicates if the power supply is a battery.
Both power[1-*]_average_{min,max} must be set before the trip points will work.
When both of them are set, an ACPI event will be broadcast on the ACPI netlink
socket and a poll notification will be sent to the appropriate
power[1-*]_average sysfs file.
The power[1-*]_{model_number, serial_number, oem_info} fields display arbitrary
strings that ACPI provides with the meter. The measures/ directory contains
symlinks to the devices that this meter measures.
Some computers have the ability to enforce a power cap in hardware. If this is
the case, the power[1-*]_cap and related sysfs files will appear. When the
average power consumption exceeds the cap, an ACPI event will be broadcast on
the netlink event socket and a poll notification will be sent to the
appropriate power[1-*]_alarm file to indicate that capping has begun, and the
hardware has taken action to reduce power consumption. Most likely this will
result in reduced performance.
There are a few other ACPI notifications that can be sent by the firmware. In
all cases the ACPI event will be broadcast on the ACPI netlink event socket as
well as sent as a poll notification to a sysfs file. The events are as
follows:
power[1-*]_cap will be notified if the firmware changes the power cap.
power[1-*]_interval will be notified if the firmware changes the averaging
interval.
Documentation/hwmon/coretemp
浏览文件 @ d9b2002c
......@@ -4,7 +4,9 @@ Kernel driver coretemp
Supported chips:
* All Intel Core family
Prefix: 'coretemp'
CPUID: family 0x6, models 0xe, 0xf, 0x16, 0x17
CPUID: family 0x6, models 0xe (Pentium M DC), 0xf (Core 2 DC 65nm),
0x16 (Core 2 SC 65nm), 0x17 (Penryn 45nm),
0x1a (Nehalem), 0x1c (Atom), 0x1e (Lynnfield)
Datasheet: Intel 64 and IA-32 Architectures Software Developer's Manual
Volume 3A: System Programming Guide
http://softwarecommunity.intel.com/Wiki/Mobility/720.htm
......
Documentation/hwmon/fscher 已删除 100644 → 0
浏览文件 @ c3b32fcb
Kernel driver fscher
====================
Supported chips:
* Fujitsu-Siemens Hermes chip
Prefix: 'fscher'
Addresses scanned: I2C 0x73
Authors:
Reinhard Nissl <rnissl@gmx.de> based on work
from Hermann Jung <hej@odn.de>,
Frodo Looijaard <frodol@dds.nl>,
Philip Edelbrock <phil@netroedge.com>
Description
-----------
This driver implements support for the Fujitsu-Siemens Hermes chip. It is
described in the 'Register Set Specification BMC Hermes based Systemboard'
from Fujitsu-Siemens.
The Hermes chip implements a hardware-based system management, e.g. for
controlling fan speed and core voltage. There is also a watchdog counter on
the chip which can trigger an alarm and even shut the system down.
The chip provides three temperature values (CPU, motherboard and
auxiliary), three voltage values (+12V, +5V and battery) and three fans
(power supply, CPU and auxiliary).
Temperatures are measured in degrees Celsius. The resolution is 1 degree.
Fan rotation speeds are reported in RPM (rotations per minute). The value
can be divided by a programmable divider (1, 2 or 4) which is stored on
the chip.
Voltage sensors (also known as "in" sensors) report their values in volts.
All values are reported as final values from the driver. There is no need
for further calculations.
Detailed description
--------------------
Below you'll find a single line description of all the bit values. With
this information, you're able to decode e. g. alarms, wdog, etc. To make
use of the watchdog, you'll need to set the watchdog time and enable the
watchdog. After that it is necessary to restart the watchdog time within
the specified period of time, or a system reset will occur.
* revision
READING & 0xff = 0x??: HERMES revision identification
* alarms
READING & 0x80 = 0x80: CPU throttling active
READING & 0x80 = 0x00: CPU running at full speed
READING & 0x10 = 0x10: software event (see control:1)
READING & 0x10 = 0x00: no software event
READING & 0x08 = 0x08: watchdog event (see wdog:2)
READING & 0x08 = 0x00: no watchdog event
READING & 0x02 = 0x02: thermal event (see temp*:1)
READING & 0x02 = 0x00: no thermal event
READING & 0x01 = 0x01: fan event (see fan*:1)
READING & 0x01 = 0x00: no fan event
READING & 0x13 ! 0x00: ALERT LED is flashing
* control
READING & 0x01 = 0x01: software event
READING & 0x01 = 0x00: no software event
WRITING & 0x01 = 0x01: set software event
WRITING & 0x01 = 0x00: clear software event
* watchdog_control
READING & 0x80 = 0x80: power off on watchdog event while thermal event
READING & 0x80 = 0x00: watchdog power off disabled (just system reset enabled)
READING & 0x40 = 0x40: watchdog timebase 60 seconds (see also wdog:1)
READING & 0x40 = 0x00: watchdog timebase 2 seconds
READING & 0x10 = 0x10: watchdog enabled
READING & 0x10 = 0x00: watchdog disabled
WRITING & 0x80 = 0x80: enable "power off on watchdog event while thermal event"
WRITING & 0x80 = 0x00: disable "power off on watchdog event while thermal event"
WRITING & 0x40 = 0x40: set watchdog timebase to 60 seconds
WRITING & 0x40 = 0x00: set watchdog timebase to 2 seconds
WRITING & 0x20 = 0x20: disable watchdog
WRITING & 0x10 = 0x10: enable watchdog / restart watchdog time
* watchdog_state
READING & 0x02 = 0x02: watchdog system reset occurred
READING & 0x02 = 0x00: no watchdog system reset occurred
WRITING & 0x02 = 0x02: clear watchdog event
* watchdog_preset
READING & 0xff = 0x??: configured watch dog time in units (see wdog:3 0x40)
WRITING & 0xff = 0x??: configure watch dog time in units
* in* (0: +5V, 1: +12V, 2: onboard 3V battery)
READING: actual voltage value
* temp*_status (1: CPU sensor, 2: onboard sensor, 3: auxiliary sensor)
READING & 0x02 = 0x02: thermal event (overtemperature)
READING & 0x02 = 0x00: no thermal event
READING & 0x01 = 0x01: sensor is working
READING & 0x01 = 0x00: sensor is faulty
WRITING & 0x02 = 0x02: clear thermal event
* temp*_input (1: CPU sensor, 2: onboard sensor, 3: auxiliary sensor)
READING: actual temperature value
* fan*_status (1: power supply fan, 2: CPU fan, 3: auxiliary fan)
READING & 0x04 = 0x04: fan event (fan fault)
READING & 0x04 = 0x00: no fan event
WRITING & 0x04 = 0x04: clear fan event
* fan*_div (1: power supply fan, 2: CPU fan, 3: auxiliary fan)
Divisors 2,4 and 8 are supported, both for reading and writing
* fan*_pwm (1: power supply fan, 2: CPU fan, 3: auxiliary fan)
READING & 0xff = 0x00: fan may be switched off
READING & 0xff = 0x01: fan must run at least at minimum speed (supply: 6V)
READING & 0xff = 0xff: fan must run at maximum speed (supply: 12V)
READING & 0xff = 0x??: fan must run at least at given speed (supply: 6V..12V)
WRITING & 0xff = 0x00: fan may be switched off
WRITING & 0xff = 0x01: fan must run at least at minimum speed (supply: 6V)
WRITING & 0xff = 0xff: fan must run at maximum speed (supply: 12V)
WRITING & 0xff = 0x??: fan must run at least at given speed (supply: 6V..12V)
* fan*_input (1: power supply fan, 2: CPU fan, 3: auxiliary fan)
READING: actual RPM value
Limitations
-----------
* Measuring fan speed
It seems that the chip counts "ripples" (typical fans produce 2 ripples per
rotation while VERAX fans produce 18) in a 9-bit register. This register is
read out every second, then the ripple prescaler (2, 4 or 8) is applied and
the result is stored in the 8 bit output register. Due to the limitation of
the counting register to 9 bits, it is impossible to measure a VERAX fan
properly (even with a prescaler of 8). At its maximum speed of 3500 RPM the
fan produces 1080 ripples per second which causes the counting register to
overflow twice, leading to only 186 RPM.
* Measuring input voltages
in2 ("battery") reports the voltage of the onboard lithium battery and not
+3.3V from the power supply.
* Undocumented features
Fujitsu-Siemens Computers has not documented all features of the chip so
far. Their software, System Guard, shows that there are a still some
features which cannot be controlled by this implementation.
Documentation/hwmon/hpfall.c
浏览文件 @ d9b2002c
......@@ -16,6 +16,34 @@
#include <stdint.h>
#include <errno.h>
#include <signal.h>
#include <sys/mman.h>
#include <sched.h>
char unload_heads_path[64];
int set_unload_heads_path(char *device)
{
char devname[64];
if (strlen(device) <= 5 || strncmp(device, "/dev/", 5) != 0)
return -EINVAL;
strncpy(devname, device + 5, sizeof(devname));
snprintf(unload_heads_path, sizeof(unload_heads_path),
"/sys/block/%s/device/unload_heads", devname);
return 0;
}
int valid_disk(void)
{
int fd = open(unload_heads_path, O_RDONLY);
if (fd < 0) {
perror(unload_heads_path);
return 0;
}
close(fd);
return 1;
}
void write_int(char *path, int i)
{
......@@ -40,7 +68,7 @@ void set_led(int on)
void protect(int seconds)
{
write_int("/sys/block/sda/device/unload_heads", seconds*1000);
write_int(unload_heads_path, seconds*1000);
}
int on_ac(void)
......@@ -57,45 +85,62 @@ void ignore_me(void)
{
protect(0);
set_led(0);
}
int main(int argc, char* argv[])
int main(int argc, char **argv)
{
int fd, ret;
int fd, ret;
struct sched_param param;
if (argc == 1)
ret = set_unload_heads_path("/dev/sda");
else if (argc == 2)
ret = set_unload_heads_path(argv[1]);
else
ret = -EINVAL;
if (ret || !valid_disk()) {
fprintf(stderr, "usage: %s <device> (default: /dev/sda)\n",
argv[0]);
exit(1);
}
fd = open("/dev/freefall", O_RDONLY);
if (fd < 0) {
perror("/dev/freefall");
return EXIT_FAILURE;
}
fd = open("/dev/freefall", O_RDONLY);
if (fd < 0) {
perror("open");
return EXIT_FAILURE;
}
daemon(0, 0);
param.sched_priority = sched_get_priority_max(SCHED_FIFO);
sched_setscheduler(0, SCHED_FIFO, &param);
mlockall(MCL_CURRENT|MCL_FUTURE);
signal(SIGALRM, ignore_me);
for (;;) {
unsigned char count;
ret = read(fd, &count, sizeof(count));
alarm(0);
if ((ret == -1) && (errno == EINTR)) {
/* Alarm expired, time to unpark the heads */
continue;
}
if (ret != sizeof(count)) {
perror("read");
break;
}
protect(21);
set_led(1);
if (1 || on_ac() || lid_open()) {
alarm(2);
} else {
alarm(20);
}
}
close(fd);
return EXIT_SUCCESS;
for (;;) {
unsigned char count;
ret = read(fd, &count, sizeof(count));
alarm(0);
if ((ret == -1) && (errno == EINTR)) {
/* Alarm expired, time to unpark the heads */
continue;
}
if (ret != sizeof(count)) {
perror("read");
break;
}
protect(21);
set_led(1);
if (1 || on_ac() || lid_open())
alarm(2);
else
alarm(20);
}
close(fd);
return EXIT_SUCCESS;
}
Documentation/hwmon/pc87427
浏览文件 @ d9b2002c
......@@ -34,5 +34,5 @@ Fan rotation speeds are reported as 14-bit values from a gated clock
signal. Speeds down to 83 RPM can be measured.
An alarm is triggered if the rotation speed drops below a programmable
limit. Another alarm is triggered if the speed is too low to to be measured
limit. Another alarm is triggered if the speed is too low to be measured
(including stalled or missing fan).
Documentation/i2c/busses/i2c-piix4
浏览文件 @ d9b2002c
......@@ -8,6 +8,8 @@ Supported adapters:
Datasheet: Only available via NDA from ServerWorks
* ATI IXP200, IXP300, IXP400, SB600, SB700 and SB800 southbridges
Datasheet: Not publicly available
* AMD SB900
Datasheet: Not publicly available
* Standard Microsystems (SMSC) SLC90E66 (Victory66) southbridge
Datasheet: Publicly available at the SMSC website http://www.smsc.com
......
Documentation/i2c/chips/pca9539 已删除 100644 → 0
浏览文件 @ c3b32fcb
Kernel driver pca9539
=====================
NOTE: this driver is deprecated and will be dropped soon, use
drivers/gpio/pca9539.c instead.
Supported chips:
* Philips PCA9539
Prefix: 'pca9539'
Addresses scanned: none
Datasheet:
http://www.semiconductors.philips.com/acrobat/datasheets/PCA9539_2.pdf
Author: Ben Gardner <bgardner@wabtec.com>
Description
-----------
The Philips PCA9539 is a 16 bit low power I/O device.
All 16 lines can be individually configured as an input or output.
The input sense can also be inverted.
The 16 lines are split between two bytes.
Detection
---------
The PCA9539 is difficult to detect and not commonly found in PC machines,
so you have to pass the I2C bus and address of the installed PCA9539
devices explicitly to the driver at load time via the force=... parameter.
Sysfs entries
-------------
Each is a byte that maps to the 8 I/O bits.
A '0' suffix is for bits 0-7, while '1' is for bits 8-15.
input[01] - read the current value
output[01] - sets the output value
direction[01] - direction of each bit: 1=input, 0=output
invert[01] - toggle the input bit sense
input reads the actual state of the line and is always available.
The direction defaults to input for all channels.
General Remarks
---------------
Note that each output, direction, and invert entry controls 8 lines.
You should use the read, modify, write sequence.
For example. to set output bit 0 of 1.
val=$(cat output0)
val=$(( $val | 1 ))
echo $val > output0
Documentation/i2c/chips/pcf8574 已删除 100644 → 0
浏览文件 @ c3b32fcb
Kernel driver pcf8574
=====================
Supported chips:
* Philips PCF8574
Prefix: 'pcf8574'
Addresses scanned: none
Datasheet: Publicly available at the Philips Semiconductors website
http://www.semiconductors.philips.com/pip/PCF8574P.html
* Philips PCF8574A
Prefix: 'pcf8574a'
Addresses scanned: none
Datasheet: Publicly available at the Philips Semiconductors website
http://www.semiconductors.philips.com/pip/PCF8574P.html
Authors:
Frodo Looijaard <frodol@dds.nl>,
Philip Edelbrock <phil@netroedge.com>,
Dan Eaton <dan.eaton@rocketlogix.com>,
Aurelien Jarno <aurelien@aurel32.net>,
Jean Delvare <khali@linux-fr.org>,
Description
-----------
The PCF8574(A) is an 8-bit I/O expander for the I2C bus produced by Philips
Semiconductors. It is designed to provide a byte I2C interface to up to 16
separate devices (8 x PCF8574 and 8 x PCF8574A).
This device consists of a quasi-bidirectional port. Each of the eight I/Os
can be independently used as an input or output. To setup an I/O as an
input, you have to write a 1 to the corresponding output.
For more informations see the datasheet.
Accessing PCF8574(A) via /sys interface
-------------------------------------
The PCF8574(A) is plainly impossible to detect ! Stupid chip.
So, you have to pass the I2C bus and address of the installed PCF857A
and PCF8574A devices explicitly to the driver at load time via the
force=... parameter.
On detection (i.e. insmod, modprobe et al.), directories are being
created for each detected PCF8574(A):
/sys/bus/i2c/devices/<0>-<1>/
where <0> is the bus the chip was detected on (e. g. i2c-0)
and <1> the chip address ([20..27] or [38..3f]):
(example: /sys/bus/i2c/devices/1-0020/)
Inside these directories, there are two files each:
read and write (and one file with chip name).
The read file is read-only. Reading gives you the current I/O input
if the corresponding output is set as 1, otherwise the current output
value, that is to say 0.
The write file is read/write. Writing a value outputs it on the I/O
port. Reading returns the last written value. As it is not possible
to read this value from the chip, you need to write at least once to
this file before you can read back from it.
Documentation/i2c/chips/pcf8575 已删除 100644 → 0
浏览文件 @ c3b32fcb
About the PCF8575 chip and the pcf8575 kernel driver
====================================================
The PCF8575 chip is produced by the following manufacturers:
* Philips NXP
http://www.nxp.com/#/pip/cb=[type=product,path=50807/41735/41850,final=PCF8575_3]|pip=[pip=PCF8575_3][0]
* Texas Instruments
http://focus.ti.com/docs/prod/folders/print/pcf8575.html
Some vendors sell small PCB's with the PCF8575 mounted on it. You can connect
such a board to a Linux host via e.g. an USB to I2C interface. Examples of
PCB boards with a PCF8575:
* SFE Breakout Board for PCF8575 I2C Expander by RobotShop
http://www.robotshop.ca/home/products/robot-parts/electronics/adapters-converters/sfe-pcf8575-i2c-expander-board.html
* Breakout Board for PCF8575 I2C Expander by Spark Fun Electronics
http://www.sparkfun.com/commerce/product_info.php?products_id=8130
Description
-----------
The PCF8575 chip is a 16-bit I/O expander for the I2C bus. Up to eight of
these chips can be connected to the same I2C bus. You can find this
chip on some custom designed hardware, but you won't find it on PC
motherboards.
The PCF8575 chip consists of a 16-bit quasi-bidirectional port and an I2C-bus
interface. Each of the sixteen I/O's can be independently used as an input or
an output. To set up an I/O pin as an input, you have to write a 1 to the
corresponding output.
For more information please see the datasheet.
Detection
---------
There is no method known to detect whether a chip on a given I2C address is
a PCF8575 or whether it is any other I2C device, so you have to pass the I2C
bus and address of the installed PCF8575 devices explicitly to the driver at
load time via the force=... parameter.
/sys interface
--------------
For each address on which a PCF8575 chip was found or forced the following
files will be created under /sys:
* /sys/bus/i2c/devices/<bus>-<address>/read
* /sys/bus/i2c/devices/<bus>-<address>/write
where bus is the I2C bus number (0, 1, ...) and address is the four-digit
hexadecimal representation of the 7-bit I2C address of the PCF8575
(0020 .. 0027).
The read file is read-only. Reading it will trigger an I2C read and will hence
report the current input state for the pins configured as inputs, and the
current output value for the pins configured as outputs.
The write file is read-write. Writing a value to it will configure all pins
as output for which the corresponding bit is zero. Reading the write file will
return the value last written, or -EAGAIN if no value has yet been written to
the write file.
On module initialization the configuration of the chip is not changed -- the
chip is left in the state it was already configured in through either power-up
or through previous I2C write actions.
Documentation/ia64/aliasing-test.c
浏览文件 @ d9b2002c
......@@ -24,7 +24,7 @@
int sum;
int map_mem(char *path, off_t offset, size_t length, int touch)
static int map_mem(char *path, off_t offset, size_t length, int touch)
{
int fd, rc;
void *addr;
......@@ -62,7 +62,7 @@ int map_mem(char *path, off_t offset, size_t length, int touch)
return 0;
}
int scan_tree(char *path, char *file, off_t offset, size_t length, int touch)
static int scan_tree(char *path, char *file, off_t offset, size_t length, int touch)
{
struct dirent **namelist;
char *name, *path2;
......@@ -119,7 +119,7 @@ int scan_tree(char *path, char *file, off_t offset, size_t length, int touch)
char buf[1024];
int read_rom(char *path)
static int read_rom(char *path)
{
int fd, rc;
size_t size = 0;
......@@ -146,7 +146,7 @@ int read_rom(char *path)
return size;
}
int scan_rom(char *path, char *file)
static int scan_rom(char *path, char *file)
{
struct dirent **namelist;
char *name, *path2;
......
Documentation/ioctl/ioctl-number.txt
浏览文件 @ d9b2002c
......@@ -135,6 +135,7 @@ Code Seq# Include File Comments
<http://mikonos.dia.unisa.it/tcfs>
'l' 40-7F linux/udf_fs_i.h in development:
<http://sourceforge.net/projects/linux-udf/>
'm' 00-09 linux/mmtimer.h
'm' all linux/mtio.h conflict!
'm' all linux/soundcard.h conflict!
'm' all linux/synclink.h conflict!
......
Documentation/kbuild/kbuild.txt
浏览文件 @ d9b2002c
......@@ -65,6 +65,22 @@ INSTALL_PATH
INSTALL_PATH specifies where to place the updated kernel and system map
images. Default is /boot, but you can set it to other values.
INSTALLKERNEL
--------------------------------------------------
Install script called when using "make install".
The default name is "installkernel".
The script will be called with the following arguments:
$1 - kernel version
$2 - kernel image file
$3 - kernel map file
$4 - default install path (use root directory if blank)
The implmentation of "make install" is architecture specific
and it may differ from the above.
INSTALLKERNEL is provided to enable the possibility to
specify a custom installer when cross compiling a kernel.
MODLIB
--------------------------------------------------
......
Documentation/kbuild/makefiles.txt
浏览文件 @ d9b2002c
......@@ -18,6 +18,7 @@ This document describes the Linux kernel Makefiles.
--- 3.9 Dependency tracking
--- 3.10 Special Rules
--- 3.11 $(CC) support functions
--- 3.12 $(LD) support functions
=== 4 Host Program support
--- 4.1 Simple Host Program
......@@ -435,14 +436,14 @@ more details, with real examples.
The second argument is optional, and if supplied will be used
if first argument is not supported.
ld-option
ld-option is used to check if $(CC) when used to link object files
cc-ldoption
cc-ldoption is used to check if $(CC) when used to link object files
supports the given option. An optional second option may be
specified if first option are not supported.
Example:
#arch/i386/kernel/Makefile
vsyscall-flags += $(call ld-option, -Wl$(comma)--hash-style=sysv)
vsyscall-flags += $(call cc-ldoption, -Wl$(comma)--hash-style=sysv)
In the above example, vsyscall-flags will be assigned the option
-Wl$(comma)--hash-style=sysv if it is supported by $(CC).
......@@ -570,6 +571,19 @@ more details, with real examples.
endif
endif
--- 3.12 $(LD) support functions
ld-option
ld-option is used to check if $(LD) supports the supplied option.
ld-option takes two options as arguments.
The second argument is an optional option that can be used if the
first option is not supported by $(LD).
Example:
#Makefile
LDFLAGS_vmlinux += $(call really-ld-option, -X)
=== 4 Host Program support
Kbuild supports building executables on the host for use during the
......
Documentation/kernel-parameters.txt
浏览文件 @ d9b2002c
......@@ -671,7 +671,7 @@ and is between 256 and 4096 characters. It is defined in the file
earlyprintk= [X86,SH,BLACKFIN]
earlyprintk=vga
earlyprintk=serial[,ttySn[,baudrate]]
earlyprintk=dbgp
earlyprintk=dbgp[debugController#]
Append ",keep" to not disable it when the real console
takes over.
......@@ -933,7 +933,7 @@ and is between 256 and 4096 characters. It is defined in the file
1 -- enable informational integrity auditing messages.
ima_hash= [IMA]
Formt: { "sha1" | "md5" }
Format: { "sha1" | "md5" }
default: "sha1"
ima_tcb [IMA]
......
Documentation/kmemcheck.txt
浏览文件 @ d9b2002c
......@@ -43,26 +43,7 @@ feature.
1. Downloading
==============
kmemcheck can only be downloaded using git. If you want to write patches
against the current code, you should use the kmemcheck development branch of
the tip tree. It is also possible to use the linux-next tree, which also
includes the latest version of kmemcheck.
Assuming that you've already cloned the linux-2.6.git repository, all you
have to do is add the -tip tree as a remote, like this:
$ git remote add tip git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
To actually download the tree, fetch the remote:
$ git fetch tip
And to check out a new local branch with the kmemcheck code:
$ git checkout -b kmemcheck tip/kmemcheck
General instructions for the -tip tree can be found here:
http://people.redhat.com/mingo/tip.git/readme.txt
As of version 2.6.31-rc1, kmemcheck is included in the mainline kernel.
2. Configuring and compiling
......
Documentation/laptops/asus-laptop.txt 0 → 100644
浏览文件 @ d9b2002c
Asus Laptop Extras
Version 0.1
August 6, 2009
Corentin Chary <corentincj@iksaif.net>
http://acpi4asus.sf.net/
This driver provides support for extra features of ACPI-compatible ASUS laptops.
It may also support some MEDION, JVC or VICTOR laptops (such as MEDION 9675 or
VICTOR XP7210 for example). It makes all the extra buttons generate standard
ACPI events that go through /proc/acpi/events and input events (like keyboards).
On some models adds support for changing the display brightness and output,
switching the LCD backlight on and off, and most importantly, allows you to
blink those fancy LEDs intended for reporting mail and wireless status.
This driver supercedes the old asus_acpi driver.
Requirements
------------
Kernel 2.6.X sources, configured for your computer, with ACPI support.
You also need CONFIG_INPUT and CONFIG_ACPI.
Status
------
The features currently supported are the following (see below for
detailed description):
- Fn key combinations
- Bluetooth enable and disable
- Wlan enable and disable
- GPS enable and disable
- Video output switching
- Ambient Light Sensor on and off
- LED control
- LED Display control
- LCD brightness control
- LCD on and off
A compatibility table by model and feature is maintained on the web
site, http://acpi4asus.sf.net/.
Usage
-----
Try "modprobe asus_acpi". Check your dmesg (simply type dmesg). You should
see some lines like this :
Asus Laptop Extras version 0.42
L2D model detected.
If it is not the output you have on your laptop, send it (and the laptop's
DSDT) to me.
That's all, now, all the events generated by the hotkeys of your laptop
should be reported in your /proc/acpi/event entry. You can check with
"acpi_listen".
Hotkeys are also reported as input keys (like keyboards) you can check
which key are supported using "xev" under X11.
You can get informations on the version of your DSDT table by reading the
/sys/devices/platform/asus-laptop/infos entry. If you have a question or a
bug report to do, please include the output of this entry.
LEDs
----
You can modify LEDs be echoing values to /sys/class/leds/asus::*/brightness :
echo 1 > /sys/class/leds/asus::mail/brightness
will switch the mail LED on.
You can also know if they are on/off by reading their content and use
kernel triggers like ide-disk or heartbeat.
Backlight
---------
You can control lcd backlight power and brightness with
/sys/class/backlight/asus-laptop/. Brightness Values are between 0 and 15.
Wireless devices
---------------
You can turn the internal Bluetooth adapter on/off with the bluetooth entry
(only on models with Bluetooth). This usually controls the associated LED.
Same for Wlan adapter.
Display switching
-----------------
Note: the display switching code is currently considered EXPERIMENTAL.
Switching works for the following models:
L3800C
A2500H
L5800C
M5200N
W1000N (albeit with some glitches)
M6700R
A6JC
F3J
Switching doesn't work for the following:
M3700N
L2X00D (locks the laptop under certain conditions)
To switch the displays, echo values from 0 to 15 to
/sys/devices/platform/asus-laptop/display. The significance of those values
is as follows:
+-------+-----+-----+-----+-----+-----+
| Bin | Val | DVI | TV | CRT | LCD |
+-------+-----+-----+-----+-----+-----+
+ 0000 + 0 + + + + +
+-------+-----+-----+-----+-----+-----+
+ 0001 + 1 + + + + X +
+-------+-----+-----+-----+-----+-----+
+ 0010 + 2 + + + X + +
+-------+-----+-----+-----+-----+-----+
+ 0011 + 3 + + + X + X +
+-------+-----+-----+-----+-----+-----+
+ 0100 + 4 + + X + + +
+-------+-----+-----+-----+-----+-----+
+ 0101 + 5 + + X + + X +
+-------+-----+-----+-----+-----+-----+
+ 0110 + 6 + + X + X + +
+-------+-----+-----+-----+-----+-----+
+ 0111 + 7 + + X + X + X +
+-------+-----+-----+-----+-----+-----+
+ 1000 + 8 + X + + + +
+-------+-----+-----+-----+-----+-----+
+ 1001 + 9 + X + + + X +
+-------+-----+-----+-----+-----+-----+
+ 1010 + 10 + X + + X + +
+-------+-----+-----+-----+-----+-----+
+ 1011 + 11 + X + + X + X +
+-------+-----+-----+-----+-----+-----+
+ 1100 + 12 + X + X + + +
+-------+-----+-----+-----+-----+-----+
+ 1101 + 13 + X + X + + X +
+-------+-----+-----+-----+-----+-----+
+ 1110 + 14 + X + X + X + +
+-------+-----+-----+-----+-----+-----+
+ 1111 + 15 + X + X + X + X +
+-------+-----+-----+-----+-----+-----+
In most cases, the appropriate displays must be plugged in for the above
combinations to work. TV-Out may need to be initialized at boot time.
Debugging:
1) Check whether the Fn+F8 key:
a) does not lock the laptop (try disabling CONFIG_X86_UP_APIC or boot with
noapic / nolapic if it does)
b) generates events (0x6n, where n is the value corresponding to the
configuration above)
c) actually works
Record the disp value at every configuration.
2) Echo values from 0 to 15 to /sys/devices/platform/asus-laptop/display.
Record its value, note any change. If nothing changes, try a broader range,
up to 65535.
3) Send ANY output (both positive and negative reports are needed, unless your
machine is already listed above) to the acpi4asus-user mailing list.
Note: on some machines (e.g. L3C), after the module has been loaded, only 0x6n
events are generated and no actual switching occurs. In such a case, a line
like:
echo $((10#$arg-60)) > /sys/devices/platform/asus-laptop/display
will usually do the trick ($arg is the 0000006n-like event passed to acpid).
Note: there is currently no reliable way to read display status on xxN
(Centrino) models.
LED display
-----------
Some models like the W1N have a LED display that can be used to display
several informations.
LED display works for the following models:
W1000N
W1J
To control the LED display, use the following :
echo 0x0T000DDD > /sys/devices/platform/asus-laptop/
where T control the 3 letters display, and DDD the 3 digits display,
according to the tables below.
DDD (digits)
000 to 999 = display digits
AAA = ---
BBB to FFF = turn-off
T (type)
0 = off
1 = dvd
2 = vcd
3 = mp3
4 = cd
5 = tv
6 = cpu
7 = vol
For example "echo 0x01000001 >/sys/devices/platform/asus-laptop/ledd"
would display "DVD001".
Driver options:
---------------
Options can be passed to the asus-laptop driver using the standard
module argument syntax (<param>=<value> when passing the option to the
module or asus-laptop.<param>=<value> on the kernel boot line when
asus-laptop is statically linked into the kernel).
wapf: WAPF defines the behavior of the Fn+Fx wlan key
The significance of values is yet to be found, but
most of the time:
- 0x0 should do nothing
- 0x1 should allow to control the device with Fn+Fx key.
- 0x4 should send an ACPI event (0x88) while pressing the Fn+Fx key
- 0x5 like 0x1 or 0x4
The default value is 0x1.
Unsupported models
------------------
These models will never be supported by this module, as they use a completely
different mechanism to handle LEDs and extra stuff (meaning we have no clue
how it works):
- ASUS A1300 (A1B), A1370D
- ASUS L7300G
- ASUS L8400
Patches, Errors, Questions:
--------------------------
I appreciate any success or failure
reports, especially if they add to or correct the compatibility table.
Please include the following information in your report:
- Asus model name
- a copy of your ACPI tables, using the "acpidump" utility
- a copy of /sys/devices/platform/asus-laptop/infos
- which driver features work and which don't
- the observed behavior of non-working features
Any other comments or patches are also more than welcome.
acpi4asus-user@lists.sourceforge.net
http://sourceforge.net/projects/acpi4asus
Documentation/laptops/thinkpad-acpi.txt
浏览文件 @ d9b2002c
......@@ -199,18 +199,22 @@ kind to allow it (and it often doesn't!).
Not all bits in the mask can be modified. Not all bits that can be
modified do anything. Not all hot keys can be individually controlled
by the mask. Some models do not support the mask at all, and in those
models, hot keys cannot be controlled individually. The behaviour of
the mask is, therefore, highly dependent on the ThinkPad model.
by the mask. Some models do not support the mask at all. The behaviour
of the mask is, therefore, highly dependent on the ThinkPad model.
The driver will filter out any unmasked hotkeys, so even if the firmware
doesn't allow disabling an specific hotkey, the driver will not report
events for unmasked hotkeys.
Note that unmasking some keys prevents their default behavior. For
example, if Fn+F5 is unmasked, that key will no longer enable/disable
Bluetooth by itself.
Bluetooth by itself in firmware.
Note also that not all Fn key combinations are supported through ACPI.
For example, on the X40, the brightness, volume and "Access IBM" buttons
do not generate ACPI events even with this driver. They *can* be used
through the "ThinkPad Buttons" utility, see http://www.nongnu.org/tpb/
Note also that not all Fn key combinations are supported through ACPI
depending on the ThinkPad model and firmware version. On those
ThinkPads, it is still possible to support some extra hotkeys by
polling the "CMOS NVRAM" at least 10 times per second. The driver
attempts to enables this functionality automatically when required.
procfs notes:
......@@ -219,7 +223,7 @@ The following commands can be written to the /proc/acpi/ibm/hotkey file:
echo 0xffffffff > /proc/acpi/ibm/hotkey -- enable all hot keys
echo 0 > /proc/acpi/ibm/hotkey -- disable all possible hot keys
... any other 8-hex-digit mask ...
echo reset > /proc/acpi/ibm/hotkey -- restore the original mask
echo reset > /proc/acpi/ibm/hotkey -- restore the recommended mask
The following commands have been deprecated and will cause the kernel
to log a warning:
......@@ -240,9 +244,13 @@ sysfs notes:
Returns 0.
hotkey_bios_mask:
DEPRECATED, DON'T USE, WILL BE REMOVED IN THE FUTURE.
Returns the hot keys mask when thinkpad-acpi was loaded.
Upon module unload, the hot keys mask will be restored
to this value.
to this value. This is always 0x80c, because those are
the hotkeys that were supported by ancient firmware
without mask support.
hotkey_enable:
DEPRECATED, WILL BE REMOVED SOON.
......@@ -251,18 +259,11 @@ sysfs notes:
1: does nothing
hotkey_mask:
bit mask to enable driver-handling (and depending on
bit mask to enable reporting (and depending on
the firmware, ACPI event generation) for each hot key
(see above). Returns the current status of the hot keys
mask, and allows one to modify it.
Note: when NVRAM polling is active, the firmware mask
will be different from the value returned by
hotkey_mask. The driver will retain enabled bits for
hotkeys that are under NVRAM polling even if the
firmware refuses them, and will not set these bits on
the firmware hot key mask.
hotkey_all_mask:
bit mask that should enable event reporting for all
supported hot keys, when echoed to hotkey_mask above.
......@@ -275,7 +276,8 @@ sysfs notes:
bit mask that should enable event reporting for all
supported hot keys, except those which are always
handled by the firmware anyway. Echo it to
hotkey_mask above, to use.
hotkey_mask above, to use. This is the default mask
used by the driver.
hotkey_source_mask:
bit mask that selects which hot keys will the driver
......@@ -283,9 +285,10 @@ sysfs notes:
based on the capabilities reported by the ACPI firmware,
but it can be overridden at runtime.
Hot keys whose bits are set in both hotkey_source_mask
and also on hotkey_mask are polled for in NVRAM. Only a
few hot keys are available through CMOS NVRAM polling.
Hot keys whose bits are set in hotkey_source_mask are
polled for in NVRAM, and reported as hotkey events if
enabled in hotkey_mask. Only a few hot keys are
available through CMOS NVRAM polling.
Warning: when in NVRAM mode, the volume up/down/mute
keys are synthesized according to changes in the mixer,
......@@ -521,6 +524,7 @@ compatibility purposes when hotkey_report_mode is set to 1.
0x2305 System is waking up from suspend to eject bay
0x2404 System is waking up from hibernation to undock
0x2405 System is waking up from hibernation to eject bay
0x5010 Brightness level changed/control event
The above events are never propagated by the driver.
......@@ -528,7 +532,6 @@ The above events are never propagated by the driver.
0x4003 Undocked (see 0x2x04), can sleep again
0x500B Tablet pen inserted into its storage bay
0x500C Tablet pen removed from its storage bay
0x5010 Brightness level changed (newer Lenovo BIOSes)
The above events are propagated by the driver.
......@@ -617,6 +620,8 @@ For Lenovo models *with* ACPI backlight control:
2. Do *NOT* load up ACPI video, enable the hotkeys in thinkpad-acpi,
and map them to KEY_BRIGHTNESS_UP and KEY_BRIGHTNESS_DOWN. Process
these keys on userspace somehow (e.g. by calling xbacklight).
The driver will do this automatically if it detects that ACPI video
has been disabled.
Bluetooth
......@@ -1455,3 +1460,8 @@ Sysfs interface changelog:
0x020400: Marker for 16 LEDs support. Also, LEDs that are known
to not exist in a given model are not registered with
the LED sysfs class anymore.
0x020500: Updated hotkey driver, hotkey_mask is always available
and it is always able to disable hot keys. Very old
thinkpads are properly supported. hotkey_bios_mask
is deprecated and marked for removal.
Documentation/leds-class.txt
浏览文件 @ d9b2002c
LED handling under Linux
========================
......@@ -5,10 +6,10 @@ If you're reading this and thinking about keyboard leds, these are
handled by the input subsystem and the led class is *not* needed.
In its simplest form, the LED class just allows control of LEDs from
userspace. LEDs appear in /sys/class/leds/. The brightness file will
set the brightness of the LED (taking a value 0-255). Most LEDs don't
have hardware brightness support so will just be turned on for non-zero
brightness settings.
userspace. LEDs appear in /sys/class/leds/. The maximum brightness of the
LED is defined in max_brightness file. The brightness file will set the brightness
of the LED (taking a value 0-max_brightness). Most LEDs don't have hardware
brightness support so will just be turned on for non-zero brightness settings.
The class also introduces the optional concept of an LED trigger. A trigger
is a kernel based source of led events. Triggers can either be simple or
......
Documentation/lguest/lguest.c
浏览文件 @ d9b2002c
......@@ -42,6 +42,7 @@
#include <signal.h>
#include "linux/lguest_launcher.h"
#include "linux/virtio_config.h"
#include <linux/virtio_ids.h>
#include "linux/virtio_net.h"
#include "linux/virtio_blk.h"
#include "linux/virtio_console.h"
......@@ -133,6 +134,9 @@ struct device {
/* Is it operational */
bool running;
/* Does Guest want an intrrupt on empty? */
bool irq_on_empty;
/* Device-specific data. */
void *priv;
};
......@@ -623,10 +627,13 @@ static void trigger_irq(struct virtqueue *vq)
return;
vq->pending_used = 0;
/* If they don't want an interrupt, don't send one, unless empty. */
if ((vq->vring.avail->flags & VRING_AVAIL_F_NO_INTERRUPT)
&& lg_last_avail(vq) != vq->vring.avail->idx)
return;
/* If they don't want an interrupt, don't send one... */
if (vq->vring.avail->flags & VRING_AVAIL_F_NO_INTERRUPT) {
/* ... unless they've asked us to force one on empty. */
if (!vq->dev->irq_on_empty
|| lg_last_avail(vq) != vq->vring.avail->idx)
return;
}
/* Send the Guest an interrupt tell them we used something up. */
if (write(lguest_fd, buf, sizeof(buf)) != 0)
......@@ -1042,6 +1049,15 @@ static void create_thread(struct virtqueue *vq)
close(vq->eventfd);
}
static bool accepted_feature(struct device *dev, unsigned int bit)
{
const u8 *features = get_feature_bits(dev) + dev->feature_len;
if (dev->feature_len < bit / CHAR_BIT)
return false;
return features[bit / CHAR_BIT] & (1 << (bit % CHAR_BIT));
}
static void start_device(struct device *dev)
{
unsigned int i;
......@@ -1055,6 +1071,8 @@ static void start_device(struct device *dev)
verbose(" %02x", get_feature_bits(dev)
[dev->feature_len+i]);
dev->irq_on_empty = accepted_feature(dev, VIRTIO_F_NOTIFY_ON_EMPTY);
for (vq = dev->vq; vq; vq = vq->next) {
if (vq->service)
create_thread(vq);
......
Documentation/memory.txt
浏览文件 @ d9b2002c
There are several classic problems related to memory on Linux
systems.
1) There are some buggy motherboards which cannot properly
deal with the memory above 16MB. Consider exchanging
your motherboard.
2) You cannot do DMA on the ISA bus to addresses above
16M. Most device drivers under Linux allow the use
of bounce buffers which work around this problem. Drivers
that don't use bounce buffers will be unstable with
more than 16M installed. Drivers that use bounce buffers
will be OK, but may have slightly higher overhead.
3) There are some motherboards that will not cache above
1) There are some motherboards that will not cache above
a certain quantity of memory. If you have one of these
motherboards, your system will be SLOWER, not faster
as you add more memory. Consider exchanging your
......@@ -24,7 +13,7 @@ It can also tell Linux to use less memory than is actually installed.
If you use "mem=" on a machine with PCI, consider using "memmap=" to avoid
physical address space collisions.
See the documentation of your boot loader (LILO, loadlin, etc.) about
See the documentation of your boot loader (LILO, grub, loadlin, etc.) about
how to pass options to the kernel.
There are other memory problems which Linux cannot deal with. Random
......@@ -42,19 +31,3 @@ Try:
with the vendor. Consider testing it with memtest86 yourself.
* Exchanging your CPU, cache, or motherboard for one that works.
* Disabling the cache from the BIOS.
* Try passing the "mem=4M" option to the kernel to limit
Linux to using a very small amount of memory. Use "memmap="-option
together with "mem=" on systems with PCI to avoid physical address
space collisions.
Other tricks:
* Try passing the "no-387" option to the kernel to ignore
a buggy FPU.
* Try passing the "no-hlt" option to disable the potentially
buggy HLT instruction in your CPU.
Documentation/networking/regulatory.txt
浏览文件 @ d9b2002c
......@@ -96,7 +96,7 @@ Example code - drivers hinting an alpha2:
This example comes from the zd1211rw device driver. You can start
by having a mapping of your device's EEPROM country/regulatory
domain value to to a specific alpha2 as follows:
domain value to a specific alpha2 as follows:
static struct zd_reg_alpha2_map reg_alpha2_map[] = {
{ ZD_REGDOMAIN_FCC, "US" },
......
Documentation/numastat.txt
浏览文件 @ d9b2002c
......@@ -7,10 +7,10 @@ All units are pages. Hugepages have separate counters.
numa_hit A process wanted to allocate memory from this node,
and succeeded.
numa_miss A process wanted to allocate memory from this node,
but ended up with memory from another.
numa_foreign A process wanted to allocate on another node,
but ended up with memory from this one.
numa_miss A process wanted to allocate memory from another node,
but ended up with memory from this node.
numa_foreign A process wanted to allocate on this node,
but ended up with memory from another one.
local_node A process ran on this node and got memory from it.
other_node A process ran on this node and got memory from another node.
interleave_hit Interleaving wanted to allocate from this node
......
Documentation/pcmcia/crc32hash.c
浏览文件 @ d9b2002c
......@@ -8,7 +8,7 @@
#include <ctype.h>
#include <stdlib.h>
unsigned int crc32(unsigned char const *p, unsigned int len)
static unsigned int crc32(unsigned char const *p, unsigned int len)
{
int i;
unsigned int crc = 0;
......
Documentation/power/power_supply_class.txt
浏览文件 @ d9b2002c
......@@ -76,6 +76,11 @@ STATUS - this attribute represents operating status (charging, full,
discharging (i.e. powering a load), etc.). This corresponds to
BATTERY_STATUS_* values, as defined in battery.h.
CHARGE_TYPE - batteries can typically charge at different rates.
This defines trickle and fast charges. For batteries that
are already charged or discharging, 'n/a' can be displayed (or
'unknown', if the status is not known).
HEALTH - represents health of the battery, values corresponds to
POWER_SUPPLY_HEALTH_*, defined in battery.h.
......@@ -108,6 +113,8 @@ relative, time-based measurements.
ENERGY_FULL, ENERGY_EMPTY - same as above but for energy.
CAPACITY - capacity in percents.
CAPACITY_LEVEL - capacity level. This corresponds to
POWER_SUPPLY_CAPACITY_LEVEL_*.
TEMP - temperature of the power supply.
TEMP_AMBIENT - ambient temperature.
......
Documentation/power/regulator/design.txt 0 → 100644
浏览文件 @ d9b2002c
Regulator API design notes
==========================
This document provides a brief, partially structured, overview of some
of the design considerations which impact the regulator API design.
Safety
------
- Errors in regulator configuration can have very serious consequences
for the system, potentially including lasting hardware damage.
- It is not possible to automatically determine the power confugration
of the system - software-equivalent variants of the same chip may
have different power requirments, and not all components with power
requirements are visible to software.
=> The API should make no changes to the hardware state unless it has
specific knowledge that these changes are safe to do perform on
this particular system.
Consumer use cases
------------------
- The overwhelming majority of devices in a system will have no
requirement to do any runtime configuration of their power beyond
being able to turn it on or off.
- Many of the power supplies in the system will be shared between many
different consumers.
=> The consumer API should be structured so that these use cases are
very easy to handle and so that consumers will work with shared
supplies without any additional effort.
Documentation/power/regulator/machine.txt
浏览文件 @ d9b2002c
......@@ -87,7 +87,7 @@ static struct platform_device regulator_devices[] = {
},
};
/* register regulator 1 device */
platform_device_register(&wm8350_regulator_devices[0]);
platform_device_register(&regulator_devices[0]);
/* register regulator 2 device */
platform_device_register(&wm8350_regulator_devices[1]);
platform_device_register(&regulator_devices[1]);
Documentation/power/regulator/overview.txt
浏览文件 @ d9b2002c
......@@ -29,7 +29,7 @@ Some terms used in this document:-
o PMIC - Power Management IC. An IC that contains numerous regulators
and often contains other susbsystems.
and often contains other subsystems.
o Consumer - Electronic device that is supplied power by a regulator.
......@@ -168,4 +168,4 @@ relevant to non SoC devices and is split into the following four interfaces:-
userspace via sysfs. This could be used to help monitor device power
consumption and status.
See Documentation/ABI/testing/regulator-sysfs.txt
See Documentation/ABI/testing/sysfs-class-regulator
Documentation/power/regulator/regulator.txt
浏览文件 @ d9b2002c
......@@ -10,8 +10,9 @@ Registration
Drivers can register a regulator by calling :-
struct regulator_dev *regulator_register(struct device *dev,
struct regulator_desc *regulator_desc);
struct regulator_dev *regulator_register(struct regulator_desc *regulator_desc,
struct device *dev, struct regulator_init_data *init_data,
void *driver_data);
This will register the regulators capabilities and operations to the regulator
core.
......
Documentation/powerpc/dts-bindings/fsl/esdhc.txt
浏览文件 @ d9b2002c
......@@ -10,6 +10,8 @@ Required properties:
- interrupts : should contain eSDHC interrupt.
- interrupt-parent : interrupt source phandle.
- clock-frequency : specifies eSDHC base clock frequency.
- sdhci,wp-inverted : (optional) specifies that eSDHC controller
reports inverted write-protect state;
- sdhci,1-bit-only : (optional) specifies that a controller can
only handle 1-bit data transfers.
......
Documentation/powerpc/dts-bindings/marvell.txt
浏览文件 @ d9b2002c
......@@ -32,7 +32,7 @@ prefixed with the string "marvell,", for Marvell Technology Group Ltd.
devices. This field represents the number of cells needed to
represent the address of the memory-mapped registers of devices
within the system controller chip.
- #size-cells : Size representation for for the memory-mapped
- #size-cells : Size representation for the memory-mapped
registers within the system controller chip.
- #interrupt-cells : Defines the width of cells used to represent
interrupts.
......
Documentation/powerpc/dts-bindings/mtd-physmap.txt
浏览文件 @ d9b2002c
CFI or JEDEC memory-mapped NOR flash
CFI or JEDEC memory-mapped NOR flash, MTD-RAM (NVRAM...)
Flash chips (Memory Technology Devices) are often used for solid state
file systems on embedded devices.
- compatible : should contain the specific model of flash chip(s)
used, if known, followed by either "cfi-flash" or "jedec-flash"
- reg : Address range(s) of the flash chip(s)
- compatible : should contain the specific model of mtd chip(s)
used, if known, followed by either "cfi-flash", "jedec-flash"
or "mtd-ram".
- reg : Address range(s) of the mtd chip(s)
It's possible to (optionally) define multiple "reg" tuples so that
non-identical NOR chips can be described in one flash node.
- bank-width : Width (in bytes) of the flash bank. Equal to the
non-identical chips can be described in one node.
- bank-width : Width (in bytes) of the bank. Equal to the
device width times the number of interleaved chips.
- device-width : (optional) Width of a single flash chip. If
- device-width : (optional) Width of a single mtd chip. If
omitted, assumed to be equal to 'bank-width'.
- #address-cells, #size-cells : Must be present if the flash has
- #address-cells, #size-cells : Must be present if the device has
sub-nodes representing partitions (see below). In this case
both #address-cells and #size-cells must be equal to 1.
......@@ -22,24 +23,24 @@ are defined:
- vendor-id : Contains the flash chip's vendor id (1 byte).
- device-id : Contains the flash chip's device id (1 byte).
In addition to the information on the flash bank itself, the
In addition to the information on the mtd bank itself, the
device tree may optionally contain additional information
describing partitions of the flash address space. This can be
describing partitions of the address space. This can be
used on platforms which have strong conventions about which
portions of the flash are used for what purposes, but which don't
portions of a flash are used for what purposes, but which don't
use an on-flash partition table such as RedBoot.
Each partition is represented as a sub-node of the flash device.
Each partition is represented as a sub-node of the mtd device.
Each node's name represents the name of the corresponding
partition of the flash device.
partition of the mtd device.
Flash partitions
- reg : The partition's offset and size within the flash bank.
- label : (optional) The label / name for this flash partition.
- reg : The partition's offset and size within the mtd bank.
- label : (optional) The label / name for this partition.
If omitted, the label is taken from the node name (excluding
the unit address).
- read-only : (optional) This parameter, if present, is a hint to
Linux that this flash partition should only be mounted
Linux that this partition should only be mounted
read-only. This is usually used for flash partitions
containing early-boot firmware images or data which should not
be clobbered.
......@@ -78,3 +79,12 @@ Here an example with multiple "reg" tuples:
reg = <0 0x04000000>;
};
};
An example using SRAM:
sram@2,0 {
compatible = "samsung,k6f1616u6a", "mtd-ram";
reg = <2 0 0x00200000>;
bank-width = <2>;
};
Documentation/rtc.txt
浏览文件 @ d9b2002c
......@@ -135,6 +135,30 @@ a high functionality RTC is integrated into the SOC. That system might read
the system clock from the discrete RTC, but use the integrated one for all
other tasks, because of its greater functionality.
SYSFS INTERFACE
---------------
The sysfs interface under /sys/class/rtc/rtcN provides access to various
rtc attributes without requiring the use of ioctls. All dates and times
are in the RTC's timezone, rather than in system time.
date: RTC-provided date
hctosys: 1 if the RTC provided the system time at boot via the
CONFIG_RTC_HCTOSYS kernel option, 0 otherwise
max_user_freq: The maximum interrupt rate an unprivileged user may request
from this RTC.
name: The name of the RTC corresponding to this sysfs directory
since_epoch: The number of seconds since the epoch according to the RTC
time: RTC-provided time
wakealarm: The time at which the clock will generate a system wakeup
event. This is a one shot wakeup event, so must be reset
after wake if a daily wakeup is required. Format is either
seconds since the epoch or, if there's a leading +, seconds
in the future.
IOCTL INTERFACE
---------------
The ioctl() calls supported by /dev/rtc are also supported by the RTC class
framework. However, because the chips and systems are not standardized,
some PC/AT functionality might not be provided. And in the same way, some
......@@ -185,6 +209,8 @@ driver returns ENOIOCTLCMD. Some common examples:
hardware in the irq_set_freq function. If it isn't, return -EINVAL. If
you cannot actually change the frequency, do not define irq_set_freq.
* RTC_PIE_ON, RTC_PIE_OFF: the irq_set_state function will be called.
If all else fails, check out the rtc-test.c driver!
......
Documentation/scsi/ChangeLog.megaraid
浏览文件 @ d9b2002c
......@@ -514,7 +514,7 @@ iv. Remove yield() while mailbox handshake in synchronous commands
v. Remove redundant __megaraid_busywait_mbox routine
vi. Fix bug in the managment module, which causes a system lockup when the
vi. Fix bug in the management module, which causes a system lockup when the
IO module is loaded and then unloaded, followed by executing any
management utility. The current version of management module does not
handle the adapter unregister properly.
......
Documentation/scsi/scsi_fc_transport.txt
浏览文件 @ d9b2002c
......@@ -378,7 +378,7 @@ Vport Disable/Enable:
int vport_disable(struct fc_vport *vport, bool disable)
where:
vport: Is vport to to be enabled or disabled
vport: Is vport to be enabled or disabled
disable: If "true", the vport is to be disabled.
If "false", the vport is to be enabled.
......
Documentation/sound/alsa/HD-Audio-Models.txt
浏览文件 @ d9b2002c
......@@ -387,7 +387,7 @@ STAC92HD73*
STAC92HD83*
===========
ref Reference board
mic-ref Reference board with power managment for ports
mic-ref Reference board with power management for ports
dell-s14 Dell laptop
auto BIOS setup (default)
......
Documentation/spi/spi-summary
浏览文件 @ d9b2002c
......@@ -350,7 +350,7 @@ SPI protocol drivers somewhat resemble platform device drivers:
.resume = CHIP_resume,
};
The driver core will autmatically attempt to bind this driver to any SPI
The driver core will automatically attempt to bind this driver to any SPI
device whose board_info gave a modalias of "CHIP". Your probe() code
might look like this unless you're creating a device which is managing
a bus (appearing under /sys/class/spi_master).
......
Documentation/spi/spidev_test.c
浏览文件 @ d9b2002c
......@@ -69,7 +69,7 @@ static void transfer(int fd)
puts("");
}
void print_usage(const char *prog)
static void print_usage(const char *prog)
{
printf("Usage: %s [-DsbdlHOLC3]\n", prog);
puts(" -D --device device to use (default /dev/spidev1.1)\n"
......@@ -85,7 +85,7 @@ void print_usage(const char *prog)
exit(1);
}
void parse_opts(int argc, char *argv[])
static void parse_opts(int argc, char *argv[])
{
while (1) {
static const struct option lopts[] = {
......
Documentation/sysctl/fs.txt
浏览文件 @ d9b2002c
......@@ -96,13 +96,16 @@ handles that the Linux kernel will allocate. When you get lots
of error messages about running out of file handles, you might
want to increase this limit.
The three values in file-nr denote the number of allocated
file handles, the number of unused file handles and the maximum
number of file handles. When the allocated file handles come
close to the maximum, but the number of unused file handles is
significantly greater than 0, you've encountered a peak in your
usage of file handles and you don't need to increase the maximum.
Historically, the three values in file-nr denoted the number of
allocated file handles, the number of allocated but unused file
handles, and the maximum number of file handles. Linux 2.6 always
reports 0 as the number of free file handles -- this is not an
error, it just means that the number of allocated file handles
exactly matches the number of used file handles.
Attempts to allocate more file descriptors than file-max are
reported with printk, look for "VFS: file-max limit <number>
reached".
==============================================================
nr_open:
......
Documentation/sysctl/kernel.txt
浏览文件 @ d9b2002c
......@@ -22,6 +22,7 @@ show up in /proc/sys/kernel:
- callhome [ S390 only ]
- auto_msgmni
- core_pattern
- core_pipe_limit
- core_uses_pid
- ctrl-alt-del
- dentry-state
......@@ -135,6 +136,27 @@ core_pattern is used to specify a core dumpfile pattern name.
==============================================================
core_pipe_limit:
This sysctl is only applicable when core_pattern is configured to pipe core
files to user space helper a (when the first character of core_pattern is a '|',
see above). When collecting cores via a pipe to an application, it is
occasionally usefull for the collecting application to gather data about the
crashing process from its /proc/pid directory. In order to do this safely, the
kernel must wait for the collecting process to exit, so as not to remove the
crashing processes proc files prematurely. This in turn creates the possibility
that a misbehaving userspace collecting process can block the reaping of a
crashed process simply by never exiting. This sysctl defends against that. It
defines how many concurrent crashing processes may be piped to user space
applications in parallel. If this value is exceeded, then those crashing
processes above that value are noted via the kernel log and their cores are
skipped. 0 is a special value, indicating that unlimited processes may be
captured in parallel, but that no waiting will take place (i.e. the collecting
process is not guaranteed access to /proc/<crahing pid>/). This value defaults
to 0.
==============================================================
core_uses_pid:
The default coredump filename is "core". By setting
......@@ -313,31 +335,43 @@ send before ratelimiting kicks in.
==============================================================
printk_delay:
Delay each printk message in printk_delay milliseconds
Value from 0 - 10000 is allowed.
==============================================================
randomize-va-space:
This option can be used to select the type of process address
space randomization that is used in the system, for architectures
that support this feature.
0 - Turn the process address space randomization off by default.
0 - Turn the process address space randomization off. This is the
default for architectures that do not support this feature anyways,
and kernels that are booted with the "norandmaps" parameter.
1 - Make the addresses of mmap base, stack and VDSO page randomized.
This, among other things, implies that shared libraries will be
loaded to random addresses. Also for PIE-linked binaries, the location
of code start is randomized.
loaded to random addresses. Also for PIE-linked binaries, the
location of code start is randomized. This is the default if the
CONFIG_COMPAT_BRK option is enabled.
With heap randomization, the situation is a little bit more
complicated.
There a few legacy applications out there (such as some ancient
2 - Additionally enable heap randomization. This is the default if
CONFIG_COMPAT_BRK is disabled.
There are a few legacy applications out there (such as some ancient
versions of libc.so.5 from 1996) that assume that brk area starts
just after the end of the code+bss. These applications break when
start of the brk area is randomized. There are however no known
just after the end of the code+bss. These applications break when
start of the brk area is randomized. There are however no known
non-legacy applications that would be broken this way, so for most
systems it is safe to choose full randomization. However there is
a CONFIG_COMPAT_BRK option for systems with ancient and/or broken
binaries, that makes heap non-randomized, but keeps all other
parts of process address space randomized if randomize_va_space
sysctl is turned on.
systems it is safe to choose full randomization.
Systems with ancient and/or broken binaries should be configured
with CONFIG_COMPAT_BRK enabled, which excludes the heap from process
address space randomization.
==============================================================
......
Documentation/sysctl/vm.txt
浏览文件 @ d9b2002c
......@@ -32,6 +32,8 @@ Currently, these files are in /proc/sys/vm:
- legacy_va_layout
- lowmem_reserve_ratio
- max_map_count
- memory_failure_early_kill
- memory_failure_recovery
- min_free_kbytes
- min_slab_ratio
- min_unmapped_ratio
......@@ -53,7 +55,6 @@ Currently, these files are in /proc/sys/vm:
- vfs_cache_pressure
- zone_reclaim_mode
==============================================================
block_dump
......@@ -275,6 +276,44 @@ e.g., up to one or two maps per allocation.
The default value is 65536.
=============================================================
memory_failure_early_kill:
Control how to kill processes when uncorrected memory error (typically
a 2bit error in a memory module) is detected in the background by hardware
that cannot be handled by the kernel. In some cases (like the page
still having a valid copy on disk) the kernel will handle the failure
transparently without affecting any applications. But if there is
no other uptodate copy of the data it will kill to prevent any data
corruptions from propagating.
1: Kill all processes that have the corrupted and not reloadable page mapped
as soon as the corruption is detected. Note this is not supported
for a few types of pages, like kernel internally allocated data or
the swap cache, but works for the majority of user pages.
0: Only unmap the corrupted page from all processes and only kill a process
who tries to access it.
The kill is done using a catchable SIGBUS with BUS_MCEERR_AO, so processes can
handle this if they want to.
This is only active on architectures/platforms with advanced machine
check handling and depends on the hardware capabilities.
Applications can override this setting individually with the PR_MCE_KILL prctl
==============================================================
memory_failure_recovery
Enable memory failure recovery (when supported by the platform)
1: Attempt recovery.
0: Always panic on a memory failure.
==============================================================
min_free_kbytes:
......@@ -585,7 +624,9 @@ caching of directory and inode objects.
At the default value of vfs_cache_pressure=100 the kernel will attempt to
reclaim dentries and inodes at a "fair" rate with respect to pagecache and
swapcache reclaim. Decreasing vfs_cache_pressure causes the kernel to prefer
to retain dentry and inode caches. Increasing vfs_cache_pressure beyond 100
to retain dentry and inode caches. When vfs_cache_pressure=0, the kernel will
never reclaim dentries and inodes due to memory pressure and this can easily
lead to out-of-memory conditions. Increasing vfs_cache_pressure beyond 100
causes the kernel to prefer to reclaim dentries and inodes.
==============================================================
......
Documentation/trace/events-kmem.txt 0 → 100644
浏览文件 @ d9b2002c
Subsystem Trace Points: kmem
The tracing system kmem captures events related to object and page allocation
within the kernel. Broadly speaking there are four major subheadings.
o Slab allocation of small objects of unknown type (kmalloc)
o Slab allocation of small objects of known type
o Page allocation
o Per-CPU Allocator Activity
o External Fragmentation
This document will describe what each of the tracepoints are and why they
might be useful.
1. Slab allocation of small objects of unknown type
===================================================
kmalloc call_site=%lx ptr=%p bytes_req=%zu bytes_alloc=%zu gfp_flags=%s
kmalloc_node call_site=%lx ptr=%p bytes_req=%zu bytes_alloc=%zu gfp_flags=%s node=%d
kfree call_site=%lx ptr=%p
Heavy activity for these events may indicate that a specific cache is
justified, particularly if kmalloc slab pages are getting significantly
internal fragmented as a result of the allocation pattern. By correlating
kmalloc with kfree, it may be possible to identify memory leaks and where
the allocation sites were.
2. Slab allocation of small objects of known type
=================================================
kmem_cache_alloc call_site=%lx ptr=%p bytes_req=%zu bytes_alloc=%zu gfp_flags=%s
kmem_cache_alloc_node call_site=%lx ptr=%p bytes_req=%zu bytes_alloc=%zu gfp_flags=%s node=%d
kmem_cache_free call_site=%lx ptr=%p
These events are similar in usage to the kmalloc-related events except that
it is likely easier to pin the event down to a specific cache. At the time
of writing, no information is available on what slab is being allocated from,
but the call_site can usually be used to extrapolate that information
3. Page allocation
==================
mm_page_alloc page=%p pfn=%lu order=%d migratetype=%d gfp_flags=%s
mm_page_alloc_zone_locked page=%p pfn=%lu order=%u migratetype=%d cpu=%d percpu_refill=%d
mm_page_free_direct page=%p pfn=%lu order=%d
mm_pagevec_free page=%p pfn=%lu order=%d cold=%d
These four events deal with page allocation and freeing. mm_page_alloc is
a simple indicator of page allocator activity. Pages may be allocated from
the per-CPU allocator (high performance) or the buddy allocator.
If pages are allocated directly from the buddy allocator, the
mm_page_alloc_zone_locked event is triggered. This event is important as high
amounts of activity imply high activity on the zone->lock. Taking this lock
impairs performance by disabling interrupts, dirtying cache lines between
CPUs and serialising many CPUs.
When a page is freed directly by the caller, the mm_page_free_direct event
is triggered. Significant amounts of activity here could indicate that the
callers should be batching their activities.
When pages are freed using a pagevec, the mm_pagevec_free is
triggered. Broadly speaking, pages are taken off the LRU lock in bulk and
freed in batch with a pagevec. Significant amounts of activity here could
indicate that the system is under memory pressure and can also indicate
contention on the zone->lru_lock.
4. Per-CPU Allocator Activity
=============================
mm_page_alloc_zone_locked page=%p pfn=%lu order=%u migratetype=%d cpu=%d percpu_refill=%d
mm_page_pcpu_drain page=%p pfn=%lu order=%d cpu=%d migratetype=%d
In front of the page allocator is a per-cpu page allocator. It exists only
for order-0 pages, reduces contention on the zone->lock and reduces the
amount of writing on struct page.
When a per-CPU list is empty or pages of the wrong type are allocated,
the zone->lock will be taken once and the per-CPU list refilled. The event
triggered is mm_page_alloc_zone_locked for each page allocated with the
event indicating whether it is for a percpu_refill or not.
When the per-CPU list is too full, a number of pages are freed, each one
which triggers a mm_page_pcpu_drain event.
The individual nature of the events are so that pages can be tracked
between allocation and freeing. A number of drain or refill pages that occur
consecutively imply the zone->lock being taken once. Large amounts of PCP
refills and drains could imply an imbalance between CPUs where too much work
is being concentrated in one place. It could also indicate that the per-CPU
lists should be a larger size. Finally, large amounts of refills on one CPU
and drains on another could be a factor in causing large amounts of cache
line bounces due to writes between CPUs and worth investigating if pages
can be allocated and freed on the same CPU through some algorithm change.
5. External Fragmentation
=========================
mm_page_alloc_extfrag page=%p pfn=%lu alloc_order=%d fallback_order=%d pageblock_order=%d alloc_migratetype=%d fallback_migratetype=%d fragmenting=%d change_ownership=%d
External fragmentation affects whether a high-order allocation will be
successful or not. For some types of hardware, this is important although
it is avoided where possible. If the system is using huge pages and needs
to be able to resize the pool over the lifetime of the system, this value
is important.
Large numbers of this event implies that memory is fragmenting and
high-order allocations will start failing at some time in the future. One
means of reducing the occurange of this event is to increase the size of
min_free_kbytes in increments of 3*pageblock_size*nr_online_nodes where
pageblock_size is usually the size of the default hugepage size.
Documentation/trace/events.txt
浏览文件 @ d9b2002c
......@@ -72,7 +72,7 @@ To enable all events in sched subsystem:
# echo 1 > /sys/kernel/debug/tracing/events/sched/enable
To eanble all events:
To enable all events:
# echo 1 > /sys/kernel/debug/tracing/events/enable
......
Documentation/trace/ftrace.txt
浏览文件 @ d9b2002c
......@@ -133,7 +133,7 @@ of ftrace. Here is a list of some of the key files:
than requested, the rest of the page will be used,
making the actual allocation bigger than requested.
( Note, the size may not be a multiple of the page size
due to buffer managment overhead. )
due to buffer management overhead. )
This can only be updated when the current_tracer
is set to "nop".
......
Documentation/trace/postprocess/trace-pagealloc-postprocess.pl 0 → 100644
浏览文件 @ d9b2002c
#!/usr/bin/perl
# This is a POC (proof of concept or piece of crap, take your pick) for reading the
# text representation of trace output related to page allocation. It makes an attempt
# to extract some high-level information on what is going on. The accuracy of the parser
# may vary considerably
#
# Example usage: trace-pagealloc-postprocess.pl < /sys/kernel/debug/tracing/trace_pipe
# other options
# --prepend-parent Report on the parent proc and PID
# --read-procstat If the trace lacks process info, get it from /proc
# --ignore-pid Aggregate processes of the same name together
#
# Copyright (c) IBM Corporation 2009
# Author: Mel Gorman <mel@csn.ul.ie>
use strict;
use Getopt::Long;
# Tracepoint events
use constant MM_PAGE_ALLOC => 1;
use constant MM_PAGE_FREE_DIRECT => 2;
use constant MM_PAGEVEC_FREE => 3;
use constant MM_PAGE_PCPU_DRAIN => 4;
use constant MM_PAGE_ALLOC_ZONE_LOCKED => 5;
use constant MM_PAGE_ALLOC_EXTFRAG => 6;
use constant EVENT_UNKNOWN => 7;
# Constants used to track state
use constant STATE_PCPU_PAGES_DRAINED => 8;
use constant STATE_PCPU_PAGES_REFILLED => 9;
# High-level events extrapolated from tracepoints
use constant HIGH_PCPU_DRAINS => 10;
use constant HIGH_PCPU_REFILLS => 11;
use constant HIGH_EXT_FRAGMENT => 12;
use constant HIGH_EXT_FRAGMENT_SEVERE => 13;
use constant HIGH_EXT_FRAGMENT_MODERATE => 14;
use constant HIGH_EXT_FRAGMENT_CHANGED => 15;
my %perprocesspid;
my %perprocess;
my $opt_ignorepid;
my $opt_read_procstat;
my $opt_prepend_parent;
# Catch sigint and exit on request
my $sigint_report = 0;
my $sigint_exit = 0;
my $sigint_pending = 0;
my $sigint_received = 0;
sub sigint_handler {
my $current_time = time;
if ($current_time - 2 > $sigint_received) {
print "SIGINT received, report pending. Hit ctrl-c again to exit\n";
$sigint_report = 1;
} else {
if (!$sigint_exit) {
print "Second SIGINT received quickly, exiting\n";
}
$sigint_exit++;
}
if ($sigint_exit > 3) {
print "Many SIGINTs received, exiting now without report\n";
exit;
}
$sigint_received = $current_time;
$sigint_pending = 1;
}
$SIG{INT} = "sigint_handler";
# Parse command line options
GetOptions(
'ignore-pid' => \$opt_ignorepid,
'read-procstat' => \$opt_read_procstat,
'prepend-parent' => \$opt_prepend_parent,
);
# Defaults for dynamically discovered regex's
my $regex_fragdetails_default = 'page=([0-9a-f]*) pfn=([0-9]*) alloc_order=([-0-9]*) fallback_order=([-0-9]*) pageblock_order=([-0-9]*) alloc_migratetype=([-0-9]*) fallback_migratetype=([-0-9]*) fragmenting=([-0-9]) change_ownership=([-0-9])';
# Dyanically discovered regex
my $regex_fragdetails;
# Static regex used. Specified like this for readability and for use with /o
# (process_pid) (cpus ) ( time ) (tpoint ) (details)
my $regex_traceevent = '\s*([a-zA-Z0-9-]*)\s*(\[[0-9]*\])\s*([0-9.]*):\s*([a-zA-Z_]*):\s*(.*)';
my $regex_statname = '[-0-9]*\s\((.*)\).*';
my $regex_statppid = '[-0-9]*\s\(.*\)\s[A-Za-z]\s([0-9]*).*';
sub generate_traceevent_regex {
my $event = shift;
my $default = shift;
my $regex;
# Read the event format or use the default
if (!open (FORMAT, "/sys/kernel/debug/tracing/events/$event/format")) {
$regex = $default;
} else {
my $line;
while (!eof(FORMAT)) {
$line = <FORMAT>;
if ($line =~ /^print fmt:\s"(.*)",.*/) {
$regex = $1;
$regex =~ s/%p/\([0-9a-f]*\)/g;
$regex =~ s/%d/\([-0-9]*\)/g;
$regex =~ s/%lu/\([0-9]*\)/g;
}
}
}
# Verify fields are in the right order
my $tuple;
foreach $tuple (split /\s/, $regex) {
my ($key, $value) = split(/=/, $tuple);
my $expected = shift;
if ($key ne $expected) {
print("WARNING: Format not as expected '$key' != '$expected'");
$regex =~ s/$key=\((.*)\)/$key=$1/;
}
}
if (defined shift) {
die("Fewer fields than expected in format");
}
return $regex;
}
$regex_fragdetails = generate_traceevent_regex("kmem/mm_page_alloc_extfrag",
$regex_fragdetails_default,
"page", "pfn",
"alloc_order", "fallback_order", "pageblock_order",
"alloc_migratetype", "fallback_migratetype",
"fragmenting", "change_ownership");
sub read_statline($) {
my $pid = $_[0];
my $statline;
if (open(STAT, "/proc/$pid/stat")) {
$statline = <STAT>;
close(STAT);
}
if ($statline eq '') {
$statline = "-1 (UNKNOWN_PROCESS_NAME) R 0";
}
return $statline;
}
sub guess_process_pid($$) {
my $pid = $_[0];
my $statline = $_[1];
if ($pid == 0) {
return "swapper-0";
}
if ($statline !~ /$regex_statname/o) {
die("Failed to math stat line for process name :: $statline");
}
return "$1-$pid";
}
sub parent_info($$) {
my $pid = $_[0];
my $statline = $_[1];
my $ppid;
if ($pid == 0) {
return "NOPARENT-0";
}
if ($statline !~ /$regex_statppid/o) {
die("Failed to match stat line process ppid:: $statline");
}
# Read the ppid stat line
$ppid = $1;
return guess_process_pid($ppid, read_statline($ppid));
}
sub process_events {
my $traceevent;
my $process_pid;
my $cpus;
my $timestamp;
my $tracepoint;
my $details;
my $statline;
# Read each line of the event log
EVENT_PROCESS:
while ($traceevent = <STDIN>) {
if ($traceevent =~ /$regex_traceevent/o) {
$process_pid = $1;
$tracepoint = $4;
if ($opt_read_procstat || $opt_prepend_parent) {
$process_pid =~ /(.*)-([0-9]*)$/;
my $process = $1;
my $pid = $2;
$statline = read_statline($pid);
if ($opt_read_procstat && $process eq '') {
$process_pid = guess_process_pid($pid, $statline);
}
if ($opt_prepend_parent) {
$process_pid = parent_info($pid, $statline) . " :: $process_pid";
}
}
# Unnecessary in this script. Uncomment if required
# $cpus = $2;
# $timestamp = $3;
} else {
next;
}
# Perl Switch() sucks majorly
if ($tracepoint eq "mm_page_alloc") {
$perprocesspid{$process_pid}->{MM_PAGE_ALLOC}++;
} elsif ($tracepoint eq "mm_page_free_direct") {
$perprocesspid{$process_pid}->{MM_PAGE_FREE_DIRECT}++;
} elsif ($tracepoint eq "mm_pagevec_free") {
$perprocesspid{$process_pid}->{MM_PAGEVEC_FREE}++;
} elsif ($tracepoint eq "mm_page_pcpu_drain") {
$perprocesspid{$process_pid}->{MM_PAGE_PCPU_DRAIN}++;
$perprocesspid{$process_pid}->{STATE_PCPU_PAGES_DRAINED}++;
} elsif ($tracepoint eq "mm_page_alloc_zone_locked") {
$perprocesspid{$process_pid}->{MM_PAGE_ALLOC_ZONE_LOCKED}++;
$perprocesspid{$process_pid}->{STATE_PCPU_PAGES_REFILLED}++;
} elsif ($tracepoint eq "mm_page_alloc_extfrag") {
# Extract the details of the event now
$details = $5;
my ($page, $pfn);
my ($alloc_order, $fallback_order, $pageblock_order);
my ($alloc_migratetype, $fallback_migratetype);
my ($fragmenting, $change_ownership);
if ($details !~ /$regex_fragdetails/o) {
print "WARNING: Failed to parse mm_page_alloc_extfrag as expected\n";
next;
}
$perprocesspid{$process_pid}->{MM_PAGE_ALLOC_EXTFRAG}++;
$page = $1;
$pfn = $2;
$alloc_order = $3;
$fallback_order = $4;
$pageblock_order = $5;
$alloc_migratetype = $6;
$fallback_migratetype = $7;
$fragmenting = $8;
$change_ownership = $9;
if ($fragmenting) {
$perprocesspid{$process_pid}->{HIGH_EXT_FRAG}++;
if ($fallback_order <= 3) {
$perprocesspid{$process_pid}->{HIGH_EXT_FRAGMENT_SEVERE}++;
} else {
$perprocesspid{$process_pid}->{HIGH_EXT_FRAGMENT_MODERATE}++;
}
}
if ($change_ownership) {
$perprocesspid{$process_pid}->{HIGH_EXT_FRAGMENT_CHANGED}++;
}
} else {
$perprocesspid{$process_pid}->{EVENT_UNKNOWN}++;
}
# Catch a full pcpu drain event
if ($perprocesspid{$process_pid}->{STATE_PCPU_PAGES_DRAINED} &&
$tracepoint ne "mm_page_pcpu_drain") {
$perprocesspid{$process_pid}->{HIGH_PCPU_DRAINS}++;
$perprocesspid{$process_pid}->{STATE_PCPU_PAGES_DRAINED} = 0;
}
# Catch a full pcpu refill event
if ($perprocesspid{$process_pid}->{STATE_PCPU_PAGES_REFILLED} &&
$tracepoint ne "mm_page_alloc_zone_locked") {
$perprocesspid{$process_pid}->{HIGH_PCPU_REFILLS}++;
$perprocesspid{$process_pid}->{STATE_PCPU_PAGES_REFILLED} = 0;
}
if ($sigint_pending) {
last EVENT_PROCESS;
}
}
}
sub dump_stats {
my $hashref = shift;
my %stats = %$hashref;
# Dump per-process stats
my $process_pid;
my $max_strlen = 0;
# Get the maximum process name
foreach $process_pid (keys %perprocesspid) {
my $len = length($process_pid);
if ($len > $max_strlen) {
$max_strlen = $len;
}
}
$max_strlen += 2;
printf("\n");
printf("%-" . $max_strlen . "s %8s %10s %8s %8s %8s %8s %8s %8s %8s %8s %8s %8s %8s\n",
"Process", "Pages", "Pages", "Pages", "Pages", "PCPU", "PCPU", "PCPU", "Fragment", "Fragment", "MigType", "Fragment", "Fragment", "Unknown");
printf("%-" . $max_strlen . "s %8s %10s %8s %8s %8s %8s %8s %8s %8s %8s %8s %8s %8s\n",
"details", "allocd", "allocd", "freed", "freed", "pages", "drains", "refills", "Fallback", "Causing", "Changed", "Severe", "Moderate", "");
printf("%-" . $max_strlen . "s %8s %10s %8s %8s %8s %8s %8s %8s %8s %8s %8s %8s %8s\n",
"", "", "under lock", "direct", "pagevec", "drain", "", "", "", "", "", "", "", "");
foreach $process_pid (keys %stats) {
# Dump final aggregates
if ($stats{$process_pid}->{STATE_PCPU_PAGES_DRAINED}) {
$stats{$process_pid}->{HIGH_PCPU_DRAINS}++;
$stats{$process_pid}->{STATE_PCPU_PAGES_DRAINED} = 0;
}
if ($stats{$process_pid}->{STATE_PCPU_PAGES_REFILLED}) {
$stats{$process_pid}->{HIGH_PCPU_REFILLS}++;
$stats{$process_pid}->{STATE_PCPU_PAGES_REFILLED} = 0;
}
printf("%-" . $max_strlen . "s %8d %10d %8d %8d %8d %8d %8d %8d %8d %8d %8d %8d %8d\n",
$process_pid,
$stats{$process_pid}->{MM_PAGE_ALLOC},
$stats{$process_pid}->{MM_PAGE_ALLOC_ZONE_LOCKED},
$stats{$process_pid}->{MM_PAGE_FREE_DIRECT},
$stats{$process_pid}->{MM_PAGEVEC_FREE},
$stats{$process_pid}->{MM_PAGE_PCPU_DRAIN},
$stats{$process_pid}->{HIGH_PCPU_DRAINS},
$stats{$process_pid}->{HIGH_PCPU_REFILLS},
$stats{$process_pid}->{MM_PAGE_ALLOC_EXTFRAG},
$stats{$process_pid}->{HIGH_EXT_FRAG},
$stats{$process_pid}->{HIGH_EXT_FRAGMENT_CHANGED},
$stats{$process_pid}->{HIGH_EXT_FRAGMENT_SEVERE},
$stats{$process_pid}->{HIGH_EXT_FRAGMENT_MODERATE},
$stats{$process_pid}->{EVENT_UNKNOWN});
}
}
sub aggregate_perprocesspid() {
my $process_pid;
my $process;
undef %perprocess;
foreach $process_pid (keys %perprocesspid) {
$process = $process_pid;
$process =~ s/-([0-9])*$//;
if ($process eq '') {
$process = "NO_PROCESS_NAME";
}
$perprocess{$process}->{MM_PAGE_ALLOC} += $perprocesspid{$process_pid}->{MM_PAGE_ALLOC};
$perprocess{$process}->{MM_PAGE_ALLOC_ZONE_LOCKED} += $perprocesspid{$process_pid}->{MM_PAGE_ALLOC_ZONE_LOCKED};
$perprocess{$process}->{MM_PAGE_FREE_DIRECT} += $perprocesspid{$process_pid}->{MM_PAGE_FREE_DIRECT};
$perprocess{$process}->{MM_PAGEVEC_FREE} += $perprocesspid{$process_pid}->{MM_PAGEVEC_FREE};
$perprocess{$process}->{MM_PAGE_PCPU_DRAIN} += $perprocesspid{$process_pid}->{MM_PAGE_PCPU_DRAIN};
$perprocess{$process}->{HIGH_PCPU_DRAINS} += $perprocesspid{$process_pid}->{HIGH_PCPU_DRAINS};
$perprocess{$process}->{HIGH_PCPU_REFILLS} += $perprocesspid{$process_pid}->{HIGH_PCPU_REFILLS};
$perprocess{$process}->{MM_PAGE_ALLOC_EXTFRAG} += $perprocesspid{$process_pid}->{MM_PAGE_ALLOC_EXTFRAG};
$perprocess{$process}->{HIGH_EXT_FRAG} += $perprocesspid{$process_pid}->{HIGH_EXT_FRAG};
$perprocess{$process}->{HIGH_EXT_FRAGMENT_CHANGED} += $perprocesspid{$process_pid}->{HIGH_EXT_FRAGMENT_CHANGED};
$perprocess{$process}->{HIGH_EXT_FRAGMENT_SEVERE} += $perprocesspid{$process_pid}->{HIGH_EXT_FRAGMENT_SEVERE};
$perprocess{$process}->{HIGH_EXT_FRAGMENT_MODERATE} += $perprocesspid{$process_pid}->{HIGH_EXT_FRAGMENT_MODERATE};
$perprocess{$process}->{EVENT_UNKNOWN} += $perprocesspid{$process_pid}->{EVENT_UNKNOWN};
}
}
sub report() {
if (!$opt_ignorepid) {
dump_stats(\%perprocesspid);
} else {
aggregate_perprocesspid();
dump_stats(\%perprocess);
}
}
# Process events or signals until neither is available
sub signal_loop() {
my $sigint_processed;
do {
$sigint_processed = 0;
process_events();
# Handle pending signals if any
if ($sigint_pending) {
my $current_time = time;
if ($sigint_exit) {
print "Received exit signal\n";
$sigint_pending = 0;
}
if ($sigint_report) {
if ($current_time >= $sigint_received + 2) {
report();
$sigint_report = 0;
$sigint_pending = 0;
$sigint_processed = 1;
}
}
}
} while ($sigint_pending || $sigint_processed);
}
signal_loop();
report();
Documentation/trace/tracepoint-analysis.txt 0 → 100644
浏览文件 @ d9b2002c
Notes on Analysing Behaviour Using Events and Tracepoints
Documentation written by Mel Gorman
PCL information heavily based on email from Ingo Molnar
1. Introduction
===============
Tracepoints (see Documentation/trace/tracepoints.txt) can be used without
creating custom kernel modules to register probe functions using the event
tracing infrastructure.
Simplistically, tracepoints will represent an important event that when can
be taken in conjunction with other tracepoints to build a "Big Picture" of
what is going on within the system. There are a large number of methods for
gathering and interpreting these events. Lacking any current Best Practises,
this document describes some of the methods that can be used.
This document assumes that debugfs is mounted on /sys/kernel/debug and that
the appropriate tracing options have been configured into the kernel. It is
assumed that the PCL tool tools/perf has been installed and is in your path.
2. Listing Available Events
===========================
2.1 Standard Utilities
----------------------
All possible events are visible from /sys/kernel/debug/tracing/events. Simply
calling
$ find /sys/kernel/debug/tracing/events -type d
will give a fair indication of the number of events available.
2.2 PCL
-------
Discovery and enumeration of all counters and events, including tracepoints
are available with the perf tool. Getting a list of available events is a
simple case of
$ perf list 2>&1 | grep Tracepoint
ext4:ext4_free_inode [Tracepoint event]
ext4:ext4_request_inode [Tracepoint event]
ext4:ext4_allocate_inode [Tracepoint event]
ext4:ext4_write_begin [Tracepoint event]
ext4:ext4_ordered_write_end [Tracepoint event]
[ .... remaining output snipped .... ]
2. Enabling Events
==================
2.1 System-Wide Event Enabling
------------------------------
See Documentation/trace/events.txt for a proper description on how events
can be enabled system-wide. A short example of enabling all events related
to page allocation would look something like
$ for i in `find /sys/kernel/debug/tracing/events -name "enable" | grep mm_`; do echo 1 > $i; done
2.2 System-Wide Event Enabling with SystemTap
---------------------------------------------
In SystemTap, tracepoints are accessible using the kernel.trace() function
call. The following is an example that reports every 5 seconds what processes
were allocating the pages.
global page_allocs
probe kernel.trace("mm_page_alloc") {
page_allocs[execname()]++
}
function print_count() {
printf ("%-25s %-s\n", "#Pages Allocated", "Process Name")
foreach (proc in page_allocs-)
printf("%-25d %s\n", page_allocs[proc], proc)
printf ("\n")
delete page_allocs
}
probe timer.s(5) {
print_count()
}
2.3 System-Wide Event Enabling with PCL
---------------------------------------
By specifying the -a switch and analysing sleep, the system-wide events
for a duration of time can be examined.
$ perf stat -a \
-e kmem:mm_page_alloc -e kmem:mm_page_free_direct \
-e kmem:mm_pagevec_free \
sleep 10
Performance counter stats for 'sleep 10':
9630 kmem:mm_page_alloc
2143 kmem:mm_page_free_direct
7424 kmem:mm_pagevec_free
10.002577764 seconds time elapsed
Similarly, one could execute a shell and exit it as desired to get a report
at that point.
2.4 Local Event Enabling
------------------------
Documentation/trace/ftrace.txt describes how to enable events on a per-thread
basis using set_ftrace_pid.
2.5 Local Event Enablement with PCL
-----------------------------------
Events can be activate and tracked for the duration of a process on a local
basis using PCL such as follows.
$ perf stat -e kmem:mm_page_alloc -e kmem:mm_page_free_direct \
-e kmem:mm_pagevec_free ./hackbench 10
Time: 0.909
Performance counter stats for './hackbench 10':
17803 kmem:mm_page_alloc
12398 kmem:mm_page_free_direct
4827 kmem:mm_pagevec_free
0.973913387 seconds time elapsed
3. Event Filtering
==================
Documentation/trace/ftrace.txt covers in-depth how to filter events in
ftrace. Obviously using grep and awk of trace_pipe is an option as well
as any script reading trace_pipe.
4. Analysing Event Variances with PCL
=====================================
Any workload can exhibit variances between runs and it can be important
to know what the standard deviation in. By and large, this is left to the
performance analyst to do it by hand. In the event that the discrete event
occurrences are useful to the performance analyst, then perf can be used.
$ perf stat --repeat 5 -e kmem:mm_page_alloc -e kmem:mm_page_free_direct
-e kmem:mm_pagevec_free ./hackbench 10
Time: 0.890
Time: 0.895
Time: 0.915
Time: 1.001
Time: 0.899
Performance counter stats for './hackbench 10' (5 runs):
16630 kmem:mm_page_alloc ( +- 3.542% )
11486 kmem:mm_page_free_direct ( +- 4.771% )
4730 kmem:mm_pagevec_free ( +- 2.325% )
0.982653002 seconds time elapsed ( +- 1.448% )
In the event that some higher-level event is required that depends on some
aggregation of discrete events, then a script would need to be developed.
Using --repeat, it is also possible to view how events are fluctuating over
time on a system wide basis using -a and sleep.
$ perf stat -e kmem:mm_page_alloc -e kmem:mm_page_free_direct \
-e kmem:mm_pagevec_free \
-a --repeat 10 \
sleep 1
Performance counter stats for 'sleep 1' (10 runs):
1066 kmem:mm_page_alloc ( +- 26.148% )
182 kmem:mm_page_free_direct ( +- 5.464% )
890 kmem:mm_pagevec_free ( +- 30.079% )
1.002251757 seconds time elapsed ( +- 0.005% )
5. Higher-Level Analysis with Helper Scripts
============================================
When events are enabled the events that are triggering can be read from
/sys/kernel/debug/tracing/trace_pipe in human-readable format although binary
options exist as well. By post-processing the output, further information can
be gathered on-line as appropriate. Examples of post-processing might include
o Reading information from /proc for the PID that triggered the event
o Deriving a higher-level event from a series of lower-level events.
o Calculate latencies between two events
Documentation/trace/postprocess/trace-pagealloc-postprocess.pl is an example
script that can read trace_pipe from STDIN or a copy of a trace. When used
on-line, it can be interrupted once to generate a report without existing
and twice to exit.
Simplistically, the script just reads STDIN and counts up events but it
also can do more such as
o Derive high-level events from many low-level events. If a number of pages
are freed to the main allocator from the per-CPU lists, it recognises
that as one per-CPU drain even though there is no specific tracepoint
for that event
o It can aggregate based on PID or individual process number
o In the event memory is getting externally fragmented, it reports
on whether the fragmentation event was severe or moderate.
o When receiving an event about a PID, it can record who the parent was so
that if large numbers of events are coming from very short-lived
processes, the parent process responsible for creating all the helpers
can be identified
6. Lower-Level Analysis with PCL
================================
There may also be a requirement to identify what functions with a program
were generating events within the kernel. To begin this sort of analysis, the
data must be recorded. At the time of writing, this required root
$ perf record -c 1 \
-e kmem:mm_page_alloc -e kmem:mm_page_free_direct \
-e kmem:mm_pagevec_free \
./hackbench 10
Time: 0.894
[ perf record: Captured and wrote 0.733 MB perf.data (~32010 samples) ]
Note the use of '-c 1' to set the event period to sample. The default sample
period is quite high to minimise overhead but the information collected can be
very coarse as a result.
This record outputted a file called perf.data which can be analysed using
perf report.
$ perf report
# Samples: 30922
#
# Overhead Command Shared Object
# ........ ......... ................................
#
87.27% hackbench [vdso]
6.85% hackbench /lib/i686/cmov/libc-2.9.so
2.62% hackbench /lib/ld-2.9.so
1.52% perf [vdso]
1.22% hackbench ./hackbench
0.48% hackbench [kernel]
0.02% perf /lib/i686/cmov/libc-2.9.so
0.01% perf /usr/bin/perf
0.01% perf /lib/ld-2.9.so
0.00% hackbench /lib/i686/cmov/libpthread-2.9.so
#
# (For more details, try: perf report --sort comm,dso,symbol)
#
According to this, the vast majority of events occured triggered on events
within the VDSO. With simple binaries, this will often be the case so lets
take a slightly different example. In the course of writing this, it was
noticed that X was generating an insane amount of page allocations so lets look
at it
$ perf record -c 1 -f \
-e kmem:mm_page_alloc -e kmem:mm_page_free_direct \
-e kmem:mm_pagevec_free \
-p `pidof X`
This was interrupted after a few seconds and
$ perf report
# Samples: 27666
#
# Overhead Command Shared Object
# ........ ....... .......................................
#
51.95% Xorg [vdso]
47.95% Xorg /opt/gfx-test/lib/libpixman-1.so.0.13.1
0.09% Xorg /lib/i686/cmov/libc-2.9.so
0.01% Xorg [kernel]
#
# (For more details, try: perf report --sort comm,dso,symbol)
#
So, almost half of the events are occuring in a library. To get an idea which
symbol.
$ perf report --sort comm,dso,symbol
# Samples: 27666
#
# Overhead Command Shared Object Symbol
# ........ ....... ....................................... ......
#
51.95% Xorg [vdso] [.] 0x000000ffffe424
47.93% Xorg /opt/gfx-test/lib/libpixman-1.so.0.13.1 [.] pixmanFillsse2
0.09% Xorg /lib/i686/cmov/libc-2.9.so [.] _int_malloc
0.01% Xorg /opt/gfx-test/lib/libpixman-1.so.0.13.1 [.] pixman_region32_copy_f
0.01% Xorg [kernel] [k] read_hpet
0.01% Xorg /opt/gfx-test/lib/libpixman-1.so.0.13.1 [.] get_fast_path
0.00% Xorg [kernel] [k] ftrace_trace_userstack
To see where within the function pixmanFillsse2 things are going wrong
$ perf annotate pixmanFillsse2
[ ... ]
0.00 : 34eeb: 0f 18 08 prefetcht0 (%eax)
: }
:
: extern __inline void __attribute__((__gnu_inline__, __always_inline__, _
: _mm_store_si128 (__m128i *__P, __m128i __B) : {
: *__P = __B;
12.40 : 34eee: 66 0f 7f 80 40 ff ff movdqa %xmm0,-0xc0(%eax)
0.00 : 34ef5: ff
12.40 : 34ef6: 66 0f 7f 80 50 ff ff movdqa %xmm0,-0xb0(%eax)
0.00 : 34efd: ff
12.39 : 34efe: 66 0f 7f 80 60 ff ff movdqa %xmm0,-0xa0(%eax)
0.00 : 34f05: ff
12.67 : 34f06: 66 0f 7f 80 70 ff ff movdqa %xmm0,-0x90(%eax)
0.00 : 34f0d: ff
12.58 : 34f0e: 66 0f 7f 40 80 movdqa %xmm0,-0x80(%eax)
12.31 : 34f13: 66 0f 7f 40 90 movdqa %xmm0,-0x70(%eax)
12.40 : 34f18: 66 0f 7f 40 a0 movdqa %xmm0,-0x60(%eax)
12.31 : 34f1d: 66 0f 7f 40 b0 movdqa %xmm0,-0x50(%eax)
At a glance, it looks like the time is being spent copying pixmaps to
the card. Further investigation would be needed to determine why pixmaps
are being copied around so much but a starting point would be to take an
ancient build of libpixmap out of the library path where it was totally
forgotten about from months ago!
Documentation/usb/authorization.txt
浏览文件 @ d9b2002c
......@@ -16,20 +16,20 @@ Usage:
Authorize a device to connect:
$ echo 1 > /sys/usb/devices/DEVICE/authorized
$ echo 1 > /sys/bus/usb/devices/DEVICE/authorized
Deauthorize a device:
$ echo 0 > /sys/usb/devices/DEVICE/authorized
$ echo 0 > /sys/bus/usb/devices/DEVICE/authorized
Set new devices connected to hostX to be deauthorized by default (ie:
lock down):
$ echo 0 > /sys/bus/devices/usbX/authorized_default
$ echo 0 > /sys/bus/usb/devices/usbX/authorized_default
Remove the lock down:
$ echo 1 > /sys/bus/devices/usbX/authorized_default
$ echo 1 > /sys/bus/usb/devices/usbX/authorized_default
By default, Wired USB devices are authorized by default to
connect. Wireless USB hosts deauthorize by default all new connected
......@@ -47,7 +47,7 @@ USB port):
boot up
rc.local ->
for host in /sys/bus/devices/usb*
for host in /sys/bus/usb/devices/usb*
do
echo 0 > $host/authorized_default
done
......
Documentation/usb/usbmon.txt
浏览文件 @ d9b2002c
......@@ -33,7 +33,7 @@ if usbmon is built into the kernel.
Verify that bus sockets are present.
# ls /sys/kernel/debug/usbmon
# ls /sys/kernel/debug/usb/usbmon
0s 0u 1s 1t 1u 2s 2t 2u 3s 3t 3u 4s 4t 4u
#
......@@ -58,11 +58,11 @@ Bus=03 means it's bus 3.
3. Start 'cat'
# cat /sys/kernel/debug/usbmon/3u > /tmp/1.mon.out
# cat /sys/kernel/debug/usb/usbmon/3u > /tmp/1.mon.out
to listen on a single bus, otherwise, to listen on all buses, type:
# cat /sys/kernel/debug/usbmon/0u > /tmp/1.mon.out
# cat /sys/kernel/debug/usb/usbmon/0u > /tmp/1.mon.out
This process will be reading until killed. Naturally, the output can be
redirected to a desirable location. This is preferred, because it is going
......@@ -305,7 +305,7 @@ Before the call, hdr, data, and alloc should be filled. Upon return, the area
pointed by hdr contains the next event structure, and the data buffer contains
the data, if any. The event is removed from the kernel buffer.
The MON_IOCX_GET copies 48 bytes, MON_IOCX_GETX copies 64 bytes.
The MON_IOCX_GET copies 48 bytes to hdr area, MON_IOCX_GETX copies 64 bytes.
MON_IOCX_MFETCH, defined as _IOWR(MON_IOC_MAGIC, 7, struct mon_mfetch_arg)
......
Documentation/video4linux/v4lgrab.c
浏览文件 @ d9b2002c
......@@ -89,7 +89,7 @@
} \
}
int get_brightness_adj(unsigned char *image, long size, int *brightness) {
static int get_brightness_adj(unsigned char *image, long size, int *brightness) {
long i, tot = 0;
for (i=0;i<size*3;i++)
tot += image[i];
......
Documentation/vm/00-INDEX
浏览文件 @ d9b2002c
......@@ -6,6 +6,8 @@ balance
- various information on memory balancing.
hugetlbpage.txt
- a brief summary of hugetlbpage support in the Linux kernel.
ksm.txt
- how to use the Kernel Samepage Merging feature.
locking
- info on how locking and synchronization is done in the Linux vm code.
numa
......@@ -20,3 +22,5 @@ slabinfo.c
- source code for a tool to get reports about slabs.
slub.txt
- a short users guide for SLUB.
map_hugetlb.c
- an example program that uses the MAP_HUGETLB mmap flag.
Documentation/vm/hugetlbpage.txt
浏览文件 @ d9b2002c
......@@ -18,13 +18,13 @@ First the Linux kernel needs to be built with the CONFIG_HUGETLBFS
automatically when CONFIG_HUGETLBFS is selected) configuration
options.
The kernel built with hugepage support should show the number of configured
hugepages in the system by running the "cat /proc/meminfo" command.
The kernel built with huge page support should show the number of configured
huge pages in the system by running the "cat /proc/meminfo" command.
/proc/meminfo also provides information about the total number of hugetlb
pages configured in the kernel. It also displays information about the
number of free hugetlb pages at any time. It also displays information about
the configured hugepage size - this is needed for generating the proper
the configured huge page size - this is needed for generating the proper
alignment and size of the arguments to the above system calls.
The output of "cat /proc/meminfo" will have lines like:
......@@ -37,25 +37,27 @@ HugePages_Surp: yyy
Hugepagesize: zzz kB
where:
HugePages_Total is the size of the pool of hugepages.
HugePages_Free is the number of hugepages in the pool that are not yet
allocated.
HugePages_Rsvd is short for "reserved," and is the number of hugepages
for which a commitment to allocate from the pool has been made, but no
allocation has yet been made. It's vaguely analogous to overcommit.
HugePages_Surp is short for "surplus," and is the number of hugepages in
the pool above the value in /proc/sys/vm/nr_hugepages. The maximum
number of surplus hugepages is controlled by
/proc/sys/vm/nr_overcommit_hugepages.
HugePages_Total is the size of the pool of huge pages.
HugePages_Free is the number of huge pages in the pool that are not yet
allocated.
HugePages_Rsvd is short for "reserved," and is the number of huge pages for
which a commitment to allocate from the pool has been made,
but no allocation has yet been made. Reserved huge pages
guarantee that an application will be able to allocate a
huge page from the pool of huge pages at fault time.
HugePages_Surp is short for "surplus," and is the number of huge pages in
the pool above the value in /proc/sys/vm/nr_hugepages. The
maximum number of surplus huge pages is controlled by
/proc/sys/vm/nr_overcommit_hugepages.
/proc/filesystems should also show a filesystem of type "hugetlbfs" configured
in the kernel.
/proc/sys/vm/nr_hugepages indicates the current number of configured hugetlb
pages in the kernel. Super user can dynamically request more (or free some
pre-configured) hugepages.
pre-configured) huge pages.
The allocation (or deallocation) of hugetlb pages is possible only if there are
enough physically contiguous free pages in system (freeing of hugepages is
enough physically contiguous free pages in system (freeing of huge pages is
possible only if there are enough hugetlb pages free that can be transferred
back to regular memory pool).
......@@ -67,43 +69,82 @@ use either the mmap system call or shared memory system calls to start using
the huge pages. It is required that the system administrator preallocate
enough memory for huge page purposes.
Use the following command to dynamically allocate/deallocate hugepages:
The administrator can preallocate huge pages on the kernel boot command line by
specifying the "hugepages=N" parameter, where 'N' = the number of huge pages
requested. This is the most reliable method for preallocating huge pages as
memory has not yet become fragmented.
Some platforms support multiple huge page sizes. To preallocate huge pages
of a specific size, one must preceed the huge pages boot command parameters
with a huge page size selection parameter "hugepagesz=<size>". <size> must
be specified in bytes with optional scale suffix [kKmMgG]. The default huge
page size may be selected with the "default_hugepagesz=<size>" boot parameter.
/proc/sys/vm/nr_hugepages indicates the current number of configured [default
size] hugetlb pages in the kernel. Super user can dynamically request more
(or free some pre-configured) huge pages.
Use the following command to dynamically allocate/deallocate default sized
huge pages:
echo 20 > /proc/sys/vm/nr_hugepages
This command will try to configure 20 hugepages in the system. The success
or failure of allocation depends on the amount of physically contiguous
memory that is preset in system at this time. System administrators may want
to put this command in one of the local rc init files. This will enable the
kernel to request huge pages early in the boot process (when the possibility
of getting physical contiguous pages is still very high). In either
case, administrators will want to verify the number of hugepages actually
allocated by checking the sysctl or meminfo.
/proc/sys/vm/nr_overcommit_hugepages indicates how large the pool of
hugepages can grow, if more hugepages than /proc/sys/vm/nr_hugepages are
requested by applications. echo'ing any non-zero value into this file
indicates that the hugetlb subsystem is allowed to try to obtain
hugepages from the buddy allocator, if the normal pool is exhausted. As
these surplus hugepages go out of use, they are freed back to the buddy
This command will try to configure 20 default sized huge pages in the system.
On a NUMA platform, the kernel will attempt to distribute the huge page pool
over the all on-line nodes. These huge pages, allocated when nr_hugepages
is increased, are called "persistent huge pages".
The success or failure of huge page allocation depends on the amount of
physically contiguous memory that is preset in system at the time of the
allocation attempt. If the kernel is unable to allocate huge pages from
some nodes in a NUMA system, it will attempt to make up the difference by
allocating extra pages on other nodes with sufficient available contiguous
memory, if any.
System administrators may want to put this command in one of the local rc init
files. This will enable the kernel to request huge pages early in the boot
process when the possibility of getting physical contiguous pages is still
very high. Administrators can verify the number of huge pages actually
allocated by checking the sysctl or meminfo. To check the per node
distribution of huge pages in a NUMA system, use:
cat /sys/devices/system/node/node*/meminfo | fgrep Huge
/proc/sys/vm/nr_overcommit_hugepages specifies how large the pool of
huge pages can grow, if more huge pages than /proc/sys/vm/nr_hugepages are
requested by applications. Writing any non-zero value into this file
indicates that the hugetlb subsystem is allowed to try to obtain "surplus"
huge pages from the buddy allocator, when the normal pool is exhausted. As
these surplus huge pages go out of use, they are freed back to the buddy
allocator.
When increasing the huge page pool size via nr_hugepages, any surplus
pages will first be promoted to persistent huge pages. Then, additional
huge pages will be allocated, if necessary and if possible, to fulfill
the new huge page pool size.
The administrator may shrink the pool of preallocated huge pages for
the default huge page size by setting the nr_hugepages sysctl to a
smaller value. The kernel will attempt to balance the freeing of huge pages
across all on-line nodes. Any free huge pages on the selected nodes will
be freed back to the buddy allocator.
Caveat: Shrinking the pool via nr_hugepages such that it becomes less
than the number of hugepages in use will convert the balance to surplus
than the number of huge pages in use will convert the balance to surplus
huge pages even if it would exceed the overcommit value. As long as
this condition holds, however, no more surplus huge pages will be
allowed on the system until one of the two sysctls are increased
sufficiently, or the surplus huge pages go out of use and are freed.
With support for multiple hugepage pools at run-time available, much of
the hugepage userspace interface has been duplicated in sysfs. The above
information applies to the default hugepage size (which will be
controlled by the proc interfaces for backwards compatibility). The root
hugepage control directory is
With support for multiple huge page pools at run-time available, much of
the huge page userspace interface has been duplicated in sysfs. The above
information applies to the default huge page size which will be
controlled by the /proc interfaces for backwards compatibility. The root
huge page control directory in sysfs is:
/sys/kernel/mm/hugepages
For each hugepage size supported by the running kernel, a subdirectory
For each huge page size supported by the running kernel, a subdirectory
will exist, of the form
hugepages-${size}kB
......@@ -116,9 +157,9 @@ Inside each of these directories, the same set of files will exist:
resv_hugepages
surplus_hugepages
which function as described above for the default hugepage-sized case.
which function as described above for the default huge page-sized case.
If the user applications are going to request hugepages using mmap system
If the user applications are going to request huge pages using mmap system
call, then it is required that system administrator mount a file system of
type hugetlbfs:
......@@ -127,7 +168,7 @@ type hugetlbfs:
none /mnt/huge
This command mounts a (pseudo) filesystem of type hugetlbfs on the directory
/mnt/huge. Any files created on /mnt/huge uses hugepages. The uid and gid
/mnt/huge. Any files created on /mnt/huge uses huge pages. The uid and gid
options sets the owner and group of the root of the file system. By default
the uid and gid of the current process are taken. The mode option sets the
mode of root of file system to value & 0777. This value is given in octal.
......@@ -146,24 +187,26 @@ Regular chown, chgrp, and chmod commands (with right permissions) could be
used to change the file attributes on hugetlbfs.
Also, it is important to note that no such mount command is required if the
applications are going to use only shmat/shmget system calls. Users who
wish to use hugetlb page via shared memory segment should be a member of
a supplementary group and system admin needs to configure that gid into
/proc/sys/vm/hugetlb_shm_group. It is possible for same or different
applications to use any combination of mmaps and shm* calls, though the
mount of filesystem will be required for using mmap calls.
applications are going to use only shmat/shmget system calls or mmap with
MAP_HUGETLB. Users who wish to use hugetlb page via shared memory segment
should be a member of a supplementary group and system admin needs to
configure that gid into /proc/sys/vm/hugetlb_shm_group. It is possible for
same or different applications to use any combination of mmaps and shm*
calls, though the mount of filesystem will be required for using mmap calls
without MAP_HUGETLB. For an example of how to use mmap with MAP_HUGETLB see
map_hugetlb.c.
*******************************************************************
/*
* Example of using hugepage memory in a user application using Sys V shared
* Example of using huge page memory in a user application using Sys V shared
* memory system calls. In this example the app is requesting 256MB of
* memory that is backed by huge pages. The application uses the flag
* SHM_HUGETLB in the shmget system call to inform the kernel that it is
* requesting hugepages.
* requesting huge pages.
*
* For the ia64 architecture, the Linux kernel reserves Region number 4 for
* hugepages. That means the addresses starting with 0x800000... will need
* huge pages. That means the addresses starting with 0x800000... will need
* to be specified. Specifying a fixed address is not required on ppc64,
* i386 or x86_64.
*
......@@ -252,14 +295,14 @@ int main(void)
*******************************************************************
/*
* Example of using hugepage memory in a user application using the mmap
* Example of using huge page memory in a user application using the mmap
* system call. Before running this application, make sure that the
* administrator has mounted the hugetlbfs filesystem (on some directory
* like /mnt) using the command mount -t hugetlbfs nodev /mnt. In this
* example, the app is requesting memory of size 256MB that is backed by
* huge pages.
*
* For ia64 architecture, Linux kernel reserves Region number 4 for hugepages.
* For ia64 architecture, Linux kernel reserves Region number 4 for huge pages.
* That means the addresses starting with 0x800000... will need to be
* specified. Specifying a fixed address is not required on ppc64, i386
* or x86_64.
......
Documentation/vm/ksm.txt 0 → 100644
浏览文件 @ d9b2002c
How to use the Kernel Samepage Merging feature
----------------------------------------------
KSM is a memory-saving de-duplication feature, enabled by CONFIG_KSM=y,
added to the Linux kernel in 2.6.32. See mm/ksm.c for its implementation,
and http://lwn.net/Articles/306704/ and http://lwn.net/Articles/330589/
The KSM daemon ksmd periodically scans those areas of user memory which
have been registered with it, looking for pages of identical content which
can be replaced by a single write-protected page (which is automatically
copied if a process later wants to update its content).
KSM was originally developed for use with KVM (where it was known as
Kernel Shared Memory), to fit more virtual machines into physical memory,
by sharing the data common between them. But it can be useful to any
application which generates many instances of the same data.
KSM only merges anonymous (private) pages, never pagecache (file) pages.
KSM's merged pages are at present locked into kernel memory for as long
as they are shared: so cannot be swapped out like the user pages they
replace (but swapping KSM pages should follow soon in a later release).
KSM only operates on those areas of address space which an application
has advised to be likely candidates for merging, by using the madvise(2)
system call: int madvise(addr, length, MADV_MERGEABLE).
The app may call int madvise(addr, length, MADV_UNMERGEABLE) to cancel
that advice and restore unshared pages: whereupon KSM unmerges whatever
it merged in that range. Note: this unmerging call may suddenly require
more memory than is available - possibly failing with EAGAIN, but more
probably arousing the Out-Of-Memory killer.
If KSM is not configured into the running kernel, madvise MADV_MERGEABLE
and MADV_UNMERGEABLE simply fail with EINVAL. If the running kernel was
built with CONFIG_KSM=y, those calls will normally succeed: even if the
the KSM daemon is not currently running, MADV_MERGEABLE still registers
the range for whenever the KSM daemon is started; even if the range
cannot contain any pages which KSM could actually merge; even if
MADV_UNMERGEABLE is applied to a range which was never MADV_MERGEABLE.
Like other madvise calls, they are intended for use on mapped areas of
the user address space: they will report ENOMEM if the specified range
includes unmapped gaps (though working on the intervening mapped areas),
and might fail with EAGAIN if not enough memory for internal structures.
Applications should be considerate in their use of MADV_MERGEABLE,
restricting its use to areas likely to benefit. KSM's scans may use
a lot of processing power, and its kernel-resident pages are a limited
resource. Some installations will disable KSM for these reasons.
The KSM daemon is controlled by sysfs files in /sys/kernel/mm/ksm/,
readable by all but writable only by root:
max_kernel_pages - set to maximum number of kernel pages that KSM may use
e.g. "echo 2000 > /sys/kernel/mm/ksm/max_kernel_pages"
Value 0 imposes no limit on the kernel pages KSM may use;
but note that any process using MADV_MERGEABLE can cause
KSM to allocate these pages, unswappable until it exits.
Default: 2000 (chosen for demonstration purposes)
pages_to_scan - how many present pages to scan before ksmd goes to sleep
e.g. "echo 200 > /sys/kernel/mm/ksm/pages_to_scan"
Default: 200 (chosen for demonstration purposes)
sleep_millisecs - how many milliseconds ksmd should sleep before next scan
e.g. "echo 20 > /sys/kernel/mm/ksm/sleep_millisecs"
Default: 20 (chosen for demonstration purposes)
run - set 0 to stop ksmd from running but keep merged pages,
set 1 to run ksmd e.g. "echo 1 > /sys/kernel/mm/ksm/run",
set 2 to stop ksmd and unmerge all pages currently merged,
but leave mergeable areas registered for next run
Default: 1 (for immediate use by apps which register)
The effectiveness of KSM and MADV_MERGEABLE is shown in /sys/kernel/mm/ksm/:
pages_shared - how many shared unswappable kernel pages KSM is using
pages_sharing - how many more sites are sharing them i.e. how much saved
pages_unshared - how many pages unique but repeatedly checked for merging
pages_volatile - how many pages changing too fast to be placed in a tree
full_scans - how many times all mergeable areas have been scanned
A high ratio of pages_sharing to pages_shared indicates good sharing, but
a high ratio of pages_unshared to pages_sharing indicates wasted effort.
pages_volatile embraces several different kinds of activity, but a high
proportion there would also indicate poor use of madvise MADV_MERGEABLE.
Izik Eidus,
Hugh Dickins, 30 July 2009
Documentation/vm/locking
浏览文件 @ d9b2002c
......@@ -80,7 +80,7 @@ Note: PTL can also be used to guarantee that no new clones using the
mm start up ... this is a loose form of stability on mm_users. For
example, it is used in copy_mm to protect against a racing tlb_gather_mmu
single address space optimization, so that the zap_page_range (from
vmtruncate) does not lose sending ipi's to cloned threads that might
truncate) does not lose sending ipi's to cloned threads that might
be spawned underneath it and go to user mode to drag in pte's into tlbs.
swap_lock
......
Documentation/vm/map_hugetlb.c 0 → 100644
浏览文件 @ d9b2002c
/*
* Example of using hugepage memory in a user application using the mmap
* system call with MAP_HUGETLB flag. Before running this program make
* sure the administrator has allocated enough default sized huge pages
* to cover the 256 MB allocation.
*
* For ia64 architecture, Linux kernel reserves Region number 4 for hugepages.
* That means the addresses starting with 0x800000... will need to be
* specified. Specifying a fixed address is not required on ppc64, i386
* or x86_64.
*/
#include <stdlib.h>
#include <stdio.h>
#include <unistd.h>
#include <sys/mman.h>
#include <fcntl.h>
#define LENGTH (256UL*1024*1024)
#define PROTECTION (PROT_READ | PROT_WRITE)
#ifndef MAP_HUGETLB
#define MAP_HUGETLB 0x40
#endif
/* Only ia64 requires this */
#ifdef __ia64__
#define ADDR (void *)(0x8000000000000000UL)
#define FLAGS (MAP_PRIVATE | MAP_ANONYMOUS | MAP_HUGETLB | MAP_FIXED)
#else
#define ADDR (void *)(0x0UL)
#define FLAGS (MAP_PRIVATE | MAP_ANONYMOUS | MAP_HUGETLB)
#endif
void check_bytes(char *addr)
{
printf("First hex is %x\n", *((unsigned int *)addr));
}
void write_bytes(char *addr)
{
unsigned long i;
for (i = 0; i < LENGTH; i++)
*(addr + i) = (char)i;
}
void read_bytes(char *addr)
{
unsigned long i;
check_bytes(addr);
for (i = 0; i < LENGTH; i++)
if (*(addr + i) != (char)i) {
printf("Mismatch at %lu\n", i);
break;
}
}
int main(void)
{
void *addr;
addr = mmap(ADDR, LENGTH, PROTECTION, FLAGS, 0, 0);
if (addr == MAP_FAILED) {
perror("mmap");
exit(1);
}
printf("Returned address is %p\n", addr);
check_bytes(addr);
write_bytes(addr);
read_bytes(addr);
munmap(addr, LENGTH);
return 0;
}
Documentation/vm/page-types.c
浏览文件 @ d9b2002c
此差异已折叠。
Documentation/vm/slabinfo.c
浏览文件 @ d9b2002c
......@@ -87,7 +87,7 @@ int page_size;
regex_t pattern;
void fatal(const char *x, ...)
static void fatal(const char *x, ...)
{
va_list ap;
......@@ -97,7 +97,7 @@ void fatal(const char *x, ...)
exit(EXIT_FAILURE);
}
void usage(void)
static void usage(void)
{
printf("slabinfo 5/7/2007. (c) 2007 sgi.\n\n"
"slabinfo [-ahnpvtsz] [-d debugopts] [slab-regexp]\n"
......@@ -131,7 +131,7 @@ void usage(void)
);
}
unsigned long read_obj(const char *name)
static unsigned long read_obj(const char *name)
{
FILE *f = fopen(name, "r");
......@@ -151,7 +151,7 @@ unsigned long read_obj(const char *name)
/*
* Get the contents of an attribute
*/
unsigned long get_obj(const char *name)
static unsigned long get_obj(const char *name)
{
if (!read_obj(name))
return 0;
......@@ -159,7 +159,7 @@ unsigned long get_obj(const char *name)
return atol(buffer);
}
unsigned long get_obj_and_str(const char *name, char **x)
static unsigned long get_obj_and_str(const char *name, char **x)
{
unsigned long result = 0;
char *p;
......@@ -178,7 +178,7 @@ unsigned long get_obj_and_str(const char *name, char **x)
return result;
}
void set_obj(struct slabinfo *s, const char *name, int n)
static void set_obj(struct slabinfo *s, const char *name, int n)
{
char x[100];
FILE *f;
......@@ -192,7 +192,7 @@ void set_obj(struct slabinfo *s, const char *name, int n)
fclose(f);
}
unsigned long read_slab_obj(struct slabinfo *s, const char *name)
static unsigned long read_slab_obj(struct slabinfo *s, const char *name)
{
char x[100];
FILE *f;
......@@ -215,7 +215,7 @@ unsigned long read_slab_obj(struct slabinfo *s, const char *name)
/*
* Put a size string together
*/
int store_size(char *buffer, unsigned long value)
static int store_size(char *buffer, unsigned long value)
{
unsigned long divisor = 1;
char trailer = 0;
......@@ -247,7 +247,7 @@ int store_size(char *buffer, unsigned long value)
return n;
}
void decode_numa_list(int *numa, char *t)
static void decode_numa_list(int *numa, char *t)
{
int node;
int nr;
......@@ -272,7 +272,7 @@ void decode_numa_list(int *numa, char *t)
}
}
void slab_validate(struct slabinfo *s)
static void slab_validate(struct slabinfo *s)
{
if (strcmp(s->name, "*") == 0)
return;
......@@ -280,7 +280,7 @@ void slab_validate(struct slabinfo *s)
set_obj(s, "validate", 1);
}
void slab_shrink(struct slabinfo *s)
static void slab_shrink(struct slabinfo *s)
{
if (strcmp(s->name, "*") == 0)
return;
......@@ -290,7 +290,7 @@ void slab_shrink(struct slabinfo *s)
int line = 0;
void first_line(void)
static void first_line(void)
{
if (show_activity)
printf("Name Objects Alloc Free %%Fast Fallb O\n");
......@@ -302,7 +302,7 @@ void first_line(void)
/*
* Find the shortest alias of a slab
*/
struct aliasinfo *find_one_alias(struct slabinfo *find)
static struct aliasinfo *find_one_alias(struct slabinfo *find)
{
struct aliasinfo *a;
struct aliasinfo *best = NULL;
......@@ -318,18 +318,18 @@ struct aliasinfo *find_one_alias(struct slabinfo *find)
return best;
}
unsigned long slab_size(struct slabinfo *s)
static unsigned long slab_size(struct slabinfo *s)
{
return s->slabs * (page_size << s->order);
}
unsigned long slab_activity(struct slabinfo *s)
static unsigned long slab_activity(struct slabinfo *s)
{
return s->alloc_fastpath + s->free_fastpath +
s->alloc_slowpath + s->free_slowpath;
}
void slab_numa(struct slabinfo *s, int mode)
static void slab_numa(struct slabinfo *s, int mode)
{
int node;
......@@ -374,7 +374,7 @@ void slab_numa(struct slabinfo *s, int mode)
line++;
}
void show_tracking(struct slabinfo *s)
static void show_tracking(struct slabinfo *s)
{
printf("\n%s: Kernel object allocation\n", s->name);
printf("-----------------------------------------------------------------------\n");
......@@ -392,7 +392,7 @@ void show_tracking(struct slabinfo *s)
}
void ops(struct slabinfo *s)
static void ops(struct slabinfo *s)
{
if (strcmp(s->name, "*") == 0)
return;
......@@ -405,14 +405,14 @@ void ops(struct slabinfo *s)
printf("\n%s has no kmem_cache operations\n", s->name);
}
const char *onoff(int x)
static const char *onoff(int x)
{
if (x)
return "On ";
return "Off";
}
void slab_stats(struct slabinfo *s)
static void slab_stats(struct slabinfo *s)
{
unsigned long total_alloc;
unsigned long total_free;
......@@ -477,7 +477,7 @@ void slab_stats(struct slabinfo *s)
s->deactivate_to_tail, (s->deactivate_to_tail * 100) / total);
}
void report(struct slabinfo *s)
static void report(struct slabinfo *s)
{
if (strcmp(s->name, "*") == 0)
return;
......@@ -518,7 +518,7 @@ void report(struct slabinfo *s)
slab_stats(s);
}
void slabcache(struct slabinfo *s)
static void slabcache(struct slabinfo *s)
{
char size_str[20];
char dist_str[40];
......@@ -593,7 +593,7 @@ void slabcache(struct slabinfo *s)
/*
* Analyze debug options. Return false if something is amiss.
*/
int debug_opt_scan(char *opt)
static int debug_opt_scan(char *opt)
{
if (!opt || !opt[0] || strcmp(opt, "-") == 0)
return 1;
......@@ -642,7 +642,7 @@ int debug_opt_scan(char *opt)
return 1;
}
int slab_empty(struct slabinfo *s)
static int slab_empty(struct slabinfo *s)
{
if (s->objects > 0)
return 0;
......@@ -657,7 +657,7 @@ int slab_empty(struct slabinfo *s)
return 1;
}
void slab_debug(struct slabinfo *s)
static void slab_debug(struct slabinfo *s)
{
if (strcmp(s->name, "*") == 0)
return;
......@@ -717,7 +717,7 @@ void slab_debug(struct slabinfo *s)
set_obj(s, "trace", 1);
}
void totals(void)
static void totals(void)
{
struct slabinfo *s;
......@@ -976,7 +976,7 @@ void totals(void)
b1, b2, b3);
}
void sort_slabs(void)
static void sort_slabs(void)
{
struct slabinfo *s1,*s2;
......@@ -1005,7 +1005,7 @@ void sort_slabs(void)
}
}
void sort_aliases(void)
static void sort_aliases(void)
{
struct aliasinfo *a1,*a2;
......@@ -1030,7 +1030,7 @@ void sort_aliases(void)
}
}
void link_slabs(void)
static void link_slabs(void)
{
struct aliasinfo *a;
struct slabinfo *s;
......@@ -1048,7 +1048,7 @@ void link_slabs(void)
}
}
void alias(void)
static void alias(void)
{
struct aliasinfo *a;
char *active = NULL;
......@@ -1079,7 +1079,7 @@ void alias(void)
}
void rename_slabs(void)
static void rename_slabs(void)
{
struct slabinfo *s;
struct aliasinfo *a;
......@@ -1102,12 +1102,12 @@ void rename_slabs(void)
}
}
int slab_mismatch(char *slab)
static int slab_mismatch(char *slab)
{
return regexec(&pattern, slab, 0, NULL, 0);
}
void read_slab_dir(void)
static void read_slab_dir(void)
{
DIR *dir;
struct dirent *de;
......@@ -1209,7 +1209,7 @@ void read_slab_dir(void)
fatal("Too many aliases\n");
}
void output_slabs(void)
static void output_slabs(void)
{
struct slabinfo *slab;
......
Documentation/watchdog/src/watchdog-test.c
浏览文件 @ d9b2002c
......@@ -18,7 +18,7 @@ int fd;
* the PC Watchdog card to reset its internal timer so it doesn't trigger
* a computer reset.
*/
void keep_alive(void)
static void keep_alive(void)
{
int dummy;
......
Documentation/x86/earlyprintk.txt
浏览文件 @ d9b2002c
......@@ -7,7 +7,7 @@ and two USB cables, connected like this:
[host/target] <-------> [USB debug key] <-------> [client/console]
1. There are three specific hardware requirements:
1. There are a number of specific hardware requirements:
a.) Host/target system needs to have USB debug port capability.
......@@ -42,7 +42,35 @@ and two USB cables, connected like this:
This is a small blue plastic connector with two USB connections,
it draws power from its USB connections.
c.) Thirdly, you need a second client/console system with a regular USB port.
c.) You need a second client/console system with a high speed USB 2.0
port.
d.) The Netchip device must be plugged directly into the physical
debug port on the "host/target" system. You cannot use a USB hub in
between the physical debug port and the "host/target" system.
The EHCI debug controller is bound to a specific physical USB
port and the Netchip device will only work as an early printk
device in this port. The EHCI host controllers are electrically
wired such that the EHCI debug controller is hooked up to the
first physical and there is no way to change this via software.
You can find the physical port through experimentation by trying
each physical port on the system and rebooting. Or you can try
and use lsusb or look at the kernel info messages emitted by the
usb stack when you plug a usb device into various ports on the
"host/target" system.
Some hardware vendors do not expose the usb debug port with a
physical connector and if you find such a device send a complaint
to the hardware vendor, because there is no reason not to wire
this port into one of the physically accessible ports.
e.) It is also important to note, that many versions of the Netchip
device require the "client/console" system to be plugged into the
right and side of the device (with the product logo facing up and
readable left to right). The reason being is that the 5 volt
power supply is taken from only one side of the device and it
must be the side that does not get rebooted.
2. Software requirements:
......@@ -56,6 +84,13 @@ and two USB cables, connected like this:
(If you are using Grub, append it to the 'kernel' line in
/etc/grub.conf)
On systems with more than one EHCI debug controller you must
specify the correct EHCI debug controller number. The ordering
comes from the PCI bus enumeration of the EHCI controllers. The
default with no number argument is "0" the first EHCI debug
controller. To use the second EHCI debug controller, you would
use the command line: "earlyprintk=dbgp1"
NOTE: normally earlyprintk console gets turned off once the
regular console is alive - use "earlyprintk=dbgp,keep" to keep
this channel open beyond early bootup. This can be useful for
......
MAINTAINERS
浏览文件 @ d9b2002c
此差异已折叠。
Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/alpha/Kconfig
浏览文件 @ d9b2002c
......@@ -45,6 +45,14 @@ config GENERIC_CALIBRATE_DELAY
bool
default y
config GENERIC_TIME
bool
default y
config ARCH_USES_GETTIMEOFFSET
bool
default y
config ZONE_DMA
bool
default y
......
arch/alpha/boot/tools/objstrip.c
浏览文件 @ d9b2002c
......@@ -93,7 +93,7 @@ main (int argc, char *argv[])
ofd = 1;
if (i < argc) {
ofd = open(argv[i++], O_WRONLY | O_CREAT | O_TRUNC, 0666);
if (fd == -1) {
if (ofd == -1) {
perror("open");
exit(1);
}
......
arch/alpha/include/asm/fcntl.h
浏览文件 @ d9b2002c
......@@ -26,6 +26,8 @@
#define F_GETOWN 6 /* for sockets. */
#define F_SETSIG 10 /* for sockets. */
#define F_GETSIG 11 /* for sockets. */
#define F_SETOWN_EX 12
#define F_GETOWN_EX 13
/* for posix fcntl() and lockf() */
#define F_RDLCK 1
......
arch/alpha/include/asm/hardirq.h
浏览文件 @ d9b2002c
#ifndef _ALPHA_HARDIRQ_H
#define _ALPHA_HARDIRQ_H
#include <linux/threads.h>
#include <linux/cache.h>
/* entry.S is sensitive to the offsets of these fields */
typedef struct {
unsigned long __softirq_pending;
} ____cacheline_aligned irq_cpustat_t;
#include <linux/irq_cpustat.h> /* Standard mappings for irq_cpustat_t above */
void ack_bad_irq(unsigned int irq);
#define ack_bad_irq ack_bad_irq
#include <asm-generic/hardirq.h>
#endif /* _ALPHA_HARDIRQ_H */
arch/alpha/include/asm/mman.h
浏览文件 @ d9b2002c
......@@ -28,6 +28,8 @@
#define MAP_NORESERVE 0x10000 /* don't check for reservations */
#define MAP_POPULATE 0x20000 /* populate (prefault) pagetables */
#define MAP_NONBLOCK 0x40000 /* do not block on IO */
#define MAP_STACK 0x80000 /* give out an address that is best suited for process/thread stacks */
#define MAP_HUGETLB 0x100000 /* create a huge page mapping */
#define MS_ASYNC 1 /* sync memory asynchronously */
#define MS_SYNC 2 /* synchronous memory sync */
......@@ -48,6 +50,9 @@
#define MADV_DONTFORK 10 /* don't inherit across fork */
#define MADV_DOFORK 11 /* do inherit across fork */
#define MADV_MERGEABLE 12 /* KSM may merge identical pages */
#define MADV_UNMERGEABLE 13 /* KSM may not merge identical pages */
/* compatibility flags */
#define MAP_FILE 0
......
arch/alpha/include/asm/smp.h
浏览文件 @ d9b2002c
......@@ -47,7 +47,7 @@ extern struct cpuinfo_alpha cpu_data[NR_CPUS];
extern int smp_num_cpus;
extern void arch_send_call_function_single_ipi(int cpu);
extern void arch_send_call_function_ipi(cpumask_t mask);
extern void arch_send_call_function_ipi_mask(const struct cpumask *mask);
#else /* CONFIG_SMP */
......
arch/alpha/include/asm/topology.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/alpha/kernel/core_marvel.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/alpha/kernel/core_titan.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/alpha/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/alpha/kernel/pci_impl.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/alpha/kernel/pci_iommu.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/alpha/kernel/process.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/alpha/kernel/smp.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/alpha/kernel/time.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/alpha/kernel/vmlinux.lds.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/alpha/mm/init.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/alpha/mm/numa.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/boot/install.sh
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/common/locomo.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/common/vic.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/configs/n770_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/configs/nhk8815_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/configs/omap_ldp_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/include/asm/atomic.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/include/asm/cache.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/include/asm/cacheflush.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/include/asm/cputype.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/include/asm/mman.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/include/asm/mmu_context.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/include/asm/smp.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/include/asm/tcm.h 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/include/asm/tlbflush.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/include/asm/unified.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/kernel/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/kernel/entry-armv.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/kernel/entry-header.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/kernel/kprobes.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/kernel/setup.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/kernel/smp.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/kernel/sys_arm.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/kernel/tcm.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/kernel/tcm.h 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/kernel/vmlinux.lds.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/lib/copy_page.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-at91/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-at91/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-at91/board-cam60.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-at91/board-cap9adk.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-at91/board-sam9g20ek-2slot-mmc.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-at91/board-sam9rlek.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-ep93xx/clock.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-ep93xx/core.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-ep93xx/include/mach/fb.h 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-iop13xx/setup.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-ixp4xx/common.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-nomadik/include/mach/fsmc.h 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-nomadik/include/mach/nand.h 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-omap2/board-apollon.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-omap2/devices.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-omap2/gpmc.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-omap2/mmc-twl4030.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-omap2/mmc-twl4030.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/balloon3.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/clock.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/cm-x270.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/cm-x300.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/colibri-pxa300.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/colibri-pxa320.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/colibri-pxa3xx.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/corgi.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/csb726.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/devices.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/devices.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/e740.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/e750.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/em-x270.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/eseries.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/gumstix.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/hx4700.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/idp.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/imote2.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/include/mach/balloon3.h 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/include/mach/palmtc.h 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/irq.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/littleton.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/lubbock.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/magician.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/mainstone.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/mioa701.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/palmld.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/palmt5.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/palmtc.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/palmte2.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/palmtx.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/palmz72.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/poodle.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/pxa2xx.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/pxa300.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/pxa320.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/pxa930.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/spitz.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/tosa.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/treo680.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/trizeps4.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/xcep.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-pxa/zylonite.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-realview/core.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-realview/core.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-s3c2410/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-s3c2412/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-s3c2440/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-s3c6400/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-s3c6410/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-sa1100/dma.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-u300/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-u300/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-u300/core.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-u300/dummyspichip.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-u300/gpio.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-u300/i2c.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-u300/i2c.h 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-u300/mmc.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-u300/padmux.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-u300/padmux.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-u300/spi.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-u300/spi.h 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-u300/timer.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mach-versatile/core.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mm/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mm/context.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mm/fault.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mm/flush.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/mm/init.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/plat-iop/adma.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/plat-mxc/include/mach/spi.h 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/plat-pxa/dma.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/plat-pxa/mfp.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/plat-s3c/gpio.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/plat-s3c64xx/dma.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/plat-stmp3xxx/dma.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/arm/tools/mach-types
浏览文件 @ d9b2002c
此差异已折叠。
arch/avr32/include/asm/mman.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/avr32/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/avr32/mm/init.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/blackfin/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/blackfin/boot/install.sh
浏览文件 @ d9b2002c
此差异已折叠。
arch/blackfin/kernel/vmlinux.lds.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/cris/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/cris/arch-v10/kernel/time.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/cris/arch-v32/kernel/smp.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/cris/arch-v32/kernel/time.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/cris/arch-v32/mach-a3/io.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/cris/arch-v32/mach-fs/io.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/cris/include/asm/hardirq.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/cris/include/asm/mman.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/cris/include/asm/pgtable.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/cris/kernel/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/cris/kernel/irq.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/cris/kernel/process.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/cris/kernel/vmlinux.lds.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/cris/mm/init.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/frv/include/asm/gdb-stub.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/frv/include/asm/hardirq.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/frv/include/asm/mman.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/frv/kernel/debug-stub.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/frv/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/frv/kernel/pm.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/frv/kernel/process.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/frv/kernel/sys_frv.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/frv/lib/cache.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/frv/mb93090-mb00/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/frv/mb93090-mb00/flash.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/h8300/include/asm/hardirq.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/h8300/include/asm/mman.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/h8300/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/h8300/kernel/irq.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/h8300/kernel/sys_h8300.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/h8300/kernel/timer/tpu.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/h8300/kernel/vmlinux.lds.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/hp/common/sba_iommu.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/ia32/binfmt_elf32.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/ia32/sys_ia32.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/include/asm/acpi.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/include/asm/cputime.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/include/asm/mman.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/include/asm/smp.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/include/asm/spinlock.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/include/asm/topology.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/install.sh
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/kernel/Makefile.gate
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/kernel/head.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/kernel/ia64_ksyms.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/kernel/pci-swiotlb.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/kernel/smp.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/mm/init.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/ia64/oprofile/backtrace.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/m32r/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/m32r/include/asm/hardirq.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/m32r/include/asm/mman.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/m32r/include/asm/mmu_context.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/m32r/include/asm/page.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/m32r/include/asm/processor.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/m32r/include/asm/smp.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/m32r/include/asm/thread_info.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/m32r/kernel/entry.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/m32r/kernel/head.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/m32r/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/m32r/kernel/ptrace.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/m32r/kernel/smp.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/m32r/kernel/smpboot.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/m32r/kernel/time.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/m32r/kernel/vmlinux.lds.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/m32r/mm/init.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/m68k/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/m68k/include/asm/hardirq_mm.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/m68k/include/asm/mman.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/m68k/install.sh
浏览文件 @ d9b2002c
此差异已折叠。
arch/m68k/kernel/process.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/m68k/kernel/sys_m68k.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/m68k/kernel/time.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/m68k/mm/init.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/m68knommu/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/m68knommu/kernel/sys_m68k.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/microblaze/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/microblaze/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/microblaze/boot/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/microblaze/boot/dts/system.dts 0 → 120000
浏览文件 @ d9b2002c
此差异已折叠。
arch/microblaze/boot/linked_dtb.S 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/microblaze/include/asm/asm-compat.h 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/microblaze/include/asm/io.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/microblaze/include/asm/ipc.h 已删除 100644 → 0
浏览文件 @ c3b32fcb
此差异已折叠。
arch/microblaze/include/asm/page.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/microblaze/include/asm/setup.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/microblaze/include/asm/syscall.h 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/microblaze/kernel/entry.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/microblaze/kernel/exceptions.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/microblaze/kernel/head.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/microblaze/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/microblaze/kernel/process.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/microblaze/kernel/ptrace.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/microblaze/kernel/setup.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/microblaze/mm/init.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/alchemy/common/time.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/include/asm/mman.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/include/asm/mmu_context.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/include/asm/pgtable.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/include/asm/smp-ops.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/include/asm/smp.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/kernel/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/kernel/smp-cmp.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/kernel/smp-mt.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/kernel/smp-up.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/kernel/smp.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/kernel/smtc.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/kernel/vmlinux.lds.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/lasat/sysctl.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/mipssim/sim_smtc.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/mm/c-octeon.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/mm/init.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/mti-malta/malta-smtc.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/pmc-sierra/yosemite/smp.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/sgi-ip27/ip27-memory.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/sgi-ip27/ip27-smp.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/sibyte/bcm1480/smp.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mips/sibyte/sb1250/smp.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mn10300/include/asm/gdb-stub.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/mn10300/include/asm/mman.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/mn10300/kernel/asm-offsets.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mn10300/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mn10300/kernel/setup.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mn10300/kernel/sys_mn10300.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/mn10300/kernel/vmlinux.lds.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/mn10300/mm/init.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/parisc/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/parisc/include/asm/fcntl.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/parisc/include/asm/mman.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/parisc/include/asm/smp.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/parisc/install.sh
浏览文件 @ d9b2002c
此差异已折叠。
arch/parisc/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/parisc/kernel/sys_parisc32.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/parisc/kernel/vmlinux.lds.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/parisc/mm/init.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/boot/install.sh
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/include/asm/cputime.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/include/asm/device.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/include/asm/fsldma.h 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/include/asm/iommu.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/include/asm/mman.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/include/asm/pmc.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/include/asm/pte-40x.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/include/asm/pte-8xx.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/include/asm/smp.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/include/asm/topology.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/kernel/dma-iommu.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/kernel/dma.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/kernel/pci-common.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/kernel/process.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/kernel/prom_init.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/kernel/setup-common.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/kernel/smp.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/kernel/sys_ppc32.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/kernel/time.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/kernel/udbg_16550.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/kernel/vdso.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/kernel/vdso32/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/kernel/vdso64/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/kernel/vio.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/kernel/vmlinux.lds.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/mm/init_32.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/mm/init_64.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/mm/mem.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/mm/pgtable.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/mm/tlb_low_64e.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/platforms/cell/iommu.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/relocs_check.pl 0 → 100755
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/sysdev/axonram.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/sysdev/dart_iommu.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/powerpc/xmon/xmon.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/appldata/appldata_base.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/boot/install.sh
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/hypfs/inode.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/include/asm/cputime.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/include/asm/lowcore.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/include/asm/mman.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/include/asm/processor.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/include/asm/smp.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/include/asm/topology.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/kernel/asm-offsets.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/kernel/compat_linux.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/kernel/compat_linux.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/kernel/compat_wrapper.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/kernel/debug.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/kernel/entry.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/kernel/process.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/kernel/ptrace.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/kernel/sclp.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/kernel/smp.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/kernel/suspend.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/kernel/swsusp_asm64.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/kernel/syscalls.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/kernel/vdso.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/kernel/vdso32/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/kernel/vdso64/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/kvm/interrupt.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/mm/cmm.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/mm/init.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/mm/page-states.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/s390/mm/pgtable.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/score/include/asm/page.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/score/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/score/kernel/vmlinux.lds.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/boards/mach-se/7724/setup.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/boot/compressed/install.sh
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/ap325rxa_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/dreamcast_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/ecovec24_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/edosk7705_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/edosk7760_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/espt_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/hp6xx_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/kfr2r09_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/landisk_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/lboxre2_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/microdev_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/migor_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/polaris_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/r7780mp_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/r7785rp_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/rsk7201_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/rsk7203_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/sdk7780_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/se7206_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/se7343_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/se7619_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/se7705_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/se7712_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/se7721_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/se7722_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/se7724_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/se7750_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/se7751_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/se7780_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/sh03_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/sh7763rdp_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/sh7785lcr_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/shmin_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/shx3_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/snapgear_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/systemh_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/titan_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/ul2_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/configs/urquell_defconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/drivers/dma/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/drivers/dma/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/include/asm/dma-sh.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/include/asm/smp.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/include/asm/topology.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/kernel/dwarf.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/kernel/irq.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/kernel/sys_sh32.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/kernel/sys_sh64.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/kernel/traps_32.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/kernel/vsyscall/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/sh/mm/init.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/sparc/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/sparc/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/sparc/include/asm/mman.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/sparc/include/asm/smp_64.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/sparc/include/asm/vio.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/sparc/kernel/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/sparc/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/sparc/kernel/irq_64.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/sparc/kernel/sys_sparc32.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/sparc/kernel/systbls.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/sparc/mm/init_32.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/um/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/um/drivers/net_kern.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/um/drivers/ubd_kern.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/um/include/asm/common.lds.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/um/include/asm/hardirq.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/um/include/asm/mmu_context.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/um/kernel/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/um/kernel/dyn.lds.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/um/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/um/kernel/mem.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/um/kernel/skas/mmu.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/um/kernel/smp.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/um/kernel/uml.lds.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/um/kernel/vmlinux.lds.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/boot/compressed/head_32.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/boot/compressed/head_64.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/boot/install.sh
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/include/asm/acpi.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/include/asm/cache.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/include/asm/mmu_context.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/include/asm/nmi.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/include/asm/pci.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/include/asm/smp.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/include/asm/syscall.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/include/asm/topology.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/acpi/cstate.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/apic/io_apic.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/apic/nmi.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/cpu/amd.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/cpu/mcheck/mce.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/dumpstack_32.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/dumpstack_64.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/e820.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/early_printk.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/entry_64.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/head_32.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/head_64.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/ldt.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/microcode_core.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/pci-swiotlb.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/process.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/ptrace.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/setup.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/sfi.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/smpboot.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/time.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/traps.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/tsc_sync.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/vmlinux.lds.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/kernel/vsyscall_64.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/lguest/boot.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/mm/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/mm/fault.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/mm/init.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/mm/init_32.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/mm/init_64.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/mm/kmemcheck/kmemcheck.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/mm/pageattr.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/mm/pat.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/mm/setup_nx.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/mm/tlb.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/pci/common.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/pci/i386.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/pci/mmconfig-shared.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/pci/mmconfig_32.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/vdso/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/xen/enlighten.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/x86/xen/mmu.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/xtensa/include/asm/mman.h
浏览文件 @ d9b2002c
此差异已折叠。
arch/xtensa/kernel/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
arch/xtensa/kernel/head.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/xtensa/kernel/init_task.c
浏览文件 @ d9b2002c
此差异已折叠。
arch/xtensa/kernel/vmlinux.lds.S
浏览文件 @ d9b2002c
此差异已折叠。
arch/xtensa/mm/init.c
浏览文件 @ d9b2002c
此差异已折叠。
crypto/async_tx/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
crypto/async_tx/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
crypto/async_tx/async_memcpy.c
浏览文件 @ d9b2002c
此差异已折叠。
crypto/async_tx/async_memset.c
浏览文件 @ d9b2002c
此差异已折叠。
crypto/async_tx/async_pq.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
crypto/async_tx/async_raid6_recov.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
crypto/async_tx/async_tx.c
浏览文件 @ d9b2002c
此差异已折叠。
crypto/async_tx/async_xor.c
浏览文件 @ d9b2002c
此差异已折叠。
crypto/async_tx/raid6test.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/ac.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpi_memhotplug.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/acconfig.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/acdebug.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/acglobal.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/achware.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/acinterp.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/aclocal.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/acmacros.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/acnamesp.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/acobject.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/acparser.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/acpredef.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/acutils.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/amlcode.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/dsfield.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/dsmethod.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/dsmthdat.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/dsobject.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/dswload.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/evgpe.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/evgpeblk.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/evrgnini.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/exconfig.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/exdump.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/exfield.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/exfldio.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/exutils.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/hwgpe.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/hwregs.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/hwtimer.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/hwxface.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/nsalloc.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/nsdumpdv.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/nseval.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/nsinit.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/nsload.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/nspredef.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/nsrepair.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/nsutils.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/nsxfeval.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/nsxfname.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/psloop.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/psxface.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/tbutils.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/utdelete.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/uteval.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/utglobal.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/utids.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/utinit.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/utmisc.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/acpica/utxface.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/battery.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/blacklist.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/bus.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/button.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/cm_sbs.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/container.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/debug.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/dock.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/ec.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/event.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/fan.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/glue.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/internal.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/numa.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/osl.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/pci_irq.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/pci_link.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/pci_root.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/pci_slot.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/power.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/power_meter.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/processor_core.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/processor_idle.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/processor_perflib.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/processor_thermal.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/processor_throttling.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/sbs.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/sbshc.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/scan.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/sleep.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/system.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/tables.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/thermal.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/utils.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/video.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/acpi/video_detect.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/ata/pata_hpt37x.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/atm/he.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/atm/solos-attrlist.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/atm/solos-pci.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/base/node.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/DAC960.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/amiflop.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/aoe/aoeblk.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/ataflop.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/brd.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/cciss.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/cpqarray.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/floppy.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/hd.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/loop.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/mg_disk.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/nbd.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/osdblk.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/paride/pcd.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/paride/pd.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/paride/pf.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/pktcdvd.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/ps3disk.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/ps3vram.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/sunvdc.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/swim.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/swim3.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/sx8.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/ub.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/umem.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/viodasd.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/virtio_blk.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/xd.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/xen-blkfront.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/xsysace.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/block/z2ram.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/cdrom/cdrom.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/cdrom/gdrom.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/cdrom/viocd.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/agp/agp.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/agp/alpha-agp.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/agp/backend.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/agp/hp-agp.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/agp/intel-agp.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/agp/uninorth-agp.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/bfin-otp.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/epca.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/hpet.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/hvc_console.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/hvc_console.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/hvc_iucv.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/hw_random/virtio-rng.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/ipmi/ipmi_poweroff.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/mem.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/misc.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/mspec.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/mwave/mwavedd.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/pcmcia/cm4000_cs.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/random.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/rio/rioctrl.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/tpm/tpm.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/tpm/tpm_bios.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/tty_io.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/uv_mmtimer.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/char/virtio_console.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/connector/cn_proc.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/cpuidle/governors/menu.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dca/dca-core.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/at_hdmac.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/at_hdmac_regs.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/dmaengine.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/dmatest.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/dw_dmac.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/dw_dmac_regs.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/fsldma.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/fsldma.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/ioat/Makefile 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/ioat/dma.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/ioat/dma.h 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/ioat/dma_v2.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/ioat/dma_v2.h 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/ioat/dma_v3.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/ioat_dma.c 已删除 100644 → 0
浏览文件 @ c3b32fcb
此差异已折叠。
drivers/dma/ioatdma.h 已删除 100644 → 0
浏览文件 @ c3b32fcb
此差异已折叠。
drivers/dma/iop-adma.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/iovlock.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/mv_xor.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/mv_xor.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/shdma.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/shdma.h 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/txx9dmac.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/dma/txx9dmac.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/edac/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
drivers/edac/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
drivers/edac/cpc925_edac.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/edac/edac_core.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/edac/edac_device.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/edac/edac_mc.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/edac/edac_pci.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/edac/i3200_edac.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/edac/mpc85xx_edac.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/edac/mv64x60_edac.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/firewire/core-card.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/firewire/core-transaction.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/firewire/core.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/firewire/ohci.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/firewire/sbp2.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/firmware/memmap.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpio/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpio/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpio/adp5520-gpio.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpio/bt8xxgpio.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpio/gpiolib.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpio/langwell_gpio.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpio/max7301.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpio/mc33880.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpio/mcp23s08.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpio/pca953x.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpio/pcf857x.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpio/ucb1400_gpio.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/drm_gem.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/drm_vm.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/i915/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/i915/i915_debugfs.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/i915/i915_dma.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/i915/i915_drv.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/i915/i915_drv.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/i915/i915_gem.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/i915/i915_irq.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/i915/i915_reg.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/i915/i915_suspend.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/i915/i915_trace.h 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/i915/i915_trace_points.c 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/i915/intel_bios.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/i915/intel_crt.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/i915/intel_dp.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/i915/intel_drv.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/i915/intel_lvds.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/i915/intel_sdvo.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/mga/mga_state.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/radeon/r600_blit.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/radeon/radeon.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/radeon/radeon_drv.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/radeon/radeon_family.h 0 → 100644
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/radeon/radeon_ttm.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/gpu/drm/ttm/ttm_bo_vm.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hid/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hid/hid-core.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hid/usbhid/hid-core.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hwmon/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hwmon/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hwmon/adcxx.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hwmon/adm1021.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hwmon/adm1031.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hwmon/applesmc.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hwmon/coretemp.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hwmon/dme1737.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hwmon/fscher.c 已删除 100644 → 0
浏览文件 @ c3b32fcb
此差异已折叠。
drivers/hwmon/fscpos.c 已删除 100644 → 0
浏览文件 @ c3b32fcb
此差异已折叠。
drivers/hwmon/lis3lv02d.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hwmon/lis3lv02d.h
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hwmon/lis3lv02d_spi.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hwmon/lm70.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hwmon/ltc4215.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hwmon/ltc4245.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hwmon/max1111.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/hwmon/sht15.c
浏览文件 @ d9b2002c
此差异已折叠。
drivers/i2c/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
drivers/i2c/busses/Kconfig
浏览文件 @ d9b2002c
此差异已折叠。
drivers/i2c/busses/Makefile
浏览文件 @ d9b2002c
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或