Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
提交 74511020 编写于 作者: M Mark Brown
浏览文件
操作

Merge branch 'for-2.6.34' into for-2.6.35

上级 69266866 3cc4e53f
展开全部 隐藏空白更改
内联 并排
Showing with 64758 addition and 14438 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
.gitignore
浏览文件 @ 74511020
......@@ -34,14 +34,18 @@ modules.builtin
#
# Top-level generic files
#
tags
TAGS
linux
vmlinux
vmlinuz
System.map
Module.markers
Module.symvers
/tags
/TAGS
/linux
/vmlinux
/vmlinuz
/System.map
/Module.markers
/Module.symvers
#
# git files that we don't want to ignore even it they are dot-files
#
!.gitignore
!.mailmap
......
Documentation/ABI/testing/sysfs-bus-usb
浏览文件 @ 74511020
......@@ -160,7 +160,7 @@ Description:
match the driver to the device. For example:
# echo "046d c315" > /sys/bus/usb/drivers/foo/remove_id
What: /sys/bus/usb/device/.../avoid_reset
What: /sys/bus/usb/device/.../avoid_reset_quirk
Date: December 2009
Contact: Oliver Neukum <oliver@neukum.org>
Description:
......
Documentation/DMA-API.txt
浏览文件 @ 74511020
......@@ -4,20 +4,18 @@
James E.J. Bottomley <James.Bottomley@HansenPartnership.com>
This document describes the DMA API. For a more gentle introduction
phrased in terms of the pci_ equivalents (and actual examples) see
Documentation/PCI/PCI-DMA-mapping.txt.
of the API (and actual examples) see
Documentation/DMA-API-HOWTO.txt.
This API is split into two pieces. Part I describes the API and the
corresponding pci_ API. Part II describes the extensions to the API
for supporting non-consistent memory machines. Unless you know that
your driver absolutely has to support non-consistent platforms (this
is usually only legacy platforms) you should only use the API
described in part I.
This API is split into two pieces. Part I describes the API. Part II
describes the extensions to the API for supporting non-consistent
memory machines. Unless you know that your driver absolutely has to
support non-consistent platforms (this is usually only legacy
platforms) you should only use the API described in part I.
Part I - pci_ and dma_ Equivalent API
Part I - dma_ API
-------------------------------------
To get the pci_ API, you must #include <linux/pci.h>
To get the dma_ API, you must #include <linux/dma-mapping.h>
......@@ -27,9 +25,6 @@ Part Ia - Using large dma-coherent buffers
void *
dma_alloc_coherent(struct device *dev, size_t size,
dma_addr_t *dma_handle, gfp_t flag)
void *
pci_alloc_consistent(struct pci_dev *dev, size_t size,
dma_addr_t *dma_handle)
Consistent memory is memory for which a write by either the device or
the processor can immediately be read by the processor or device
......@@ -53,15 +48,11 @@ The simplest way to do that is to use the dma_pool calls (see below).
The flag parameter (dma_alloc_coherent only) allows the caller to
specify the GFP_ flags (see kmalloc) for the allocation (the
implementation may choose to ignore flags that affect the location of
the returned memory, like GFP_DMA). For pci_alloc_consistent, you
must assume GFP_ATOMIC behaviour.
the returned memory, like GFP_DMA).
void
dma_free_coherent(struct device *dev, size_t size, void *cpu_addr,
dma_addr_t dma_handle)
void
pci_free_consistent(struct pci_dev *dev, size_t size, void *cpu_addr,
dma_addr_t dma_handle)
Free the region of consistent memory you previously allocated. dev,
size and dma_handle must all be the same as those passed into the
......@@ -89,10 +80,6 @@ for alignment, like queue heads needing to be aligned on N-byte boundaries.
dma_pool_create(const char *name, struct device *dev,
size_t size, size_t align, size_t alloc);
struct pci_pool *
pci_pool_create(const char *name, struct pci_device *dev,
size_t size, size_t align, size_t alloc);
The pool create() routines initialize a pool of dma-coherent buffers
for use with a given device. It must be called in a context which
can sleep.
......@@ -108,9 +95,6 @@ from this pool must not cross 4KByte boundaries.
void *dma_pool_alloc(struct dma_pool *pool, gfp_t gfp_flags,
dma_addr_t *dma_handle);
void *pci_pool_alloc(struct pci_pool *pool, gfp_t gfp_flags,
dma_addr_t *dma_handle);
This allocates memory from the pool; the returned memory will meet the size
and alignment requirements specified at creation time. Pass GFP_ATOMIC to
prevent blocking, or if it's permitted (not in_interrupt, not holding SMP locks),
......@@ -122,9 +106,6 @@ pool's device.
void dma_pool_free(struct dma_pool *pool, void *vaddr,
dma_addr_t addr);
void pci_pool_free(struct pci_pool *pool, void *vaddr,
dma_addr_t addr);
This puts memory back into the pool. The pool is what was passed to
the pool allocation routine; the cpu (vaddr) and dma addresses are what
were returned when that routine allocated the memory being freed.
......@@ -132,8 +113,6 @@ were returned when that routine allocated the memory being freed.
void dma_pool_destroy(struct dma_pool *pool);
void pci_pool_destroy(struct pci_pool *pool);
The pool destroy() routines free the resources of the pool. They must be
called in a context which can sleep. Make sure you've freed all allocated
memory back to the pool before you destroy it.
......@@ -144,8 +123,6 @@ Part Ic - DMA addressing limitations
int
dma_supported(struct device *dev, u64 mask)
int
pci_dma_supported(struct pci_dev *hwdev, u64 mask)
Checks to see if the device can support DMA to the memory described by
mask.
......@@ -159,8 +136,14 @@ driver writers.
int
dma_set_mask(struct device *dev, u64 mask)
Checks to see if the mask is possible and updates the device
parameters if it is.
Returns: 0 if successful and a negative error if not.
int
pci_set_dma_mask(struct pci_device *dev, u64 mask)
dma_set_coherent_mask(struct device *dev, u64 mask)
Checks to see if the mask is possible and updates the device
parameters if it is.
......@@ -187,9 +170,6 @@ Part Id - Streaming DMA mappings
dma_addr_t
dma_map_single(struct device *dev, void *cpu_addr, size_t size,
enum dma_data_direction direction)
dma_addr_t
pci_map_single(struct pci_dev *hwdev, void *cpu_addr, size_t size,
int direction)
Maps a piece of processor virtual memory so it can be accessed by the
device and returns the physical handle of the memory.
......@@ -198,14 +178,10 @@ The direction for both api's may be converted freely by casting.
However the dma_ API uses a strongly typed enumerator for its
direction:
DMA_NONE = PCI_DMA_NONE no direction (used for
debugging)
DMA_TO_DEVICE = PCI_DMA_TODEVICE data is going from the
memory to the device
DMA_FROM_DEVICE = PCI_DMA_FROMDEVICE data is coming from
the device to the
memory
DMA_BIDIRECTIONAL = PCI_DMA_BIDIRECTIONAL direction isn't known
DMA_NONE no direction (used for debugging)
DMA_TO_DEVICE data is going from the memory to the device
DMA_FROM_DEVICE data is coming from the device to the memory
DMA_BIDIRECTIONAL direction isn't known
Notes: Not all memory regions in a machine can be mapped by this
API. Further, regions that appear to be physically contiguous in
......@@ -268,9 +244,6 @@ cache lines are updated with data that the device may have changed).
void
dma_unmap_single(struct device *dev, dma_addr_t dma_addr, size_t size,
enum dma_data_direction direction)
void
pci_unmap_single(struct pci_dev *hwdev, dma_addr_t dma_addr,
size_t size, int direction)
Unmaps the region previously mapped. All the parameters passed in
must be identical to those passed in (and returned) by the mapping
......@@ -280,15 +253,9 @@ dma_addr_t
dma_map_page(struct device *dev, struct page *page,
unsigned long offset, size_t size,
enum dma_data_direction direction)
dma_addr_t
pci_map_page(struct pci_dev *hwdev, struct page *page,
unsigned long offset, size_t size, int direction)
void
dma_unmap_page(struct device *dev, dma_addr_t dma_address, size_t size,
enum dma_data_direction direction)
void
pci_unmap_page(struct pci_dev *hwdev, dma_addr_t dma_address,
size_t size, int direction)
API for mapping and unmapping for pages. All the notes and warnings
for the other mapping APIs apply here. Also, although the <offset>
......@@ -299,9 +266,6 @@ cache width is.
int
dma_mapping_error(struct device *dev, dma_addr_t dma_addr)
int
pci_dma_mapping_error(struct pci_dev *hwdev, dma_addr_t dma_addr)
In some circumstances dma_map_single and dma_map_page will fail to create
a mapping. A driver can check for these errors by testing the returned
dma address with dma_mapping_error(). A non-zero return value means the mapping
......@@ -311,9 +275,6 @@ reduce current DMA mapping usage or delay and try again later).
int
dma_map_sg(struct device *dev, struct scatterlist *sg,
int nents, enum dma_data_direction direction)
int
pci_map_sg(struct pci_dev *hwdev, struct scatterlist *sg,
int nents, int direction)
Returns: the number of physical segments mapped (this may be shorter
than <nents> passed in if some elements of the scatter/gather list are
......@@ -353,9 +314,6 @@ accessed sg->address and sg->length as shown above.
void
dma_unmap_sg(struct device *dev, struct scatterlist *sg,
int nhwentries, enum dma_data_direction direction)
void
pci_unmap_sg(struct pci_dev *hwdev, struct scatterlist *sg,
int nents, int direction)
Unmap the previously mapped scatter/gather list. All the parameters
must be the same as those and passed in to the scatter/gather mapping
......@@ -365,21 +323,23 @@ Note: <nents> must be the number you passed in, *not* the number of
physical entries returned.
void
dma_sync_single(struct device *dev, dma_addr_t dma_handle, size_t size,
enum dma_data_direction direction)
dma_sync_single_for_cpu(struct device *dev, dma_addr_t dma_handle, size_t size,
enum dma_data_direction direction)
void
pci_dma_sync_single(struct pci_dev *hwdev, dma_addr_t dma_handle,
size_t size, int direction)
dma_sync_single_for_device(struct device *dev, dma_addr_t dma_handle, size_t size,
enum dma_data_direction direction)
void
dma_sync_sg(struct device *dev, struct scatterlist *sg, int nelems,
enum dma_data_direction direction)
dma_sync_sg_for_cpu(struct device *dev, struct scatterlist *sg, int nelems,
enum dma_data_direction direction)
void
pci_dma_sync_sg(struct pci_dev *hwdev, struct scatterlist *sg,
int nelems, int direction)
dma_sync_sg_for_device(struct device *dev, struct scatterlist *sg, int nelems,
enum dma_data_direction direction)
Synchronise a single contiguous or scatter/gather mapping. All the
parameters must be the same as those passed into the single mapping
API.
Synchronise a single contiguous or scatter/gather mapping for the cpu
and device. With the sync_sg API, all the parameters must be the same
as those passed into the single mapping API. With the sync_single API,
you can use dma_handle and size parameters that aren't identical to
those passed into the single mapping API to do a partial sync.
Notes: You must do this:
......@@ -461,9 +421,9 @@ void whizco_dma_map_sg_attrs(struct device *dev, dma_addr_t dma_addr,
Part II - Advanced dma_ usage
-----------------------------
Warning: These pieces of the DMA API have no PCI equivalent. They
should also not be used in the majority of cases, since they cater for
unlikely corner cases that don't belong in usual drivers.
Warning: These pieces of the DMA API should not be used in the
majority of cases, since they cater for unlikely corner cases that
don't belong in usual drivers.
If you don't understand how cache line coherency works between a
processor and an I/O device, you should not be using this part of the
......@@ -513,16 +473,6 @@ line, but it will guarantee that one or more cache lines fit exactly
into the width returned by this call. It will also always be a power
of two for easy alignment.
void
dma_sync_single_range(struct device *dev, dma_addr_t dma_handle,
unsigned long offset, size_t size,
enum dma_data_direction direction)
Does a partial sync, starting at offset and continuing for size. You
must be careful to observe the cache alignment and width when doing
anything like this. You must also be extra careful about accessing
memory you intend to sync partially.
void
dma_cache_sync(struct device *dev, void *vaddr, size_t size,
enum dma_data_direction direction)
......
Documentation/DocBook/mtdnand.tmpl
浏览文件 @ 74511020
......@@ -488,7 +488,7 @@ static void board_select_chip (struct mtd_info *mtd, int chip)
The ECC bytes must be placed immidiately after the data
bytes in order to make the syndrome generator work. This
is contrary to the usual layout used by software ECC. The
seperation of data and out of band area is not longer
separation of data and out of band area is not longer
possible. The nand driver code handles this layout and
the remaining free bytes in the oob area are managed by
the autoplacement code. Provide a matching oob-layout
......@@ -560,7 +560,7 @@ static void board_select_chip (struct mtd_info *mtd, int chip)
bad blocks. They have factory marked good blocks. The marker pattern
is erased when the block is erased to be reused. So in case of
powerloss before writing the pattern back to the chip this block
would be lost and added to the bad blocks. Therefor we scan the
would be lost and added to the bad blocks. Therefore we scan the
chip(s) when we detect them the first time for good blocks and
store this information in a bad block table before erasing any
of the blocks.
......@@ -1094,7 +1094,7 @@ in this page</entry>
manufacturers specifications. This applies similar to the spare area.
</para>
<para>
Therefor NAND aware filesystems must either write in page size chunks
Therefore NAND aware filesystems must either write in page size chunks
or hold a writebuffer to collect smaller writes until they sum up to
pagesize. Available NAND aware filesystems: JFFS2, YAFFS.
</para>
......
Documentation/DocBook/v4l/common.xml
浏览文件 @ 74511020
......@@ -1170,7 +1170,7 @@ frames per second. If less than this number of frames is to be
captured or output, applications can request frame skipping or
duplicating on the driver side. This is especially useful when using
the &func-read; or &func-write;, which are not augmented by timestamps
or sequence counters, and to avoid unneccessary data copying.</para>
or sequence counters, and to avoid unnecessary data copying.</para>
<para>Finally these ioctls can be used to determine the number of
buffers used internally by a driver in read/write mode. For
......
Documentation/DocBook/v4l/vidioc-g-parm.xml
浏览文件 @ 74511020
......@@ -55,7 +55,7 @@ captured or output, applications can request frame skipping or
duplicating on the driver side. This is especially useful when using
the <function>read()</function> or <function>write()</function>, which
are not augmented by timestamps or sequence counters, and to avoid
unneccessary data copying.</para>
unnecessary data copying.</para>
<para>Further these ioctls can be used to determine the number of
buffers used internally by a driver in read/write mode. For
......
Documentation/IPMI.txt
浏览文件 @ 74511020
......@@ -365,6 +365,7 @@ You can change this at module load time (for a module) with:
regshifts=<shift1>,<shift2>,...
slave_addrs=<addr1>,<addr2>,...
force_kipmid=<enable1>,<enable2>,...
kipmid_max_busy_us=<ustime1>,<ustime2>,...
unload_when_empty=[0|1]
Each of these except si_trydefaults is a list, the first item for the
......@@ -433,6 +434,7 @@ kernel command line as:
ipmi_si.regshifts=<shift1>,<shift2>,...
ipmi_si.slave_addrs=<addr1>,<addr2>,...
ipmi_si.force_kipmid=<enable1>,<enable2>,...
ipmi_si.kipmid_max_busy_us=<ustime1>,<ustime2>,...
It works the same as the module parameters of the same names.
......@@ -450,6 +452,16 @@ force this thread on or off. If you force it off and don't have
interrupts, the driver will run VERY slowly. Don't blame me,
these interfaces suck.
Unfortunately, this thread can use a lot of CPU depending on the
interface's performance. This can waste a lot of CPU and cause
various issues with detecting idle CPU and using extra power. To
avoid this, the kipmid_max_busy_us sets the maximum amount of time, in
microseconds, that kipmid will spin before sleeping for a tick. This
value sets a balance between performance and CPU waste and needs to be
tuned to your needs. Maybe, someday, auto-tuning will be added, but
that's not a simple thing and even the auto-tuning would need to be
tuned to the user's desired performance.
The driver supports a hot add and remove of interfaces. This way,
interfaces can be added or removed after the kernel is up and running.
This is done using /sys/modules/ipmi_si/parameters/hotmod, which is a
......
Documentation/Makefile
浏览文件 @ 74511020
obj-m := DocBook/ accounting/ auxdisplay/ connector/ \
filesystems/configfs/ ia64/ networking/ \
pcmcia/ spi/ video4linux/ vm/ watchdog/src/
filesystems/ filesystems/configfs/ ia64/ laptops/ networking/ \
pcmcia/ spi/ timers/ video4linux/ vm/ watchdog/src/
Documentation/SubmitChecklist
浏览文件 @ 74511020
......@@ -9,10 +9,14 @@ Documentation/SubmittingPatches and elsewhere regarding submitting Linux
kernel patches.
1: Builds cleanly with applicable or modified CONFIG options =y, =m, and
1: If you use a facility then #include the file that defines/declares
that facility. Don't depend on other header files pulling in ones
that you use.
2: Builds cleanly with applicable or modified CONFIG options =y, =m, and
=n. No gcc warnings/errors, no linker warnings/errors.
2: Passes allnoconfig, allmodconfig
2b: Passes allnoconfig, allmodconfig
3: Builds on multiple CPU architectures by using local cross-compile tools
or some other build farm.
......
Documentation/arm/Samsung-S3C24XX/CPUfreq.txt
浏览文件 @ 74511020
......@@ -14,8 +14,8 @@ Introduction
how the clocks are arranged. The first implementation used as single
PLL to feed the ARM, memory and peripherals via a series of dividers
and muxes and this is the implementation that is documented here. A
newer version where there is a seperate PLL and clock divider for the
ARM core is available as a seperate driver.
newer version where there is a separate PLL and clock divider for the
ARM core is available as a separate driver.
Layout
......
Documentation/arm/Samsung/Overview.txt 0 → 100644
浏览文件 @ 74511020
Samsung ARM Linux Overview
==========================
Introduction
------------
The Samsung range of ARM SoCs spans many similar devices, from the initial
ARM9 through to the newest ARM cores. This document shows an overview of
the current kernel support, how to use it and where to find the code
that supports this.
The currently supported SoCs are:
- S3C24XX: See Documentation/arm/Samsung-S3C24XX/Overview.txt for full list
- S3C64XX: S3C6400 and S3C6410
- S5PC6440
S5PC100 and S5PC110 support is currently being merged
S3C24XX Systems
---------------
There is still documentation in Documnetation/arm/Samsung-S3C24XX/ which
deals with the architecture and drivers specific to these devices.
See Documentation/arm/Samsung-S3C24XX/Overview.txt for more information
on the implementation details and specific support.
Configuration
-------------
A number of configurations are supplied, as there is no current way of
unifying all the SoCs into one kernel.
s5p6440_defconfig - S5P6440 specific default configuration
s5pc100_defconfig - S5PC100 specific default configuration
Layout
------
The directory layout is currently being restructured, and consists of
several platform directories and then the machine specific directories
of the CPUs being built for.
plat-samsung provides the base for all the implementations, and is the
last in the line of include directories that are processed for the build
specific information. It contains the base clock, GPIO and device definitions
to get the system running.
plat-s3c is the s3c24xx/s3c64xx platform directory, although it is currently
involved in other builds this will be phased out once the relevant code is
moved elsewhere.
plat-s3c24xx is for s3c24xx specific builds, see the S3C24XX docs.
plat-s3c64xx is for the s3c64xx specific bits, see the S3C24XX docs.
plat-s5p is for s5p specific builds, more to be added.
[ to finish ]
Port Contributors
-----------------
Ben Dooks (BJD)
Vincent Sanders
Herbert Potzl
Arnaud Patard (RTP)
Roc Wu
Klaus Fetscher
Dimitry Andric
Shannon Holland
Guillaume Gourat (NexVision)
Christer Weinigel (wingel) (Acer N30)
Lucas Correia Villa Real (S3C2400 port)
Document Author
---------------
Copyright 2009-2010 Ben Dooks <ben-linux@fluff.org>
Documentation/arm/Samsung/clksrc-change-registers.awk 0 → 100755
浏览文件 @ 74511020
#!/usr/bin/awk -f
#
# Copyright 2010 Ben Dooks <ben-linux@fluff.org>
#
# Released under GPLv2
# example usage
# ./clksrc-change-registers.awk arch/arm/plat-s5pc1xx/include/plat/regs-clock.h < src > dst
function extract_value(s)
{
eqat = index(s, "=")
comat = index(s, ",")
return substr(s, eqat+2, (comat-eqat)-2)
}
function remove_brackets(b)
{
return substr(b, 2, length(b)-2)
}
function splitdefine(l, p)
{
r = split(l, tp)
p[0] = tp[2]
p[1] = remove_brackets(tp[3])
}
function find_length(f)
{
if (0)
printf "find_length " f "\n" > "/dev/stderr"
if (f ~ /0x1/)
return 1
else if (f ~ /0x3/)
return 2
else if (f ~ /0x7/)
return 3
else if (f ~ /0xf/)
return 4
printf "unknown legnth " f "\n" > "/dev/stderr"
exit
}
function find_shift(s)
{
id = index(s, "<")
if (id <= 0) {
printf "cannot find shift " s "\n" > "/dev/stderr"
exit
}
return substr(s, id+2)
}
BEGIN {
if (ARGC < 2) {
print "too few arguments" > "/dev/stderr"
exit
}
# read the header file and find the mask values that we will need
# to replace and create an associative array of values
while (getline line < ARGV[1] > 0) {
if (line ~ /\#define.*_MASK/ &&
!(line ~ /S5PC100_EPLL_MASK/) &&
!(line ~ /USB_SIG_MASK/)) {
splitdefine(line, fields)
name = fields[0]
if (0)
printf "MASK " line "\n" > "/dev/stderr"
dmask[name,0] = find_length(fields[1])
dmask[name,1] = find_shift(fields[1])
if (0)
printf "=> '" name "' LENGTH=" dmask[name,0] " SHIFT=" dmask[name,1] "\n" > "/dev/stderr"
} else {
}
}
delete ARGV[1]
}
/clksrc_clk.*=.*{/ {
shift=""
mask=""
divshift=""
reg_div=""
reg_src=""
indent=1
print $0
for(; indent >= 1;) {
if ((getline line) <= 0) {
printf "unexpected end of file" > "/dev/stderr"
exit 1;
}
if (line ~ /\.shift/) {
shift = extract_value(line)
} else if (line ~ /\.mask/) {
mask = extract_value(line)
} else if (line ~ /\.reg_divider/) {
reg_div = extract_value(line)
} else if (line ~ /\.reg_source/) {
reg_src = extract_value(line)
} else if (line ~ /\.divider_shift/) {
divshift = extract_value(line)
} else if (line ~ /{/) {
indent++
print line
} else if (line ~ /}/) {
indent--
if (indent == 0) {
if (0) {
printf "shift '" shift "' ='" dmask[shift,0] "'\n" > "/dev/stderr"
printf "mask '" mask "'\n" > "/dev/stderr"
printf "dshft '" divshift "'\n" > "/dev/stderr"
printf "rdiv '" reg_div "'\n" > "/dev/stderr"
printf "rsrc '" reg_src "'\n" > "/dev/stderr"
}
generated = mask
sub(reg_src, reg_div, generated)
if (0) {
printf "/* rsrc " reg_src " */\n"
printf "/* rdiv " reg_div " */\n"
printf "/* shift " shift " */\n"
printf "/* mask " mask " */\n"
printf "/* generated " generated " */\n"
}
if (reg_div != "") {
printf "\t.reg_div = { "
printf ".reg = " reg_div ", "
printf ".shift = " dmask[generated,1] ", "
printf ".size = " dmask[generated,0] ", "
printf "},\n"
}
printf "\t.reg_src = { "
printf ".reg = " reg_src ", "
printf ".shift = " dmask[mask,1] ", "
printf ".size = " dmask[mask,0] ", "
printf "},\n"
}
print line
} else {
print line
}
if (0)
printf indent ":" line "\n" > "/dev/stderr"
}
}
// && ! /clksrc_clk.*=.*{/ { print $0 }
Documentation/cgroups/cgroup_event_listener.c 0 → 100644
浏览文件 @ 74511020
/*
* cgroup_event_listener.c - Simple listener of cgroup events
*
* Copyright (C) Kirill A. Shutemov <kirill@shutemov.name>
*/
#include <assert.h>
#include <errno.h>
#include <fcntl.h>
#include <libgen.h>
#include <limits.h>
#include <stdio.h>
#include <string.h>
#include <unistd.h>
#include <sys/eventfd.h>
#define USAGE_STR "Usage: cgroup_event_listener <path-to-control-file> <args>\n"
int main(int argc, char **argv)
{
int efd = -1;
int cfd = -1;
int event_control = -1;
char event_control_path[PATH_MAX];
char line[LINE_MAX];
int ret;
if (argc != 3) {
fputs(USAGE_STR, stderr);
return 1;
}
cfd = open(argv[1], O_RDONLY);
if (cfd == -1) {
fprintf(stderr, "Cannot open %s: %s\n", argv[1],
strerror(errno));
goto out;
}
ret = snprintf(event_control_path, PATH_MAX, "%s/cgroup.event_control",
dirname(argv[1]));
if (ret >= PATH_MAX) {
fputs("Path to cgroup.event_control is too long\n", stderr);
goto out;
}
event_control = open(event_control_path, O_WRONLY);
if (event_control == -1) {
fprintf(stderr, "Cannot open %s: %s\n", event_control_path,
strerror(errno));
goto out;
}
efd = eventfd(0, 0);
if (efd == -1) {
perror("eventfd() failed");
goto out;
}
ret = snprintf(line, LINE_MAX, "%d %d %s", efd, cfd, argv[2]);
if (ret >= LINE_MAX) {
fputs("Arguments string is too long\n", stderr);
goto out;
}
ret = write(event_control, line, strlen(line) + 1);
if (ret == -1) {
perror("Cannot write to cgroup.event_control");
goto out;
}
while (1) {
uint64_t result;
ret = read(efd, &result, sizeof(result));
if (ret == -1) {
if (errno == EINTR)
continue;
perror("Cannot read from eventfd");
break;
}
assert(ret == sizeof(result));
ret = access(event_control_path, W_OK);
if ((ret == -1) && (errno == ENOENT)) {
puts("The cgroup seems to have removed.");
ret = 0;
break;
}
if (ret == -1) {
perror("cgroup.event_control "
"is not accessable any more");
break;
}
printf("%s %s: crossed\n", argv[1], argv[2]);
}
out:
if (efd >= 0)
close(efd);
if (event_control >= 0)
close(event_control);
if (cfd >= 0)
close(cfd);
return (ret != 0);
}
Documentation/cgroups/cgroups.txt
浏览文件 @ 74511020
......@@ -22,6 +22,8 @@ CONTENTS:
2. Usage Examples and Syntax
2.1 Basic Usage
2.2 Attaching processes
2.3 Mounting hierarchies by name
2.4 Notification API
3. Kernel API
3.1 Overview
3.2 Synchronization
......@@ -434,6 +436,25 @@ 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.
2.4 Notification API
--------------------
There is mechanism which allows to get notifications about changing
status of a cgroup.
To register new notification handler you need:
- create a file descriptor for event notification using eventfd(2);
- open a control file to be monitored (e.g. memory.usage_in_bytes);
- write "<event_fd> <control_fd> <args>" to cgroup.event_control.
Interpretation of args is defined by control file implementation;
eventfd will be woken up by control file implementation or when the
cgroup is removed.
To unregister notification handler just close eventfd.
NOTE: Support of notifications should be implemented for the control
file. See documentation for the subsystem.
3. Kernel API
=============
......@@ -488,6 +509,11 @@ Each subsystem should:
- add an entry in linux/cgroup_subsys.h
- define a cgroup_subsys object called <name>_subsys
If a subsystem can be compiled as a module, it should also have in its
module initcall a call to cgroup_load_subsys(), and in its exitcall a
call to cgroup_unload_subsys(). It should also set its_subsys.module =
THIS_MODULE in its .c file.
Each subsystem may export the following methods. The only mandatory
methods are create/destroy. Any others that are null are presumed to
be successful no-ops.
......@@ -536,10 +562,21 @@ 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. If threadgroup is
remain valid while the caller holds cgroup_mutex and it is ensured that either
attach() or cancel_attach() will be called in future. If threadgroup is
true, then a successful result indicates that all threads in the given
thread's threadgroup can be moved together.
void cancel_attach(struct cgroup_subsys *ss, struct cgroup *cgrp,
struct task_struct *task, bool threadgroup)
(cgroup_mutex held by caller)
Called when a task attach operation has failed after can_attach() has succeeded.
A subsystem whose can_attach() has some side-effects should provide this
function, so that the subsytem can implement a rollback. If not, not necessary.
This will be called only about subsystems whose can_attach() operation have
succeeded.
void attach(struct cgroup_subsys *ss, struct cgroup *cgrp,
struct cgroup *old_cgrp, struct task_struct *task,
bool threadgroup)
......
Documentation/cgroups/cpusets.txt
浏览文件 @ 74511020
......@@ -168,20 +168,20 @@ Each cpuset is represented by a directory in the cgroup file system
containing (on top of the standard cgroup files) the following
files describing that cpuset:
- cpus: list of CPUs in that cpuset
- mems: list of Memory Nodes in that cpuset
- memory_migrate flag: if set, move pages to cpusets nodes
- cpu_exclusive flag: is cpu placement exclusive?
- mem_exclusive flag: is memory placement exclusive?
- mem_hardwall flag: is memory allocation hardwalled
- memory_pressure: measure of how much paging pressure in cpuset
- memory_spread_page flag: if set, spread page cache evenly on allowed nodes
- memory_spread_slab flag: if set, spread slab cache evenly on allowed nodes
- sched_load_balance flag: if set, load balance within CPUs on that cpuset
- sched_relax_domain_level: the searching range when migrating tasks
- cpuset.cpus: list of CPUs in that cpuset
- cpuset.mems: list of Memory Nodes in that cpuset
- cpuset.memory_migrate flag: if set, move pages to cpusets nodes
- cpuset.cpu_exclusive flag: is cpu placement exclusive?
- cpuset.mem_exclusive flag: is memory placement exclusive?
- cpuset.mem_hardwall flag: is memory allocation hardwalled
- cpuset.memory_pressure: measure of how much paging pressure in cpuset
- cpuset.memory_spread_page flag: if set, spread page cache evenly on allowed nodes
- cpuset.memory_spread_slab flag: if set, spread slab cache evenly on allowed nodes
- cpuset.sched_load_balance flag: if set, load balance within CPUs on that cpuset
- cpuset.sched_relax_domain_level: the searching range when migrating tasks
In addition, the root cpuset only has the following file:
- memory_pressure_enabled flag: compute memory_pressure?
- cpuset.memory_pressure_enabled flag: compute memory_pressure?
New cpusets are created using the mkdir system call or shell
command. The properties of a cpuset, such as its flags, allowed
......@@ -229,7 +229,7 @@ If a cpuset is cpu or mem exclusive, no other cpuset, other than
a direct ancestor or descendant, may share any of the same CPUs or
Memory Nodes.
A cpuset that is mem_exclusive *or* mem_hardwall is "hardwalled",
A cpuset that is cpuset.mem_exclusive *or* cpuset.mem_hardwall is "hardwalled",
i.e. it restricts kernel allocations for page, buffer and other data
commonly shared by the kernel across multiple users. All cpusets,
whether hardwalled or not, restrict allocations of memory for user
......@@ -304,15 +304,15 @@ times 1000.
---------------------------
There are two boolean flag files per cpuset that control where the
kernel allocates pages for the file system buffers and related in
kernel data structures. They are called 'memory_spread_page' and
'memory_spread_slab'.
kernel data structures. They are called 'cpuset.memory_spread_page' and
'cpuset.memory_spread_slab'.
If the per-cpuset boolean flag file 'memory_spread_page' is set, then
If the per-cpuset boolean flag file 'cpuset.memory_spread_page' is set, then
the kernel will spread the file system buffers (page cache) evenly
over all the nodes that the faulting task is allowed to use, instead
of preferring to put those pages on the node where the task is running.
If the per-cpuset boolean flag file 'memory_spread_slab' is set,
If the per-cpuset boolean flag file 'cpuset.memory_spread_slab' is set,
then the kernel will spread some file system related slab caches,
such as for inodes and dentries evenly over all the nodes that the
faulting task is allowed to use, instead of preferring to put those
......@@ -337,21 +337,21 @@ their containing tasks memory spread settings. If memory spreading
is turned off, then the currently specified NUMA mempolicy once again
applies to memory page allocations.
Both 'memory_spread_page' and 'memory_spread_slab' are boolean flag
Both 'cpuset.memory_spread_page' and 'cpuset.memory_spread_slab' are boolean flag
files. By default they contain "0", meaning that the feature is off
for that cpuset. If a "1" is written to that file, then that turns
the named feature on.
The implementation is simple.
Setting the flag 'memory_spread_page' turns on a per-process flag
Setting the flag 'cpuset.memory_spread_page' turns on a per-process flag
PF_SPREAD_PAGE for each task that is in that cpuset or subsequently
joins that cpuset. The page allocation calls for the page cache
is modified to perform an inline check for this PF_SPREAD_PAGE task
flag, and if set, a call to a new routine cpuset_mem_spread_node()
returns the node to prefer for the allocation.
Similarly, setting 'memory_spread_slab' turns on the flag
Similarly, setting 'cpuset.memory_spread_slab' turns on the flag
PF_SPREAD_SLAB, and appropriately marked slab caches will allocate
pages from the node returned by cpuset_mem_spread_node().
......@@ -404,24 +404,24 @@ the following two situations:
system overhead on those CPUs, including avoiding task load
balancing if that is not needed.
When the per-cpuset flag "sched_load_balance" is enabled (the default
setting), it requests that all the CPUs in that cpusets allowed 'cpus'
When the per-cpuset flag "cpuset.sched_load_balance" is enabled (the default
setting), it requests that all the CPUs in that cpusets allowed 'cpuset.cpus'
be contained in a single sched domain, ensuring that load balancing
can move a task (not otherwised pinned, as by sched_setaffinity)
from any CPU in that cpuset to any other.
When the per-cpuset flag "sched_load_balance" is disabled, then the
When the per-cpuset flag "cpuset.sched_load_balance" is disabled, then the
scheduler will avoid load balancing across the CPUs in that cpuset,
--except-- in so far as is necessary because some overlapping cpuset
has "sched_load_balance" enabled.
So, for example, if the top cpuset has the flag "sched_load_balance"
So, for example, if the top cpuset has the flag "cpuset.sched_load_balance"
enabled, then the scheduler will have one sched domain covering all
CPUs, and the setting of the "sched_load_balance" flag in any other
CPUs, and the setting of the "cpuset.sched_load_balance" flag in any other
cpusets won't matter, as we're already fully load balancing.
Therefore in the above two situations, the top cpuset flag
"sched_load_balance" should be disabled, and only some of the smaller,
"cpuset.sched_load_balance" should be disabled, and only some of the smaller,
child cpusets have this flag enabled.
When doing this, you don't usually want to leave any unpinned tasks in
......@@ -433,7 +433,7 @@ scheduler might not consider the possibility of load balancing that
task to that underused CPU.
Of course, tasks pinned to a particular CPU can be left in a cpuset
that disables "sched_load_balance" as those tasks aren't going anywhere
that disables "cpuset.sched_load_balance" as those tasks aren't going anywhere
else anyway.
There is an impedance mismatch here, between cpusets and sched domains.
......@@ -443,19 +443,19 @@ overlap and each CPU is in at most one sched domain.
It is necessary for sched domains to be flat because load balancing
across partially overlapping sets of CPUs would risk unstable dynamics
that would be beyond our understanding. So if each of two partially
overlapping cpusets enables the flag 'sched_load_balance', then we
overlapping cpusets enables the flag 'cpuset.sched_load_balance', then we
form a single sched domain that is a superset of both. We won't move
a task to a CPU outside it cpuset, but the scheduler load balancing
code might waste some compute cycles considering that possibility.
This mismatch is why there is not a simple one-to-one relation
between which cpusets have the flag "sched_load_balance" enabled,
between which cpusets have the flag "cpuset.sched_load_balance" enabled,
and the sched domain configuration. If a cpuset enables the flag, it
will get balancing across all its CPUs, but if it disables the flag,
it will only be assured of no load balancing if no other overlapping
cpuset enables the flag.
If two cpusets have partially overlapping 'cpus' allowed, and only
If two cpusets have partially overlapping 'cpuset.cpus' allowed, and only
one of them has this flag enabled, then the other may find its
tasks only partially load balanced, just on the overlapping CPUs.
This is just the general case of the top_cpuset example given a few
......@@ -468,23 +468,23 @@ load balancing to the other CPUs.
1.7.1 sched_load_balance implementation details.
------------------------------------------------
The per-cpuset flag 'sched_load_balance' defaults to enabled (contrary
The per-cpuset flag 'cpuset.sched_load_balance' defaults to enabled (contrary
to most cpuset flags.) When enabled for a cpuset, the kernel will
ensure that it can load balance across all the CPUs in that cpuset
(makes sure that all the CPUs in the cpus_allowed of that cpuset are
in the same sched domain.)
If two overlapping cpusets both have 'sched_load_balance' enabled,
If two overlapping cpusets both have 'cpuset.sched_load_balance' enabled,
then they will be (must be) both in the same sched domain.
If, as is the default, the top cpuset has 'sched_load_balance' enabled,
If, as is the default, the top cpuset has 'cpuset.sched_load_balance' enabled,
then by the above that means there is a single sched domain covering
the whole system, regardless of any other cpuset settings.
The kernel commits to user space that it will avoid load balancing
where it can. It will pick as fine a granularity partition of sched
domains as it can while still providing load balancing for any set
of CPUs allowed to a cpuset having 'sched_load_balance' enabled.
of CPUs allowed to a cpuset having 'cpuset.sched_load_balance' enabled.
The internal kernel cpuset to scheduler interface passes from the
cpuset code to the scheduler code a partition of the load balanced
......@@ -495,9 +495,9 @@ all the CPUs that must be load balanced.
The cpuset code builds a new such partition and passes it to the
scheduler sched domain setup code, to have the sched domains rebuilt
as necessary, whenever:
- the 'sched_load_balance' flag of a cpuset with non-empty CPUs changes,
- the 'cpuset.sched_load_balance' flag of a cpuset with non-empty CPUs changes,
- or CPUs come or go from a cpuset with this flag enabled,
- or 'sched_relax_domain_level' value of a cpuset with non-empty CPUs
- or 'cpuset.sched_relax_domain_level' value of a cpuset with non-empty CPUs
and with this flag enabled changes,
- or a cpuset with non-empty CPUs and with this flag enabled is removed,
- or a cpu is offlined/onlined.
......@@ -542,7 +542,7 @@ As the result, task B on CPU X need to wait task A or wait load balance
on the next tick. For some applications in special situation, waiting
1 tick may be too long.
The 'sched_relax_domain_level' file allows you to request changing
The 'cpuset.sched_relax_domain_level' file allows you to request changing
this searching range as you like. This file takes int value which
indicates size of searching range in levels ideally as follows,
otherwise initial value -1 that indicates the cpuset has no request.
......@@ -559,8 +559,8 @@ The system default is architecture dependent. The system default
can be changed using the relax_domain_level= boot parameter.
This file is per-cpuset and affect the sched domain where the cpuset
belongs to. Therefore if the flag 'sched_load_balance' of a cpuset
is disabled, then 'sched_relax_domain_level' have no effect since
belongs to. Therefore if the flag 'cpuset.sched_load_balance' of a cpuset
is disabled, then 'cpuset.sched_relax_domain_level' have no effect since
there is no sched domain belonging the cpuset.
If multiple cpusets are overlapping and hence they form a single sched
......@@ -607,9 +607,9 @@ from one cpuset to another, then the kernel will adjust the tasks
memory placement, as above, the next time that the kernel attempts
to allocate a page of memory for that task.
If a cpuset has its 'cpus' modified, then each task in that cpuset
If a cpuset has its 'cpuset.cpus' modified, then each task in that cpuset
will have its allowed CPU placement changed immediately. Similarly,
if a tasks pid is written to another cpusets 'tasks' file, then its
if a tasks pid is written to another cpusets 'cpuset.tasks' file, then its
allowed CPU placement is changed immediately. If such a task had been
bound to some subset of its cpuset using the sched_setaffinity() call,
the task will be allowed to run on any CPU allowed in its new cpuset,
......@@ -622,8 +622,8 @@ and the processor placement is updated immediately.
Normally, once a page is allocated (given a physical page
of main memory) then that page stays on whatever node it
was allocated, so long as it remains allocated, even if the
cpusets memory placement policy 'mems' subsequently changes.
If the cpuset flag file 'memory_migrate' is set true, then when
cpusets memory placement policy 'cpuset.mems' subsequently changes.
If the cpuset flag file 'cpuset.memory_migrate' is set true, then when
tasks are attached to that cpuset, any pages that task had
allocated to it on nodes in its previous cpuset are migrated
to the tasks new cpuset. The relative placement of the page within
......@@ -631,12 +631,12 @@ the cpuset is preserved during these migration operations if possible.
For example if the page was on the second valid node of the prior cpuset
then the page will be placed on the second valid node of the new cpuset.
Also if 'memory_migrate' is set true, then if that cpusets
'mems' file is modified, pages allocated to tasks in that
cpuset, that were on nodes in the previous setting of 'mems',
Also if 'cpuset.memory_migrate' is set true, then if that cpusets
'cpuset.mems' file is modified, pages allocated to tasks in that
cpuset, that were on nodes in the previous setting of 'cpuset.mems',
will be moved to nodes in the new setting of 'mems.'
Pages that were not in the tasks prior cpuset, or in the cpusets
prior 'mems' setting, will not be moved.
prior 'cpuset.mems' setting, will not be moved.
There is an exception to the above. If hotplug functionality is used
to remove all the CPUs that are currently assigned to a cpuset,
......@@ -678,8 +678,8 @@ and then start a subshell 'sh' in that cpuset:
cd /dev/cpuset
mkdir Charlie
cd Charlie
/bin/echo 2-3 > cpus
/bin/echo 1 > mems
/bin/echo 2-3 > cpuset.cpus
/bin/echo 1 > cpuset.mems
/bin/echo $$ > tasks
sh
# The subshell 'sh' is now running in cpuset Charlie
......@@ -725,10 +725,13 @@ Now you want to do something with this cpuset.
In this directory you can find several files:
# ls
cpu_exclusive memory_migrate mems tasks
cpus memory_pressure notify_on_release
mem_exclusive memory_spread_page sched_load_balance
mem_hardwall memory_spread_slab sched_relax_domain_level
cpuset.cpu_exclusive cpuset.memory_spread_slab
cpuset.cpus cpuset.mems
cpuset.mem_exclusive cpuset.sched_load_balance
cpuset.mem_hardwall cpuset.sched_relax_domain_level
cpuset.memory_migrate notify_on_release
cpuset.memory_pressure tasks
cpuset.memory_spread_page
Reading them will give you information about the state of this cpuset:
the CPUs and Memory Nodes it can use, the processes that are using
......@@ -736,13 +739,13 @@ it, its properties. By writing to these files you can manipulate
the cpuset.
Set some flags:
# /bin/echo 1 > cpu_exclusive
# /bin/echo 1 > cpuset.cpu_exclusive
Add some cpus:
# /bin/echo 0-7 > cpus
# /bin/echo 0-7 > cpuset.cpus
Add some mems:
# /bin/echo 0-7 > mems
# /bin/echo 0-7 > cpuset.mems
Now attach your shell to this cpuset:
# /bin/echo $$ > tasks
......@@ -774,28 +777,28 @@ echo "/sbin/cpuset_release_agent" > /dev/cpuset/release_agent
This is the syntax to use when writing in the cpus or mems files
in cpuset directories:
# /bin/echo 1-4 > cpus -> set cpus list to cpus 1,2,3,4
# /bin/echo 1,2,3,4 > cpus -> set cpus list to cpus 1,2,3,4
# /bin/echo 1-4 > cpuset.cpus -> set cpus list to cpus 1,2,3,4
# /bin/echo 1,2,3,4 > cpuset.cpus -> set cpus list to cpus 1,2,3,4
To add a CPU to a cpuset, write the new list of CPUs including the
CPU to be added. To add 6 to the above cpuset:
# /bin/echo 1-4,6 > cpus -> set cpus list to cpus 1,2,3,4,6
# /bin/echo 1-4,6 > cpuset.cpus -> set cpus list to cpus 1,2,3,4,6
Similarly to remove a CPU from a cpuset, write the new list of CPUs
without the CPU to be removed.
To remove all the CPUs:
# /bin/echo "" > cpus -> clear cpus list
# /bin/echo "" > cpuset.cpus -> clear cpus list
2.3 Setting flags
-----------------
The syntax is very simple:
# /bin/echo 1 > cpu_exclusive -> set flag 'cpu_exclusive'
# /bin/echo 0 > cpu_exclusive -> unset flag 'cpu_exclusive'
# /bin/echo 1 > cpuset.cpu_exclusive -> set flag 'cpuset.cpu_exclusive'
# /bin/echo 0 > cpuset.cpu_exclusive -> unset flag 'cpuset.cpu_exclusive'
2.4 Attaching processes
-----------------------
......
Documentation/cgroups/memcg_test.txt
浏览文件 @ 74511020
Memory Resource Controller(Memcg) Implementation Memo.
Last Updated: 2009/1/20
Base Kernel Version: based on 2.6.29-rc2.
Last Updated: 2010/2
Base Kernel Version: based on 2.6.33-rc7-mm(candidate for 34).
Because VM is getting complex (one of reasons is memcg...), memcg's behavior
is complex. This is a document for memcg's internal behavior.
......@@ -337,7 +337,7 @@ Under below explanation, we assume CONFIG_MEM_RES_CTRL_SWAP=y.
race and lock dependency with other cgroup subsystems.
example)
# mount -t cgroup none /cgroup -t cpuset,memory,cpu,devices
# mount -t cgroup none /cgroup -o cpuset,memory,cpu,devices
and do task move, mkdir, rmdir etc...under this.
......@@ -348,7 +348,7 @@ Under below explanation, we assume CONFIG_MEM_RES_CTRL_SWAP=y.
For example, test like following is good.
(Shell-A)
# mount -t cgroup none /cgroup -t memory
# mount -t cgroup none /cgroup -o memory
# mkdir /cgroup/test
# echo 40M > /cgroup/test/memory.limit_in_bytes
# echo 0 > /cgroup/test/tasks
......@@ -378,3 +378,42 @@ Under below explanation, we assume CONFIG_MEM_RES_CTRL_SWAP=y.
#echo 50M > memory.limit_in_bytes
#echo 50M > memory.memsw.limit_in_bytes
run 51M of malloc
9.9 Move charges at task migration
Charges associated with a task can be moved along with task migration.
(Shell-A)
#mkdir /cgroup/A
#echo $$ >/cgroup/A/tasks
run some programs which uses some amount of memory in /cgroup/A.
(Shell-B)
#mkdir /cgroup/B
#echo 1 >/cgroup/B/memory.move_charge_at_immigrate
#echo "pid of the program running in group A" >/cgroup/B/tasks
You can see charges have been moved by reading *.usage_in_bytes or
memory.stat of both A and B.
See 8.2 of Documentation/cgroups/memory.txt to see what value should be
written to move_charge_at_immigrate.
9.10 Memory thresholds
Memory controler implements memory thresholds using cgroups notification
API. You can use Documentation/cgroups/cgroup_event_listener.c to test
it.
(Shell-A) Create cgroup and run event listener
# mkdir /cgroup/A
# ./cgroup_event_listener /cgroup/A/memory.usage_in_bytes 5M
(Shell-B) Add task to cgroup and try to allocate and free memory
# echo $$ >/cgroup/A/tasks
# a="$(dd if=/dev/zero bs=1M count=10)"
# a=
You will see message from cgroup_event_listener every time you cross
the thresholds.
Use /cgroup/A/memory.memsw.usage_in_bytes to test memsw thresholds.
It's good idea to test root cgroup as well.
Documentation/cgroups/memory.txt
浏览文件 @ 74511020
......@@ -182,6 +182,8 @@ list.
NOTE: Reclaim does not work for the root cgroup, since we cannot set any
limits on the root cgroup.
Note2: When panic_on_oom is set to "2", the whole system will panic.
2. Locking
The memory controller uses the following hierarchy
......@@ -262,10 +264,12 @@ some of the pages cached in the cgroup (page cache pages).
4.2 Task migration
When a task migrates from one cgroup to another, it's charge is not
carried forward. The pages allocated from the original cgroup still
carried forward by default. The pages allocated from the original cgroup still
remain charged to it, the charge is dropped when the page is freed or
reclaimed.
Note: You can move charges of a task along with task migration. See 8.
4.3 Removing a cgroup
A cgroup can be removed by rmdir, but as discussed in sections 4.1 and 4.2, a
......@@ -377,7 +381,8 @@ The feature can be disabled by
NOTE1: Enabling/disabling will fail if the cgroup already has other
cgroups created below it.
NOTE2: This feature can be enabled/disabled per subtree.
NOTE2: When panic_on_oom is set to "2", the whole system will panic in
case of an oom event in any cgroup.
7. Soft limits
......@@ -414,7 +419,76 @@ NOTE1: Soft limits take effect over a long period of time, since they involve
NOTE2: It is recommended to set the soft limit always below the hard limit,
otherwise the hard limit will take precedence.
8. TODO
8. Move charges at task migration
Users can move charges associated with a task along with task migration, that
is, uncharge task's pages from the old cgroup and charge them to the new cgroup.
This feature is not supported in !CONFIG_MMU environments because of lack of
page tables.
8.1 Interface
This feature is disabled by default. It can be enabled(and disabled again) by
writing to memory.move_charge_at_immigrate of the destination cgroup.
If you want to enable it:
# echo (some positive value) > memory.move_charge_at_immigrate
Note: Each bits of move_charge_at_immigrate has its own meaning about what type
of charges should be moved. See 8.2 for details.
Note: Charges are moved only when you move mm->owner, IOW, a leader of a thread
group.
Note: If we cannot find enough space for the task in the destination cgroup, we
try to make space by reclaiming memory. Task migration may fail if we
cannot make enough space.
Note: It can take several seconds if you move charges in giga bytes order.
And if you want disable it again:
# echo 0 > memory.move_charge_at_immigrate
8.2 Type of charges which can be move
Each bits of move_charge_at_immigrate has its own meaning about what type of
charges should be moved.
bit | what type of charges would be moved ?
-----+------------------------------------------------------------------------
0 | A charge of an anonymous page(or swap of it) used by the target task.
| Those pages and swaps must be used only by the target task. You must
| enable Swap Extension(see 2.4) to enable move of swap charges.
Note: Those pages and swaps must be charged to the old cgroup.
Note: More type of pages(e.g. file cache, shmem,) will be supported by other
bits in future.
8.3 TODO
- Add support for other types of pages(e.g. file cache, shmem, etc.).
- Implement madvise(2) to let users decide the vma to be moved or not to be
moved.
- All of moving charge operations are done under cgroup_mutex. It's not good
behavior to hold the mutex too long, so we may need some trick.
9. Memory thresholds
Memory controler implements memory thresholds using cgroups notification
API (see cgroups.txt). It allows to register multiple memory and memsw
thresholds and gets notifications when it crosses.
To register a threshold application need:
- create an eventfd using eventfd(2);
- open memory.usage_in_bytes or memory.memsw.usage_in_bytes;
- write string like "<event_fd> <memory.usage_in_bytes> <threshold>" to
cgroup.event_control.
Application will be notified through eventfd when memory usage crosses
threshold in any direction.
It's applicable for root and non-root cgroup.
10. TODO
1. Add support for accounting huge pages (as a separate controller)
2. Make per-cgroup scanner reclaim not-shared pages first
......
Documentation/console/console.txt
浏览文件 @ 74511020
......@@ -74,7 +74,7 @@ driver takes over the consoles vacated by the driver. Binding, on the other
hand, will bind the driver to the consoles that are currently occupied by a
system driver.
NOTE1: Binding and binding must be selected in Kconfig. It's under:
NOTE1: Binding and unbinding must be selected in Kconfig. It's under:
Device Drivers -> Character devices -> Support for binding and unbinding
console drivers
......
Documentation/driver-model/platform.txt
浏览文件 @ 74511020
......@@ -192,7 +192,7 @@ command line. This will execute all matching early_param() callbacks.
User specified early platform devices will be registered at this point.
For the early serial console case the user can specify port on the
kernel command line as "earlyprintk=serial.0" where "earlyprintk" is
the class string, "serial" is the name of the platfrom driver and
the class string, "serial" is the name of the platform driver and
0 is the platform device id. If the id is -1 then the dot and the
id can be omitted.
......
Documentation/eisa.txt
浏览文件 @ 74511020
......@@ -171,7 +171,7 @@ device.
virtual_root.force_probe :
Force the probing code to probe EISA slots even when it cannot find an
EISA compliant mainboard (nothing appears on slot 0). Defaultd to 0
EISA compliant mainboard (nothing appears on slot 0). Defaults to 0
(don't force), and set to 1 (force probing) when either
CONFIG_ALPHA_JENSEN or CONFIG_EISA_VLB_PRIMING are set.
......
Documentation/email-clients.txt
浏览文件 @ 74511020
......@@ -216,26 +216,14 @@ Works. Use "Insert file..." or external editor.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Gmail (Web GUI)
If you just have to use Gmail to send patches, it CAN be made to work. It
requires a bit of external help, though.
The first problem is that Gmail converts tabs to spaces. This will
totally break your patches. To prevent this, you have to use a different
editor. There is a firefox extension called "ViewSourceWith"
(https://addons.mozilla.org/en-US/firefox/addon/394) which allows you to
edit any text box in the editor of your choice. Configure it to launch
your favorite editor. When you want to send a patch, use this technique.
Once you have crafted your messsage + patch, save and exit the editor,
which should reload the Gmail edit box. GMAIL WILL PRESERVE THE TABS.
Hoorah. Apparently you can cut-n-paste literal tabs, but Gmail will
convert those to spaces upon sending!
The second problem is that Gmail converts tabs to spaces on replies. If
you reply to a patch, don't expect to be able to apply it as a patch.
The last problem is that Gmail will base64-encode any message that has a
non-ASCII character. That includes things like European names. Be aware.
Gmail is not convenient for lkml patches, but CAN be made to work.
Does not work for sending patches.
Gmail web client converts tabs to spaces automatically.
At the same time it wraps lines every 78 chars with CRLF style line breaks
although tab2space problem can be solved with external editor.
Another problem is that Gmail will base64-encode any message that has a
non-ASCII character. That includes things like European names.
###
Documentation/feature-removal-schedule.txt
浏览文件 @ 74511020
......@@ -582,3 +582,10 @@ Why: The paravirt mmu host support is slower than non-paravirt mmu, both
Who: Avi Kivity <avi@redhat.com>
----------------------------
What: "acpi=ht" boot option
When: 2.6.35
Why: Useful in 2003, implementation is a hack.
Generally invoked by accident today.
Seen as doing more harm than good.
Who: Len Brown <len.brown@intel.com>
Documentation/filesystems/00-INDEX
浏览文件 @ 74511020
......@@ -32,6 +32,8 @@ dlmfs.txt
- info on the userspace interface to the OCFS2 DLM.
dnotify.txt
- info about directory notification in Linux.
dnotify_test.c
- example program for dnotify
ecryptfs.txt
- docs on eCryptfs: stacked cryptographic filesystem for Linux.
exofs.txt
......
Documentation/filesystems/Makefile 0 → 100644
浏览文件 @ 74511020
# kbuild trick to avoid linker error. Can be omitted if a module is built.
obj- := dummy.o
# List of programs to build
hostprogs-y := dnotify_test
# Tell kbuild to always build the programs
always := $(hostprogs-y)
Documentation/filesystems/ceph.txt 0 → 100644
浏览文件 @ 74511020
Ceph Distributed File System
============================
Ceph is a distributed network file system designed to provide good
performance, reliability, and scalability.
Basic features include:
* POSIX semantics
* Seamless scaling from 1 to many thousands of nodes
* High availability and reliability. No single points of failure.
* N-way replication of data across storage nodes
* Fast recovery from node failures
* Automatic rebalancing of data on node addition/removal
* Easy deployment: most FS components are userspace daemons
Also,
* Flexible snapshots (on any directory)
* Recursive accounting (nested files, directories, bytes)
In contrast to cluster filesystems like GFS, OCFS2, and GPFS that rely
on symmetric access by all clients to shared block devices, Ceph
separates data and metadata management into independent server
clusters, similar to Lustre. Unlike Lustre, however, metadata and
storage nodes run entirely as user space daemons. Storage nodes
utilize btrfs to store data objects, leveraging its advanced features
(checksumming, metadata replication, etc.). File data is striped
across storage nodes in large chunks to distribute workload and
facilitate high throughputs. When storage nodes fail, data is
re-replicated in a distributed fashion by the storage nodes themselves
(with some minimal coordination from a cluster monitor), making the
system extremely efficient and scalable.
Metadata servers effectively form a large, consistent, distributed
in-memory cache above the file namespace that is extremely scalable,
dynamically redistributes metadata in response to workload changes,
and can tolerate arbitrary (well, non-Byzantine) node failures. The
metadata server takes a somewhat unconventional approach to metadata
storage to significantly improve performance for common workloads. In
particular, inodes with only a single link are embedded in
directories, allowing entire directories of dentries and inodes to be
loaded into its cache with a single I/O operation. The contents of
extremely large directories can be fragmented and managed by
independent metadata servers, allowing scalable concurrent access.
The system offers automatic data rebalancing/migration when scaling
from a small cluster of just a few nodes to many hundreds, without
requiring an administrator carve the data set into static volumes or
go through the tedious process of migrating data between servers.
When the file system approaches full, new nodes can be easily added
and things will "just work."
Ceph includes flexible snapshot mechanism that allows a user to create
a snapshot on any subdirectory (and its nested contents) in the
system. Snapshot creation and deletion are as simple as 'mkdir
.snap/foo' and 'rmdir .snap/foo'.
Ceph also provides some recursive accounting on directories for nested
files and bytes. That is, a 'getfattr -d foo' on any directory in the
system will reveal the total number of nested regular files and
subdirectories, and a summation of all nested file sizes. This makes
the identification of large disk space consumers relatively quick, as
no 'du' or similar recursive scan of the file system is required.
Mount Syntax
============
The basic mount syntax is:
# mount -t ceph monip[:port][,monip2[:port]...]:/[subdir] mnt
You only need to specify a single monitor, as the client will get the
full list when it connects. (However, if the monitor you specify
happens to be down, the mount won't succeed.) The port can be left
off if the monitor is using the default. So if the monitor is at
1.2.3.4,
# mount -t ceph 1.2.3.4:/ /mnt/ceph
is sufficient. If /sbin/mount.ceph is installed, a hostname can be
used instead of an IP address.
Mount Options
=============
ip=A.B.C.D[:N]
Specify the IP and/or port the client should bind to locally.
There is normally not much reason to do this. If the IP is not
specified, the client's IP address is determined by looking at the
address it's connection to the monitor originates from.
wsize=X
Specify the maximum write size in bytes. By default there is no
maximu. Ceph will normally size writes based on the file stripe
size.
rsize=X
Specify the maximum readahead.
mount_timeout=X
Specify the timeout value for mount (in seconds), in the case
of a non-responsive Ceph file system. The default is 30
seconds.
rbytes
When stat() is called on a directory, set st_size to 'rbytes',
the summation of file sizes over all files nested beneath that
directory. This is the default.
norbytes
When stat() is called on a directory, set st_size to the
number of entries in that directory.
nocrc
Disable CRC32C calculation for data writes. If set, the OSD
must rely on TCP's error correction to detect data corruption
in the data payload.
noasyncreaddir
Disable client's use its local cache to satisfy readdir
requests. (This does not change correctness; the client uses
cached metadata only when a lease or capability ensures it is
valid.)
More Information
================
For more information on Ceph, see the home page at
http://ceph.newdream.net/
The Linux kernel client source tree is available at
git://ceph.newdream.net/linux-ceph-client.git
and the source for the full system is at
git://ceph.newdream.net/ceph.git
Documentation/filesystems/dnotify.txt
浏览文件 @ 74511020
......@@ -62,38 +62,9 @@ disabled, fcntl(fd, F_NOTIFY, ...) will return -EINVAL.
Example
-------
See Documentation/filesystems/dnotify_test.c for an example.
#define _GNU_SOURCE /* needed to get the defines */
#include <fcntl.h> /* in glibc 2.2 this has the needed
values defined */
#include <signal.h>
#include <stdio.h>
#include <unistd.h>
static volatile int event_fd;
static void handler(int sig, siginfo_t *si, void *data)
{
event_fd = si->si_fd;
}
int main(void)
{
struct sigaction act;
int fd;
act.sa_sigaction = handler;
sigemptyset(&act.sa_mask);
act.sa_flags = SA_SIGINFO;
sigaction(SIGRTMIN + 1, &act, NULL);
fd = open(".", O_RDONLY);
fcntl(fd, F_SETSIG, SIGRTMIN + 1);
fcntl(fd, F_NOTIFY, DN_MODIFY|DN_CREATE|DN_MULTISHOT);
/* we will now be notified if any of the files
in "." is modified or new files are created */
while (1) {
pause();
printf("Got event on fd=%d\n", event_fd);
}
}
NOTE
----
Beginning with Linux 2.6.13, dnotify has been replaced by inotify.
See Documentation/filesystems/inotify.txt for more information on it.
Documentation/filesystems/dnotify_test.c 0 → 100644
浏览文件 @ 74511020
#define _GNU_SOURCE /* needed to get the defines */
#include <fcntl.h> /* in glibc 2.2 this has the needed
values defined */
#include <signal.h>
#include <stdio.h>
#include <unistd.h>
static volatile int event_fd;
static void handler(int sig, siginfo_t *si, void *data)
{
event_fd = si->si_fd;
}
int main(void)
{
struct sigaction act;
int fd;
act.sa_sigaction = handler;
sigemptyset(&act.sa_mask);
act.sa_flags = SA_SIGINFO;
sigaction(SIGRTMIN + 1, &act, NULL);
fd = open(".", O_RDONLY);
fcntl(fd, F_SETSIG, SIGRTMIN + 1);
fcntl(fd, F_NOTIFY, DN_MODIFY|DN_CREATE|DN_MULTISHOT);
/* we will now be notified if any of the files
in "." is modified or new files are created */
while (1) {
pause();
printf("Got event on fd=%d\n", event_fd);
}
}
Documentation/filesystems/proc.txt
浏览文件 @ 74511020
......@@ -195,7 +195,7 @@ asynchronous manner and the vaule may not be very precise. To see a precise
snapshot of a moment, you can see /proc/<pid>/smaps file and scan page table.
It's slow but very precise.
Table 1-2: Contents of the statm files (as of 2.6.30-rc7)
Table 1-2: Contents of the status files (as of 2.6.30-rc7)
..............................................................................
Field Content
Name filename of the executable
......
Documentation/hwmon/abituguru
浏览文件 @ 74511020
......@@ -30,7 +30,7 @@ Supported chips:
bank1_types=1,1,0,0,0,0,0,2,0,0,0,0,2,0,0,1
You may also need to specify the fan_sensors option for these boards
fan_sensors=5
2) There is a seperate abituguru3 driver for these motherboards,
2) There is a separate abituguru3 driver for these motherboards,
the abituguru (without the 3 !) driver will not work on these
motherboards (and visa versa)!
......
Documentation/input/rotary-encoder.txt
浏览文件 @ 74511020
......@@ -75,7 +75,7 @@ and the number of steps or will clamp at the maximum and zero depending on
the configuration.
Because GPIO to IRQ mapping is platform specific, this information must
be given in seperately to the driver. See the example below.
be given in separately to the driver. See the example below.
---------<snip>---------
......
Documentation/ioctl/ioctl-number.txt
浏览文件 @ 74511020
......@@ -291,6 +291,7 @@ Code Seq#(hex) Include File Comments
0x92 00-0F drivers/usb/mon/mon_bin.c
0x93 60-7F linux/auto_fs.h
0x94 all fs/btrfs/ioctl.h
0x97 00-7F fs/ceph/ioctl.h Ceph file system
0x99 00-0F 537-Addinboard driver
<mailto:buk@buks.ipn.de>
0xA0 all linux/sdp/sdp.h Industrial Device Project
......
Documentation/kernel-parameters.txt
浏览文件 @ 74511020
......@@ -200,10 +200,6 @@ and is between 256 and 4096 characters. It is defined in the file
acpi_display_output=video
See above.
acpi_early_pdc_eval [HW,ACPI] Evaluate processor _PDC methods
early. Needed on some platforms to properly
initialize the EC.
acpi_irq_balance [HW,ACPI]
ACPI will balance active IRQs
default in APIC mode
......
Documentation/kobject.txt
浏览文件 @ 74511020
......@@ -59,37 +59,56 @@ nice to have in other objects. The C language does not allow for the
direct expression of inheritance, so other techniques - such as structure
embedding - must be used.
So, for example, the UIO code has a structure that defines the memory
region associated with a uio device:
(As an aside, for those familiar with the kernel linked list implementation,
this is analogous as to how "list_head" structs are rarely useful on
their own, but are invariably found embedded in the larger objects of
interest.)
struct uio_mem {
So, for example, the UIO code in drivers/uio/uio.c has a structure that
defines the memory region associated with a uio device:
struct uio_map {
struct kobject kobj;
unsigned long addr;
unsigned long size;
int memtype;
void __iomem *internal_addr;
};
struct uio_mem *mem;
};
If you have a struct uio_mem structure, finding its embedded kobject is
If you have a struct uio_map structure, finding its embedded kobject is
just a matter of using the kobj member. Code that works with kobjects will
often have the opposite problem, however: given a struct kobject pointer,
what is the pointer to the containing structure? You must avoid tricks
(such as assuming that the kobject is at the beginning of the structure)
and, instead, use the container_of() macro, found in <linux/kernel.h>:
container_of(pointer, type, member)
container_of(pointer, type, member)
where:
* "pointer" is the pointer to the embedded kobject,
* "type" is the type of the containing structure, and
* "member" is the name of the structure field to which "pointer" points.
The return value from container_of() is a pointer to the corresponding
container type. So, for example, a pointer "kp" to a struct kobject
embedded *within* a struct uio_map could be converted to a pointer to the
*containing* uio_map structure with:
struct uio_map *u_map = container_of(kp, struct uio_map, kobj);
For convenience, programmers often define a simple macro for "back-casting"
kobject pointers to the containing type. Exactly this happens in the
earlier drivers/uio/uio.c, as you can see here:
struct uio_map {
struct kobject kobj;
struct uio_mem *mem;
};
where pointer is the pointer to the embedded kobject, type is the type of
the containing structure, and member is the name of the structure field to
which pointer points. The return value from container_of() is a pointer to
the given type. So, for example, a pointer "kp" to a struct kobject
embedded within a struct uio_mem could be converted to a pointer to the
containing uio_mem structure with:
#define to_map(map) container_of(map, struct uio_map, kobj)
struct uio_mem *u_mem = container_of(kp, struct uio_mem, kobj);
where the macro argument "map" is a pointer to the struct kobject in
question. That macro is subsequently invoked with:
Programmers often define a simple macro for "back-casting" kobject pointers
to the containing type.
struct uio_map *map = to_map(kobj);
Initialization of kobjects
......@@ -387,4 +406,5 @@ called, and the objects in the former circle release each other.
Example code to copy from
For a more complete example of using ksets and kobjects properly, see the
sample/kobject/kset-example.c code.
example programs samples/kobject/{kobject-example.c,kset-example.c},
which will be built as loadable modules if you select CONFIG_SAMPLE_KOBJECT.
Documentation/laptops/00-INDEX
浏览文件 @ 74511020
......@@ -2,6 +2,12 @@
- This file
acer-wmi.txt
- information on the Acer Laptop WMI Extras driver.
asus-laptop.txt
- information on the Asus Laptop Extras driver.
disk-shock-protection.txt
- information on hard disk shock protection.
dslm.c
- Simple Disk Sleep Monitor program
laptop-mode.txt
- how to conserve battery power using laptop-mode.
sony-laptop.txt
......
Documentation/laptops/Makefile 0 → 100644
浏览文件 @ 74511020
# kbuild trick to avoid linker error. Can be omitted if a module is built.
obj- := dummy.o
# List of programs to build
hostprogs-y := dslm
# Tell kbuild to always build the programs
always := $(hostprogs-y)
Documentation/laptops/dslm.c 0 → 100644
浏览文件 @ 74511020
/*
* dslm.c
* Simple Disk Sleep Monitor
* by Bartek Kania
* Licenced under the GPL
*/
#include <unistd.h>
#include <stdlib.h>
#include <stdio.h>
#include <fcntl.h>
#include <errno.h>
#include <time.h>
#include <string.h>
#include <signal.h>
#include <sys/ioctl.h>
#include <linux/hdreg.h>
#ifdef DEBUG
#define D(x) x
#else
#define D(x)
#endif
int endit = 0;
/* Check if the disk is in powersave-mode
* Most of the code is stolen from hdparm.
* 1 = active, 0 = standby/sleep, -1 = unknown */
static int check_powermode(int fd)
{
unsigned char args[4] = {WIN_CHECKPOWERMODE1,0,0,0};
int state;
if (ioctl(fd, HDIO_DRIVE_CMD, &args)
&& (args[0] = WIN_CHECKPOWERMODE2) /* try again with 0x98 */
&& ioctl(fd, HDIO_DRIVE_CMD, &args)) {
if (errno != EIO || args[0] != 0 || args[1] != 0) {
state = -1; /* "unknown"; */
} else
state = 0; /* "sleeping"; */
} else {
state = (args[2] == 255) ? 1 : 0;
}
D(printf(" drive state is: %d\n", state));
return state;
}
static char *state_name(int i)
{
if (i == -1) return "unknown";
if (i == 0) return "sleeping";
if (i == 1) return "active";
return "internal error";
}
static char *myctime(time_t time)
{
char *ts = ctime(&time);
ts[strlen(ts) - 1] = 0;
return ts;
}
static void measure(int fd)
{
time_t start_time;
int last_state;
time_t last_time;
int curr_state;
time_t curr_time = 0;
time_t time_diff;
time_t active_time = 0;
time_t sleep_time = 0;
time_t unknown_time = 0;
time_t total_time = 0;
int changes = 0;
float tmp;
printf("Starting measurements\n");
last_state = check_powermode(fd);
start_time = last_time = time(0);
printf(" System is in state %s\n\n", state_name(last_state));
while(!endit) {
sleep(1);
curr_state = check_powermode(fd);
if (curr_state != last_state || endit) {
changes++;
curr_time = time(0);
time_diff = curr_time - last_time;
if (last_state == 1) active_time += time_diff;
else if (last_state == 0) sleep_time += time_diff;
else unknown_time += time_diff;
last_state = curr_state;
last_time = curr_time;
printf("%s: State-change to %s\n", myctime(curr_time),
state_name(curr_state));
}
}
changes--; /* Compensate for SIGINT */
total_time = time(0) - start_time;
printf("\nTotal running time: %lus\n", curr_time - start_time);
printf(" State changed %d times\n", changes);
tmp = (float)sleep_time / (float)total_time * 100;
printf(" Time in sleep state: %lus (%.2f%%)\n", sleep_time, tmp);
tmp = (float)active_time / (float)total_time * 100;
printf(" Time in active state: %lus (%.2f%%)\n", active_time, tmp);
tmp = (float)unknown_time / (float)total_time * 100;
printf(" Time in unknown state: %lus (%.2f%%)\n", unknown_time, tmp);
}
static void ender(int s)
{
endit = 1;
}
static void usage(void)
{
puts("usage: dslm [-w <time>] <disk>");
exit(0);
}
int main(int argc, char **argv)
{
int fd;
char *disk = 0;
int settle_time = 60;
/* Parse the simple command-line */
if (argc == 2)
disk = argv[1];
else if (argc == 4) {
settle_time = atoi(argv[2]);
disk = argv[3];
} else
usage();
if (!(fd = open(disk, O_RDONLY|O_NONBLOCK))) {
printf("Can't open %s, because: %s\n", disk, strerror(errno));
exit(-1);
}
if (settle_time) {
printf("Waiting %d seconds for the system to settle down to "
"'normal'\n", settle_time);
sleep(settle_time);
} else
puts("Not waiting for system to settle down");
signal(SIGINT, ender);
measure(fd);
close(fd);
return 0;
}
Documentation/laptops/laptop-mode.txt
浏览文件 @ 74511020
......@@ -779,172 +779,4 @@ Monitoring tool
---------------
Bartek Kania submitted this, it can be used to measure how much time your disk
spends spun up/down.
---------------------------dslm.c BEGIN-----------------------------------------
/*
* Simple Disk Sleep Monitor
* by Bartek Kania
* Licenced under the GPL
*/
#include <unistd.h>
#include <stdlib.h>
#include <stdio.h>
#include <fcntl.h>
#include <errno.h>
#include <time.h>
#include <string.h>
#include <signal.h>
#include <sys/ioctl.h>
#include <linux/hdreg.h>
#ifdef DEBUG
#define D(x) x
#else
#define D(x)
#endif
int endit = 0;
/* Check if the disk is in powersave-mode
* Most of the code is stolen from hdparm.
* 1 = active, 0 = standby/sleep, -1 = unknown */
int check_powermode(int fd)
{
unsigned char args[4] = {WIN_CHECKPOWERMODE1,0,0,0};
int state;
if (ioctl(fd, HDIO_DRIVE_CMD, &args)
&& (args[0] = WIN_CHECKPOWERMODE2) /* try again with 0x98 */
&& ioctl(fd, HDIO_DRIVE_CMD, &args)) {
if (errno != EIO || args[0] != 0 || args[1] != 0) {
state = -1; /* "unknown"; */
} else
state = 0; /* "sleeping"; */
} else {
state = (args[2] == 255) ? 1 : 0;
}
D(printf(" drive state is: %d\n", state));
return state;
}
char *state_name(int i)
{
if (i == -1) return "unknown";
if (i == 0) return "sleeping";
if (i == 1) return "active";
return "internal error";
}
char *myctime(time_t time)
{
char *ts = ctime(&time);
ts[strlen(ts) - 1] = 0;
return ts;
}
void measure(int fd)
{
time_t start_time;
int last_state;
time_t last_time;
int curr_state;
time_t curr_time = 0;
time_t time_diff;
time_t active_time = 0;
time_t sleep_time = 0;
time_t unknown_time = 0;
time_t total_time = 0;
int changes = 0;
float tmp;
printf("Starting measurements\n");
last_state = check_powermode(fd);
start_time = last_time = time(0);
printf(" System is in state %s\n\n", state_name(last_state));
while(!endit) {
sleep(1);
curr_state = check_powermode(fd);
if (curr_state != last_state || endit) {
changes++;
curr_time = time(0);
time_diff = curr_time - last_time;
if (last_state == 1) active_time += time_diff;
else if (last_state == 0) sleep_time += time_diff;
else unknown_time += time_diff;
last_state = curr_state;
last_time = curr_time;
printf("%s: State-change to %s\n", myctime(curr_time),
state_name(curr_state));
}
}
changes--; /* Compensate for SIGINT */
total_time = time(0) - start_time;
printf("\nTotal running time: %lus\n", curr_time - start_time);
printf(" State changed %d times\n", changes);
tmp = (float)sleep_time / (float)total_time * 100;
printf(" Time in sleep state: %lus (%.2f%%)\n", sleep_time, tmp);
tmp = (float)active_time / (float)total_time * 100;
printf(" Time in active state: %lus (%.2f%%)\n", active_time, tmp);
tmp = (float)unknown_time / (float)total_time * 100;
printf(" Time in unknown state: %lus (%.2f%%)\n", unknown_time, tmp);
}
void ender(int s)
{
endit = 1;
}
void usage()
{
puts("usage: dslm [-w <time>] <disk>");
exit(0);
}
int main(int argc, char **argv)
{
int fd;
char *disk = 0;
int settle_time = 60;
/* Parse the simple command-line */
if (argc == 2)
disk = argv[1];
else if (argc == 4) {
settle_time = atoi(argv[2]);
disk = argv[3];
} else
usage();
if (!(fd = open(disk, O_RDONLY|O_NONBLOCK))) {
printf("Can't open %s, because: %s\n", disk, strerror(errno));
exit(-1);
}
if (settle_time) {
printf("Waiting %d seconds for the system to settle down to "
"'normal'\n", settle_time);
sleep(settle_time);
} else
puts("Not waiting for system to settle down");
signal(SIGINT, ender);
measure(fd);
close(fd);
return 0;
}
---------------------------dslm.c END-------------------------------------------
spends spun up/down. See Documentation/laptops/dslm.c
Documentation/networking/Makefile
浏览文件 @ 74511020
......@@ -6,3 +6,5 @@ hostprogs-y := ifenslave
# Tell kbuild to always build the programs
always := $(hostprogs-y)
obj-m := timestamping/
Documentation/networking/skfp.txt
浏览文件 @ 74511020
......@@ -68,7 +68,7 @@ Compaq adapters (not tested):
=======================
From v2.01 on, the driver is integrated in the linux kernel sources.
Therefor, the installation is the same as for any other adapter
Therefore, the installation is the same as for any other adapter
supported by the kernel.
Refer to the manual of your distribution about the installation
of network adapters.
......
Documentation/networking/timestamping/Makefile
浏览文件 @ 74511020
CPPFLAGS = -I../../../include
# kbuild trick to avoid linker error. Can be omitted if a module is built.
obj- := dummy.o
timestamping: timestamping.c
# List of programs to build
hostprogs-y := timestamping
# Tell kbuild to always build the programs
always := $(hostprogs-y)
HOSTCFLAGS_timestamping.o += -I$(objtree)/usr/include
clean:
rm -f timestamping
Documentation/networking/timestamping/timestamping.c
浏览文件 @ 74511020
......@@ -41,9 +41,9 @@
#include <arpa/inet.h>
#include <net/if.h>
#include "asm/types.h"
#include "linux/net_tstamp.h"
#include "linux/errqueue.h"
#include <asm/types.h>
#include <linux/net_tstamp.h>
#include <linux/errqueue.h>
#ifndef SO_TIMESTAMPING
# define SO_TIMESTAMPING 37
......@@ -164,7 +164,7 @@ static void printpacket(struct msghdr *msg, int res,
gettimeofday(&now, 0);
printf("%ld.%06ld: received %s data, %d bytes from %s, %d bytes control messages\n",
printf("%ld.%06ld: received %s data, %d bytes from %s, %zu bytes control messages\n",
(long)now.tv_sec, (long)now.tv_usec,
(recvmsg_flags & MSG_ERRQUEUE) ? "error" : "regular",
res,
......@@ -173,7 +173,7 @@ static void printpacket(struct msghdr *msg, int res,
for (cmsg = CMSG_FIRSTHDR(msg);
cmsg;
cmsg = CMSG_NXTHDR(msg, cmsg)) {
printf(" cmsg len %d: ", cmsg->cmsg_len);
printf(" cmsg len %zu: ", cmsg->cmsg_len);
switch (cmsg->cmsg_level) {
case SOL_SOCKET:
printf("SOL_SOCKET ");
......@@ -370,7 +370,7 @@ int main(int argc, char **argv)
}
sock = socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP);
if (socket < 0)
if (sock < 0)
bail("socket");
memset(&device, 0, sizeof(device));
......
Documentation/pnp.txt
浏览文件 @ 74511020
......@@ -57,7 +57,7 @@ PC standard floppy disk controller
# cat resources
DISABLED
- Notice the string "DISABLED". THis means the device is not active.
- Notice the string "DISABLED". This means the device is not active.
3.) check the device's possible configurations (optional)
# cat options
......@@ -139,7 +139,7 @@ Plug and Play but it is planned to be in the near future.
Requirements for a Linux PnP protocol:
1.) the protocol must use EISA IDs
2.) the protocol must inform the PnP Layer of a devices current configuration
2.) the protocol must inform the PnP Layer of a device's current configuration
- the ability to set resources is optional but preferred.
The following are PnP protocol related functions:
......@@ -158,7 +158,7 @@ pnp_remove_device
- automatically will free mem used by the device and related structures
pnp_add_id
- adds a EISA ID to the list of supported IDs for the specified device
- adds an EISA ID to the list of supported IDs for the specified device
For more information consult the source of a protocol such as
/drivers/pnp/pnpbios/core.c.
......@@ -167,7 +167,7 @@ For more information consult the source of a protocol such as
Linux Plug and Play Drivers
---------------------------
This section contains information for linux PnP driver developers.
This section contains information for Linux PnP driver developers.
The New Way
...........
......@@ -235,11 +235,10 @@ static int __init serial8250_pnp_init(void)
The Old Way
...........
a series of compatibility functions have been created to make it easy to convert
A series of compatibility functions have been created to make it easy to convert
ISAPNP drivers. They should serve as a temporary solution only.
they are as follows:
They are as follows:
struct pnp_card *pnp_find_card(unsigned short vendor,
unsigned short device,
......
Documentation/power/runtime_pm.txt
浏览文件 @ 74511020
......@@ -256,7 +256,7 @@ drivers/base/power/runtime.c and include/linux/pm_runtime.h:
to suspend the device again in future
int pm_runtime_resume(struct device *dev);
- execute the subsystem-leve resume callback for the device; returns 0 on
- execute the subsystem-level resume callback for the device; returns 0 on
success, 1 if the device's run-time PM status was already 'active' or
error code on failure, where -EAGAIN means it may be safe to attempt to
resume the device again in future, but 'power.runtime_error' should be
......
Documentation/s390/kvm.txt
浏览文件 @ 74511020
......@@ -102,7 +102,7 @@ args: unsigned long
see also: include/linux/kvm.h
This ioctl stores the state of the cpu at the guest real address given as
argument, unless one of the following values defined in include/linux/kvm.h
is given as arguement:
is given as argument:
KVM_S390_STORE_STATUS_NOADDR - the CPU stores its status to the save area in
absolute lowcore as defined by the principles of operation
KVM_S390_STORE_STATUS_PREFIXED - the CPU stores its status to the save area in
......
Documentation/scsi/ChangeLog.lpfc
浏览文件 @ 74511020
......@@ -989,8 +989,8 @@ Changes from 20040709 to 20040716
* Remove redundant port_cmp != 2 check in if
(!port_cmp) { .... if (port_cmp != 2).... }
* Clock changes: removed struct clk_data and timerList.
* Clock changes: seperate nodev_tmo and els_retry_delay into 2
seperate timers and convert to 1 argument changed
* Clock changes: separate nodev_tmo and els_retry_delay into 2
separate timers and convert to 1 argument changed
LPFC_NODE_FARP_PEND_t to struct lpfc_node_farp_pend convert
ipfarp_tmo to 1 argument convert target struct tmofunc and
rtplunfunc to 1 argument * cr_count, cr_delay and
......@@ -1514,7 +1514,7 @@ Changes from 20040402 to 20040409
* Remove unused elxclock declaration in elx_sli.h.
* Since everywhere IOCB_ENTRY is used, the return value is cast,
move the cast into the macro.
* Split ioctls out into seperate files
* Split ioctls out into separate files
Changes from 20040326 to 20040402
......@@ -1534,7 +1534,7 @@ Changes from 20040326 to 20040402
* Unused variable cleanup
* Use Linux list macros for DMABUF_t
* Break up ioctls into 3 sections, dfc, util, hbaapi
rearranged code so this could be easily seperated into a
rearranged code so this could be easily separated into a
differnet module later All 3 are currently turned on by
defines in lpfc_ioctl.c LPFC_DFC_IOCTL, LPFC_UTIL_IOCTL,
LPFC_HBAAPI_IOCTL
......@@ -1551,7 +1551,7 @@ Changes from 20040326 to 20040402
started by lpfc_online(). lpfc_offline() only stopped
els_timeout routine. It now stops all timeout routines
associated with that hba.
* Replace seperate next and prev pointers in struct
* Replace separate next and prev pointers in struct
lpfc_bindlist with list_head type. In elxHBA_t, replace
fc_nlpbind_start and _end with fc_nlpbind_list and use
list_head macros to access it.
......
Documentation/serial/tty.txt
浏览文件 @ 74511020
......@@ -105,6 +105,10 @@ write_wakeup() - May be called at any point between open and close.
is permitted to call the driver write method from
this function. In such a situation defer it.
dcd_change() - Report to the tty line the current DCD pin status
changes and the relative timestamp. The timestamp
can be NULL.
Driver Access
......
Documentation/sysctl/vm.txt
浏览文件 @ 74511020
......@@ -573,11 +573,14 @@ Because other nodes' memory may be free. This means system total status
may be not fatal yet.
If this is set to 2, the kernel panics compulsorily even on the
above-mentioned.
above-mentioned. Even oom happens under memory cgroup, the whole
system panics.
The default value is 0.
1 and 2 are for failover of clustering. Please select either
according to your policy of failover.
panic_on_oom=2+kdump gives you very strong tool to investigate
why oom happens. You can get snapshot.
=============================================================
......
Documentation/timers/00-INDEX
浏览文件 @ 74511020
......@@ -4,6 +4,8 @@ highres.txt
- High resolution timers and dynamic ticks design notes
hpet.txt
- High Precision Event Timer Driver for Linux
hpet_example.c
- sample hpet timer test program
hrtimers.txt
- subsystem for high-resolution kernel timers
timer_stats.txt
......
Documentation/timers/Makefile 0 → 100644
浏览文件 @ 74511020
# kbuild trick to avoid linker error. Can be omitted if a module is built.
obj- := dummy.o
# List of programs to build
hostprogs-y := hpet_example
# Tell kbuild to always build the programs
always := $(hostprogs-y)
Documentation/timers/hpet.txt
浏览文件 @ 74511020
......@@ -26,274 +26,5 @@ initialization. An example of this initialization can be found in
arch/x86/kernel/hpet.c.
The driver provides a userspace API which resembles the API found in the
RTC driver framework. An example user space program is provided below.
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
#include <string.h>
#include <memory.h>
#include <malloc.h>
#include <time.h>
#include <ctype.h>
#include <sys/types.h>
#include <sys/wait.h>
#include <signal.h>
#include <fcntl.h>
#include <errno.h>
#include <sys/time.h>
#include <linux/hpet.h>
extern void hpet_open_close(int, const char **);
extern void hpet_info(int, const char **);
extern void hpet_poll(int, const char **);
extern void hpet_fasync(int, const char **);
extern void hpet_read(int, const char **);
#include <sys/poll.h>
#include <sys/ioctl.h>
#include <signal.h>
struct hpet_command {
char *command;
void (*func)(int argc, const char ** argv);
} hpet_command[] = {
{
"open-close",
hpet_open_close
},
{
"info",
hpet_info
},
{
"poll",
hpet_poll
},
{
"fasync",
hpet_fasync
},
};
int
main(int argc, const char ** argv)
{
int i;
argc--;
argv++;
if (!argc) {
fprintf(stderr, "-hpet: requires command\n");
return -1;
}
for (i = 0; i < (sizeof (hpet_command) / sizeof (hpet_command[0])); i++)
if (!strcmp(argv[0], hpet_command[i].command)) {
argc--;
argv++;
fprintf(stderr, "-hpet: executing %s\n",
hpet_command[i].command);
hpet_command[i].func(argc, argv);
return 0;
}
fprintf(stderr, "do_hpet: command %s not implemented\n", argv[0]);
return -1;
}
void
hpet_open_close(int argc, const char **argv)
{
int fd;
if (argc != 1) {
fprintf(stderr, "hpet_open_close: device-name\n");
return;
}
fd = open(argv[0], O_RDONLY);
if (fd < 0)
fprintf(stderr, "hpet_open_close: open failed\n");
else
close(fd);
return;
}
void
hpet_info(int argc, const char **argv)
{
}
void
hpet_poll(int argc, const char **argv)
{
unsigned long freq;
int iterations, i, fd;
struct pollfd pfd;
struct hpet_info info;
struct timeval stv, etv;
struct timezone tz;
long usec;
if (argc != 3) {
fprintf(stderr, "hpet_poll: device-name freq iterations\n");
return;
}
freq = atoi(argv[1]);
iterations = atoi(argv[2]);
fd = open(argv[0], O_RDONLY);
if (fd < 0) {
fprintf(stderr, "hpet_poll: open of %s failed\n", argv[0]);
return;
}
if (ioctl(fd, HPET_IRQFREQ, freq) < 0) {
fprintf(stderr, "hpet_poll: HPET_IRQFREQ failed\n");
goto out;
}
if (ioctl(fd, HPET_INFO, &info) < 0) {
fprintf(stderr, "hpet_poll: failed to get info\n");
goto out;
}
fprintf(stderr, "hpet_poll: info.hi_flags 0x%lx\n", info.hi_flags);
if (info.hi_flags && (ioctl(fd, HPET_EPI, 0) < 0)) {
fprintf(stderr, "hpet_poll: HPET_EPI failed\n");
goto out;
}
if (ioctl(fd, HPET_IE_ON, 0) < 0) {
fprintf(stderr, "hpet_poll, HPET_IE_ON failed\n");
goto out;
}
pfd.fd = fd;
pfd.events = POLLIN;
for (i = 0; i < iterations; i++) {
pfd.revents = 0;
gettimeofday(&stv, &tz);
if (poll(&pfd, 1, -1) < 0)
fprintf(stderr, "hpet_poll: poll failed\n");
else {
long data;
gettimeofday(&etv, &tz);
usec = stv.tv_sec * 1000000 + stv.tv_usec;
usec = (etv.tv_sec * 1000000 + etv.tv_usec) - usec;
fprintf(stderr,
"hpet_poll: expired time = 0x%lx\n", usec);
fprintf(stderr, "hpet_poll: revents = 0x%x\n",
pfd.revents);
if (read(fd, &data, sizeof(data)) != sizeof(data)) {
fprintf(stderr, "hpet_poll: read failed\n");
}
else
fprintf(stderr, "hpet_poll: data 0x%lx\n",
data);
}
}
out:
close(fd);
return;
}
static int hpet_sigio_count;
static void
hpet_sigio(int val)
{
fprintf(stderr, "hpet_sigio: called\n");
hpet_sigio_count++;
}
void
hpet_fasync(int argc, const char **argv)
{
unsigned long freq;
int iterations, i, fd, value;
sig_t oldsig;
struct hpet_info info;
hpet_sigio_count = 0;
fd = -1;
if ((oldsig = signal(SIGIO, hpet_sigio)) == SIG_ERR) {
fprintf(stderr, "hpet_fasync: failed to set signal handler\n");
return;
}
if (argc != 3) {
fprintf(stderr, "hpet_fasync: device-name freq iterations\n");
goto out;
}
fd = open(argv[0], O_RDONLY);
if (fd < 0) {
fprintf(stderr, "hpet_fasync: failed to open %s\n", argv[0]);
return;
}
if ((fcntl(fd, F_SETOWN, getpid()) == 1) ||
((value = fcntl(fd, F_GETFL)) == 1) ||
(fcntl(fd, F_SETFL, value | O_ASYNC) == 1)) {
fprintf(stderr, "hpet_fasync: fcntl failed\n");
goto out;
}
freq = atoi(argv[1]);
iterations = atoi(argv[2]);
if (ioctl(fd, HPET_IRQFREQ, freq) < 0) {
fprintf(stderr, "hpet_fasync: HPET_IRQFREQ failed\n");
goto out;
}
if (ioctl(fd, HPET_INFO, &info) < 0) {
fprintf(stderr, "hpet_fasync: failed to get info\n");
goto out;
}
fprintf(stderr, "hpet_fasync: info.hi_flags 0x%lx\n", info.hi_flags);
if (info.hi_flags && (ioctl(fd, HPET_EPI, 0) < 0)) {
fprintf(stderr, "hpet_fasync: HPET_EPI failed\n");
goto out;
}
if (ioctl(fd, HPET_IE_ON, 0) < 0) {
fprintf(stderr, "hpet_fasync, HPET_IE_ON failed\n");
goto out;
}
for (i = 0; i < iterations; i++) {
(void) pause();
fprintf(stderr, "hpet_fasync: count = %d\n", hpet_sigio_count);
}
out:
signal(SIGIO, oldsig);
if (fd >= 0)
close(fd);
return;
}
RTC driver framework. An example user space program is provided in
file:Documentation/timers/hpet_example.c
Documentation/timers/hpet_example.c 0 → 100644
浏览文件 @ 74511020
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
#include <string.h>
#include <memory.h>
#include <malloc.h>
#include <time.h>
#include <ctype.h>
#include <sys/types.h>
#include <sys/wait.h>
#include <signal.h>
#include <fcntl.h>
#include <errno.h>
#include <sys/time.h>
#include <linux/hpet.h>
extern void hpet_open_close(int, const char **);
extern void hpet_info(int, const char **);
extern void hpet_poll(int, const char **);
extern void hpet_fasync(int, const char **);
extern void hpet_read(int, const char **);
#include <sys/poll.h>
#include <sys/ioctl.h>
#include <signal.h>
struct hpet_command {
char *command;
void (*func)(int argc, const char ** argv);
} hpet_command[] = {
{
"open-close",
hpet_open_close
},
{
"info",
hpet_info
},
{
"poll",
hpet_poll
},
{
"fasync",
hpet_fasync
},
};
int
main(int argc, const char ** argv)
{
int i;
argc--;
argv++;
if (!argc) {
fprintf(stderr, "-hpet: requires command\n");
return -1;
}
for (i = 0; i < (sizeof (hpet_command) / sizeof (hpet_command[0])); i++)
if (!strcmp(argv[0], hpet_command[i].command)) {
argc--;
argv++;
fprintf(stderr, "-hpet: executing %s\n",
hpet_command[i].command);
hpet_command[i].func(argc, argv);
return 0;
}
fprintf(stderr, "do_hpet: command %s not implemented\n", argv[0]);
return -1;
}
void
hpet_open_close(int argc, const char **argv)
{
int fd;
if (argc != 1) {
fprintf(stderr, "hpet_open_close: device-name\n");
return;
}
fd = open(argv[0], O_RDONLY);
if (fd < 0)
fprintf(stderr, "hpet_open_close: open failed\n");
else
close(fd);
return;
}
void
hpet_info(int argc, const char **argv)
{
}
void
hpet_poll(int argc, const char **argv)
{
unsigned long freq;
int iterations, i, fd;
struct pollfd pfd;
struct hpet_info info;
struct timeval stv, etv;
struct timezone tz;
long usec;
if (argc != 3) {
fprintf(stderr, "hpet_poll: device-name freq iterations\n");
return;
}
freq = atoi(argv[1]);
iterations = atoi(argv[2]);
fd = open(argv[0], O_RDONLY);
if (fd < 0) {
fprintf(stderr, "hpet_poll: open of %s failed\n", argv[0]);
return;
}
if (ioctl(fd, HPET_IRQFREQ, freq) < 0) {
fprintf(stderr, "hpet_poll: HPET_IRQFREQ failed\n");
goto out;
}
if (ioctl(fd, HPET_INFO, &info) < 0) {
fprintf(stderr, "hpet_poll: failed to get info\n");
goto out;
}
fprintf(stderr, "hpet_poll: info.hi_flags 0x%lx\n", info.hi_flags);
if (info.hi_flags && (ioctl(fd, HPET_EPI, 0) < 0)) {
fprintf(stderr, "hpet_poll: HPET_EPI failed\n");
goto out;
}
if (ioctl(fd, HPET_IE_ON, 0) < 0) {
fprintf(stderr, "hpet_poll, HPET_IE_ON failed\n");
goto out;
}
pfd.fd = fd;
pfd.events = POLLIN;
for (i = 0; i < iterations; i++) {
pfd.revents = 0;
gettimeofday(&stv, &tz);
if (poll(&pfd, 1, -1) < 0)
fprintf(stderr, "hpet_poll: poll failed\n");
else {
long data;
gettimeofday(&etv, &tz);
usec = stv.tv_sec * 1000000 + stv.tv_usec;
usec = (etv.tv_sec * 1000000 + etv.tv_usec) - usec;
fprintf(stderr,
"hpet_poll: expired time = 0x%lx\n", usec);
fprintf(stderr, "hpet_poll: revents = 0x%x\n",
pfd.revents);
if (read(fd, &data, sizeof(data)) != sizeof(data)) {
fprintf(stderr, "hpet_poll: read failed\n");
}
else
fprintf(stderr, "hpet_poll: data 0x%lx\n",
data);
}
}
out:
close(fd);
return;
}
static int hpet_sigio_count;
static void
hpet_sigio(int val)
{
fprintf(stderr, "hpet_sigio: called\n");
hpet_sigio_count++;
}
void
hpet_fasync(int argc, const char **argv)
{
unsigned long freq;
int iterations, i, fd, value;
sig_t oldsig;
struct hpet_info info;
hpet_sigio_count = 0;
fd = -1;
if ((oldsig = signal(SIGIO, hpet_sigio)) == SIG_ERR) {
fprintf(stderr, "hpet_fasync: failed to set signal handler\n");
return;
}
if (argc != 3) {
fprintf(stderr, "hpet_fasync: device-name freq iterations\n");
goto out;
}
fd = open(argv[0], O_RDONLY);
if (fd < 0) {
fprintf(stderr, "hpet_fasync: failed to open %s\n", argv[0]);
return;
}
if ((fcntl(fd, F_SETOWN, getpid()) == 1) ||
((value = fcntl(fd, F_GETFL)) == 1) ||
(fcntl(fd, F_SETFL, value | O_ASYNC) == 1)) {
fprintf(stderr, "hpet_fasync: fcntl failed\n");
goto out;
}
freq = atoi(argv[1]);
iterations = atoi(argv[2]);
if (ioctl(fd, HPET_IRQFREQ, freq) < 0) {
fprintf(stderr, "hpet_fasync: HPET_IRQFREQ failed\n");
goto out;
}
if (ioctl(fd, HPET_INFO, &info) < 0) {
fprintf(stderr, "hpet_fasync: failed to get info\n");
goto out;
}
fprintf(stderr, "hpet_fasync: info.hi_flags 0x%lx\n", info.hi_flags);
if (info.hi_flags && (ioctl(fd, HPET_EPI, 0) < 0)) {
fprintf(stderr, "hpet_fasync: HPET_EPI failed\n");
goto out;
}
if (ioctl(fd, HPET_IE_ON, 0) < 0) {
fprintf(stderr, "hpet_fasync, HPET_IE_ON failed\n");
goto out;
}
for (i = 0; i < iterations; i++) {
(void) pause();
fprintf(stderr, "hpet_fasync: count = %d\n", hpet_sigio_count);
}
out:
signal(SIGIO, oldsig);
if (fd >= 0)
close(fd);
return;
}
Documentation/trace/ftrace.txt
浏览文件 @ 74511020
......@@ -1588,7 +1588,7 @@ module author does not need to worry about it.
When tracing is enabled, kstop_machine is called to prevent
races with the CPUS executing code being modified (which can
cause the CPU to do undesireable things), and the nops are
cause the CPU to do undesirable things), and the nops are
patched back to calls. But this time, they do not call mcount
(which is just a function stub). They now call into the ftrace
infrastructure.
......
Documentation/vm/00-INDEX
浏览文件 @ 74511020
......@@ -4,23 +4,35 @@ active_mm.txt
- An explanation from Linus about tsk->active_mm vs tsk->mm.
balance
- various information on memory balancing.
hugepage-mmap.c
- Example app using huge page memory with the mmap system call.
hugepage-shm.c
- Example app using huge page memory with Sys V shared memory system calls.
hugetlbpage.txt
- a brief summary of hugetlbpage support in the Linux kernel.
hwpoison.txt
- explains what hwpoison is
ksm.txt
- how to use the Kernel Samepage Merging feature.
locking
- info on how locking and synchronization is done in the Linux vm code.
map_hugetlb.c
- an example program that uses the MAP_HUGETLB mmap flag.
numa
- information about NUMA specific code in the Linux vm.
numa_memory_policy.txt
- documentation of concepts and APIs of the 2.6 memory policy support.
overcommit-accounting
- description of the Linux kernels overcommit handling modes.
page-types.c
- Tool for querying page flags
page_migration
- description of page migration in NUMA systems.
pagemap.txt
- pagemap, from the userspace perspective
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.
unevictable-lru.txt
- Unevictable LRU infrastructure
Documentation/vm/Makefile
浏览文件 @ 74511020
......@@ -2,7 +2,7 @@
obj- := dummy.o
# List of programs to build
hostprogs-y := slabinfo page-types
hostprogs-y := slabinfo page-types hugepage-mmap hugepage-shm map_hugetlb
# Tell kbuild to always build the programs
always := $(hostprogs-y)
Documentation/vm/hugepage-mmap.c 0 → 100644
浏览文件 @ 74511020
/*
* hugepage-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 the ia64 architecture, the Linux kernel reserves Region number 4 for
* huge pages. That means that if one requires a fixed address, a huge page
* aligned address starting with 0x800000... will be required. If a fixed
* address is not required, the kernel will select an address in the proper
* range.
* Other architectures, such as ppc64, i386 or x86_64 are not so constrained.
*/
#include <stdlib.h>
#include <stdio.h>
#include <unistd.h>
#include <sys/mman.h>
#include <fcntl.h>
#define FILE_NAME "/mnt/hugepagefile"
#define LENGTH (256UL*1024*1024)
#define PROTECTION (PROT_READ | PROT_WRITE)
/* Only ia64 requires this */
#ifdef __ia64__
#define ADDR (void *)(0x8000000000000000UL)
#define FLAGS (MAP_SHARED | MAP_FIXED)
#else
#define ADDR (void *)(0x0UL)
#define FLAGS (MAP_SHARED)
#endif
static void check_bytes(char *addr)
{
printf("First hex is %x\n", *((unsigned int *)addr));
}
static void write_bytes(char *addr)
{
unsigned long i;
for (i = 0; i < LENGTH; i++)
*(addr + i) = (char)i;
}
static 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;
int fd;
fd = open(FILE_NAME, O_CREAT | O_RDWR, 0755);
if (fd < 0) {
perror("Open failed");
exit(1);
}
addr = mmap(ADDR, LENGTH, PROTECTION, FLAGS, fd, 0);
if (addr == MAP_FAILED) {
perror("mmap");
unlink(FILE_NAME);
exit(1);
}
printf("Returned address is %p\n", addr);
check_bytes(addr);
write_bytes(addr);
read_bytes(addr);
munmap(addr, LENGTH);
close(fd);
unlink(FILE_NAME);
return 0;
}
Documentation/vm/hugepage-shm.c 0 → 100644
浏览文件 @ 74511020
/*
* hugepage-shm:
*
* 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 huge pages.
*
* For the ia64 architecture, the Linux kernel reserves Region number 4 for
* huge pages. That means that if one requires a fixed address, a huge page
* aligned address starting with 0x800000... will be required. If a fixed
* address is not required, the kernel will select an address in the proper
* range.
* Other architectures, such as ppc64, i386 or x86_64 are not so constrained.
*
* Note: The default shared memory limit is quite low on many kernels,
* you may need to increase it via:
*
* echo 268435456 > /proc/sys/kernel/shmmax
*
* This will increase the maximum size per shared memory segment to 256MB.
* The other limit that you will hit eventually is shmall which is the
* total amount of shared memory in pages. To set it to 16GB on a system
* with a 4kB pagesize do:
*
* echo 4194304 > /proc/sys/kernel/shmall
*/
#include <stdlib.h>
#include <stdio.h>
#include <sys/types.h>
#include <sys/ipc.h>
#include <sys/shm.h>
#include <sys/mman.h>
#ifndef SHM_HUGETLB
#define SHM_HUGETLB 04000
#endif
#define LENGTH (256UL*1024*1024)
#define dprintf(x) printf(x)
/* Only ia64 requires this */
#ifdef __ia64__
#define ADDR (void *)(0x8000000000000000UL)
#define SHMAT_FLAGS (SHM_RND)
#else
#define ADDR (void *)(0x0UL)
#define SHMAT_FLAGS (0)
#endif
int main(void)
{
int shmid;
unsigned long i;
char *shmaddr;
if ((shmid = shmget(2, LENGTH,
SHM_HUGETLB | IPC_CREAT | SHM_R | SHM_W)) < 0) {
perror("shmget");
exit(1);
}
printf("shmid: 0x%x\n", shmid);
shmaddr = shmat(shmid, ADDR, SHMAT_FLAGS);
if (shmaddr == (char *)-1) {
perror("Shared memory attach failure");
shmctl(shmid, IPC_RMID, NULL);
exit(2);
}
printf("shmaddr: %p\n", shmaddr);
dprintf("Starting the writes:\n");
for (i = 0; i < LENGTH; i++) {
shmaddr[i] = (char)(i);
if (!(i % (1024 * 1024)))
dprintf(".");
}
dprintf("\n");
dprintf("Starting the Check...");
for (i = 0; i < LENGTH; i++)
if (shmaddr[i] != (char)i)
printf("\nIndex %lu mismatched\n", i);
dprintf("Done.\n");
if (shmdt((const void *)shmaddr) != 0) {
perror("Detach failure");
shmctl(shmid, IPC_RMID, NULL);
exit(3);
}
shmctl(shmid, IPC_RMID, NULL);
return 0;
}
Documentation/vm/hugetlbpage.txt
浏览文件 @ 74511020
......@@ -299,176 +299,11 @@ map_hugetlb.c.
*******************************************************************
/*
* 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 huge pages.
*
* For the ia64 architecture, the Linux kernel reserves Region number 4 for
* huge pages. That means that if one requires a fixed address, a huge page
* aligned address starting with 0x800000... will be required. If a fixed
* address is not required, the kernel will select an address in the proper
* range.
* Other architectures, such as ppc64, i386 or x86_64 are not so constrained.
*
* Note: The default shared memory limit is quite low on many kernels,
* you may need to increase it via:
*
* echo 268435456 > /proc/sys/kernel/shmmax
*
* This will increase the maximum size per shared memory segment to 256MB.
* The other limit that you will hit eventually is shmall which is the
* total amount of shared memory in pages. To set it to 16GB on a system
* with a 4kB pagesize do:
*
* echo 4194304 > /proc/sys/kernel/shmall
* hugepage-shm: see Documentation/vm/hugepage-shm.c
*/
#include <stdlib.h>
#include <stdio.h>
#include <sys/types.h>
#include <sys/ipc.h>
#include <sys/shm.h>
#include <sys/mman.h>
#ifndef SHM_HUGETLB
#define SHM_HUGETLB 04000
#endif
#define LENGTH (256UL*1024*1024)
#define dprintf(x) printf(x)
#define ADDR (void *)(0x0UL) /* let kernel choose address */
#define SHMAT_FLAGS (0)
int main(void)
{
int shmid;
unsigned long i;
char *shmaddr;
if ((shmid = shmget(2, LENGTH,
SHM_HUGETLB | IPC_CREAT | SHM_R | SHM_W)) < 0) {
perror("shmget");
exit(1);
}
printf("shmid: 0x%x\n", shmid);
shmaddr = shmat(shmid, ADDR, SHMAT_FLAGS);
if (shmaddr == (char *)-1) {
perror("Shared memory attach failure");
shmctl(shmid, IPC_RMID, NULL);
exit(2);
}
printf("shmaddr: %p\n", shmaddr);
dprintf("Starting the writes:\n");
for (i = 0; i < LENGTH; i++) {
shmaddr[i] = (char)(i);
if (!(i % (1024 * 1024)))
dprintf(".");
}
dprintf("\n");
dprintf("Starting the Check...");
for (i = 0; i < LENGTH; i++)
if (shmaddr[i] != (char)i)
printf("\nIndex %lu mismatched\n", i);
dprintf("Done.\n");
if (shmdt((const void *)shmaddr) != 0) {
perror("Detach failure");
shmctl(shmid, IPC_RMID, NULL);
exit(3);
}
shmctl(shmid, IPC_RMID, NULL);
return 0;
}
*******************************************************************
/*
* 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 the ia64 architecture, the Linux kernel reserves Region number 4 for
* huge pages. That means that if one requires a fixed address, a huge page
* aligned address starting with 0x800000... will be required. If a fixed
* address is not required, the kernel will select an address in the proper
* range.
* Other architectures, such as ppc64, i386 or x86_64 are not so constrained.
* hugepage-mmap: see Documentation/vm/hugepage-mmap.c
*/
#include <stdlib.h>
#include <stdio.h>
#include <unistd.h>
#include <sys/mman.h>
#include <fcntl.h>
#define FILE_NAME "/mnt/hugepagefile"
#define LENGTH (256UL*1024*1024)
#define PROTECTION (PROT_READ | PROT_WRITE)
#define ADDR (void *)(0x0UL) /* let kernel choose address */
#define FLAGS (MAP_SHARED)
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;
int fd;
fd = open(FILE_NAME, O_CREAT | O_RDWR, 0755);
if (fd < 0) {
perror("Open failed");
exit(1);
}
addr = mmap(ADDR, LENGTH, PROTECTION, FLAGS, fd, 0);
if (addr == MAP_FAILED) {
perror("mmap");
unlink(FILE_NAME);
exit(1);
}
printf("Returned address is %p\n", addr);
check_bytes(addr);
write_bytes(addr);
read_bytes(addr);
munmap(addr, LENGTH);
close(fd);
unlink(FILE_NAME);
return 0;
}
Documentation/vm/map_hugetlb.c
浏览文件 @ 74511020
......@@ -31,12 +31,12 @@
#define FLAGS (MAP_PRIVATE | MAP_ANONYMOUS | MAP_HUGETLB)
#endif
void check_bytes(char *addr)
static void check_bytes(char *addr)
{
printf("First hex is %x\n", *((unsigned int *)addr));
}
void write_bytes(char *addr)
static void write_bytes(char *addr)
{
unsigned long i;
......@@ -44,7 +44,7 @@ void write_bytes(char *addr)
*(addr + i) = (char)i;
}
void read_bytes(char *addr)
static void read_bytes(char *addr)
{
unsigned long i;
......
Documentation/voyager.txt 已删除 100644 → 0
浏览文件 @ 69266866
Running Linux on the Voyager Architecture
=========================================
For full details and current project status, see
http://www.hansenpartnership.com/voyager
The voyager architecture was designed by NCR in the mid 80s to be a
fully SMP capable RAS computing architecture built around intel's 486
chip set. The voyager came in three levels of architectural
sophistication: 3,4 and 5 --- 1 and 2 never made it out of prototype.
The linux patches support only the Level 5 voyager architecture (any
machine class 3435 and above).
The Voyager Architecture
------------------------
Voyager machines consist of a Baseboard with a 386 diagnostic
processor, a Power Supply Interface (PSI) a Primary and possibly
Secondary Microchannel bus and between 2 and 20 voyager slots. The
voyager slots can be populated with memory and cpu cards (up to 4GB
memory and from 1 486 to 32 Pentium Pro processors). Internally, the
voyager has a dual arbitrated system bus and a configuration and test
bus (CAT). The voyager bus speed is 40MHz. Therefore (since all
voyager cards are dual ported for each system bus) the maximum
transfer rate is 320Mb/s but only if you have your slot configuration
tuned (only memory cards can communicate with both busses at once, CPU
cards utilise them one at a time).
Voyager SMP
-----------
Since voyager was the first intel based SMP system, it is slightly
more primitive than the Intel IO-APIC approach to SMP. Voyager allows
arbitrary interrupt routing (including processor affinity routing) of
all 16 PC type interrupts. However it does this by using a modified
5259 master/slave chip set instead of an APIC bus. Additionally,
voyager supports Cross Processor Interrupts (CPI) equivalent to the
APIC IPIs. There are two routed voyager interrupt lines provided to
each slot.
Processor Cards
---------------
These come in single, dyadic and quad configurations (the quads are
problematic--see later). The maximum configuration is 8 quad cards
for 32 way SMP.
Quad Processors
---------------
Because voyager only supplies two interrupt lines to each Processor
card, the Quad processors have to be configured (and Bootstrapped) in
as a pair of Master/Slave processors.
In fact, most Quad cards only accept one VIC interrupt line, so they
have one interrupt handling processor (called the VIC extended
processor) and three non-interrupt handling processors.
Current Status
--------------
The System will boot on Mono, Dyad and Quad cards. There was
originally a Quad boot problem which has been fixed by proper gdt
alignment in the initial boot loader. If you still cannot get your
voyager system to boot, email me at:
<J.E.J.Bottomley@HansenPartnership.com>
The Quad cards now support using the separate Quad CPI vectors instead
of going through the VIC mailbox system.
The Level 4 architecture (3430 and 3360 Machines) should also work
fine.
Dump Switch
-----------
The voyager dump switch sends out a broadcast NMI which the voyager
code intercepts and does a task dump.
Power Switch
------------
The front panel power switch is intercepted by the kernel and should
cause a system shutdown and power off.
A Note About Mixed CPU Systems
------------------------------
Linux isn't designed to handle mixed CPU systems very well. In order
to get everything going you *must* make sure that your lowest
capability CPU is used for booting. Also, mixing CPU classes
(e.g. 486 and 586) is really not going to work very well at all.
MAINTAINERS
浏览文件 @ 74511020
......@@ -666,6 +666,12 @@ T: git://git.pengutronix.de/git/imx/linux-2.6.git
F: arch/arm/mach-mx*/
F: arch/arm/plat-mxc/
ARM/FREESCALE IMX51
M: Amit Kucheria <amit.kucheria@canonical.com>
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
S: Maintained
F: arch/arm/mach-mx5/
ARM/GLOMATION GESBC9312SX MACHINE SUPPORT
M: Lennert Buytenhek <kernel@wantstofly.org>
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
......@@ -939,6 +945,16 @@ W: http://www.fluff.org/ben/linux/
S: Maintained
F: arch/arm/mach-s3c6410/
ARM/SHMOBILE ARM ARCHITECTURE
M: Paul Mundt <lethal@linux-sh.org>
M: Magnus Damm <magnus.damm@gmail.com>
L: linux-sh@vger.kernel.org
T: git git://git.kernel.org/pub/scm/linux/kernel/git/lethal/genesis-2.6.git
W: http://oss.renesas.com
S: Supported
F: arch/arm/mach-shmobile/
F: drivers/sh/
ARM/TECHNOLOGIC SYSTEMS TS7250 MACHINE SUPPORT
M: Lennert Buytenhek <kernel@wantstofly.org>
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
......@@ -1235,6 +1251,13 @@ W: http://blackfin.uclinux.org
S: Supported
F: drivers/rtc/rtc-bfin.c
BLACKFIN SDH DRIVER
M: Cliff Cai <cliff.cai@analog.com>
L: uclinux-dist-devel@blackfin.uclinux.org
W: http://blackfin.uclinux.org
S: Supported
F: drivers/mmc/host/bfin_sdh.c
BLACKFIN SERIAL DRIVER
M: Sonic Zhang <sonic.zhang@analog.com>
L: uclinux-dist-devel@blackfin.uclinux.org
......@@ -1382,20 +1405,30 @@ F: arch/x86/include/asm/calgary.h
F: arch/x86/include/asm/tce.h
CAN NETWORK LAYER
M: Urs Thuermann <urs.thuermann@volkswagen.de>
M: Oliver Hartkopp <socketcan@hartkopp.net>
M: Oliver Hartkopp <oliver.hartkopp@volkswagen.de>
L: socketcan-core@lists.berlios.de (subscribers-only)
M: Urs Thuermann <urs.thuermann@volkswagen.de>
L: socketcan-core@lists.berlios.de
L: netdev@vger.kernel.org
W: http://developer.berlios.de/projects/socketcan/
S: Maintained
F: drivers/net/can/
F: include/linux/can/
F: net/can/
F: include/linux/can.h
F: include/linux/can/core.h
F: include/linux/can/bcm.h
F: include/linux/can/raw.h
CAN NETWORK DRIVERS
M: Wolfgang Grandegger <wg@grandegger.com>
L: socketcan-core@lists.berlios.de (subscribers-only)
L: socketcan-core@lists.berlios.de
L: netdev@vger.kernel.org
W: http://developer.berlios.de/projects/socketcan/
S: Maintained
F: drivers/net/can/
F: include/linux/can/dev.h
F: include/linux/can/error.h
F: include/linux/can/netlink.h
F: include/linux/can/platform/
CELL BROADBAND ENGINE ARCHITECTURE
M: Arnd Bergmann <arnd@arndb.de>
......@@ -1408,6 +1441,15 @@ F: arch/powerpc/include/asm/spu*.h
F: arch/powerpc/oprofile/*cell*
F: arch/powerpc/platforms/cell/
CEPH DISTRIBUTED FILE SYSTEM CLIENT
M: Sage Weil <sage@newdream.net>
L: ceph-devel@lists.sourceforge.net
W: http://ceph.newdream.net/
T: git git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git
S: Supported
F: Documentation/filesystems/ceph.txt
F: fs/ceph
CERTIFIED WIRELESS USB (WUSB) SUBSYSTEM:
M: David Vrabel <david.vrabel@csr.com>
L: linux-usb@vger.kernel.org
......@@ -2107,6 +2149,7 @@ F: drivers/net/eexpress.*
ETHERNET BRIDGE
M: Stephen Hemminger <shemminger@linux-foundation.org>
L: bridge@lists.linux-foundation.org
L: netdev@vger.kernel.org
W: http://www.linux-foundation.org/en/Net:Bridge
S: Maintained
F: include/linux/netfilter_bridge/
......@@ -2804,7 +2847,7 @@ S: Maintained
F: drivers/input/
INTEL FRAMEBUFFER DRIVER (excluding 810 and 815)
M: Sylvain Meyer <sylvain.meyer@worldonline.fr>
M: Maik Broemme <mbroemme@plusserver.de>
L: linux-fbdev@vger.kernel.org
S: Maintained
F: Documentation/fb/intelfb.txt
......@@ -3621,7 +3664,7 @@ F: mm/
MEMORY RESOURCE CONTROLLER
M: Balbir Singh <balbir@linux.vnet.ibm.com>
M: Pavel Emelyanov <xemul@openvz.org>
M: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
M: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
L: linux-mm@kvack.org
S: Maintained
......@@ -4293,6 +4336,7 @@ PERFORMANCE EVENTS SUBSYSTEM
M: Peter Zijlstra <a.p.zijlstra@chello.nl>
M: Paul Mackerras <paulus@samba.org>
M: Ingo Molnar <mingo@elte.hu>
M: Arnaldo Carvalho de Melo <acme@redhat.com>
S: Supported
F: kernel/perf_event.c
F: include/linux/perf_event.h
......@@ -4495,6 +4539,13 @@ L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
T: git git://git.kernel.org/pub/scm/linux/kernel/git/ycmiao/pxa-linux-2.6.git
S: Maintained
MMP2 SUPPORT (aka ARMADA610)
M: Haojian Zhuang <haojian.zhuang@marvell.com>
M: Eric Miao <eric.y.miao@gmail.com>
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
T: git git://git.kernel.org/pub/scm/linux/kernel/git/ycmiao/pxa-linux-2.6.git
S: Maintained
PXA MMCI DRIVER
S: Orphan
......@@ -5172,6 +5223,21 @@ T: git git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc-next-2.6.git
S: Maintained
F: arch/sparc/
SPARC SERIAL DRIVERS
M: "David S. Miller" <davem@davemloft.net>
L: sparclinux@vger.kernel.org
T: git git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc-2.6.git
T: git git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc-next-2.6.git
S: Maintained
F: drivers/serial/suncore.c
F: drivers/serial/suncore.h
F: drivers/serial/sunhv.c
F: drivers/serial/sunsab.c
F: drivers/serial/sunsab.h
F: drivers/serial/sunsu.c
F: drivers/serial/sunzilog.c
F: drivers/serial/sunzilog.h
SPECIALIX IO8+ MULTIPORT SERIAL CARD DRIVER
M: Roger Wolff <R.E.Wolff@BitWizard.nl>
S: Supported
......
Makefile
浏览文件 @ 74511020
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 34
EXTRAVERSION = -rc1
EXTRAVERSION = -rc2
NAME = Man-Eating Seals of Antiquity
# *DOCUMENTATION*
......
arch/alpha/Kconfig
浏览文件 @ 74511020
......@@ -10,6 +10,7 @@ config ALPHA
select HAVE_OPROFILE
select HAVE_SYSCALL_WRAPPERS
select HAVE_PERF_EVENTS
select HAVE_DMA_ATTRS
help
The Alpha is a 64-bit general-purpose processor designed and
marketed by the Digital Equipment Corporation of blessed memory,
......@@ -58,6 +59,9 @@ config ZONE_DMA
bool
default y
config NEED_DMA_MAP_STATE
def_bool y
config GENERIC_ISA_DMA
bool
default y
......
arch/alpha/include/asm/core_marvel.h
浏览文件 @ 74511020
......@@ -12,7 +12,6 @@
#define __ALPHA_MARVEL__H__
#include <linux/types.h>
#include <linux/pci.h>
#include <linux/spinlock.h>
#include <asm/compiler.h>
......
arch/alpha/include/asm/core_mcpcia.h
浏览文件 @ 74511020
......@@ -6,7 +6,6 @@
#define MCPCIA_ONE_HAE_WINDOW 1
#include <linux/types.h>
#include <linux/pci.h>
#include <asm/compiler.h>
/*
......
arch/alpha/include/asm/core_titan.h
浏览文件 @ 74511020
......@@ -2,7 +2,6 @@
#define __ALPHA_TITAN__H__
#include <linux/types.h>
#include <linux/pci.h>
#include <asm/compiler.h>
/*
......
arch/alpha/include/asm/core_tsunami.h
浏览文件 @ 74511020
......@@ -2,7 +2,6 @@
#define __ALPHA_TSUNAMI__H__
#include <linux/types.h>
#include <linux/pci.h>
#include <asm/compiler.h>
/*
......
arch/alpha/include/asm/dma-mapping.h
浏览文件 @ 74511020
#ifndef _ALPHA_DMA_MAPPING_H
#define _ALPHA_DMA_MAPPING_H
#include <linux/dma-attrs.h>
#ifdef CONFIG_PCI
extern struct dma_map_ops *dma_ops;
#include <linux/pci.h>
static inline struct dma_map_ops *get_dma_ops(struct device *dev)
{
return dma_ops;
}
#define dma_map_single(dev, va, size, dir) \
pci_map_single(alpha_gendev_to_pci(dev), va, size, dir)
#define dma_unmap_single(dev, addr, size, dir) \
pci_unmap_single(alpha_gendev_to_pci(dev), addr, size, dir)
#define dma_alloc_coherent(dev, size, addr, gfp) \
__pci_alloc_consistent(alpha_gendev_to_pci(dev), size, addr, gfp)
#define dma_free_coherent(dev, size, va, addr) \
pci_free_consistent(alpha_gendev_to_pci(dev), size, va, addr)
#define dma_map_page(dev, page, off, size, dir) \
pci_map_page(alpha_gendev_to_pci(dev), page, off, size, dir)
#define dma_unmap_page(dev, addr, size, dir) \
pci_unmap_page(alpha_gendev_to_pci(dev), addr, size, dir)
#define dma_map_sg(dev, sg, nents, dir) \
pci_map_sg(alpha_gendev_to_pci(dev), sg, nents, dir)
#define dma_unmap_sg(dev, sg, nents, dir) \
pci_unmap_sg(alpha_gendev_to_pci(dev), sg, nents, dir)
#define dma_supported(dev, mask) \
pci_dma_supported(alpha_gendev_to_pci(dev), mask)
#define dma_mapping_error(dev, addr) \
pci_dma_mapping_error(alpha_gendev_to_pci(dev), addr)
#include <asm-generic/dma-mapping-common.h>
#else /* no PCI - no IOMMU. */
static inline void *dma_alloc_coherent(struct device *dev, size_t size,
dma_addr_t *dma_handle, gfp_t gfp)
{
return get_dma_ops(dev)->alloc_coherent(dev, size, dma_handle, gfp);
}
#include <asm/io.h> /* for virt_to_phys() */
static inline void dma_free_coherent(struct device *dev, size_t size,
void *vaddr, dma_addr_t dma_handle)
{
get_dma_ops(dev)->free_coherent(dev, size, vaddr, dma_handle);
}
struct scatterlist;
void *dma_alloc_coherent(struct device *dev, size_t size,
dma_addr_t *dma_handle, gfp_t gfp);
int dma_map_sg(struct device *dev, struct scatterlist *sg, int nents,
enum dma_data_direction direction);
static inline int dma_mapping_error(struct device *dev, dma_addr_t dma_addr)
{
return get_dma_ops(dev)->mapping_error(dev, dma_addr);
}
#define dma_free_coherent(dev, size, va, addr) \
free_pages((unsigned long)va, get_order(size))
#define dma_supported(dev, mask) (mask < 0x00ffffffUL ? 0 : 1)
#define dma_map_single(dev, va, size, dir) virt_to_phys(va)
#define dma_map_page(dev, page, off, size, dir) (page_to_pa(page) + off)
static inline int dma_supported(struct device *dev, u64 mask)
{
return get_dma_ops(dev)->dma_supported(dev, mask);
}
#define dma_unmap_single(dev, addr, size, dir) ((void)0)
#define dma_unmap_page(dev, addr, size, dir) ((void)0)
#define dma_unmap_sg(dev, sg, nents, dir) ((void)0)
#define dma_mapping_error(dev, addr) (0)
#endif /* !CONFIG_PCI */
static inline int dma_set_mask(struct device *dev, u64 mask)
{
return get_dma_ops(dev)->set_dma_mask(dev, mask);
}
#define dma_alloc_noncoherent(d, s, h, f) dma_alloc_coherent(d, s, h, f)
#define dma_free_noncoherent(d, s, v, h) dma_free_coherent(d, s, v, h)
#define dma_is_consistent(d, h) (1)
int dma_set_mask(struct device *dev, u64 mask);
#define dma_sync_single_for_cpu(dev, addr, size, dir) ((void)0)
#define dma_sync_single_for_device(dev, addr, size, dir) ((void)0)
#define dma_sync_single_range(dev, addr, off, size, dir) ((void)0)
#define dma_sync_sg_for_cpu(dev, sg, nents, dir) ((void)0)
#define dma_sync_sg_for_device(dev, sg, nents, dir) ((void)0)
#define dma_cache_sync(dev, va, size, dir) ((void)0)
#define dma_sync_single_range_for_cpu(dev, addr, offset, size, dir) ((void)0)
#define dma_sync_single_range_for_device(dev, addr, offset, size, dir) ((void)0)
#define dma_get_cache_alignment() L1_CACHE_BYTES
#endif /* _ALPHA_DMA_MAPPING_H */
arch/alpha/include/asm/pci.h
浏览文件 @ 74511020
......@@ -70,142 +70,11 @@ extern inline void pcibios_penalize_isa_irq(int irq, int active)
decisions. */
#define PCI_DMA_BUS_IS_PHYS 0
/* Allocate and map kernel buffer using consistent mode DMA for PCI
device. Returns non-NULL cpu-view pointer to the buffer if
successful and sets *DMA_ADDRP to the pci side dma address as well,
else DMA_ADDRP is undefined. */
extern void *__pci_alloc_consistent(struct pci_dev *, size_t,
dma_addr_t *, gfp_t);
static inline void *
pci_alloc_consistent(struct pci_dev *dev, size_t size, dma_addr_t *dma)
{
return __pci_alloc_consistent(dev, size, dma, GFP_ATOMIC);
}
/* Free and unmap a consistent DMA buffer. CPU_ADDR and DMA_ADDR must
be values that were returned from pci_alloc_consistent. SIZE must
be the same as what as passed into pci_alloc_consistent.
References to the memory and mappings associated with CPU_ADDR or
DMA_ADDR past this call are illegal. */
extern void pci_free_consistent(struct pci_dev *, size_t, void *, dma_addr_t);
/* Map a single buffer of the indicate size for PCI DMA in streaming mode.
The 32-bit PCI bus mastering address to use is returned. Once the device
is given the dma address, the device owns this memory until either
pci_unmap_single or pci_dma_sync_single_for_cpu is performed. */
extern dma_addr_t pci_map_single(struct pci_dev *, void *, size_t, int);
/* Likewise, but for a page instead of an address. */
extern dma_addr_t pci_map_page(struct pci_dev *, struct page *,
unsigned long, size_t, int);
/* Test for pci_map_single or pci_map_page having generated an error. */
static inline int
pci_dma_mapping_error(struct pci_dev *pdev, dma_addr_t dma_addr)
{
return dma_addr == 0;
}
/* Unmap a single streaming mode DMA translation. The DMA_ADDR and
SIZE must match what was provided for in a previous pci_map_single
call. All other usages are undefined. After this call, reads by
the cpu to the buffer are guaranteed to see whatever the device
wrote there. */
extern void pci_unmap_single(struct pci_dev *, dma_addr_t, size_t, int);
extern void pci_unmap_page(struct pci_dev *, dma_addr_t, size_t, int);
/* pci_unmap_{single,page} is not a nop, thus... */
#define DECLARE_PCI_UNMAP_ADDR(ADDR_NAME) \
dma_addr_t ADDR_NAME;
#define DECLARE_PCI_UNMAP_LEN(LEN_NAME) \
__u32 LEN_NAME;
#define pci_unmap_addr(PTR, ADDR_NAME) \
((PTR)->ADDR_NAME)
#define pci_unmap_addr_set(PTR, ADDR_NAME, VAL) \
(((PTR)->ADDR_NAME) = (VAL))
#define pci_unmap_len(PTR, LEN_NAME) \
((PTR)->LEN_NAME)
#define pci_unmap_len_set(PTR, LEN_NAME, VAL) \
(((PTR)->LEN_NAME) = (VAL))
/* Map a set of buffers described by scatterlist in streaming mode for
PCI DMA. This is the scatter-gather version of the above
pci_map_single interface. Here the scatter gather list elements
are each tagged with the appropriate PCI dma address and length.
They are obtained via sg_dma_{address,length}(SG).
NOTE: An implementation may be able to use a smaller number of DMA
address/length pairs than there are SG table elements. (for
example via virtual mapping capabilities) The routine returns the
number of addr/length pairs actually used, at most nents.
Device ownership issues as mentioned above for pci_map_single are
the same here. */
extern int pci_map_sg(struct pci_dev *, struct scatterlist *, int, int);
/* Unmap a set of streaming mode DMA translations. Again, cpu read
rules concerning calls here are the same as for pci_unmap_single()
above. */
extern void pci_unmap_sg(struct pci_dev *, struct scatterlist *, int, int);
/* Make physical memory consistent for a single streaming mode DMA
translation after a transfer and device currently has ownership
of the buffer.
If you perform a pci_map_single() but wish to interrogate the
buffer using the cpu, yet do not wish to teardown the PCI dma
mapping, you must call this function before doing so. At the next
point you give the PCI dma address back to the card, you must first
perform a pci_dma_sync_for_device, and then the device again owns
the buffer. */
static inline void
pci_dma_sync_single_for_cpu(struct pci_dev *dev, dma_addr_t dma_addr,
long size, int direction)
{
/* Nothing to do. */
}
static inline void
pci_dma_sync_single_for_device(struct pci_dev *dev, dma_addr_t dma_addr,
size_t size, int direction)
{
/* Nothing to do. */
}
/* Make physical memory consistent for a set of streaming mode DMA
translations after a transfer. The same as pci_dma_sync_single_*
but for a scatter-gather list, same rules and usage. */
static inline void
pci_dma_sync_sg_for_cpu(struct pci_dev *dev, struct scatterlist *sg,
int nents, int direction)
{
/* Nothing to do. */
}
static inline void
pci_dma_sync_sg_for_device(struct pci_dev *dev, struct scatterlist *sg,
int nents, int direction)
{
/* Nothing to do. */
}
/* Return whether the given PCI device DMA address mask can
be supported properly. For example, if your device can
only drive the low 24-bits during PCI bus mastering, then
you would pass 0x00ffffff as the mask to this function. */
#ifdef CONFIG_PCI
extern int pci_dma_supported(struct pci_dev *hwdev, u64 mask);
/* implement the pci_ DMA API in terms of the generic device dma_ one */
#include <asm-generic/pci-dma-compat.h>
#ifdef CONFIG_PCI
static inline void pci_dma_burst_advice(struct pci_dev *pdev,
enum pci_dma_burst_strategy *strat,
unsigned long *strategy_parameter)
......@@ -244,8 +113,6 @@ static inline int pci_proc_domain(struct pci_bus *bus)
return hose->need_domain_info;
}
struct pci_dev *alpha_gendev_to_pci(struct device *dev);
#endif /* __KERNEL__ */
/* Values for the `which' argument to sys_pciconfig_iobase. */
......
arch/alpha/include/asm/ptrace.h
浏览文件 @ 74511020
......@@ -68,6 +68,7 @@ struct switch_stack {
#ifdef __KERNEL__
#define arch_has_single_step() (1)
#define user_mode(regs) (((regs)->ps & 8) != 0)
#define instruction_pointer(regs) ((regs)->pc)
#define profile_pc(regs) instruction_pointer(regs)
......
arch/alpha/kernel/pci-noop.c
浏览文件 @ 74511020
......@@ -106,58 +106,8 @@ sys_pciconfig_write(unsigned long bus, unsigned long dfn,
return -ENODEV;
}
/* Stubs for the routines in pci_iommu.c: */
void *
__pci_alloc_consistent(struct pci_dev *pdev, size_t size,
dma_addr_t *dma_addrp, gfp_t gfp)
{
return NULL;
}
void
pci_free_consistent(struct pci_dev *pdev, size_t size, void *cpu_addr,
dma_addr_t dma_addr)
{
}
dma_addr_t
pci_map_single(struct pci_dev *pdev, void *cpu_addr, size_t size,
int direction)
{
return (dma_addr_t) 0;
}
void
pci_unmap_single(struct pci_dev *pdev, dma_addr_t dma_addr, size_t size,
int direction)
{
}
int
pci_map_sg(struct pci_dev *pdev, struct scatterlist *sg, int nents,
int direction)
{
return 0;
}
void
pci_unmap_sg(struct pci_dev *pdev, struct scatterlist *sg, int nents,
int direction)
{
}
int
pci_dma_supported(struct pci_dev *hwdev, dma_addr_t mask)
{
return 0;
}
/* Generic DMA mapping functions: */
void *
dma_alloc_coherent(struct device *dev, size_t size,
dma_addr_t *dma_handle, gfp_t gfp)
static void *alpha_noop_alloc_coherent(struct device *dev, size_t size,
dma_addr_t *dma_handle, gfp_t gfp)
{
void *ret;
......@@ -171,11 +121,22 @@ dma_alloc_coherent(struct device *dev, size_t size,
return ret;
}
EXPORT_SYMBOL(dma_alloc_coherent);
static void alpha_noop_free_coherent(struct device *dev, size_t size,
void *cpu_addr, dma_addr_t dma_addr)
{
free_pages((unsigned long)cpu_addr, get_order(size));
}
static dma_addr_t alpha_noop_map_page(struct device *dev, struct page *page,
unsigned long offset, size_t size,
enum dma_data_direction dir,
struct dma_attrs *attrs)
{
return page_to_pa(page) + offset;
}
int
dma_map_sg(struct device *dev, struct scatterlist *sgl, int nents,
enum dma_data_direction direction)
static int alpha_noop_map_sg(struct device *dev, struct scatterlist *sgl, int nents,
enum dma_data_direction dir, struct dma_attrs *attrs)
{
int i;
struct scatterlist *sg;
......@@ -192,19 +153,37 @@ dma_map_sg(struct device *dev, struct scatterlist *sgl, int nents,
return nents;
}
EXPORT_SYMBOL(dma_map_sg);
static int alpha_noop_mapping_error(struct device *dev, dma_addr_t dma_addr)
{
return 0;
}
static int alpha_noop_supported(struct device *dev, u64 mask)
{
return mask < 0x00ffffffUL ? 0 : 1;
}
int
dma_set_mask(struct device *dev, u64 mask)
static int alpha_noop_set_mask(struct device *dev, u64 mask)
{
if (!dev->dma_mask || !dma_supported(dev, mask))
return -EIO;
*dev->dma_mask = mask;
return 0;
}
EXPORT_SYMBOL(dma_set_mask);
struct dma_map_ops alpha_noop_ops = {
.alloc_coherent = alpha_noop_alloc_coherent,
.free_coherent = alpha_noop_free_coherent,
.map_page = alpha_noop_map_page,
.map_sg = alpha_noop_map_sg,
.mapping_error = alpha_noop_mapping_error,
.dma_supported = alpha_noop_supported,
.set_dma_mask = alpha_noop_set_mask,
};
struct dma_map_ops *dma_ops = &alpha_noop_ops;
EXPORT_SYMBOL(dma_ops);
void __iomem *pci_iomap(struct pci_dev *dev, int bar, unsigned long maxlen)
{
......
arch/alpha/kernel/pci_iommu.c
浏览文件 @ 74511020
......@@ -216,10 +216,30 @@ iommu_arena_free(struct pci_iommu_arena *arena, long ofs, long n)
for (i = 0; i < n; ++i)
p[i] = 0;
}
/* True if the machine supports DAC addressing, and DEV can
make use of it given MASK. */
static int pci_dac_dma_supported(struct pci_dev *hwdev, u64 mask);
/*
* True if the machine supports DAC addressing, and DEV can
* make use of it given MASK.
*/
static int pci_dac_dma_supported(struct pci_dev *dev, u64 mask)
{
dma64_addr_t dac_offset = alpha_mv.pci_dac_offset;
int ok = 1;
/* If this is not set, the machine doesn't support DAC at all. */
if (dac_offset == 0)
ok = 0;
/* The device has to be able to address our DAC bit. */
if ((dac_offset & dev->dma_mask) != dac_offset)
ok = 0;
/* If both conditions above are met, we are fine. */
DBGA("pci_dac_dma_supported %s from %p\n",
ok ? "yes" : "no", __builtin_return_address(0));
return ok;
}
/* Map a single buffer of the indicated size for PCI DMA in streaming
mode. The 32-bit PCI bus mastering address to use is returned.
......@@ -301,23 +321,36 @@ pci_map_single_1(struct pci_dev *pdev, void *cpu_addr, size_t size,
return ret;
}
dma_addr_t
pci_map_single(struct pci_dev *pdev, void *cpu_addr, size_t size, int dir)
/* Helper for generic DMA-mapping functions. */
static struct pci_dev *alpha_gendev_to_pci(struct device *dev)
{
int dac_allowed;
if (dev && dev->bus == &pci_bus_type)
return to_pci_dev(dev);
if (dir == PCI_DMA_NONE)
BUG();
/* Assume that non-PCI devices asking for DMA are either ISA or EISA,
BUG() otherwise. */
BUG_ON(!isa_bridge);
dac_allowed = pdev ? pci_dac_dma_supported(pdev, pdev->dma_mask) : 0;
return pci_map_single_1(pdev, cpu_addr, size, dac_allowed);
/* Assume non-busmaster ISA DMA when dma_mask is not set (the ISA
bridge is bus master then). */
if (!dev || !dev->dma_mask || !*dev->dma_mask)
return isa_bridge;
/* For EISA bus masters, return isa_bridge (it might have smaller
dma_mask due to wiring limitations). */
if (*dev->dma_mask >= isa_bridge->dma_mask)
return isa_bridge;
/* This assumes ISA bus master with dma_mask 0xffffff. */
return NULL;
}
EXPORT_SYMBOL(pci_map_single);
dma_addr_t
pci_map_page(struct pci_dev *pdev, struct page *page, unsigned long offset,
size_t size, int dir)
static dma_addr_t alpha_pci_map_page(struct device *dev, struct page *page,
unsigned long offset, size_t size,
enum dma_data_direction dir,
struct dma_attrs *attrs)
{
struct pci_dev *pdev = alpha_gendev_to_pci(dev);
int dac_allowed;
if (dir == PCI_DMA_NONE)
......@@ -327,7 +360,6 @@ pci_map_page(struct pci_dev *pdev, struct page *page, unsigned long offset,
return pci_map_single_1(pdev, (char *)page_address(page) + offset,
size, dac_allowed);
}
EXPORT_SYMBOL(pci_map_page);
/* Unmap a single streaming mode DMA translation. The DMA_ADDR and
SIZE must match what was provided for in a previous pci_map_single
......@@ -335,16 +367,17 @@ EXPORT_SYMBOL(pci_map_page);
the cpu to the buffer are guaranteed to see whatever the device
wrote there. */
void
pci_unmap_single(struct pci_dev *pdev, dma_addr_t dma_addr, size_t size,
int direction)
static void alpha_pci_unmap_page(struct device *dev, dma_addr_t dma_addr,
size_t size, enum dma_data_direction dir,
struct dma_attrs *attrs)
{
unsigned long flags;
struct pci_dev *pdev = alpha_gendev_to_pci(dev);
struct pci_controller *hose = pdev ? pdev->sysdata : pci_isa_hose;
struct pci_iommu_arena *arena;
long dma_ofs, npages;
if (direction == PCI_DMA_NONE)
if (dir == PCI_DMA_NONE)
BUG();
if (dma_addr >= __direct_map_base
......@@ -393,25 +426,16 @@ pci_unmap_single(struct pci_dev *pdev, dma_addr_t dma_addr, size_t size,
DBGA2("pci_unmap_single: sg [%llx,%zx] np %ld from %p\n",
dma_addr, size, npages, __builtin_return_address(0));
}
EXPORT_SYMBOL(pci_unmap_single);
void
pci_unmap_page(struct pci_dev *pdev, dma_addr_t dma_addr,
size_t size, int direction)
{
pci_unmap_single(pdev, dma_addr, size, direction);
}
EXPORT_SYMBOL(pci_unmap_page);
/* Allocate and map kernel buffer using consistent mode DMA for PCI
device. Returns non-NULL cpu-view pointer to the buffer if
successful and sets *DMA_ADDRP to the pci side dma address as well,
else DMA_ADDRP is undefined. */
void *
__pci_alloc_consistent(struct pci_dev *pdev, size_t size,
dma_addr_t *dma_addrp, gfp_t gfp)
static void *alpha_pci_alloc_coherent(struct device *dev, size_t size,
dma_addr_t *dma_addrp, gfp_t gfp)
{
struct pci_dev *pdev = alpha_gendev_to_pci(dev);
void *cpu_addr;
long order = get_order(size);
......@@ -439,13 +463,12 @@ __pci_alloc_consistent(struct pci_dev *pdev, size_t size,
gfp |= GFP_DMA;
goto try_again;
}
DBGA2("pci_alloc_consistent: %zx -> [%p,%llx] from %p\n",
size, cpu_addr, *dma_addrp, __builtin_return_address(0));
return cpu_addr;
}
EXPORT_SYMBOL(__pci_alloc_consistent);
/* Free and unmap a consistent DMA buffer. CPU_ADDR and DMA_ADDR must
be values that were returned from pci_alloc_consistent. SIZE must
......@@ -453,17 +476,16 @@ EXPORT_SYMBOL(__pci_alloc_consistent);
References to the memory and mappings associated with CPU_ADDR or
DMA_ADDR past this call are illegal. */
void
pci_free_consistent(struct pci_dev *pdev, size_t size, void *cpu_addr,
dma_addr_t dma_addr)
static void alpha_pci_free_coherent(struct device *dev, size_t size,
void *cpu_addr, dma_addr_t dma_addr)
{
struct pci_dev *pdev = alpha_gendev_to_pci(dev);
pci_unmap_single(pdev, dma_addr, size, PCI_DMA_BIDIRECTIONAL);
free_pages((unsigned long)cpu_addr, get_order(size));
DBGA2("pci_free_consistent: [%llx,%zx] from %p\n",
dma_addr, size, __builtin_return_address(0));
}
EXPORT_SYMBOL(pci_free_consistent);
/* Classify the elements of the scatterlist. Write dma_address
of each element with:
......@@ -626,23 +648,21 @@ sg_fill(struct device *dev, struct scatterlist *leader, struct scatterlist *end,
return 1;
}
int
pci_map_sg(struct pci_dev *pdev, struct scatterlist *sg, int nents,
int direction)
static int alpha_pci_map_sg(struct device *dev, struct scatterlist *sg,
int nents, enum dma_data_direction dir,
struct dma_attrs *attrs)
{
struct pci_dev *pdev = alpha_gendev_to_pci(dev);
struct scatterlist *start, *end, *out;
struct pci_controller *hose;
struct pci_iommu_arena *arena;
dma_addr_t max_dma;
int dac_allowed;
struct device *dev;
if (direction == PCI_DMA_NONE)
if (dir == PCI_DMA_NONE)
BUG();
dac_allowed = pdev ? pci_dac_dma_supported(pdev, pdev->dma_mask) : 0;
dev = pdev ? &pdev->dev : NULL;
dac_allowed = dev ? pci_dac_dma_supported(pdev, pdev->dma_mask) : 0;
/* Fast path single entry scatterlists. */
if (nents == 1) {
......@@ -699,19 +719,19 @@ pci_map_sg(struct pci_dev *pdev, struct scatterlist *sg, int nents,
/* Some allocation failed while mapping the scatterlist
entries. Unmap them now. */
if (out > start)
pci_unmap_sg(pdev, start, out - start, direction);
pci_unmap_sg(pdev, start, out - start, dir);
return 0;
}
EXPORT_SYMBOL(pci_map_sg);
/* Unmap a set of streaming mode DMA translations. Again, cpu read
rules concerning calls here are the same as for pci_unmap_single()
above. */
void
pci_unmap_sg(struct pci_dev *pdev, struct scatterlist *sg, int nents,
int direction)
static void alpha_pci_unmap_sg(struct device *dev, struct scatterlist *sg,
int nents, enum dma_data_direction dir,
struct dma_attrs *attrs)
{
struct pci_dev *pdev = alpha_gendev_to_pci(dev);
unsigned long flags;
struct pci_controller *hose;
struct pci_iommu_arena *arena;
......@@ -719,7 +739,7 @@ pci_unmap_sg(struct pci_dev *pdev, struct scatterlist *sg, int nents,
dma_addr_t max_dma;
dma_addr_t fbeg, fend;
if (direction == PCI_DMA_NONE)
if (dir == PCI_DMA_NONE)
BUG();
if (! alpha_mv.mv_pci_tbi)
......@@ -783,15 +803,13 @@ pci_unmap_sg(struct pci_dev *pdev, struct scatterlist *sg, int nents,
DBGA("pci_unmap_sg: %ld entries\n", nents - (end - sg));
}
EXPORT_SYMBOL(pci_unmap_sg);
/* Return whether the given PCI device DMA address mask can be
supported properly. */
int
pci_dma_supported(struct pci_dev *pdev, u64 mask)
static int alpha_pci_supported(struct device *dev, u64 mask)
{
struct pci_dev *pdev = alpha_gendev_to_pci(dev);
struct pci_controller *hose;
struct pci_iommu_arena *arena;
......@@ -818,7 +836,6 @@ pci_dma_supported(struct pci_dev *pdev, u64 mask)
return 0;
}
EXPORT_SYMBOL(pci_dma_supported);
/*
......@@ -918,66 +935,32 @@ iommu_unbind(struct pci_iommu_arena *arena, long pg_start, long pg_count)
return 0;
}
/* True if the machine supports DAC addressing, and DEV can
make use of it given MASK. */
static int
pci_dac_dma_supported(struct pci_dev *dev, u64 mask)
{
dma64_addr_t dac_offset = alpha_mv.pci_dac_offset;
int ok = 1;
/* If this is not set, the machine doesn't support DAC at all. */
if (dac_offset == 0)
ok = 0;
/* The device has to be able to address our DAC bit. */
if ((dac_offset & dev->dma_mask) != dac_offset)
ok = 0;
/* If both conditions above are met, we are fine. */
DBGA("pci_dac_dma_supported %s from %p\n",
ok ? "yes" : "no", __builtin_return_address(0));
return ok;
}
/* Helper for generic DMA-mapping functions. */
struct pci_dev *
alpha_gendev_to_pci(struct device *dev)
static int alpha_pci_mapping_error(struct device *dev, dma_addr_t dma_addr)
{
if (dev && dev->bus == &pci_bus_type)
return to_pci_dev(dev);
/* Assume that non-PCI devices asking for DMA are either ISA or EISA,
BUG() otherwise. */
BUG_ON(!isa_bridge);
/* Assume non-busmaster ISA DMA when dma_mask is not set (the ISA
bridge is bus master then). */
if (!dev || !dev->dma_mask || !*dev->dma_mask)
return isa_bridge;
/* For EISA bus masters, return isa_bridge (it might have smaller
dma_mask due to wiring limitations). */
if (*dev->dma_mask >= isa_bridge->dma_mask)
return isa_bridge;
/* This assumes ISA bus master with dma_mask 0xffffff. */
return NULL;
return dma_addr == 0;
}
EXPORT_SYMBOL(alpha_gendev_to_pci);
int
dma_set_mask(struct device *dev, u64 mask)
static int alpha_pci_set_mask(struct device *dev, u64 mask)
{
if (!dev->dma_mask ||
!pci_dma_supported(alpha_gendev_to_pci(dev), mask))
return -EIO;
*dev->dma_mask = mask;
return 0;
}
EXPORT_SYMBOL(dma_set_mask);
struct dma_map_ops alpha_pci_ops = {
.alloc_coherent = alpha_pci_alloc_coherent,
.free_coherent = alpha_pci_free_coherent,
.map_page = alpha_pci_map_page,
.unmap_page = alpha_pci_unmap_page,
.map_sg = alpha_pci_map_sg,
.unmap_sg = alpha_pci_unmap_sg,
.mapping_error = alpha_pci_mapping_error,
.dma_supported = alpha_pci_supported,
.set_dma_mask = alpha_pci_set_mask,
};
struct dma_map_ops *dma_ops = &alpha_pci_ops;
EXPORT_SYMBOL(dma_ops);
arch/alpha/kernel/ptrace.c
浏览文件 @ 74511020
此差异已折叠。
arch/alpha/kernel/sys_dp264.c
浏览文件 @ 74511020
此差异已折叠。
arch/alpha/kernel/sys_titan.c
浏览文件 @ 74511020
此差异已折叠。
arch/alpha/kernel/traps.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/Kconfig.debug
浏览文件 @ 74511020
此差异已折叠。
arch/arm/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/arm/boot/bootp/init.S
浏览文件 @ 74511020
此差异已折叠。
arch/arm/boot/compressed/decompress.c
浏览文件 @ 74511020
......@@ -11,6 +11,7 @@ extern unsigned long free_mem_end_ptr;
extern void error(char *);
#define STATIC static
#define STATIC_RW_DATA /* non-static please */
#define ARCH_HAS_DECOMP_WDOG
......
arch/arm/boot/compressed/head.S
浏览文件 @ 74511020
此差异已折叠。
arch/arm/boot/compressed/misc.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/common/clkdev.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/common/it8152.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/common/locomo.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/common/sa1111.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/common/scoop.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/ap4evb_defconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/cm_t35_defconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/g3evm_defconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/g4evm_defconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/imote2_defconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/kirkwood_defconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/mini2440_defconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/mmp2_defconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/mv78xx0_defconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/mx1ads_defconfig 已删除 100644 → 0
浏览文件 @ 69266866
此差异已折叠。
arch/arm/configs/mx27_defconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/mx51_defconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/n770_defconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/n8x0_defconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/nuc950_defconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/omap3_defconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/orion5x_defconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/pxa168_defconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/raumfeld_defconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/rx51_defconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/s3c2410_defconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/s3c6400_defconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/s5p6440_defconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/s5p6442_defconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/s5pc110_defconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/configs/s5pv210_defconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/include/asm/dma-mapping.h
浏览文件 @ 74511020
此差异已折叠。
arch/arm/include/asm/elf.h
浏览文件 @ 74511020
此差异已折叠。
arch/arm/include/asm/pci.h
浏览文件 @ 74511020
此差异已折叠。
arch/arm/include/asm/ptrace.h
浏览文件 @ 74511020
此差异已折叠。
arch/arm/include/asm/unistd.h
浏览文件 @ 74511020
此差异已折叠。
arch/arm/kernel/calls.S
浏览文件 @ 74511020
此差异已折叠。
arch/arm/kernel/entry-header.S
浏览文件 @ 74511020
此差异已折叠。
arch/arm/kernel/kgdb.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/kernel/perf_event.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/kernel/ptrace.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/kernel/ptrace.h
浏览文件 @ 74511020
此差异已折叠。
arch/arm/kernel/smp.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/kernel/sys_arm.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/kernel/sys_oabi-compat.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/kernel/unwind.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-dove/common.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-ep93xx/micro9.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-ixp4xx/common-pci.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-kirkwood/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-kirkwood/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-kirkwood/common.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mmp/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mmp/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mmp/avengers_lite.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mmp/common.h
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mmp/flint.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mmp/include/mach/mfp-mmp2.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mmp/include/mach/mmp2.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mmp/irq-mmp2.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mmp/jasper.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mmp/mmp2.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mmp/time.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mv78xx0/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mv78xx0/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mv78xx0/buffalo-wxl-setup.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mv78xx0/mpp.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mv78xx0/mpp.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx1/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx2/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx2/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx2/clock_imx21.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx2/clock_imx27.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx2/cpu_imx27.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx2/crm_regs.h 已删除 100644 → 0
浏览文件 @ 69266866
此差异已折叠。
arch/arm/mach-mx2/devices.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx2/devices.h
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx2/mm-imx21.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx2/serial.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx25/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx25/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx25/clock.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx25/devices.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx25/devices.h
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx3/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx3/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx3/clock-imx35.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx3/cpu.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx3/crm_regs.h
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx3/mx31lite-db.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx3/mx31moboard-smartbot.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx5/Kconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx5/Makefile 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx5/Makefile.boot 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx5/board-mx51_babbage.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx5/clock-mx51.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx5/cpu.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx5/crm_regs.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx5/devices.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx5/devices.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mx5/mm.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-mxc91231/magx-zn5.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-omap2/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-omap2/board-3430sdp.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-omap2/board-3630sdp.c 100755 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-omap2/board-4430sdp.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-omap2/board-cm-t35.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-omap2/board-n8x0.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-omap2/board-overo.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-omap2/board-zoom-peripherals.c 100755 → 100644
浏览文件 @ 74511020
文件模式从 100755 更改为 100644
arch/arm/mach-omap2/board-zoom3.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-omap2/io.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-omap2/mailbox.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-omap2/omap44xx-smc.S 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-omap2/prcm.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-omap2/serial.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-omap2/usb-ehci.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-orion5x/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-orion5x/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-orion5x/common.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-orion5x/d2net-setup.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-orion5x/ls_hgl-setup.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/am300epd.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/balloon3.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/capc7117.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/cm-x255.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/cm-x270.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/cm-x2xx-pci.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/e740.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/e750.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/e800.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/em-x270.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/icontrol.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/idp.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/imote2.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/include/mach/mxm8x10.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/lpd270.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/lubbock.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/magician.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/mainstone.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/mioa701.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/mxm8x10.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/palmld.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/palmt5.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/palmtc.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/palmte2.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/palmtreo.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/palmtx.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/palmz72.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/poodle.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/pxa27x.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/raumfeld.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/spitz.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/ssp.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/time.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/tosa.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/trizeps4.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/viper.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-pxa/zeus.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2410/dma.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2410/mach-bast.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2410/mach-h1940.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2410/mach-n30.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2410/mach-otom.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2410/mach-qt2410.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2410/mach-vr1000.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2410/usb-simtec.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2412/clock.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2412/dma.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2412/mach-jive.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2412/mach-vstms.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2440/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2440/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2440/clock.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2440/dma.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2440/dsc.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2440/mach-anubis.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2440/mach-rx3715.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2440/s3c2440.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2442/Kconfig 已删除 100644 → 0
浏览文件 @ 69266866
此差异已折叠。
arch/arm/mach-s3c2442/Makefile 已删除 100644 → 0
浏览文件 @ 69266866
此差异已折叠。
arch/arm/mach-s3c2443/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2443/clock.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c2443/dma.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c6400/Kconfig 已删除 100644 → 0
浏览文件 @ 69266866
此差异已折叠。
arch/arm/mach-s3c6400/Makefile 已删除 100644 → 0
浏览文件 @ 69266866
此差异已折叠。
arch/arm/mach-s3c6400/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ 69266866
此差异已折叠。
arch/arm/mach-s3c6400/include/mach/irqs.h 已删除 100644 → 0
浏览文件 @ 69266866
此差异已折叠。
arch/arm/mach-s3c6410/Makefile 已删除 100644 → 0
浏览文件 @ 69266866
此差异已折叠。
arch/arm/mach-s3c6410/setup-sdhci.c 已删除 100644 → 0
浏览文件 @ 69266866
此差异已折叠。
arch/arm/mach-s3c64xx/dev-adc.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c64xx/dev-rtc.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c64xx/dev-spi.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c64xx/include/mach/entry-macro.S 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c64xx/include/mach/io.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c64xx/include/mach/regs-srom.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c64xx/include/mach/spi-clocks.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c64xx/include/mach/timex.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c64xx/include/mach/vmalloc.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s3c64xx/irq.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/Kconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/Makefile 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/Makefile.boot 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/clock.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/cpu.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/gpio.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/include/mach/debug-macro.S 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/include/mach/gpio.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/include/mach/hardware.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/include/mach/io.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/include/mach/irqs.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/include/mach/map.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/include/mach/memory.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/include/mach/pwm-clock.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/include/mach/regs-clock.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/include/mach/regs-gpio.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/include/mach/regs-irq.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/include/mach/system.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/include/mach/tick.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/include/mach/timex.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/include/mach/uncompress.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/init.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6440/mach-smdk6440.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/Kconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/Makefile 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/Makefile.boot 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/clock.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/cpu.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/include/mach/debug-macro.S 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/include/mach/entry-macro.S 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/include/mach/gpio.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/include/mach/hardware.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/include/mach/io.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/include/mach/irqs.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/include/mach/map.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/include/mach/memory.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/include/mach/pwm-clock.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/include/mach/regs-clock.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/include/mach/regs-irq.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/include/mach/system.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/include/mach/tick.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/include/mach/timex.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/include/mach/uncompress.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/include/mach/vmalloc.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5p6442/mach-smdk6442.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pc100/include/mach/io.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pc100/include/mach/timex.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pc100/include/mach/vmalloc.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pc100/setup-sdhci.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/Kconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/Makefile 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/Makefile.boot 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/clock.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/cpu.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/include/mach/debug-macro.S 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/include/mach/entry-macro.S 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/include/mach/gpio.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/include/mach/hardware.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/include/mach/io.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/include/mach/irqs.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/include/mach/map.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/include/mach/memory.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/include/mach/pwm-clock.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/include/mach/regs-clock.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/include/mach/regs-irq.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/include/mach/system.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/include/mach/tick.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/include/mach/timex.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/include/mach/uncompress.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/mach-smdkc110.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-s5pv210/mach-smdkv210.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-sa1100/badge4.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-sa1100/collie.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-sa1100/jornada720.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-sa1100/neponset.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-sa1100/time.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/Kconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/Makefile 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/Makefile.boot 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/board-ap4evb.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/board-g3evm.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/board-g4evm.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/clock-sh7367.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/console.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/include/mach/clkdev.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/include/mach/common.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/include/mach/dma.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/include/mach/entry-macro.S 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/include/mach/gpio.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/include/mach/hardware.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/include/mach/io.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/include/mach/irqs.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/include/mach/memory.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/include/mach/sh7367.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/include/mach/sh7372.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/include/mach/sh7377.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/include/mach/system.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/include/mach/timex.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/include/mach/uncompress.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/include/mach/vmalloc.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/intc-sh7367.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/intc-sh7372.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/intc-sh7377.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/pfc-sh7367.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/pfc-sh7372.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/pfc-sh7377.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/setup-sh7367.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/setup-sh7372.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/setup-sh7377.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-shmobile/timer.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-u300/core.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-w90x900/cpu.h
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-w90x900/dev.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-w90x900/include/mach/fb.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-w90x900/include/mach/regs-ldm.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/mach-w90x900/nuc950.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-mxc/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-mxc/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-mxc/audmux-v1.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-mxc/audmux-v2.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-mxc/clock.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-mxc/dma-mx1-mx2.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-mxc/ehci.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-mxc/gpio.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-mxc/include/mach/iomux-mx51.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-mxc/include/mach/iomux-v1.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-mxc/include/mach/mtd-xip.h 已删除 100644 → 0
浏览文件 @ 69266866
此差异已折叠。
arch/arm/plat-mxc/include/mach/mx51.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-mxc/include/mach/ssi.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-mxc/iomux-mx1-mx2.c 已删除 100644 → 0
浏览文件 @ 69266866
此差异已折叠。
arch/arm/plat-mxc/iomux-v1.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-mxc/time.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-mxc/tzic.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-nomadik/timer.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-omap/gpio.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-omap/mcbsp.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s3c/Kconfig 已删除 100644 → 0
浏览文件 @ 69266866
此差异已折叠。
arch/arm/plat-s3c/Makefile 已删除 100644 → 0
浏览文件 @ 69266866
此差异已折叠。
arch/arm/plat-s3c24xx/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s3c24xx/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s3c24xx/clock-dclk.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s3c24xx/cpu.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s3c24xx/devs.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s3c24xx/dma.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s3c24xx/gpiolib.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s3c64xx/Kconfig 已删除 100644 → 0
浏览文件 @ 69266866
此差异已折叠。
arch/arm/plat-s3c64xx/clock.c 已删除 100644 → 0
浏览文件 @ 69266866
此差异已折叠。
arch/arm/plat-s5p/Kconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s5p/Makefile 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s5p/clock.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s5p/cpu.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s5p/dev-uart.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s5p/include/plat/irqs.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s5p/include/plat/map-s5p.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s5p/include/plat/pll.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s5p/include/plat/s5p-clock.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s5p/include/plat/s5p6440.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s5p/include/plat/s5p6442.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s5p/include/plat/s5pv210.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s5p/irq.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s5pc1xx/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s5pc1xx/clock.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s5pc1xx/dev-uart.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s5pc1xx/gpio-config.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s5pc1xx/gpiolib.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-s5pc1xx/irq.c
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-samsung/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-samsung/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-samsung/clock-clksrc.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-samsung/dev-uart.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-samsung/gpiolib.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-samsung/include/plat/clock-clksrc.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-samsung/include/plat/irq-uart.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-samsung/include/plat/s3c64xx-spi.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/arm/plat-samsung/irq-vic-timer.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/avr32/include/asm/ptrace.h
浏览文件 @ 74511020
此差异已折叠。
arch/avr32/kernel/ptrace.c
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/Kconfig.debug
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/boot/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/configs/BF527-EZKIT-V2_defconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/configs/TCM-BF518_defconfig 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/bfin_can.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/bfin_watchdog.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/bitops.h
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/context.S
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/cpu.h
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/delay.h
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/dma.h
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/dpmc.h
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/elf.h
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/ftrace.h
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/gpio.h
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/irq.h
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/nand.h
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/nmi.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/page.h
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/ptrace.h
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/smp.h
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/syscall.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/include/asm/time.h
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/kernel/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/kernel/bfin_dma_5xx.c
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/kernel/bfin_gpio.c
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/kernel/dma-mapping.c
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/kernel/entry.S
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/kernel/ftrace-entry.S
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/kernel/ftrace.c
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/kernel/init_task.c
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/kernel/kgdb.c
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/kernel/nmi.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/kernel/process.c
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/kernel/ptrace.c
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/kernel/setup.c
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/kernel/signal.c
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/kernel/time-ts.c
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/kernel/traps.c
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/kernel/vmlinux.lds.S
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/mach-bf518/boards/tcm-bf518.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/mach-bf561/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/mach-bf561/hotplug.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/mach-bf561/smp.c
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/mach-common/cpufreq.c
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/mach-common/entry.S
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/mach-common/head.S
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/mach-common/smp.c
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/mm/isram-driver.c
浏览文件 @ 74511020
此差异已折叠。
arch/blackfin/mm/sram-alloc.c
浏览文件 @ 74511020
此差异已折叠。
arch/cris/arch-v10/kernel/entry.S
浏览文件 @ 74511020
此差异已折叠。
arch/cris/arch-v10/kernel/ptrace.c
浏览文件 @ 74511020
此差异已折叠。
arch/cris/arch-v32/kernel/entry.S
浏览文件 @ 74511020
此差异已折叠。
arch/cris/arch-v32/kernel/ptrace.c
浏览文件 @ 74511020
此差异已折叠。
arch/cris/arch-v32/mm/tlb.c
浏览文件 @ 74511020
此差异已折叠。
arch/cris/include/asm/pci.h
浏览文件 @ 74511020
此差异已折叠。
arch/cris/include/asm/unistd.h
浏览文件 @ 74511020
此差异已折叠。
arch/cris/kernel/sys_cris.c
浏览文件 @ 74511020
此差异已折叠。
arch/frv/include/asm/dma-mapping.h
浏览文件 @ 74511020
此差异已折叠。
arch/frv/include/asm/pci.h
浏览文件 @ 74511020
此差异已折叠。
arch/frv/include/asm/ptrace.h
浏览文件 @ 74511020
此差异已折叠。
arch/frv/include/asm/unistd.h
浏览文件 @ 74511020
此差异已折叠。
arch/frv/kernel/sys_frv.c
浏览文件 @ 74511020
此差异已折叠。
arch/frv/mb93090-mb00/pci-dma.c
浏览文件 @ 74511020
此差异已折叠。
arch/h8300/include/asm/io.h
浏览文件 @ 74511020
此差异已折叠。
arch/h8300/include/asm/ptrace.h
浏览文件 @ 74511020
此差异已折叠。
arch/h8300/include/asm/unistd.h
浏览文件 @ 74511020
此差异已折叠。
arch/h8300/kernel/ptrace.c
浏览文件 @ 74511020
此差异已折叠。
arch/h8300/kernel/sys_h8300.c
浏览文件 @ 74511020
此差异已折叠。
arch/h8300/kernel/syscalls.S
浏览文件 @ 74511020
此差异已折叠。
arch/ia64/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/ia64/include/asm/compat.h
浏览文件 @ 74511020
此差异已折叠。
arch/ia64/include/asm/pci.h
浏览文件 @ 74511020
此差异已折叠。
arch/ia64/include/asm/ptrace.h
浏览文件 @ 74511020
此差异已折叠。
arch/ia64/kernel/acpi.c
浏览文件 @ 74511020
此差异已折叠。
arch/ia64/sn/kernel/setup.c
浏览文件 @ 74511020
此差异已折叠。
arch/m32r/include/asm/ptrace.h
浏览文件 @ 74511020
此差异已折叠。
arch/m32r/include/asm/unistd.h
浏览文件 @ 74511020
此差异已折叠。
arch/m32r/kernel/ptrace.c
浏览文件 @ 74511020
此差异已折叠。
arch/m32r/kernel/sys_m32r.c
浏览文件 @ 74511020
此差异已折叠。
arch/m68k/atari/atakeyb.c
浏览文件 @ 74511020
此差异已折叠。
arch/m68k/include/asm/fbio.h
浏览文件 @ 74511020
此差异已折叠。
arch/m68k/include/asm/io_no.h
浏览文件 @ 74511020
此差异已折叠。
arch/m68k/include/asm/ptrace.h
浏览文件 @ 74511020
此差异已折叠。
arch/m68k/include/asm/unistd.h
浏览文件 @ 74511020
此差异已折叠。
arch/m68k/kernel/entry.S
浏览文件 @ 74511020
此差异已折叠。
arch/m68k/kernel/sys_m68k.c
浏览文件 @ 74511020
此差异已折叠。
arch/m68knommu/kernel/ptrace.c
浏览文件 @ 74511020
此差异已折叠。
arch/m68knommu/kernel/sys_m68k.c
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/include/asm/io.h
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/include/asm/irq.h
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/include/asm/page.h
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/include/asm/pci.h
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/include/asm/prom.h
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/kernel/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/kernel/cpu/cache.c
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/kernel/dma.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/kernel/entry.S
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/kernel/head.S
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/kernel/irq.c
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/kernel/ptrace.c
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/kernel/setup.c
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/mm/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/mm/consistent.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/mm/init.c
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/mm/pgtable.c
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/pci/Makefile 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/pci/indirect_pci.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/pci/iomap.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/pci/pci-common.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/pci/pci_32.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/microblaze/pci/xilinx_pci.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/mips/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/mips/include/asm/compat.h
浏览文件 @ 74511020
此差异已折叠。
arch/mips/include/asm/pci.h
浏览文件 @ 74511020
此差异已折叠。
arch/mips/include/asm/unistd.h
浏览文件 @ 74511020
此差异已折叠。
arch/mips/kernel/linux32.c
浏览文件 @ 74511020
此差异已折叠。
arch/mips/kernel/ptrace.c
浏览文件 @ 74511020
此差异已折叠。
arch/mips/kernel/scall64-n32.S
浏览文件 @ 74511020
此差异已折叠。
arch/mips/kernel/scall64-o32.S
浏览文件 @ 74511020
此差异已折叠。
arch/mips/kernel/syscall.c
浏览文件 @ 74511020
此差异已折叠。
arch/mips/txx9/generic/setup.c
浏览文件 @ 74511020
此差异已折叠。
arch/mn10300/include/asm/ptrace.h
浏览文件 @ 74511020
此差异已折叠。
arch/mn10300/include/asm/unistd.h
浏览文件 @ 74511020
此差异已折叠。
arch/mn10300/kernel/entry.S
浏览文件 @ 74511020
此差异已折叠。
arch/mn10300/kernel/sys_mn10300.c
浏览文件 @ 74511020
此差异已折叠。
arch/parisc/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/parisc/include/asm/compat.h
浏览文件 @ 74511020
此差异已折叠。
arch/parisc/include/asm/pci.h
浏览文件 @ 74511020
此差异已折叠。
arch/parisc/include/asm/ptrace.h
浏览文件 @ 74511020
此差异已折叠。
arch/parisc/kernel/sys_parisc.c
浏览文件 @ 74511020
此差异已折叠。
arch/parisc/kernel/syscall_table.S
浏览文件 @ 74511020
此差异已折叠。
arch/powerpc/Kconfig
浏览文件 @ 74511020
此差异已折叠。
arch/powerpc/boot/dts/gef_ppc9a.dts
浏览文件 @ 74511020
此差异已折叠。
arch/powerpc/boot/dts/kmeter1.dts
浏览文件 @ 74511020
此差异已折叠。
arch/powerpc/include/asm/compat.h
浏览文件 @ 74511020
此差异已折叠。
arch/powerpc/include/asm/paca.h
浏览文件 @ 74511020
此差异已折叠。
arch/powerpc/include/asm/pci.h
浏览文件 @ 74511020
此差异已折叠。
arch/powerpc/include/asm/perf_event_fsl_emb.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/powerpc/include/asm/perf_event_server.h 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/powerpc/include/asm/ptrace.h
浏览文件 @ 74511020
此差异已折叠。
arch/powerpc/include/asm/syscall.h
浏览文件 @ 74511020
此差异已折叠。
arch/powerpc/include/asm/syscalls.h
浏览文件 @ 74511020
此差异已折叠。
arch/powerpc/include/asm/systbl.h
浏览文件 @ 74511020
此差异已折叠。
arch/powerpc/include/asm/unistd.h
浏览文件 @ 74511020
此差异已折叠。
arch/powerpc/kernel/Makefile
浏览文件 @ 74511020
此差异已折叠。
arch/powerpc/kernel/cputable.c
浏览文件 @ 74511020
此差异已折叠。
arch/powerpc/kernel/e500-pmu.c 0 → 100644
浏览文件 @ 74511020
此差异已折叠。
arch/powerpc/kernel/head_64.S
浏览文件 @ 74511020
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或