Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
提交 bcd6acd5 编写于 作者: B Benjamin Herrenschmidt
浏览文件
操作

Merge commit 'origin/master' into next 

Conflicts:
	include/linux/kvm.h
上级 11c34c7d 3ff6a468
展开全部 隐藏空白更改
内联 并排
Showing with 48799 addition and 11033 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
.gitignore
浏览文件 @ bcd6acd5
......@@ -25,6 +25,7 @@
*.elf
*.bin
*.gz
*.bz2
*.lzma
*.patch
*.gcno
......
Documentation/DocBook/tracepoint.tmpl
浏览文件 @ bcd6acd5
......@@ -86,4 +86,9 @@
!Iinclude/trace/events/irq.h
</chapter>
<chapter id="signal">
<title>SIGNAL</title>
!Iinclude/trace/events/signal.h
</chapter>
</book>
Documentation/RCU/trace.txt
浏览文件 @ bcd6acd5
CONFIG_RCU_TRACE debugfs Files and Formats
The rcupreempt and rcutree implementations of RCU provide debugfs trace
output that summarizes counters and state. This information is useful for
debugging RCU itself, and can sometimes also help to debug abuses of RCU.
Note that the rcuclassic implementation of RCU does not provide debugfs
trace output.
The following sections describe the debugfs files and formats for
preemptable RCU (rcupreempt) and hierarchical RCU (rcutree).
Preemptable RCU debugfs Files and Formats
This implementation of RCU provides three debugfs files under the
top-level directory RCU: rcu/rcuctrs (which displays the per-CPU
counters used by preemptable RCU) rcu/rcugp (which displays grace-period
counters), and rcu/rcustats (which internal counters for debugging RCU).
The output of "cat rcu/rcuctrs" looks as follows:
CPU last cur F M
0 5 -5 0 0
1 -1 0 0 0
2 0 1 0 0
3 0 1 0 0
4 0 1 0 0
5 0 1 0 0
6 0 2 0 0
7 0 -1 0 0
8 0 1 0 0
ggp = 26226, state = waitzero
The per-CPU fields are as follows:
o "CPU" gives the CPU number. Offline CPUs are not displayed.
o "last" gives the value of the counter that is being decremented
for the current grace period phase. In the example above,
the counters sum to 4, indicating that there are still four
RCU read-side critical sections still running that started
before the last counter flip.
o "cur" gives the value of the counter that is currently being
both incremented (by rcu_read_lock()) and decremented (by
rcu_read_unlock()). In the example above, the counters sum to
1, indicating that there is only one RCU read-side critical section
still running that started after the last counter flip.
o "F" indicates whether RCU is waiting for this CPU to acknowledge
a counter flip. In the above example, RCU is not waiting on any,
which is consistent with the state being "waitzero" rather than
"waitack".
o "M" indicates whether RCU is waiting for this CPU to execute a
memory barrier. In the above example, RCU is not waiting on any,
which is consistent with the state being "waitzero" rather than
"waitmb".
o "ggp" is the global grace-period counter.
o "state" is the RCU state, which can be one of the following:
o "idle": there is no grace period in progress.
o "waitack": RCU just incremented the global grace-period
counter, which has the effect of reversing the roles of
the "last" and "cur" counters above, and is waiting for
all the CPUs to acknowledge the flip. Once the flip has
been acknowledged, CPUs will no longer be incrementing
what are now the "last" counters, so that their sum will
decrease monotonically down to zero.
o "waitzero": RCU is waiting for the sum of the "last" counters
to decrease to zero.
o "waitmb": RCU is waiting for each CPU to execute a memory
barrier, which ensures that instructions from a given CPU's
last RCU read-side critical section cannot be reordered
with instructions following the memory-barrier instruction.
The output of "cat rcu/rcugp" looks as follows:
oldggp=48870 newggp=48873
Note that reading from this file provokes a synchronize_rcu(). The
"oldggp" value is that of "ggp" from rcu/rcuctrs above, taken before
executing the synchronize_rcu(), and the "newggp" value is also the
"ggp" value, but taken after the synchronize_rcu() command returns.
The output of "cat rcu/rcugp" looks as follows:
na=1337955 nl=40 wa=1337915 wl=44 da=1337871 dl=0 dr=1337871 di=1337871
1=50989 e1=6138 i1=49722 ie1=82 g1=49640 a1=315203 ae1=265563 a2=49640
z1=1401244 ze1=1351605 z2=49639 m1=5661253 me1=5611614 m2=49639
These are counters tracking internal preemptable-RCU events, however,
some of them may be useful for debugging algorithms using RCU. In
particular, the "nl", "wl", and "dl" values track the number of RCU
callbacks in various states. The fields are as follows:
o "na" is the total number of RCU callbacks that have been enqueued
since boot.
o "nl" is the number of RCU callbacks waiting for the previous
grace period to end so that they can start waiting on the next
grace period.
o "wa" is the total number of RCU callbacks that have started waiting
for a grace period since boot. "na" should be roughly equal to
"nl" plus "wa".
o "wl" is the number of RCU callbacks currently waiting for their
grace period to end.
o "da" is the total number of RCU callbacks whose grace periods
have completed since boot. "wa" should be roughly equal to
"wl" plus "da".
o "dr" is the total number of RCU callbacks that have been removed
from the list of callbacks ready to invoke. "dr" should be roughly
equal to "da".
o "di" is the total number of RCU callbacks that have been invoked
since boot. "di" should be roughly equal to "da", though some
early versions of preemptable RCU had a bug so that only the
last CPU's count of invocations was displayed, rather than the
sum of all CPU's counts.
o "1" is the number of calls to rcu_try_flip(). This should be
roughly equal to the sum of "e1", "i1", "a1", "z1", and "m1"
described below. In other words, the number of times that
the state machine is visited should be equal to the sum of the
number of times that each state is visited plus the number of
times that the state-machine lock acquisition failed.
o "e1" is the number of times that rcu_try_flip() was unable to
acquire the fliplock.
o "i1" is the number of calls to rcu_try_flip_idle().
o "ie1" is the number of times rcu_try_flip_idle() exited early
due to the calling CPU having no work for RCU.
o "g1" is the number of times that rcu_try_flip_idle() decided
to start a new grace period. "i1" should be roughly equal to
"ie1" plus "g1".
o "a1" is the number of calls to rcu_try_flip_waitack().
o "ae1" is the number of times that rcu_try_flip_waitack() found
that at least one CPU had not yet acknowledge the new grace period
(AKA "counter flip").
o "a2" is the number of time rcu_try_flip_waitack() found that
all CPUs had acknowledged. "a1" should be roughly equal to
"ae1" plus "a2". (This particular output was collected on
a 128-CPU machine, hence the smaller-than-usual fraction of
calls to rcu_try_flip_waitack() finding all CPUs having already
acknowledged.)
o "z1" is the number of calls to rcu_try_flip_waitzero().
o "ze1" is the number of times that rcu_try_flip_waitzero() found
that not all of the old RCU read-side critical sections had
completed.
o "z2" is the number of times that rcu_try_flip_waitzero() finds
the sum of the counters equal to zero, in other words, that
all of the old RCU read-side critical sections had completed.
The value of "z1" should be roughly equal to "ze1" plus
"z2".
o "m1" is the number of calls to rcu_try_flip_waitmb().
o "me1" is the number of times that rcu_try_flip_waitmb() finds
that at least one CPU has not yet executed a memory barrier.
o "m2" is the number of times that rcu_try_flip_waitmb() finds that
all CPUs have executed a memory barrier.
The rcutree implementation of RCU provides debugfs trace output that
summarizes counters and state. This information is useful for debugging
RCU itself, and can sometimes also help to debug abuses of RCU.
The following sections describe the debugfs files and formats.
Hierarchical RCU debugfs Files and Formats
......@@ -210,9 +35,10 @@ rcu_bh:
6 c=-275 g=-275 pq=1 pqc=-275 qp=0 dt=859/1 dn=0 df=15 of=0 ri=0 ql=0 b=10
7 c=-275 g=-275 pq=1 pqc=-275 qp=0 dt=3761/1 dn=0 df=15 of=0 ri=0 ql=0 b=10
The first section lists the rcu_data structures for rcu, the second for
rcu_bh. Each section has one line per CPU, or eight for this 8-CPU system.
The fields are as follows:
The first section lists the rcu_data structures for rcu_sched, the second
for rcu_bh. Note that CONFIG_TREE_PREEMPT_RCU kernels will have an
additional section for rcu_preempt. Each section has one line per CPU,
or eight for this 8-CPU system. The fields are as follows:
o The number at the beginning of each line is the CPU number.
CPUs numbers followed by an exclamation mark are offline,
......@@ -223,9 +49,9 @@ o The number at the beginning of each line is the CPU number.
o "c" is the count of grace periods that this CPU believes have
completed. CPUs in dynticks idle mode may lag quite a ways
behind, for example, CPU 4 under "rcu" above, which has slept
through the past 25 RCU grace periods. It is not unusual to
see CPUs lagging by thousands of grace periods.
behind, for example, CPU 4 under "rcu_sched" above, which has
slept through the past 25 RCU grace periods. It is not unusual
to see CPUs lagging by thousands of grace periods.
o "g" is the count of grace periods that this CPU believes have
started. Again, CPUs in dynticks idle mode may lag behind.
......@@ -308,8 +134,10 @@ The output of "cat rcu/rcugp" looks as follows:
rcu_sched: completed=33062 gpnum=33063
rcu_bh: completed=464 gpnum=464
Again, this output is for both "rcu" and "rcu_bh". The fields are
taken from the rcu_state structure, and are as follows:
Again, this output is for both "rcu_sched" and "rcu_bh". Note that
kernels built with CONFIG_TREE_PREEMPT_RCU will have an additional
"rcu_preempt" line. The fields are taken from the rcu_state structure,
and are as follows:
o "completed" is the number of grace periods that have completed.
It is comparable to the "c" field from rcu/rcudata in that a
......@@ -324,23 +152,24 @@ o "gpnum" is the number of grace periods that have started. It is
If these two fields are equal (as they are for "rcu_bh" above),
then there is no grace period in progress, in other words, RCU
is idle. On the other hand, if the two fields differ (as they
do for "rcu" above), then an RCU grace period is in progress.
do for "rcu_sched" above), then an RCU grace period is in progress.
The output of "cat rcu/rcuhier" looks as follows, with very long lines:
c=6902 g=6903 s=2 jfq=3 j=72c7 nfqs=13142/nfqsng=0(13142) fqlh=6
1/1 0:127 ^0
3/3 0:35 ^0 0/0 36:71 ^1 0/0 72:107 ^2 0/0 108:127 ^3
3/3f 0:5 ^0 2/3 6:11 ^1 0/0 12:17 ^2 0/0 18:23 ^3 0/0 24:29 ^4 0/0 30:35 ^5 0/0 36:41 ^0 0/0 42:47 ^1 0/0 48:53 ^2 0/0 54:59 ^3 0/0 60:65 ^4 0/0 66:71 ^5 0/0 72:77 ^0 0/0 78:83 ^1 0/0 84:89 ^2 0/0 90:95 ^3 0/0 96:101 ^4 0/0 102:107 ^5 0/0 108:113 ^0 0/0 114:119 ^1 0/0 120:125 ^2 0/0 126:127 ^3
c=6902 g=6903 s=2 jfq=3 j=72c7 nfqs=13142/nfqsng=0(13142) fqlh=6 oqlen=0
1/1 .>. 0:127 ^0
3/3 .>. 0:35 ^0 0/0 .>. 36:71 ^1 0/0 .>. 72:107 ^2 0/0 .>. 108:127 ^3
3/3f .>. 0:5 ^0 2/3 .>. 6:11 ^1 0/0 .>. 12:17 ^2 0/0 .>. 18:23 ^3 0/0 .>. 24:29 ^4 0/0 .>. 30:35 ^5 0/0 .>. 36:41 ^0 0/0 .>. 42:47 ^1 0/0 .>. 48:53 ^2 0/0 .>. 54:59 ^3 0/0 .>. 60:65 ^4 0/0 .>. 66:71 ^5 0/0 .>. 72:77 ^0 0/0 .>. 78:83 ^1 0/0 .>. 84:89 ^2 0/0 .>. 90:95 ^3 0/0 .>. 96:101 ^4 0/0 .>. 102:107 ^5 0/0 .>. 108:113 ^0 0/0 .>. 114:119 ^1 0/0 .>. 120:125 ^2 0/0 .>. 126:127 ^3
rcu_bh:
c=-226 g=-226 s=1 jfq=-5701 j=72c7 nfqs=88/nfqsng=0(88) fqlh=0
0/1 0:127 ^0
0/3 0:35 ^0 0/0 36:71 ^1 0/0 72:107 ^2 0/0 108:127 ^3
0/3f 0:5 ^0 0/3 6:11 ^1 0/0 12:17 ^2 0/0 18:23 ^3 0/0 24:29 ^4 0/0 30:35 ^5 0/0 36:41 ^0 0/0 42:47 ^1 0/0 48:53 ^2 0/0 54:59 ^3 0/0 60:65 ^4 0/0 66:71 ^5 0/0 72:77 ^0 0/0 78:83 ^1 0/0 84:89 ^2 0/0 90:95 ^3 0/0 96:101 ^4 0/0 102:107 ^5 0/0 108:113 ^0 0/0 114:119 ^1 0/0 120:125 ^2 0/0 126:127 ^3
c=-226 g=-226 s=1 jfq=-5701 j=72c7 nfqs=88/nfqsng=0(88) fqlh=0 oqlen=0
0/1 .>. 0:127 ^0
0/3 .>. 0:35 ^0 0/0 .>. 36:71 ^1 0/0 .>. 72:107 ^2 0/0 .>. 108:127 ^3
0/3f .>. 0:5 ^0 0/3 .>. 6:11 ^1 0/0 .>. 12:17 ^2 0/0 .>. 18:23 ^3 0/0 .>. 24:29 ^4 0/0 .>. 30:35 ^5 0/0 .>. 36:41 ^0 0/0 .>. 42:47 ^1 0/0 .>. 48:53 ^2 0/0 .>. 54:59 ^3 0/0 .>. 60:65 ^4 0/0 .>. 66:71 ^5 0/0 .>. 72:77 ^0 0/0 .>. 78:83 ^1 0/0 .>. 84:89 ^2 0/0 .>. 90:95 ^3 0/0 .>. 96:101 ^4 0/0 .>. 102:107 ^5 0/0 .>. 108:113 ^0 0/0 .>. 114:119 ^1 0/0 .>. 120:125 ^2 0/0 .>. 126:127 ^3
This is once again split into "rcu" and "rcu_bh" portions. The fields are
as follows:
This is once again split into "rcu_sched" and "rcu_bh" portions,
and CONFIG_TREE_PREEMPT_RCU kernels will again have an additional
"rcu_preempt" section. The fields are as follows:
o "c" is exactly the same as "completed" under rcu/rcugp.
......@@ -372,6 +201,11 @@ o "fqlh" is the number of calls to force_quiescent_state() that
exited immediately (without even being counted in nfqs above)
due to contention on ->fqslock.
o "oqlen" is the number of callbacks on the "orphan" callback
list. RCU callbacks are placed on this list by CPUs going
offline, and are "adopted" either by the CPU helping the outgoing
CPU or by the next rcu_barrier*() call, whichever comes first.
o Each element of the form "1/1 0:127 ^0" represents one struct
rcu_node. Each line represents one level of the hierarchy, from
root to leaves. It is best to think of the rcu_data structures
......@@ -379,7 +213,7 @@ o Each element of the form "1/1 0:127 ^0" represents one struct
might be either one, two, or three levels of rcu_node structures,
depending on the relationship between CONFIG_RCU_FANOUT and
CONFIG_NR_CPUS.
o The numbers separated by the "/" are the qsmask followed
by the qsmaskinit. The qsmask will have one bit
set for each entity in the next lower level that
......@@ -389,10 +223,19 @@ o Each element of the form "1/1 0:127 ^0" represents one struct
The value of qsmaskinit is assigned to that of qsmask
at the beginning of each grace period.
For example, for "rcu", the qsmask of the first entry
of the lowest level is 0x14, meaning that we are still
waiting for CPUs 2 and 4 to check in for the current
grace period.
For example, for "rcu_sched", the qsmask of the first
entry of the lowest level is 0x14, meaning that we
are still waiting for CPUs 2 and 4 to check in for the
current grace period.
o The characters separated by the ">" indicate the state
of the blocked-tasks lists. A "T" preceding the ">"
indicates that at least one task blocked in an RCU
read-side critical section blocks the current grace
period, while a "." preceding the ">" indicates otherwise.
The character following the ">" indicates similarly for
the next grace period. A "T" should appear in this
field only for rcu-preempt.
o The numbers separated by the ":" are the range of CPUs
served by this struct rcu_node. This can be helpful
......@@ -431,8 +274,9 @@ rcu_bh:
6 np=120834 qsp=9902 cbr=0 cng=0 gpc=6 gps=3 nf=2 nn=110921
7 np=144888 qsp=26336 cbr=0 cng=0 gpc=8 gps=2 nf=0 nn=118542
As always, this is once again split into "rcu" and "rcu_bh" portions.
The fields are as follows:
As always, this is once again split into "rcu_sched" and "rcu_bh"
portions, with CONFIG_TREE_PREEMPT_RCU kernels having an additional
"rcu_preempt" section. The fields are as follows:
o "np" is the number of times that __rcu_pending() has been invoked
for the corresponding flavor of RCU.
......
Documentation/RCU/whatisRCU.txt
浏览文件 @ bcd6acd5
......@@ -830,7 +830,7 @@ sched: Critical sections Grace period Barrier
SRCU: Critical sections Grace period Barrier
srcu_read_lock synchronize_srcu N/A
srcu_read_unlock
srcu_read_unlock synchronize_srcu_expedited
SRCU: Initialization/cleanup
init_srcu_struct
......
Documentation/arm/Samsung-S3C24XX/EB2410ITX.txt
浏览文件 @ bcd6acd5
......@@ -55,4 +55,4 @@ Maintainers
This board is maintained by Simtec Electronics.
(c) 2004 Ben Dooks, Simtec Electronics
Copyright 2004 Ben Dooks, Simtec Electronics
Documentation/arm/Samsung-S3C24XX/GPIO.txt
浏览文件 @ bcd6acd5
......@@ -134,4 +134,4 @@ Authour
Ben Dooks, 03 October 2004
(c) 2004 Ben Dooks, Simtec Electronics
Copyright 2004 Ben Dooks, Simtec Electronics
Documentation/arm/Samsung-S3C24XX/Overview.txt
浏览文件 @ bcd6acd5
......@@ -299,4 +299,4 @@ Port Contributors
Document Author
---------------
Ben Dooks, (c) 2004-2005,2006 Simtec Electronics
Ben Dooks, Copyright 2004-2006 Simtec Electronics
Documentation/arm/Samsung-S3C24XX/S3C2412.txt
浏览文件 @ bcd6acd5
......@@ -117,4 +117,4 @@ ATA
Document Author
---------------
Ben Dooks, (c) 2006 Simtec Electronics
Ben Dooks, Copyright 2006 Simtec Electronics
Documentation/arm/Samsung-S3C24XX/S3C2413.txt
浏览文件 @ bcd6acd5
......@@ -18,4 +18,4 @@ Camera Interface
Document Author
---------------
Ben Dooks, (c) 2006 Simtec Electronics
Ben Dooks, Copyright 2006 Simtec Electronics
Documentation/arm/Samsung-S3C24XX/Suspend.txt
浏览文件 @ bcd6acd5
......@@ -133,5 +133,5 @@ Configuration
Document Author
---------------
Ben Dooks, (c) 2004 Simtec Electronics
Ben Dooks, Copyright 2004 Simtec Electronics
Documentation/arm/Samsung-S3C24XX/USB-Host.txt
浏览文件 @ bcd6acd5
......@@ -90,4 +90,4 @@ Platform Data
Document Author
---------------
Ben Dooks, (c) 2005 Simtec Electronics
Ben Dooks, Copyright 2005 Simtec Electronics
Documentation/blockdev/drbd/DRBD-8.3-data-packets.svg 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
Documentation/blockdev/drbd/DRBD-data-packets.svg 0 → 100644
浏览文件 @ bcd6acd5
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!-- Created with Inkscape (http://www.inkscape.org/) -->
<svg
xmlns:svg="http://www.w3.org/2000/svg"
xmlns="http://www.w3.org/2000/svg"
version="1.0"
width="210mm"
height="297mm"
viewBox="0 0 21000 29700"
id="svg2"
style="fill-rule:evenodd">
<defs
id="defs4" />
<g
id="Default"
style="visibility:visible">
<desc
id="desc176">Master slide</desc>
</g>
<path
d="M 11999,19601 L 11899,19301 L 12099,19301 L 11999,19601 z"
id="path189"
style="fill:#008000;visibility:visible" />
<path
d="M 11999,18801 L 11999,19361"
id="path193"
style="fill:none;stroke:#008000;visibility:visible" />
<path
d="M 7999,21401 L 7899,21101 L 8099,21101 L 7999,21401 z"
id="path205"
style="fill:#008000;visibility:visible" />
<path
d="M 7999,20601 L 7999,21161"
id="path209"
style="fill:none;stroke:#008000;visibility:visible" />
<path
d="M 11999,18801 L 11685,18840 L 11724,18644 L 11999,18801 z"
id="path221"
style="fill:#008000;visibility:visible" />
<path
d="M 7999,18001 L 11764,18754"
id="path225"
style="fill:none;stroke:#008000;visibility:visible" />
<text
x="-3023.845"
y="1106.8124"
transform="matrix(0.9895258,-0.1443562,0.1443562,0.9895258,0,0)"
id="text243"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="6115.1553 6344.1553 6555.1553 6784.1553 6962.1553 7051.1553 7228.1553 7457.1553 7635.1553 7813.1553 7885.1553"
y="21390.812"
id="tspan245">RSDataReply</tspan>
</text>
<path
d="M 7999,20601 L 8281,20458 L 8311,20655 L 7999,20601 z"
id="path255"
style="fill:#008000;visibility:visible" />
<path
d="M 11999,20001 L 8236,20565"
id="path259"
style="fill:none;stroke:#008000;visibility:visible" />
<text
x="3502.5356"
y="-2184.6621"
transform="matrix(0.9788674,0.2044961,-0.2044961,0.9788674,0,0)"
id="text277"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="12321.536 12550.536 12761.536 12990.536 13168.536 13257.536 13434.536 13663.536 13841.536 14019.536 14196.536 14374.536 14535.536"
y="15854.338"
id="tspan279">RSDataRequest</tspan>
</text>
<text
id="text293"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="4034 4263 4440 4703 4881 5042 5219 5397 5503 5681 5842 6003 6180 6341 6519 6625 6803 6980 7158 7336 7497 7586 7692"
y="17807"
id="tspan295">w_make_resync_request()</tspan>
</text>
<text
id="text309"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="12199 12305 12483 12644 12821 12893 13054 13232 13410 13638 13816 13905 14083 14311 14489 14667 14845 15023 15184 15272 15378"
y="18806"
id="tspan311">receive_DataRequest()</tspan>
</text>
<text
id="text325"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="12199 12377 12483 12660 12838 13016 13194 13372 13549 13621 13799 13977 14083 14261 14438 14616 14794 14955 15133 15294 15399"
y="19606"
id="tspan327">drbd_endio_read_sec()</tspan>
</text>
<text
id="text341"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="12191 12420 12597 12775 12953 13131 13309 13486 13664 13770 13931 14109 14287 14375 14553 14731 14837 15015 15192 15298"
y="20007"
id="tspan343">w_e_end_rsdata_req()</tspan>
</text>
<text
id="text357"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="4444 4550 4728 4889 5066 5138 5299 5477 5655 5883 6095 6324 6501 6590 6768 6997 7175 7352 7424 7585 7691"
y="20507"
id="tspan359">receive_RSDataReply()</tspan>
</text>
<text
id="text373"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="4457 4635 4741 4918 5096 5274 5452 5630 5807 5879 6057 6235 6464 6569 6641 6730 6908 7086 7247 7425 7585 7691"
y="21407"
id="tspan375">drbd_endio_write_sec()</tspan>
</text>
<text
id="text389"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="4647 4825 5003 5180 5358 5536 5714 5820 5997 6158 6319 6497 6658 6836 7013 7085 7263 7424 7585 7691"
y="21907"
id="tspan391">e_end_resync_block()</tspan>
</text>
<path
d="M 11999,22601 L 11685,22640 L 11724,22444 L 11999,22601 z"
id="path401"
style="fill:#000080;visibility:visible" />
<path
d="M 7999,21801 L 11764,22554"
id="path405"
style="fill:none;stroke:#000080;visibility:visible" />
<text
x="4290.3008"
y="-2369.6162"
transform="matrix(0.9788674,0.2044961,-0.2044961,0.9788674,0,0)"
id="text423"
style="font-size:318px;font-weight:400;fill:#000080;visibility:visible;font-family:Helvetica embedded">
<tspan
x="13610.301 13911.301 14016.301 14088.301 14177.301 14355.301 14567.301 14728.301"
y="19573.385"
id="tspan425">WriteAck</tspan>
</text>
<text
id="text439"
style="font-size:318px;font-weight:400;fill:#000080;visibility:visible;font-family:Helvetica embedded">
<tspan
x="12199 12377 12555 12644 12821 13033 13105 13283 13444 13604 13816 13977 14138 14244"
y="22559"
id="tspan441">got_BlockAck()</tspan>
</text>
<text
id="text455"
style="font-size:423px;font-weight:400;fill:#000000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="7999 8304 8541 8753 8964 9201 9413 9531 9769 9862 10099 10310 10522 10734 10852 10971 11208 11348 11585 11822"
y="16877"
id="tspan457">Resync blocks, 4-32K</tspan>
</text>
<path
d="M 12000,7601 L 11900,7301 L 12100,7301 L 12000,7601 z"
id="path467"
style="fill:#008000;visibility:visible" />
<path
d="M 12000,6801 L 12000,7361"
id="path471"
style="fill:none;stroke:#008000;visibility:visible" />
<path
d="M 12000,6801 L 11686,6840 L 11725,6644 L 12000,6801 z"
id="path483"
style="fill:#008000;visibility:visible" />
<path
d="M 8000,6001 L 11765,6754"
id="path487"
style="fill:none;stroke:#008000;visibility:visible" />
<text
x="-1288.1796"
y="1279.7666"
transform="matrix(0.9895258,-0.1443562,0.1443562,0.9895258,0,0)"
id="text505"
style="font-size:318px;font-weight:400;fill:#000080;visibility:visible;font-family:Helvetica embedded">
<tspan
x="8174.8208 8475.8203 8580.8203 8652.8203 8741.8203 8919.8203 9131.8203 9292.8203"
y="9516.7666"
id="tspan507">WriteAck</tspan>
</text>
<path
d="M 8000,8601 L 8282,8458 L 8312,8655 L 8000,8601 z"
id="path517"
style="fill:#000080;visibility:visible" />
<path
d="M 12000,8001 L 8237,8565"
id="path521"
style="fill:none;stroke:#000080;visibility:visible" />
<text
x="1065.6655"
y="-2097.7664"
transform="matrix(0.9788674,0.2044961,-0.2044961,0.9788674,0,0)"
id="text539"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="10682.666 10911.666 11088.666 11177.666"
y="4107.2339"
id="tspan541">Data</tspan>
</text>
<text
id="text555"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="4746 4924 5030 5207 5385 5563 5826 6003 6164 6342 6520 6626 6803 6981 7159 7337 7498 7587 7692"
y="5505"
id="tspan557">drbd_make_request()</tspan>
</text>
<text
id="text571"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="12200 12306 12484 12645 12822 12894 13055 13233 13411 13639 13817 13906 14084 14190"
y="6806"
id="tspan573">receive_Data()</tspan>
</text>
<text
id="text587"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="12200 12378 12484 12661 12839 13017 13195 13373 13550 13622 13800 13978 14207 14312 14384 14473 14651 14829 14990 15168 15328 15434"
y="7606"
id="tspan589">drbd_endio_write_sec()</tspan>
</text>
<text
id="text603"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="12192 12370 12548 12725 12903 13081 13259 13437 13509 13686 13847 14008 14114"
y="8007"
id="tspan605">e_end_block()</tspan>
</text>
<text
id="text619"
style="font-size:318px;font-weight:400;fill:#000080;visibility:visible;font-family:Helvetica embedded">
<tspan
x="5647 5825 6003 6092 6269 6481 6553 6731 6892 7052 7264 7425 7586 7692"
y="8606"
id="tspan621">got_BlockAck()</tspan>
</text>
<text
id="text635"
style="font-size:423px;font-weight:400;fill:#000000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="8000 8305 8542 8779 9016 9109 9346 9486 9604 9956 10049 10189 10328 10565 10705 10942 11179 11298 11603 11742 11835 11954 12191 12310 12428 12665 12902 13139 13279 13516 13753"
y="4877"
id="tspan637">Regular mirrored write, 512-32K</tspan>
</text>
<text
id="text651"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="5381 5610 5787 5948 6126 6304 6482 6659 6837 7015 7087 7265 7426 7587 7692"
y="6003"
id="tspan653">w_send_dblock()</tspan>
</text>
<path
d="M 8000,6800 L 7900,6500 L 8100,6500 L 8000,6800 z"
id="path663"
style="fill:#008000;visibility:visible" />
<path
d="M 8000,6000 L 8000,6560"
id="path667"
style="fill:none;stroke:#008000;visibility:visible" />
<text
id="text683"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="4602 4780 4886 5063 5241 5419 5597 5775 5952 6024 6202 6380 6609 6714 6786 6875 7053 7231 7409 7515 7587 7692"
y="6905"
id="tspan685">drbd_endio_write_pri()</tspan>
</text>
<path
d="M 12000,13602 L 11900,13302 L 12100,13302 L 12000,13602 z"
id="path695"
style="fill:#008000;visibility:visible" />
<path
d="M 12000,12802 L 12000,13362"
id="path699"
style="fill:none;stroke:#008000;visibility:visible" />
<path
d="M 12000,12802 L 11686,12841 L 11725,12645 L 12000,12802 z"
id="path711"
style="fill:#008000;visibility:visible" />
<path
d="M 8000,12002 L 11765,12755"
id="path715"
style="fill:none;stroke:#008000;visibility:visible" />
<text
x="-2155.5266"
y="1201.5964"
transform="matrix(0.9895258,-0.1443562,0.1443562,0.9895258,0,0)"
id="text733"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="7202.4736 7431.4736 7608.4736 7697.4736 7875.4736 8104.4736 8282.4736 8459.4736 8531.4736"
y="15454.597"
id="tspan735">DataReply</tspan>
</text>
<path
d="M 8000,14602 L 8282,14459 L 8312,14656 L 8000,14602 z"
id="path745"
style="fill:#008000;visibility:visible" />
<path
d="M 12000,14002 L 8237,14566"
id="path749"
style="fill:none;stroke:#008000;visibility:visible" />
<text
x="2280.3804"
y="-2103.2141"
transform="matrix(0.9788674,0.2044961,-0.2044961,0.9788674,0,0)"
id="text767"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="11316.381 11545.381 11722.381 11811.381 11989.381 12218.381 12396.381 12573.381 12751.381 12929.381 13090.381"
y="9981.7861"
id="tspan769">DataRequest</tspan>
</text>
<text
id="text783"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="4746 4924 5030 5207 5385 5563 5826 6003 6164 6342 6520 6626 6803 6981 7159 7337 7498 7587 7692"
y="11506"
id="tspan785">drbd_make_request()</tspan>
</text>
<text
id="text799"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="12200 12306 12484 12645 12822 12894 13055 13233 13411 13639 13817 13906 14084 14312 14490 14668 14846 15024 15185 15273 15379"
y="12807"
id="tspan801">receive_DataRequest()</tspan>
</text>
<text
id="text815"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="12200 12378 12484 12661 12839 13017 13195 13373 13550 13622 13800 13978 14084 14262 14439 14617 14795 14956 15134 15295 15400"
y="13607"
id="tspan817">drbd_endio_read_sec()</tspan>
</text>
<text
id="text831"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="12192 12421 12598 12776 12954 13132 13310 13487 13665 13843 14021 14110 14288 14465 14571 14749 14927 15033"
y="14008"
id="tspan833">w_e_end_data_req()</tspan>
</text>
<g
id="g835"
style="visibility:visible">
<desc
id="desc837">Drawing</desc>
<text
id="text847"
style="font-size:318px;font-weight:400;fill:#008000;font-family:Helvetica embedded">
<tspan
x="4885 4991 5169 5330 5507 5579 5740 5918 6096 6324 6502 6591 6769 6997 7175 7353 7425 7586 7692"
y="14607"
id="tspan849">receive_DataReply()</tspan>
</text>
</g>
<text
id="text863"
style="font-size:423px;font-weight:400;fill:#000000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="8000 8305 8398 8610 8821 8914 9151 9363 9575 9693 9833 10070 10307 10544 10663 10781 11018 11255 11493 11632 11869 12106"
y="10878"
id="tspan865">Diskless read, 512-32K</tspan>
</text>
<text
id="text879"
style="font-size:318px;font-weight:400;fill:#008000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="5029 5258 5435 5596 5774 5952 6130 6307 6413 6591 6769 6947 7125 7230 7408 7586 7692"
y="12004"
id="tspan881">w_send_read_req()</tspan>
</text>
<text
id="text895"
style="font-size:423px;font-weight:400;fill:#000000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="6961 7266 7571 7854 8159 8278 8515 8633 8870 9107 9226 9463 9581 9700 9793 10030"
y="2806"
id="tspan897">DRBD 8 data flow</tspan>
</text>
<path
d="M 3900,5300 L 3700,5300 L 3700,7000 L 3900,7000"
id="path907"
style="fill:none;stroke:#000000;visibility:visible" />
<path
d="M 3900,17600 L 3700,17600 L 3700,22000 L 3900,22000"
id="path919"
style="fill:none;stroke:#000000;visibility:visible" />
<path
d="M 16100,20000 L 16300,20000 L 16300,18500 L 16100,18500"
id="path931"
style="fill:none;stroke:#000000;visibility:visible" />
<text
id="text947"
style="font-size:318px;font-weight:400;fill:#000000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="2126 2304 2376 2554 2731 2909 3087 3159 3337 3515 3587 3764 3870"
y="5202"
id="tspan949">al_begin_io()</tspan>
</text>
<text
id="text963"
style="font-size:318px;font-weight:400;fill:#000000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="1632 1810 1882 2060 2220 2398 2661 2839 2910 3088 3177 3355 3533 3605 3783 3888"
y="7331"
id="tspan965">al_complete_io()</tspan>
</text>
<text
id="text979"
style="font-size:318px;font-weight:400;fill:#000000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="2126 2232 2393 2571 2748 2926 3104 3176 3354 3531 3603 3781 3887"
y="17431"
id="tspan981">rs_begin_io()</tspan>
</text>
<text
id="text995"
style="font-size:318px;font-weight:400;fill:#000000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="1626 1732 1893 2071 2231 2409 2672 2849 2921 3099 3188 3366 3544 3616 3793 3899"
y="22331"
id="tspan997">rs_complete_io()</tspan>
</text>
<text
id="text1011"
style="font-size:318px;font-weight:400;fill:#000000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="16027 16133 16294 16472 16649 16827 17005 17077 17255 17432 17504 17682 17788"
y="18402"
id="tspan1013">rs_begin_io()</tspan>
</text>
<text
id="text1027"
style="font-size:318px;font-weight:400;fill:#000000;visibility:visible;font-family:Helvetica embedded">
<tspan
x="16115 16221 16382 16560 16720 16898 17161 17338 17410 17588 17677 17855 18033 18105 18282 18388"
y="20331"
id="tspan1029">rs_complete_io()</tspan>
</text>
</svg>
Documentation/blockdev/drbd/README.txt 0 → 100644
浏览文件 @ bcd6acd5
Description
DRBD is a shared-nothing, synchronously replicated block device. It
is designed to serve as a building block for high availability
clusters and in this context, is a "drop-in" replacement for shared
storage. Simplistically, you could see it as a network RAID 1.
Please visit http://www.drbd.org to find out more.
The here included files are intended to help understand the implementation
DRBD-8.3-data-packets.svg, DRBD-data-packets.svg
relates some functions, and write packets.
conn-states-8.dot, disk-states-8.dot, node-states-8.dot
The sub graphs of DRBD's state transitions
Documentation/blockdev/drbd/conn-states-8.dot 0 → 100644
浏览文件 @ bcd6acd5
digraph conn_states {
StandAllone -> WFConnection [ label = "ioctl_set_net()" ]
WFConnection -> Unconnected [ label = "unable to bind()" ]
WFConnection -> WFReportParams [ label = "in connect() after accept" ]
WFReportParams -> StandAllone [ label = "checks in receive_param()" ]
WFReportParams -> Connected [ label = "in receive_param()" ]
WFReportParams -> WFBitMapS [ label = "sync_handshake()" ]
WFReportParams -> WFBitMapT [ label = "sync_handshake()" ]
WFBitMapS -> SyncSource [ label = "receive_bitmap()" ]
WFBitMapT -> SyncTarget [ label = "receive_bitmap()" ]
SyncSource -> Connected
SyncTarget -> Connected
SyncSource -> PausedSyncS
SyncTarget -> PausedSyncT
PausedSyncS -> SyncSource
PausedSyncT -> SyncTarget
Connected -> WFConnection [ label = "* on network error" ]
}
Documentation/blockdev/drbd/disk-states-8.dot 0 → 100644
浏览文件 @ bcd6acd5
digraph disk_states {
Diskless -> Inconsistent [ label = "ioctl_set_disk()" ]
Diskless -> Consistent [ label = "ioctl_set_disk()" ]
Diskless -> Outdated [ label = "ioctl_set_disk()" ]
Consistent -> Outdated [ label = "receive_param()" ]
Consistent -> UpToDate [ label = "receive_param()" ]
Consistent -> Inconsistent [ label = "start resync" ]
Outdated -> Inconsistent [ label = "start resync" ]
UpToDate -> Inconsistent [ label = "ioctl_replicate" ]
Inconsistent -> UpToDate [ label = "resync completed" ]
Consistent -> Failed [ label = "io completion error" ]
Outdated -> Failed [ label = "io completion error" ]
UpToDate -> Failed [ label = "io completion error" ]
Inconsistent -> Failed [ label = "io completion error" ]
Failed -> Diskless [ label = "sending notify to peer" ]
}
Documentation/blockdev/drbd/drbd-connection-state-overview.dot 0 → 100644
浏览文件 @ bcd6acd5
// vim: set sw=2 sts=2 :
digraph {
rankdir=BT
bgcolor=white
node [shape=plaintext]
node [fontcolor=black]
StandAlone [ style=filled,fillcolor=gray,label=StandAlone ]
node [fontcolor=lightgray]
Unconnected [ label=Unconnected ]
CommTrouble [ shape=record,
label="{communication loss|{Timeout|BrokenPipe|NetworkFailure}}" ]
node [fontcolor=gray]
subgraph cluster_try_connect {
label="try to connect, handshake"
rank=max
WFConnection [ label=WFConnection ]
WFReportParams [ label=WFReportParams ]
}
TearDown [ label=TearDown ]
Connected [ label=Connected,style=filled,fillcolor=green,fontcolor=black ]
node [fontcolor=lightblue]
StartingSyncS [ label=StartingSyncS ]
StartingSyncT [ label=StartingSyncT ]
subgraph cluster_bitmap_exchange {
node [fontcolor=red]
fontcolor=red
label="new application (WRITE?) requests blocked\lwhile bitmap is exchanged"
WFBitMapT [ label=WFBitMapT ]
WFSyncUUID [ label=WFSyncUUID ]
WFBitMapS [ label=WFBitMapS ]
}
node [fontcolor=blue]
cluster_resync [ shape=record,label="{<any>resynchronisation process running\l'concurrent' application requests allowed|{{<T>PausedSyncT\nSyncTarget}|{<S>PausedSyncS\nSyncSource}}}" ]
node [shape=box,fontcolor=black]
// drbdadm [label="drbdadm connect"]
// handshake [label="drbd_connect()\ndrbd_do_handshake\ndrbd_sync_handshake() etc."]
// comm_error [label="communication trouble"]
//
// edges
// --------------------------------------
StandAlone -> Unconnected [ label="drbdadm connect" ]
Unconnected -> StandAlone [ label="drbdadm disconnect\lor serious communication trouble" ]
Unconnected -> WFConnection [ label="receiver thread is started" ]
WFConnection -> WFReportParams [ headlabel="accept()\land/or \lconnect()\l" ]
WFReportParams -> StandAlone [ label="during handshake\lpeers do not agree\labout something essential" ]
WFReportParams -> Connected [ label="data identical\lno sync needed",color=green,fontcolor=green ]
WFReportParams -> WFBitMapS
WFReportParams -> WFBitMapT
WFBitMapT -> WFSyncUUID [minlen=0.1,constraint=false]
WFBitMapS -> cluster_resync:S
WFSyncUUID -> cluster_resync:T
edge [color=green]
cluster_resync:any -> Connected [ label="resnyc done",fontcolor=green ]
edge [color=red]
WFReportParams -> CommTrouble
Connected -> CommTrouble
cluster_resync:any -> CommTrouble
edge [color=black]
CommTrouble -> Unconnected [label="receiver thread is stopped" ]
}
Documentation/blockdev/drbd/node-states-8.dot 0 → 100644
浏览文件 @ bcd6acd5
digraph node_states {
Secondary -> Primary [ label = "ioctl_set_state()" ]
Primary -> Secondary [ label = "ioctl_set_state()" ]
}
digraph peer_states {
Secondary -> Primary [ label = "recv state packet" ]
Primary -> Secondary [ label = "recv state packet" ]
Primary -> Unknown [ label = "connection lost" ]
Secondary -> Unknown [ label = "connection lost" ]
Unknown -> Primary [ label = "connected" ]
Unknown -> Secondary [ label = "connected" ]
}
Documentation/cgroups/blkio-controller.txt 0 → 100644
浏览文件 @ bcd6acd5
Block IO Controller
===================
Overview
========
cgroup subsys "blkio" implements the block io controller. There seems to be
a need of various kinds of IO control policies (like proportional BW, max BW)
both at leaf nodes as well as at intermediate nodes in a storage hierarchy.
Plan is to use the same cgroup based management interface for blkio controller
and based on user options switch IO policies in the background.
In the first phase, this patchset implements proportional weight time based
division of disk policy. It is implemented in CFQ. Hence this policy takes
effect only on leaf nodes when CFQ is being used.
HOWTO
=====
You can do a very simple testing of running two dd threads in two different
cgroups. Here is what you can do.
- Enable group scheduling in CFQ
CONFIG_CFQ_GROUP_IOSCHED=y
- Compile and boot into kernel and mount IO controller (blkio).
mount -t cgroup -o blkio none /cgroup
- Create two cgroups
mkdir -p /cgroup/test1/ /cgroup/test2
- Set weights of group test1 and test2
echo 1000 > /cgroup/test1/blkio.weight
echo 500 > /cgroup/test2/blkio.weight
- Create two same size files (say 512MB each) on same disk (file1, file2) and
launch two dd threads in different cgroup to read those files.
sync
echo 3 > /proc/sys/vm/drop_caches
dd if=/mnt/sdb/zerofile1 of=/dev/null &
echo $! > /cgroup/test1/tasks
cat /cgroup/test1/tasks
dd if=/mnt/sdb/zerofile2 of=/dev/null &
echo $! > /cgroup/test2/tasks
cat /cgroup/test2/tasks
- At macro level, first dd should finish first. To get more precise data, keep
on looking at (with the help of script), at blkio.disk_time and
blkio.disk_sectors files of both test1 and test2 groups. This will tell how
much disk time (in milli seconds), each group got and how many secotors each
group dispatched to the disk. We provide fairness in terms of disk time, so
ideally io.disk_time of cgroups should be in proportion to the weight.
Various user visible config options
===================================
CONFIG_CFQ_GROUP_IOSCHED
- Enables group scheduling in CFQ. Currently only 1 level of group
creation is allowed.
CONFIG_DEBUG_CFQ_IOSCHED
- Enables some debugging messages in blktrace. Also creates extra
cgroup file blkio.dequeue.
Config options selected automatically
=====================================
These config options are not user visible and are selected/deselected
automatically based on IO scheduler configuration.
CONFIG_BLK_CGROUP
- Block IO controller. Selected by CONFIG_CFQ_GROUP_IOSCHED.
CONFIG_DEBUG_BLK_CGROUP
- Debug help. Selected by CONFIG_DEBUG_CFQ_IOSCHED.
Details of cgroup files
=======================
- blkio.weight
- Specifies per cgroup weight.
Currently allowed range of weights is from 100 to 1000.
- blkio.time
- disk time allocated to cgroup per device in milliseconds. First
two fields specify the major and minor number of the device and
third field specifies the disk time allocated to group in
milliseconds.
- blkio.sectors
- number of sectors transferred to/from disk by the group. First
two fields specify the major and minor number of the device and
third field specifies the number of sectors transferred by the
group to/from the device.
- blkio.dequeue
- Debugging aid only enabled if CONFIG_DEBUG_CFQ_IOSCHED=y. This
gives the statistics about how many a times a group was dequeued
from service tree of the device. First two fields specify the major
and minor number of the device and third field specifies the number
of times a group was dequeued from a particular device.
CFQ sysfs tunable
=================
/sys/block/<disk>/queue/iosched/group_isolation
If group_isolation=1, it provides stronger isolation between groups at the
expense of throughput. By default group_isolation is 0. In general that
means that if group_isolation=0, expect fairness for sequential workload
only. Set group_isolation=1 to see fairness for random IO workload also.
Generally CFQ will put random seeky workload in sync-noidle category. CFQ
will disable idling on these queues and it does a collective idling on group
of such queues. Generally these are slow moving queues and if there is a
sync-noidle service tree in each group, that group gets exclusive access to
disk for certain period. That means it will bring the throughput down if
group does not have enough IO to drive deeper queue depths and utilize disk
capacity to the fullest in the slice allocated to it. But the flip side is
that even a random reader should get better latencies and overall throughput
if there are lots of sequential readers/sync-idle workload running in the
system.
If group_isolation=0, then CFQ automatically moves all the random seeky queues
in the root group. That means there will be no service differentiation for
that kind of workload. This leads to better throughput as we do collective
idling on root sync-noidle tree.
By default one should run with group_isolation=0. If that is not sufficient
and one wants stronger isolation between groups, then set group_isolation=1
but this will come at cost of reduced throughput.
What works
==========
- Currently only sync IO queues are support. All the buffered writes are
still system wide and not per group. Hence we will not see service
differentiation between buffered writes between groups.
Documentation/dontdiff
浏览文件 @ bcd6acd5
......@@ -65,6 +65,7 @@ aicdb.h*
asm-offsets.h
asm_offsets.h
autoconf.h*
av_permissions.h
bbootsect
bin2c
binkernel.spec
......@@ -95,12 +96,14 @@ docproc
elf2ecoff
elfconfig.h*
fixdep
flask.h
fore200e_mkfirm
fore200e_pca_fw.c*
gconf
gen-devlist
gen_crc32table
gen_init_cpio
genheaders
genksyms
*_gray256.c
ihex2fw
......
Documentation/fb/framebuffer.txt
浏览文件 @ bcd6acd5
......@@ -312,10 +312,8 @@ and to the following documentation:
8. Mailing list
---------------
There are several frame buffer device related mailing lists at SourceForge:
- linux-fbdev-announce@lists.sourceforge.net, for announcements,
- linux-fbdev-user@lists.sourceforge.net, for generic user support,
- linux-fbdev-devel@lists.sourceforge.net, for project developers.
There is a frame buffer device related mailing list at kernel.org:
linux-fbdev@vger.kernel.org.
Point your web browser to http://sourceforge.net/projects/linux-fbdev/ for
subscription information and archive browsing.
......
Documentation/feature-removal-schedule.txt
浏览文件 @ bcd6acd5
......@@ -6,6 +6,21 @@ be removed from this file.
---------------------------
What: USER_SCHED
When: 2.6.34
Why: USER_SCHED was implemented as a proof of concept for group scheduling.
The effect of USER_SCHED can already be achieved from userspace with
the help of libcgroup. The removal of USER_SCHED will also simplify
the scheduler code with the removal of one major ifdef. There are also
issues USER_SCHED has with USER_NS. A decision was taken not to fix
those and instead remove USER_SCHED. Also new group scheduling
features will not be implemented for USER_SCHED.
Who: Dhaval Giani <dhaval@linux.vnet.ibm.com>
---------------------------
What: PRISM54
When: 2.6.34
......@@ -302,18 +317,6 @@ Who: ocfs2-devel@oss.oracle.com
---------------------------
What: SCTP_GET_PEER_ADDRS_NUM_OLD, SCTP_GET_PEER_ADDRS_OLD,
SCTP_GET_LOCAL_ADDRS_NUM_OLD, SCTP_GET_LOCAL_ADDRS_OLD
When: June 2009
Why: A newer version of the options have been introduced in 2005 that
removes the limitions of the old API. The sctp library has been
converted to use these new options at the same time. Any user
space app that directly uses the old options should convert to using
the new options.
Who: Vlad Yasevich <vladislav.yasevich@hp.com>
---------------------------
What: Ability for non root users to shm_get hugetlb pages based on mlock
resource limits
When: 2.6.31
......@@ -404,15 +407,6 @@ Who: Alex Chiang <achiang@hp.com>
---------------------------
What: i2c-voodoo3 driver
When: October 2009
Why: Superseded by tdfxfb. I2C/DDC support used to live in a separate
driver but this caused driver conflicts.
Who: Jean Delvare <khali@linux-fr.org>
Krzysztof Helt <krzysztof.h1@wp.pl>
---------------------------
What: CONFIG_RFKILL_INPUT
When: 2.6.33
Why: Should be implemented in userspace, policy daemon.
......
Documentation/filesystems/caching/fscache.txt
浏览文件 @ bcd6acd5
......@@ -235,6 +235,7 @@ proc files.
neg=N Number of negative lookups made
pos=N Number of positive lookups made
crt=N Number of objects created by lookup
tmo=N Number of lookups timed out and requeued
Updates n=N Number of update cookie requests seen
nul=N Number of upd reqs given a NULL parent
run=N Number of upd reqs granted CPU time
......@@ -250,8 +251,10 @@ proc files.
ok=N Number of successful alloc reqs
wt=N Number of alloc reqs that waited on lookup completion
nbf=N Number of alloc reqs rejected -ENOBUFS
int=N Number of alloc reqs aborted -ERESTARTSYS
ops=N Number of alloc reqs submitted
owt=N Number of alloc reqs waited for CPU time
abt=N Number of alloc reqs aborted due to object death
Retrvls n=N Number of retrieval (read) requests seen
ok=N Number of successful retr reqs
wt=N Number of retr reqs that waited on lookup completion
......@@ -261,6 +264,7 @@ proc files.
oom=N Number of retr reqs failed -ENOMEM
ops=N Number of retr reqs submitted
owt=N Number of retr reqs waited for CPU time
abt=N Number of retr reqs aborted due to object death
Stores n=N Number of storage (write) requests seen
ok=N Number of successful store reqs
agn=N Number of store reqs on a page already pending storage
......@@ -268,12 +272,37 @@ proc files.
oom=N Number of store reqs failed -ENOMEM
ops=N Number of store reqs submitted
run=N Number of store reqs granted CPU time
pgs=N Number of pages given store req processing time
rxd=N Number of store reqs deleted from tracking tree
olm=N Number of store reqs over store limit
VmScan nos=N Number of release reqs against pages with no pending store
gon=N Number of release reqs against pages stored by time lock granted
bsy=N Number of release reqs ignored due to in-progress store
can=N Number of page stores cancelled due to release req
Ops pend=N Number of times async ops added to pending queues
run=N Number of times async ops given CPU time
enq=N Number of times async ops queued for processing
can=N Number of async ops cancelled
rej=N Number of async ops rejected due to object lookup/create failure
dfr=N Number of async ops queued for deferred release
rel=N Number of async ops released
gc=N Number of deferred-release async ops garbage collected
CacheOp alo=N Number of in-progress alloc_object() cache ops
luo=N Number of in-progress lookup_object() cache ops
luc=N Number of in-progress lookup_complete() cache ops
gro=N Number of in-progress grab_object() cache ops
upo=N Number of in-progress update_object() cache ops
dro=N Number of in-progress drop_object() cache ops
pto=N Number of in-progress put_object() cache ops
syn=N Number of in-progress sync_cache() cache ops
atc=N Number of in-progress attr_changed() cache ops
rap=N Number of in-progress read_or_alloc_page() cache ops
ras=N Number of in-progress read_or_alloc_pages() cache ops
alp=N Number of in-progress allocate_page() cache ops
als=N Number of in-progress allocate_pages() cache ops
wrp=N Number of in-progress write_page() cache ops
ucp=N Number of in-progress uncache_page() cache ops
dsp=N Number of in-progress dissociate_pages() cache ops
(*) /proc/fs/fscache/histogram
......@@ -299,6 +328,87 @@ proc files.
jiffy range covered, and the SECS field the equivalent number of seconds.
===========
OBJECT LIST
===========
If CONFIG_FSCACHE_OBJECT_LIST is enabled, the FS-Cache facility will maintain a
list of all the objects currently allocated and allow them to be viewed
through:
/proc/fs/fscache/objects
This will look something like:
[root@andromeda ~]# head /proc/fs/fscache/objects
OBJECT PARENT STAT CHLDN OPS OOP IPR EX READS EM EV F S | NETFS_COOKIE_DEF TY FL NETFS_DATA OBJECT_KEY, AUX_DATA
======== ======== ==== ===== === === === == ===== == == = = | ================ == == ================ ================
17e4b 2 ACTV 0 0 0 0 0 0 7b 4 0 8 | NFS.fh DT 0 ffff88001dd82820 010006017edcf8bbc93b43298fdfbe71e50b57b13a172c0117f38472, e567634700000000000000000000000063f2404a000000000000000000000000c9030000000000000000000063f2404a
1693a 2 ACTV 0 0 0 0 0 0 7b 4 0 8 | NFS.fh DT 0 ffff88002db23380 010006017edcf8bbc93b43298fdfbe71e50b57b1e0162c01a2df0ea6, 420ebc4a000000000000000000000000420ebc4a0000000000000000000000000e1801000000000000000000420ebc4a
where the first set of columns before the '|' describe the object:
COLUMN DESCRIPTION
======= ===============================================================
OBJECT Object debugging ID (appears as OBJ%x in some debug messages)
PARENT Debugging ID of parent object
STAT Object state
CHLDN Number of child objects of this object
OPS Number of outstanding operations on this object
OOP Number of outstanding child object management operations
IPR
EX Number of outstanding exclusive operations
READS Number of outstanding read operations
EM Object's event mask
EV Events raised on this object
F Object flags
S Object slow-work work item flags
and the second set of columns describe the object's cookie, if present:
COLUMN DESCRIPTION
=============== =======================================================
NETFS_COOKIE_DEF Name of netfs cookie definition
TY Cookie type (IX - index, DT - data, hex - special)
FL Cookie flags
NETFS_DATA Netfs private data stored in the cookie
OBJECT_KEY Object key } 1 column, with separating comma
AUX_DATA Object aux data } presence may be configured
The data shown may be filtered by attaching the a key to an appropriate keyring
before viewing the file. Something like:
keyctl add user fscache:objlist <restrictions> @s
where <restrictions> are a selection of the following letters:
K Show hexdump of object key (don't show if not given)
A Show hexdump of object aux data (don't show if not given)
and the following paired letters:
C Show objects that have a cookie
c Show objects that don't have a cookie
B Show objects that are busy
b Show objects that aren't busy
W Show objects that have pending writes
w Show objects that don't have pending writes
R Show objects that have outstanding reads
r Show objects that don't have outstanding reads
S Show objects that have slow work queued
s Show objects that don't have slow work queued
If neither side of a letter pair is given, then both are implied. For example:
keyctl add user fscache:objlist KB @s
shows objects that are busy, and lists their object keys, but does not dump
their auxiliary data. It also implies "CcWwRrSs", but as 'B' is given, 'b' is
not implied.
By default all objects and all fields will be shown.
=========
DEBUGGING
=========
......
Documentation/filesystems/caching/netfs-api.txt
浏览文件 @ bcd6acd5
......@@ -641,7 +641,7 @@ data file must be retired (see the relinquish cookie function below).
Furthermore, note that this does not cancel the asynchronous read or write
operation started by the read/alloc and write functions, so the page
invalidation and release functions must use:
invalidation functions must use:
bool fscache_check_page_write(struct fscache_cookie *cookie,
struct page *page);
......@@ -654,6 +654,25 @@ to see if a page is being written to the cache, and:
to wait for it to finish if it is.
When releasepage() is being implemented, a special FS-Cache function exists to
manage the heuristics of coping with vmscan trying to eject pages, which may
conflict with the cache trying to write pages to the cache (which may itself
need to allocate memory):
bool fscache_maybe_release_page(struct fscache_cookie *cookie,
struct page *page,
gfp_t gfp);
This takes the netfs cookie, and the page and gfp arguments as supplied to
releasepage(). It will return false if the page cannot be released yet for
some reason and if it returns true, the page has been uncached and can now be
released.
To make a page available for release, this function may wait for an outstanding
storage request to complete, or it may attempt to cancel the storage request -
in which case the page will not be stored in the cache this time.
==========================
INDEX AND DATA FILE UPDATE
==========================
......
Documentation/filesystems/proc.txt
浏览文件 @ bcd6acd5
......@@ -1072,7 +1072,8 @@ second). The meanings of the columns are as follows, from left to right:
- irq: servicing interrupts
- softirq: servicing softirqs
- steal: involuntary wait
- guest: running a guest
- guest: running a normal guest
- guest_nice: running a niced guest
The "intr" line gives counts of interrupts serviced since boot time, for each
of the possible system interrupts. The first column is the total of all
......
Documentation/i2c/busses/i2c-voodoo3 已删除 100644 → 0
浏览文件 @ 11c34c7d
Kernel driver i2c-voodoo3
Supported adapters:
* 3dfx Voodoo3 based cards
* Voodoo Banshee based cards
Authors:
Frodo Looijaard <frodol@dds.nl>,
Philip Edelbrock <phil@netroedge.com>,
Ralph Metzler <rjkm@thp.uni-koeln.de>,
Mark D. Studebaker <mdsxyz123@yahoo.com>
Main contact: Philip Edelbrock <phil@netroedge.com>
The code is based upon Ralph's test code (he did the hard stuff ;')
Description
-----------
The 3dfx Voodoo3 chip contains two I2C interfaces (aka a I2C 'master' or
'host').
The first interface is used for DDC (Data Display Channel) which is a
serial channel through the VGA monitor connector to a DDC-compliant
monitor. This interface is defined by the Video Electronics Standards
Association (VESA). The standards are available for purchase at
http://www.vesa.org .
The second interface is a general-purpose I2C bus. The intent by 3dfx was
to allow manufacturers to add extra chips to the video card such as a
TV-out chip such as the BT869 or possibly even I2C based temperature
sensors like the ADM1021 or LM75.
Stability
---------
Seems to be stable on the test machine, but needs more testing on other
machines. Simultaneous accesses of the DDC and I2C busses may cause errors.
Supported Devices
-----------------
Specifically, this driver was written and tested on the '3dfx Voodoo3 AGP
3000' which has a tv-out feature (s-video or composite). According to the
docs and discussions, this code should work for any Voodoo3 based cards as
well as Voodoo Banshee based cards. The DDC interface has been tested on a
Voodoo Banshee card.
Issues
------
Probably many, but it seems to work OK on my system. :')
External Device Connection
--------------------------
The digital video input jumpers give availability to the I2C bus.
Specifically, pins 13 and 25 (bottom row middle, and bottom right-end) are
the I2C clock and I2C data lines, respectively. +5V and GND are probably
also easily available making the addition of extra I2C/SMBus devices easy
to implement.
Documentation/i2c/i2c-stub
浏览文件 @ bcd6acd5
......@@ -2,9 +2,9 @@ MODULE: i2c-stub
DESCRIPTION:
This module is a very simple fake I2C/SMBus driver. It implements four
types of SMBus commands: write quick, (r/w) byte, (r/w) byte data, and
(r/w) word data.
This module is a very simple fake I2C/SMBus driver. It implements five
types of SMBus commands: write quick, (r/w) byte, (r/w) byte data, (r/w)
word data, and (r/w) I2C block data.
You need to provide chip addresses as a module parameter when loading this
driver, which will then only react to SMBus commands to these addresses.
......@@ -21,8 +21,8 @@ EEPROMs, among others.
The typical use-case is like this:
1. load this module
2. use i2cset (from lm_sensors project) to pre-load some data
3. load the target sensors chip driver module
2. use i2cset (from the i2c-tools project) to pre-load some data
3. load the target chip driver module
4. observe its behavior in the kernel log
There's a script named i2c-stub-from-dump in the i2c-tools package which
......@@ -33,6 +33,12 @@ PARAMETERS:
int chip_addr[10]:
The SMBus addresses to emulate chips at.
unsigned long functionality:
Functionality override, to disable some commands. See I2C_FUNC_*
constants in <linux/i2c.h> for the suitable values. For example,
value 0x1f0000 would only enable the quick, byte and byte data
commands.
CAVEATS:
If your target driver polls some byte or word waiting for it to change, the
......
Documentation/i2c/old-module-parameters 0 → 100644
浏览文件 @ bcd6acd5
I2C device driver binding control from user-space
=================================================
Up to kernel 2.6.32, many i2c drivers used helper macros provided by
<linux/i2c.h> which created standard module parameters to let the user
control how the driver would probe i2c buses and attach to devices. These
parameters were known as "probe" (to let the driver probe for an extra
address), "force" (to forcibly attach the driver to a given device) and
"ignore" (to prevent a driver from probing a given address).
With the conversion of the i2c subsystem to the standard device driver
binding model, it became clear that these per-module parameters were no
longer needed, and that a centralized implementation was possible. The new,
sysfs-based interface is described in the documentation file
"instantiating-devices", section "Method 4: Instantiate from user-space".
Below is a mapping from the old module parameters to the new interface.
Attaching a driver to an I2C device
-----------------------------------
Old method (module parameters):
# modprobe <driver> probe=1,0x2d
# modprobe <driver> force=1,0x2d
# modprobe <driver> force_<device>=1,0x2d
New method (sysfs interface):
# echo <device> 0x2d > /sys/bus/i2c/devices/i2c-1/new_device
Preventing a driver from attaching to an I2C device
---------------------------------------------------
Old method (module parameters):
# modprobe <driver> ignore=1,0x2f
New method (sysfs interface):
# echo dummy 0x2f > /sys/bus/i2c/devices/i2c-1/new_device
# modprobe <driver>
Of course, it is important to instantiate the "dummy" device before loading
the driver. The dummy device will be handled by i2c-core itself, preventing
other drivers from binding to it later on. If there is a real device at the
problematic address, and you want another driver to bind to it, then simply
pass the name of the device in question instead of "dummy".
Documentation/isdn/README.gigaset
浏览文件 @ bcd6acd5
......@@ -5,7 +5,7 @@ GigaSet 307x Device Driver
------------
1.1. Hardware
--------
This release supports the connection of the Gigaset 307x/417x family of
This driver supports the connection of the Gigaset 307x/417x family of
ISDN DECT bases via Gigaset M101 Data, Gigaset M105 Data or direct USB
connection. The following devices are reported to be compatible:
......@@ -33,7 +33,7 @@ GigaSet 307x Device Driver
http://gigaset307x.sourceforge.net/
We had also reports from users of Gigaset M105 who could use the drivers
with SX 100 and CX 100 ISDN bases (only in unimodem mode, see section 2.4.)
with SX 100 and CX 100 ISDN bases (only in unimodem mode, see section 2.5.)
If you have another device that works with our driver, please let us know.
Chances of getting an USB device to work are good if the output of
......@@ -49,7 +49,7 @@ GigaSet 307x Device Driver
--------
The driver works with ISDN4linux and so can be used with any software
which is able to use ISDN4linux for ISDN connections (voice or data).
CAPI4Linux support is planned but not yet available.
Experimental Kernel CAPI support is available as a compilation option.
There are some user space tools available at
http://sourceforge.net/projects/gigaset307x/
......@@ -102,20 +102,28 @@ GigaSet 307x Device Driver
2.3. ISDN4linux
----------
This is the "normal" mode of operation. After loading the module you can
set up the ISDN system just as you'd do with any ISDN card.
Your distribution should provide some configuration utility.
If not, you can use some HOWTOs like
set up the ISDN system just as you'd do with any ISDN card supported by
the ISDN4Linux subsystem. Most distributions provide some configuration
utility. If not, you can use some HOWTOs like
http://www.linuxhaven.de/dlhp/HOWTO/DE-ISDN-HOWTO-5.html
If this doesn't work, because you have some recent device like SX100 where
If this doesn't work, because you have some device like SX100 where
debug output (see section 3.2.) shows something like this when dialing
CMD Received: ERROR
Available Params: 0
Connection State: 0, Response: -1
gigaset_process_response: resp_code -1 in ConState 0 !
Timeout occurred
you might need to use unimodem mode:
you might need to use unimodem mode. (see section 2.5.)
2.4. Unimodem mode
2.4. CAPI
----
If the driver is compiled with CAPI support (kernel configuration option
GIGASET_CAPI, experimental) it can also be used with CAPI 2.0 kernel and
user space applications. ISDN4Linux is supported in this configuration
via the capidrv compatibility driver. The kernel module capidrv.ko must
be loaded explicitly ("modprobe capidrv") if needed.
2.5. Unimodem mode
-------------
This is needed for some devices [e.g. SX100] as they have problems with
the "normal" commands.
......@@ -160,7 +168,7 @@ GigaSet 307x Device Driver
configuration file like /etc/modprobe.conf.local,
using that should be preferred.
2.5. Call-ID (CID) mode
2.6. Call-ID (CID) mode
------------------
Call-IDs are numbers used to tag commands to, and responses from, the
Gigaset base in order to support the simultaneous handling of multiple
......@@ -188,7 +196,7 @@ GigaSet 307x Device Driver
You can also use /sys/class/tty/ttyGxy/cidmode for changing the CID mode
setting (ttyGxy is ttyGU0 or ttyGB0).
2.6. Unregistered Wireless Devices (M101/M105)
2.7. Unregistered Wireless Devices (M101/M105)
-----------------------------------------
The main purpose of the ser_gigaset and usb_gigaset drivers is to allow
the M101 and M105 wireless devices to be used as ISDN devices for ISDN
......@@ -228,7 +236,7 @@ GigaSet 307x Device Driver
You have two or more DECT data adapters (M101/M105) and only the
first one you turn on works.
Solution:
Select Unimodem mode for all DECT data adapters. (see section 2.4.)
Select Unimodem mode for all DECT data adapters. (see section 2.5.)
Problem:
Messages like this:
......@@ -236,7 +244,7 @@ GigaSet 307x Device Driver
appear in your syslog.
Solution:
Check whether your M10x wireless device is correctly registered to the
Gigaset base. (see section 2.6.)
Gigaset base. (see section 2.7.)
3.2. Telling the driver to provide more information
----------------------------------------------
......
Documentation/kernel-parameters.txt
浏览文件 @ bcd6acd5
......@@ -85,7 +85,6 @@ parameter is applicable:
PPT Parallel port support is enabled.
PS2 Appropriate PS/2 support is enabled.
RAM RAM disk support is enabled.
ROOTPLUG The example Root Plug LSM is enabled.
S390 S390 architecture is enabled.
SCSI Appropriate SCSI support is enabled.
A lot of drivers has their options described inside of
......@@ -345,6 +344,15 @@ and is between 256 and 4096 characters. It is defined in the file
Change the amount of debugging information output
when initialising the APIC and IO-APIC components.
show_lapic= [APIC,X86] Advanced Programmable Interrupt Controller
Limit apic dumping. The parameter defines the maximal
number of local apics being dumped. Also it is possible
to set it to "all" by meaning -- no limit here.
Format: { 1 (default) | 2 | ... | all }.
The parameter valid if only apic=debug or
apic=verbose is specified.
Example: apic=debug show_lapic=all
apm= [APM] Advanced Power Management
See header of arch/x86/kernel/apm_32.c.
......@@ -779,6 +787,13 @@ and is between 256 and 4096 characters. It is defined in the file
by the set_ftrace_notrace file in the debugfs
tracing directory.
ftrace_graph_filter=[function-list]
[FTRACE] Limit the top level callers functions traced
by the function graph tracer at boot up.
function-list is a comma separated list of functions
that can be changed at run time by the
set_graph_function file in the debugfs tracing directory.
gamecon.map[2|3]=
[HW,JOY] Multisystem joystick and NES/SNES/PSX pad
support via parallel port (up to 5 devices per port)
......@@ -2032,8 +2047,15 @@ and is between 256 and 4096 characters. It is defined in the file
print-fatal-signals=
[KNL] debug: print fatal signals
print-fatal-signals=1: print segfault info to
the kernel console.
If enabled, warn about various signal handling
related application anomalies: too many signals,
too many POSIX.1 timers, fatal signals causing a
coredump - etc.
If you hit the warning due to signal overflow,
you might want to try "ulimit -i unlimited".
default: off.
printk.time= Show timing data prefixed to each printk message line
......@@ -2164,15 +2186,6 @@ and is between 256 and 4096 characters. It is defined in the file
Useful for devices that are detected asynchronously
(e.g. USB and MMC devices).
root_plug.vendor_id=
[ROOTPLUG] Override the default vendor ID
root_plug.product_id=
[ROOTPLUG] Override the default product ID
root_plug.debug=
[ROOTPLUG] Enable debugging output
rw [KNL] Mount root device read-write on boot
S [KNL] Run init in single mode
......@@ -2182,6 +2195,8 @@ and is between 256 and 4096 characters. It is defined in the file
sbni= [NET] Granch SBNI12 leased line adapter
sched_debug [KNL] Enables verbose scheduler debug messages.
sc1200wdt= [HW,WDT] SC1200 WDT (watchdog) driver
Format: <io>[,<timeout>[,<isapnp>]]
......@@ -2590,6 +2605,9 @@ and is between 256 and 4096 characters. It is defined in the file
uart6850= [HW,OSS]
Format: <io>,<irq>
uhash_entries= [KNL,NET]
Set number of hash buckets for UDP/UDP-Lite connections
uhci-hcd.ignore_oc=
[USB] Ignore overcurrent events (default N).
Some badly-designed motherboards generate lots of
......@@ -2729,6 +2747,15 @@ and is between 256 and 4096 characters. It is defined in the file
Default is 1, i.e. UTF-8 mode is enabled for all
newly opened terminals.
vt.global_cursor_default=
[VT]
Format=<-1|0|1>
Set system-wide default for whether a cursor
is shown on new VTs. Default is -1,
i.e. cursors will be created by default unless
overridden by individual drivers. 0 will hide
cursors, 1 will display them.
waveartist= [HW,OSS]
Format: <io>,<irq>,<dma>,<dma2>
......
Documentation/kvm/api.txt
浏览文件 @ bcd6acd5
......@@ -593,6 +593,115 @@ struct kvm_irqchip {
} chip;
};
4.27 KVM_XEN_HVM_CONFIG
Capability: KVM_CAP_XEN_HVM
Architectures: x86
Type: vm ioctl
Parameters: struct kvm_xen_hvm_config (in)
Returns: 0 on success, -1 on error
Sets the MSR that the Xen HVM guest uses to initialize its hypercall
page, and provides the starting address and size of the hypercall
blobs in userspace. When the guest writes the MSR, kvm copies one
page of a blob (32- or 64-bit, depending on the vcpu mode) to guest
memory.
struct kvm_xen_hvm_config {
__u32 flags;
__u32 msr;
__u64 blob_addr_32;
__u64 blob_addr_64;
__u8 blob_size_32;
__u8 blob_size_64;
__u8 pad2[30];
};
4.27 KVM_GET_CLOCK
Capability: KVM_CAP_ADJUST_CLOCK
Architectures: x86
Type: vm ioctl
Parameters: struct kvm_clock_data (out)
Returns: 0 on success, -1 on error
Gets the current timestamp of kvmclock as seen by the current guest. In
conjunction with KVM_SET_CLOCK, it is used to ensure monotonicity on scenarios
such as migration.
struct kvm_clock_data {
__u64 clock; /* kvmclock current value */
__u32 flags;
__u32 pad[9];
};
4.28 KVM_SET_CLOCK
Capability: KVM_CAP_ADJUST_CLOCK
Architectures: x86
Type: vm ioctl
Parameters: struct kvm_clock_data (in)
Returns: 0 on success, -1 on error
Sets the current timestamp of kvmclock to the valued specific in its parameter.
In conjunction with KVM_GET_CLOCK, it is used to ensure monotonicity on scenarios
such as migration.
struct kvm_clock_data {
__u64 clock; /* kvmclock current value */
__u32 flags;
__u32 pad[9];
};
4.29 KVM_GET_VCPU_EVENTS
Capability: KVM_CAP_VCPU_EVENTS
Architectures: x86
Type: vm ioctl
Parameters: struct kvm_vcpu_event (out)
Returns: 0 on success, -1 on error
Gets currently pending exceptions, interrupts, and NMIs as well as related
states of the vcpu.
struct kvm_vcpu_events {
struct {
__u8 injected;
__u8 nr;
__u8 has_error_code;
__u8 pad;
__u32 error_code;
} exception;
struct {
__u8 injected;
__u8 nr;
__u8 soft;
__u8 pad;
} interrupt;
struct {
__u8 injected;
__u8 pending;
__u8 masked;
__u8 pad;
} nmi;
__u32 sipi_vector;
__u32 flags; /* must be zero */
};
4.30 KVM_SET_VCPU_EVENTS
Capability: KVM_CAP_VCPU_EVENTS
Architectures: x86
Type: vm ioctl
Parameters: struct kvm_vcpu_event (in)
Returns: 0 on success, -1 on error
Set pending exceptions, interrupts, and NMIs as well as related states of the
vcpu.
See KVM_GET_VCPU_EVENTS for the data structure.
5. The kvm_run structure
Application code obtains a pointer to the kvm_run structure by
......
Documentation/networking/bonding.txt
浏览文件 @ bcd6acd5
Linux Ethernet Bonding Driver HOWTO
Latest update: 12 November 2007
Latest update: 23 September 2009
Initial release : Thomas Davis <tadavis at lbl.gov>
Corrections, HA extensions : 2000/10/03-15 :
......@@ -614,6 +614,46 @@ primary
The primary option is only valid for active-backup mode.
primary_reselect
Specifies the reselection policy for the primary slave. This
affects how the primary slave is chosen to become the active slave
when failure of the active slave or recovery of the primary slave
occurs. This option is designed to prevent flip-flopping between
the primary slave and other slaves. Possible values are:
always or 0 (default)
The primary slave becomes the active slave whenever it
comes back up.
better or 1
The primary slave becomes the active slave when it comes
back up, if the speed and duplex of the primary slave is
better than the speed and duplex of the current active
slave.
failure or 2
The primary slave becomes the active slave only if the
current active slave fails and the primary slave is up.
The primary_reselect setting is ignored in two cases:
If no slaves are active, the first slave to recover is
made the active slave.
When initially enslaved, the primary slave is always made
the active slave.
Changing the primary_reselect policy via sysfs will cause an
immediate selection of the best active slave according to the new
policy. This may or may not result in a change of the active
slave, depending upon the circumstances.
This option was added for bonding version 3.6.0.
updelay
Specifies the time, in milliseconds, to wait before enabling a
......
Documentation/networking/ip-sysctl.txt
浏览文件 @ bcd6acd5
......@@ -164,6 +164,14 @@ tcp_congestion_control - STRING
additional choices may be available based on kernel configuration.
Default is set as part of kernel configuration.
tcp_cookie_size - INTEGER
Default size of TCP Cookie Transactions (TCPCT) option, that may be
overridden on a per socket basis by the TCPCT socket option.
Values greater than the maximum (16) are interpreted as the maximum.
Values greater than zero and less than the minimum (8) are interpreted
as the minimum. Odd values are interpreted as the next even value.
Default: 0 (off).
tcp_dsack - BOOLEAN
Allows TCP to send "duplicate" SACKs.
......@@ -723,6 +731,12 @@ accept_source_route - BOOLEAN
default TRUE (router)
FALSE (host)
accept_local - BOOLEAN
Accept packets with local source addresses. In combination with
suitable routing, this can be used to direct packets between two
local interfaces over the wire and have them accepted properly.
default FALSE
rp_filter - INTEGER
0 - No source validation.
1 - Strict mode as defined in RFC3704 Strict Reverse Path
......@@ -738,8 +752,8 @@ rp_filter - INTEGER
to prevent IP spoofing from DDos attacks. If using asymmetric routing
or other complicated routing, then loose mode is recommended.
conf/all/rp_filter must also be set to non-zero to do source validation
on the interface
The max value from conf/{all,interface}/rp_filter is used
when doing source validation on the {interface}.
Default value is 0. Note that some distributions enable it
in startup scripts.
......@@ -1086,6 +1100,24 @@ accept_dad - INTEGER
2: Enable DAD, and disable IPv6 operation if MAC-based duplicate
link-local address has been found.
force_tllao - BOOLEAN
Enable sending the target link-layer address option even when
responding to a unicast neighbor solicitation.
Default: FALSE
Quoting from RFC 2461, section 4.4, Target link-layer address:
"The option MUST be included for multicast solicitations in order to
avoid infinite Neighbor Solicitation "recursion" when the peer node
does not have a cache entry to return a Neighbor Advertisements
message. When responding to unicast solicitations, the option can be
omitted since the sender of the solicitation has the correct link-
layer address; otherwise it would not have be able to send the unicast
solicitation in the first place. However, including the link-layer
address in this case adds little overhead and eliminates a potential
race condition where the sender deletes the cached link-layer address
prior to receiving a response to a previous solicitation."
icmp/*:
ratelimit - INTEGER
Limit the maximal rates for sending ICMPv6 packets.
......
Documentation/pcmcia/driver-changes.txt
浏览文件 @ bcd6acd5
This file details changes in 2.6 which affect PCMCIA card driver authors:
* no cs_error / CS_CHECK / CONFIG_PCMCIA_DEBUG (as of 2.6.33)
Instead of the cs_error() callback or the CS_CHECK() macro, please use
Linux-style checking of return values, and -- if necessary -- debug
messages using "dev_dbg()" or "pr_debug()".
* New CIS tuple access (as of 2.6.33)
Instead of pcmcia_get_{first,next}_tuple(), pcmcia_get_tuple_data() and
pcmcia_parse_tuple(), a driver shall use "pcmcia_get_tuple()" if it is
only interested in one (raw) tuple, or "pcmcia_loop_tuple()" if it is
interested in all tuples of one type. To decode the MAC from CISTPL_FUNCE,
a new helper "pcmcia_get_mac_from_cis()" was added.
* New configuration loop helper (as of 2.6.28)
By calling pcmcia_loop_config(), a driver can iterate over all available
configuration options. During a driver's probe() phase, one doesn't need
......
Documentation/power/runtime_pm.txt
浏览文件 @ bcd6acd5
......@@ -38,7 +38,7 @@ struct dev_pm_ops {
...
int (*runtime_suspend)(struct device *dev);
int (*runtime_resume)(struct device *dev);
void (*runtime_idle)(struct device *dev);
int (*runtime_idle)(struct device *dev);
...
};
......@@ -71,9 +71,9 @@ what to do to handle the device).
purpose).
In particular, if the driver requires remote wakeup capability for proper
functioning and device_may_wakeup() returns 'false' for the device, then
functioning and device_run_wake() returns 'false' for the device, then
->runtime_suspend() should return -EBUSY. On the other hand, if
device_may_wakeup() returns 'true' for the device and the device is put
device_run_wake() returns 'true' for the device and the device is put
into a low power state during the execution of its bus type's
->runtime_suspend(), it is expected that remote wake-up (i.e. hardware mechanism
allowing the device to request a change of its power state, such as PCI PME)
......@@ -114,7 +114,8 @@ The action performed by a bus type's ->runtime_idle() callback is totally
dependent on the bus type in question, but the expected and recommended action
is to check if the device can be suspended (i.e. if all of the conditions
necessary for suspending the device are satisfied) and to queue up a suspend
request for the device in that case.
request for the device in that case. The value returned by this callback is
ignored by the PM core.
The helper functions provided by the PM core, described in Section 4, guarantee
that the following constraints are met with respect to the bus type's run-time
......@@ -214,6 +215,9 @@ defined in include/linux/pm.h:
being executed for that device and it is not practical to wait for the
suspend to complete; means "start a resume as soon as you've suspended"
unsigned int run_wake;
- set if the device is capable of generating run-time wake-up events
enum rpm_status runtime_status;
- the run-time PM status of the device; this field's initial value is
RPM_SUSPENDED, which means that each device is initially regarded by the
......
Documentation/powerpc/dts-bindings/fsl/mpc5200.txt
浏览文件 @ bcd6acd5
......@@ -193,3 +193,13 @@ External interrupts:
external irq3: interrupts = <1 3 n>;
'n' is sense (0: level high, 1: edge rising, 2: edge falling 3: level low)
fsl,mpc5200-mscan nodes
-----------------------
In addition to the required compatible-, reg- and interrupt-properites, you can
also specify which clock source shall be used for the controller:
- fsl,mscan-clock-source- a string describing the clock source. Valid values
are: "ip" for ip bus clock
"ref" for reference clock (XTAL)
"ref" is default in case this property is not
present.
Documentation/slow-work.txt
浏览文件 @ bcd6acd5
......@@ -41,6 +41,13 @@ expand files, provided the time taken to do so isn't too long.
Operations of both types may sleep during execution, thus tying up the thread
loaned to it.
A further class of work item is available, based on the slow work item class:
(*) Delayed slow work items.
These are slow work items that have a timer to defer queueing of the item for
a while.
THREAD-TO-CLASS ALLOCATION
--------------------------
......@@ -64,9 +71,11 @@ USING SLOW WORK ITEMS
Firstly, a module or subsystem wanting to make use of slow work items must
register its interest:
int ret = slow_work_register_user();
int ret = slow_work_register_user(struct module *module);
This will return 0 if successful, or a -ve error upon failure.
This will return 0 if successful, or a -ve error upon failure. The module
pointer should be the module interested in using this facility (almost
certainly THIS_MODULE).
Slow work items may then be set up by:
......@@ -91,6 +100,10 @@ Slow work items may then be set up by:
slow_work_init(&myitem, &myitem_ops);
or:
delayed_slow_work_init(&myitem, &myitem_ops);
or:
vslow_work_init(&myitem, &myitem_ops);
......@@ -102,15 +115,92 @@ A suitably set up work item can then be enqueued for processing:
int ret = slow_work_enqueue(&myitem);
This will return a -ve error if the thread pool is unable to gain a reference
on the item, 0 otherwise.
on the item, 0 otherwise, or (for delayed work):
int ret = delayed_slow_work_enqueue(&myitem, my_jiffy_delay);
The items are reference counted, so there ought to be no need for a flush
operation. When all a module's slow work items have been processed, and the
operation. But as the reference counting is optional, means to cancel
existing work items are also included:
cancel_slow_work(&myitem);
cancel_delayed_slow_work(&myitem);
can be used to cancel pending work. The above cancel function waits for
existing work to have been executed (or prevent execution of them, depending
on timing).
When all a module's slow work items have been processed, and the
module has no further interest in the facility, it should unregister its
interest:
slow_work_unregister_user();
slow_work_unregister_user(struct module *module);
The module pointer is used to wait for all outstanding work items for that
module before completing the unregistration. This prevents the put_ref() code
from being taken away before it completes. module should almost certainly be
THIS_MODULE.
================
HELPER FUNCTIONS
================
The slow-work facility provides a function by which it can be determined
whether or not an item is queued for later execution:
bool queued = slow_work_is_queued(struct slow_work *work);
If it returns false, then the item is not on the queue (it may be executing
with a requeue pending). This can be used to work out whether an item on which
another depends is on the queue, thus allowing a dependent item to be queued
after it.
If the above shows an item on which another depends not to be queued, then the
owner of the dependent item might need to wait. However, to avoid locking up
the threads unnecessarily be sleeping in them, it can make sense under some
circumstances to return the work item to the queue, thus deferring it until
some other items have had a chance to make use of the yielded thread.
To yield a thread and defer an item, the work function should simply enqueue
the work item again and return. However, this doesn't work if there's nothing
actually on the queue, as the thread just vacated will jump straight back into
the item's work function, thus busy waiting on a CPU.
Instead, the item should use the thread to wait for the dependency to go away,
but rather than using schedule() or schedule_timeout() to sleep, it should use
the following function:
bool requeue = slow_work_sleep_till_thread_needed(
struct slow_work *work,
signed long *_timeout);
This will add a second wait and then sleep, such that it will be woken up if
either something appears on the queue that could usefully make use of the
thread - and behind which this item can be queued, or if the event the caller
set up to wait for happens. True will be returned if something else appeared
on the queue and this work function should perhaps return, of false if
something else woke it up. The timeout is as for schedule_timeout().
For example:
wq = bit_waitqueue(&my_flags, MY_BIT);
init_wait(&wait);
requeue = false;
do {
prepare_to_wait(wq, &wait, TASK_UNINTERRUPTIBLE);
if (!test_bit(MY_BIT, &my_flags))
break;
requeue = slow_work_sleep_till_thread_needed(&my_work,
&timeout);
} while (timeout > 0 && !requeue);
finish_wait(wq, &wait);
if (!test_bit(MY_BIT, &my_flags)
goto do_my_thing;
if (requeue)
return; // to slow_work
===============
......@@ -118,7 +208,8 @@ ITEM OPERATIONS
===============
Each work item requires a table of operations of type struct slow_work_ops.
All members are required:
Only ->execute() is required; the getting and putting of a reference and the
describing of an item are all optional.
(*) Get a reference on an item:
......@@ -148,6 +239,16 @@ All members are required:
This should perform the work required of the item. It may sleep, it may
perform disk I/O and it may wait for locks.
(*) View an item through /proc:
void (*desc)(struct slow_work *work, struct seq_file *m);
If supplied, this should print to 'm' a small string describing the work
the item is to do. This should be no more than about 40 characters, and
shouldn't include a newline character.
See the 'Viewing executing and queued items' section below.
==================
POOL CONFIGURATION
......@@ -172,3 +273,50 @@ The slow-work thread pool has a number of configurables:
is bounded to between 1 and one fewer than the number of active threads.
This ensures there is always at least one thread that can process very
slow work items, and always at least one thread that won't.
==================================
VIEWING EXECUTING AND QUEUED ITEMS
==================================
If CONFIG_SLOW_WORK_DEBUG is enabled, a debugfs file is made available:
/sys/kernel/debug/slow_work/runqueue
through which the list of work items being executed and the queues of items to
be executed may be viewed. The owner of a work item is given the chance to
add some information of its own.
The contents look something like the following:
THR PID ITEM ADDR FL MARK DESC
=== ===== ================ == ===== ==========
0 3005 ffff880023f52348 a 952ms FSC: OBJ17d3: LOOK
1 3006 ffff880024e33668 2 160ms FSC: OBJ17e5 OP60d3b: Write1/Store fl=2
2 3165 ffff8800296dd180 a 424ms FSC: OBJ17e4: LOOK
3 4089 ffff8800262c8d78 a 212ms FSC: OBJ17ea: CRTN
4 4090 ffff88002792bed8 2 388ms FSC: OBJ17e8 OP60d36: Write1/Store fl=2
5 4092 ffff88002a0ef308 2 388ms FSC: OBJ17e7 OP60d2e: Write1/Store fl=2
6 4094 ffff88002abaf4b8 2 132ms FSC: OBJ17e2 OP60d4e: Write1/Store fl=2
7 4095 ffff88002bb188e0 a 388ms FSC: OBJ17e9: CRTN
vsq - ffff880023d99668 1 308ms FSC: OBJ17e0 OP60f91: Write1/EnQ fl=2
vsq - ffff8800295d1740 1 212ms FSC: OBJ16be OP4d4b6: Write1/EnQ fl=2
vsq - ffff880025ba3308 1 160ms FSC: OBJ179a OP58dec: Write1/EnQ fl=2
vsq - ffff880024ec83e0 1 160ms FSC: OBJ17ae OP599f2: Write1/EnQ fl=2
vsq - ffff880026618e00 1 160ms FSC: OBJ17e6 OP60d33: Write1/EnQ fl=2
vsq - ffff880025a2a4b8 1 132ms FSC: OBJ16a2 OP4d583: Write1/EnQ fl=2
vsq - ffff880023cbe6d8 9 212ms FSC: OBJ17eb: LOOK
vsq - ffff880024d37590 9 212ms FSC: OBJ17ec: LOOK
vsq - ffff880027746cb0 9 212ms FSC: OBJ17ed: LOOK
vsq - ffff880024d37ae8 9 212ms FSC: OBJ17ee: LOOK
vsq - ffff880024d37cb0 9 212ms FSC: OBJ17ef: LOOK
vsq - ffff880025036550 9 212ms FSC: OBJ17f0: LOOK
vsq - ffff8800250368e0 9 212ms FSC: OBJ17f1: LOOK
vsq - ffff880025036aa8 9 212ms FSC: OBJ17f2: LOOK
In the 'THR' column, executing items show the thread they're occupying and
queued threads indicate which queue they're on. 'PID' shows the process ID of
a slow-work thread that's executing something. 'FL' shows the work item flags.
'MARK' indicates how long since an item was queued or began executing. Lastly,
the 'DESC' column permits the owner of an item to give some information.
Documentation/sound/alsa/ALSA-Configuration.txt
浏览文件 @ bcd6acd5
......@@ -798,6 +798,9 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
setup before initializing the codecs. This option is
available only when CONFIG_SND_HDA_PATCH_LOADER=y is set.
See HD-Audio.txt for details.
beep_mode - Selects the beep registration mode (0=off, 1=on, 2=
dynamic registration via mute switch on/off); the default
value is set via CONFIG_SND_HDA_INPUT_BEEP_MODE kconfig.
[Single (global) options]
single_cmd - Use single immediate commands to communicate with
......@@ -1454,6 +1457,7 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
Module for internal PC-Speaker.
nopcm - Disable PC-Speaker PCM sound. Only beeps remain.
nforce_wa - enable NForce chipset workaround. Expect bad sound.
This module supports system beeps, some kind of PCM playback and
......@@ -1631,7 +1635,7 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
Module snd-sscape
-----------------
Module for ENSONIQ SoundScape PnP cards.
Module for ENSONIQ SoundScape cards.
port - Port # (PnP setup)
wss_port - WSS Port # (PnP setup)
......@@ -1639,10 +1643,11 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
mpu_irq - MPU-401 IRQ # (PnP setup)
dma - DMA # (PnP setup)
dma2 - 2nd DMA # (PnP setup, -1 to disable)
joystick - Enable gameport - 0 = disable (default), 1 = enable
This module supports multiple cards.
This module supports multiple cards. ISA PnP must be enabled.
You need sscape_ctl tool in alsa-tools package for loading
the microcode.
The driver requires the firmware loader support on kernel.
Module snd-sun-amd7930 (on sparc only)
--------------------------------------
......
Documentation/sound/alsa/ControlNames.txt
浏览文件 @ bcd6acd5
......@@ -18,8 +18,9 @@ SOURCE:
Master
Master Mono
Hardware Master
Speaker (internal speaker)
Headphone
PC Speaker
Beep (beep generator)
Phone
Phone Input
Phone Output
......
Documentation/sound/alsa/HD-Audio-Models.txt
浏览文件 @ bcd6acd5
......@@ -391,6 +391,7 @@ STAC92HD83*
ref Reference board
mic-ref Reference board with power management for ports
dell-s14 Dell laptop
hp HP laptops with (inverted) mute-LED
auto BIOS setup (default)
STAC9872
......
Documentation/sysctl/ctl_unnumbered.txt 已删除 100644 → 0
浏览文件 @ 11c34c7d
Except for a few extremely rare exceptions user space applications do not use
the binary sysctl interface. Instead everyone uses /proc/sys/... with
readable ascii names.
Recently the kernel has started supporting setting the binary sysctl value to
CTL_UNNUMBERED so we no longer need to assign a binary sysctl path to allow
sysctls to show up in /proc/sys.
Assigning binary sysctl numbers is an endless source of conflicts in sysctl.h,
breaking of the user space ABI (because of those conflicts), and maintenance
problems. A complete pass through all of the sysctl users revealed multiple
instances where the sysctl binary interface was broken and had gone undetected
for years.
So please do not add new binary sysctl numbers. They are unneeded and
problematic.
If you really need a new binary sysctl number please first merge your sysctl
into the kernel and then as a separate patch allocate a binary sysctl number.
(ebiederm@xmission.com, June 2007)
Documentation/trace/ftrace-design.txt
浏览文件 @ bcd6acd5
......@@ -213,10 +213,19 @@ If you can't trace NMI functions, then skip this option.
<details to be filled>
HAVE_FTRACE_SYSCALLS
HAVE_SYSCALL_TRACEPOINTS
---------------------
<details to be filled>
You need very few things to get the syscalls tracing in an arch.
- Have a NR_syscalls variable in <asm/unistd.h> that provides the number
of syscalls supported by the arch.
- Implement arch_syscall_addr() that resolves a syscall address from a
syscall number.
- Support the TIF_SYSCALL_TRACEPOINT thread flags
- Put the trace_sys_enter() and trace_sys_exit() tracepoints calls from ptrace
in the ptrace syscalls tracing path.
- Tag this arch as HAVE_SYSCALL_TRACEPOINTS.
HAVE_FTRACE_MCOUNT_RECORD
......
Documentation/trace/kprobetrace.txt 0 → 100644
浏览文件 @ bcd6acd5
Kprobe-based Event Tracing
==========================
Documentation is written by Masami Hiramatsu
Overview
--------
These events are similar to tracepoint based events. Instead of Tracepoint,
this is based on kprobes (kprobe and kretprobe). So it can probe wherever
kprobes can probe (this means, all functions body except for __kprobes
functions). Unlike the Tracepoint based event, this can be added and removed
dynamically, on the fly.
To enable this feature, build your kernel with CONFIG_KPROBE_TRACING=y.
Similar to the events tracer, this doesn't need to be activated via
current_tracer. Instead of that, add probe points via
/sys/kernel/debug/tracing/kprobe_events, and enable it via
/sys/kernel/debug/tracing/events/kprobes/<EVENT>/enabled.
Synopsis of kprobe_events
-------------------------
p[:[GRP/]EVENT] SYMBOL[+offs]|MEMADDR [FETCHARGS] : Set a probe
r[:[GRP/]EVENT] SYMBOL[+0] [FETCHARGS] : Set a return probe
GRP : Group name. If omitted, use "kprobes" for it.
EVENT : Event name. If omitted, the event name is generated
based on SYMBOL+offs or MEMADDR.
SYMBOL[+offs] : Symbol+offset where the probe is inserted.
MEMADDR : Address where the probe is inserted.
FETCHARGS : Arguments. Each probe can have up to 128 args.
%REG : Fetch register REG
@ADDR : Fetch memory at ADDR (ADDR should be in kernel)
@SYM[+|-offs] : Fetch memory at SYM +|- offs (SYM should be a data symbol)
$stackN : Fetch Nth entry of stack (N >= 0)
$stack : Fetch stack address.
$argN : Fetch function argument. (N >= 0)(*)
$retval : Fetch return value.(**)
+|-offs(FETCHARG) : Fetch memory at FETCHARG +|- offs address.(***)
NAME=FETCHARG: Set NAME as the argument name of FETCHARG.
(*) aN may not correct on asmlinkaged functions and at the middle of
function body.
(**) only for return probe.
(***) this is useful for fetching a field of data structures.
Per-Probe Event Filtering
-------------------------
Per-probe event filtering feature allows you to set different filter on each
probe and gives you what arguments will be shown in trace buffer. If an event
name is specified right after 'p:' or 'r:' in kprobe_events, it adds an event
under tracing/events/kprobes/<EVENT>, at the directory you can see 'id',
'enabled', 'format' and 'filter'.
enabled:
You can enable/disable the probe by writing 1 or 0 on it.
format:
This shows the format of this probe event.
filter:
You can write filtering rules of this event.
id:
This shows the id of this probe event.
Event Profiling
---------------
You can check the total number of probe hits and probe miss-hits via
/sys/kernel/debug/tracing/kprobe_profile.
The first column is event name, the second is the number of probe hits,
the third is the number of probe miss-hits.
Usage examples
--------------
To add a probe as a new event, write a new definition to kprobe_events
as below.
echo p:myprobe do_sys_open dfd=$arg0 filename=$arg1 flags=$arg2 mode=$arg3 > /sys/kernel/debug/tracing/kprobe_events
This sets a kprobe on the top of do_sys_open() function with recording
1st to 4th arguments as "myprobe" event. As this example shows, users can
choose more familiar names for each arguments.
echo r:myretprobe do_sys_open $retval >> /sys/kernel/debug/tracing/kprobe_events
This sets a kretprobe on the return point of do_sys_open() function with
recording return value as "myretprobe" event.
You can see the format of these events via
/sys/kernel/debug/tracing/events/kprobes/<EVENT>/format.
cat /sys/kernel/debug/tracing/events/kprobes/myprobe/format
name: myprobe
ID: 75
format:
field:unsigned short common_type; offset:0; size:2;
field:unsigned char common_flags; offset:2; size:1;
field:unsigned char common_preempt_count; offset:3; size:1;
field:int common_pid; offset:4; size:4;
field:int common_tgid; offset:8; size:4;
field: unsigned long ip; offset:16;tsize:8;
field: int nargs; offset:24;tsize:4;
field: unsigned long dfd; offset:32;tsize:8;
field: unsigned long filename; offset:40;tsize:8;
field: unsigned long flags; offset:48;tsize:8;
field: unsigned long mode; offset:56;tsize:8;
print fmt: "(%lx) dfd=%lx filename=%lx flags=%lx mode=%lx", REC->ip, REC->dfd, REC->filename, REC->flags, REC->mode
You can see that the event has 4 arguments as in the expressions you specified.
echo > /sys/kernel/debug/tracing/kprobe_events
This clears all probe points.
Right after definition, each event is disabled by default. For tracing these
events, you need to enable it.
echo 1 > /sys/kernel/debug/tracing/events/kprobes/myprobe/enable
echo 1 > /sys/kernel/debug/tracing/events/kprobes/myretprobe/enable
And you can see the traced information via /sys/kernel/debug/tracing/trace.
cat /sys/kernel/debug/tracing/trace
# tracer: nop
#
# TASK-PID CPU# TIMESTAMP FUNCTION
# | | | | |
<...>-1447 [001] 1038282.286875: myprobe: (do_sys_open+0x0/0xd6) dfd=3 filename=7fffd1ec4440 flags=8000 mode=0
<...>-1447 [001] 1038282.286878: myretprobe: (sys_openat+0xc/0xe <- do_sys_open) $retval=fffffffffffffffe
<...>-1447 [001] 1038282.286885: myprobe: (do_sys_open+0x0/0xd6) dfd=ffffff9c filename=40413c flags=8000 mode=1b6
<...>-1447 [001] 1038282.286915: myretprobe: (sys_open+0x1b/0x1d <- do_sys_open) $retval=3
<...>-1447 [001] 1038282.286969: myprobe: (do_sys_open+0x0/0xd6) dfd=ffffff9c filename=4041c6 flags=98800 mode=10
<...>-1447 [001] 1038282.286976: myretprobe: (sys_open+0x1b/0x1d <- do_sys_open) $retval=3
Each line shows when the kernel hits an event, and <- SYMBOL means kernel
returns from SYMBOL(e.g. "sys_open+0x1b/0x1d <- do_sys_open" means kernel
returns from do_sys_open to sys_open+0x1b).
MAINTAINERS
浏览文件 @ bcd6acd5
......@@ -512,10 +512,32 @@ W: http://www.arm.linux.org.uk/
S: Maintained
F: arch/arm/
ARM PRIMECELL AACI PL041 DRIVER
M: Russell King <linux@arm.linux.org.uk>
S: Maintained
F: sound/arm/aaci.*
ARM PRIMECELL CLCD PL110 DRIVER
M: Russell King <linux@arm.linux.org.uk>
S: Maintained
F: drivers/video/amba-clcd.*
ARM PRIMECELL KMI PL050 DRIVER
M: Russell King <linux@arm.linux.org.uk>
S: Maintained
F: drivers/input/serio/ambakmi.*
F: include/linux/amba/kmi.h
ARM PRIMECELL MMCI PL180/1 DRIVER
S: Orphan
F: drivers/mmc/host/mmci.*
ARM PRIMECELL BUS SUPPORT
M: Russell King <linux@arm.linux.org.uk>
S: Maintained
F: drivers/amba/
F: include/linux/amba/bus.h
ARM/ADI ROADRUNNER MACHINE SUPPORT
M: Lennert Buytenhek <kernel@wantstofly.org>
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
......@@ -637,6 +659,9 @@ ARM/FREESCALE IMX / MXC ARM ARCHITECTURE
M: Sascha Hauer <kernel@pengutronix.de>
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
S: Maintained
T: git://git.pengutronix.de/git/imx/linux-2.6.git
F: arch/arm/mach-mx*/
F: arch/arm/plat-mxc/
ARM/GLOMATION GESBC9312SX MACHINE SUPPORT
M: Lennert Buytenhek <kernel@wantstofly.org>
......@@ -707,6 +732,19 @@ L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
S: Maintained
F: arch/arm/mach-ixp4xx/
ARM/INTEL RESEARCH IMOTE 2 MACHINE SUPPORT
M: Jonathan Cameron <jic23@cam.ac.uk>
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
S: Maintained
F: arch/arm/mach-pxa/imote2.c
ARM/INTEL RESEARCH STARGATE 2 MACHINE SUPPORT
M: Jonathan Cameron <jic23@cam.ac.uk>
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
S: Maintained
F: arch/arm/mach-pxa/stargate2.c
F: drivers/pcmcia/pxa2xx_stargate2.c
ARM/INTEL XSC3 (MANZANO) ARM CORE
M: Lennert Buytenhek <kernel@wantstofly.org>
M: Dan Williams <dan.j.williams@intel.com>
......@@ -749,6 +787,14 @@ ARM/NEC MOBILEPRO 900/c MACHINE SUPPORT
M: Michael Petchkovsky <mkpetch@internode.on.net>
S: Maintained
ARM/NOMADIK ARCHITECTURE
M: Alessandro Rubini <rubini@unipv.it>
M: STEricsson <STEricsson_nomadik_linux@list.st.com>
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
S: Maintained
F: arch/arm/mach-nomadik/
F: arch/arm/plat-nomadik/
ARM/OPENMOKO NEO FREERUNNER (GTA02) MACHINE SUPPORT
M: Nelson Castillo <arhuaco@freaks-unidos.net>
L: openmoko-kernel@lists.openmoko.org (subscribers-only)
......@@ -893,6 +939,12 @@ L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
W: http://www.mcuos.com
S: Maintained
ARM/U8500 ARM ARCHITECTURE
M: Srinidhi Kasagar <srinidhi.kasagar@stericsson.com>
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
S: Maintained
F: arch/arm/mach-ux500/
ARM/VFP SUPPORT
M: Russell King <linux@arm.linux.org.uk>
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
......@@ -1027,7 +1079,7 @@ F: drivers/serial/atmel_serial.c
ATMEL LCDFB DRIVER
M: Nicolas Ferre <nicolas.ferre@atmel.com>
L: linux-fbdev-devel@lists.sourceforge.net (moderated for non-subscribers)
L: linux-fbdev@vger.kernel.org
S: Maintained
F: drivers/video/atmel_lcdfb.c
F: include/video/atmel_lcdc.h
......@@ -1098,7 +1150,6 @@ F: include/net/ax25.h
F: net/ax25/
B43 WIRELESS DRIVER
M: Michael Buesch <mb@bu3sch.de>
M: Stefano Brivio <stefano.brivio@polimi.it>
L: linux-wireless@vger.kernel.org
W: http://linuxwireless.org/en/users/Drivers/b43
......@@ -1797,6 +1848,19 @@ S: Maintained
F: drivers/scsi/dpt*
F: drivers/scsi/dpt/
DRBD DRIVER
P: Philipp Reisner
P: Lars Ellenberg
M: drbd-dev@lists.linbit.com
L: drbd-user@lists.linbit.com
W: http://www.drbd.org
T: git git://git.drbd.org/linux-2.6-drbd.git drbd
T: git git://git.drbd.org/drbd-8.3.git
S: Supported
F: drivers/block/drbd/
F: lib/lru_cache.c
F: Documentation/blockdev/drbd/
DRIVER CORE, KOBJECTS, AND SYSFS
M: Greg Kroah-Hartman <gregkh@suse.de>
T: quilt kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/
......@@ -2113,7 +2177,7 @@ F: drivers/net/wan/dlci.c
F: drivers/net/wan/sdla.c
FRAMEBUFFER LAYER
L: linux-fbdev-devel@lists.sourceforge.net (moderated for non-subscribers)
L: linux-fbdev@vger.kernel.org
W: http://linux-fbdev.sourceforge.net/
S: Orphan
F: Documentation/fb/
......@@ -2136,7 +2200,7 @@ F: drivers/i2c/busses/i2c-cpm.c
FREESCALE IMX / MXC FRAMEBUFFER DRIVER
M: Sascha Hauer <kernel@pengutronix.de>
L: linux-fbdev-devel@lists.sourceforge.net (moderated for non-subscribers)
L: linux-fbdev@vger.kernel.org
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
S: Maintained
F: arch/arm/plat-mxc/include/mach/imxfb.h
......@@ -2312,6 +2376,13 @@ T: git git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6.git
S: Maintained
F: drivers/media/video/gspca/finepix.c
GSPCA GL860 SUBDRIVER
M: Olivier Lorin <o.lorin@laposte.net>
L: linux-media@vger.kernel.org
T: git git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6.git
S: Maintained
F: drivers/media/video/gspca/gl860/
GSPCA M5602 SUBDRIVER
M: Erik Andren <erik.andren@gmail.com>
L: linux-media@vger.kernel.org
......@@ -2533,8 +2604,7 @@ S: Maintained
F: Documentation/i2c/
F: drivers/i2c/
F: include/linux/i2c.h
F: include/linux/i2c-dev.h
F: include/linux/i2c-id.h
F: include/linux/i2c-*.h
I2C-TINY-USB DRIVER
M: Till Harbaum <till@harbaum.org>
......@@ -2635,7 +2705,7 @@ S: Supported
F: security/integrity/ima/
IMS TWINTURBO FRAMEBUFFER DRIVER
L: linux-fbdev-devel@lists.sourceforge.net (moderated for non-subscribers)
L: linux-fbdev@vger.kernel.org
S: Orphan
F: drivers/video/imsttfb.c
......@@ -2670,14 +2740,14 @@ F: drivers/input/
INTEL FRAMEBUFFER DRIVER (excluding 810 and 815)
M: Sylvain Meyer <sylvain.meyer@worldonline.fr>
L: linux-fbdev-devel@lists.sourceforge.net (moderated for non-subscribers)
L: linux-fbdev@vger.kernel.org
S: Maintained
F: Documentation/fb/intelfb.txt
F: drivers/video/intelfb/
INTEL 810/815 FRAMEBUFFER DRIVER
M: Antonino Daplas <adaplas@gmail.com>
L: linux-fbdev-devel@lists.sourceforge.net (moderated for non-subscribers)
L: linux-fbdev@vger.kernel.org
S: Maintained
F: drivers/video/i810/
......@@ -2789,6 +2859,15 @@ T: git git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-2.6.git
S: Supported
F: drivers/net/wireless/iwlwifi/
INTEL WIRELESS MULTICOMM 3200 WIFI (iwmc3200wifi)
M: Samuel Ortiz <samuel.ortiz@intel.com>
M: Zhu Yi <yi.zhu@intel.com>
M: Intel Linux Wireless <ilw@linux.intel.com>
L: linux-wireless@vger.kernel.org
S: Supported
W: http://wireless.kernel.org/en/users/Drivers/iwmc3200wifi
F: drivers/net/wireless/iwmc3200wifi/
IOC3 ETHERNET DRIVER
M: Ralf Baechle <ralf@linux-mips.org>
L: linux-mips@linux-mips.org
......@@ -2987,11 +3066,8 @@ S: Maintained
F: fs/autofs4/
KERNEL BUILD
M: Sam Ravnborg <sam@ravnborg.org>
T: git git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild-next.git
T: git git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild-fixes.git
L: linux-kbuild@vger.kernel.org
S: Maintained
S: Orphan
F: Documentation/kbuild/
F: Makefile
F: scripts/Makefile.*
......@@ -3406,7 +3482,7 @@ S: Supported
MATROX FRAMEBUFFER DRIVER
M: Petr Vandrovec <vandrove@vc.cvut.cz>
L: linux-fbdev-devel@lists.sourceforge.net (moderated for non-subscribers)
L: linux-fbdev@vger.kernel.org
S: Maintained
F: drivers/video/matrox/matroxfb_*
F: include/linux/matroxfb.h
......@@ -3731,9 +3807,9 @@ F: include/linux/if_*
F: include/linux/*device.h
NETXEN (1/10) GbE SUPPORT
M: Dhananjay Phadke <dhananjay@netxen.com>
M: Amit Kumar Salecha <amit.salecha@qlogic.com>
L: netdev@vger.kernel.org
W: http://www.netxen.com
W: http://www.qlogic.com
S: Supported
F: drivers/net/netxen/
......@@ -3793,7 +3869,7 @@ F: fs/ntfs/
NVIDIA (rivafb and nvidiafb) FRAMEBUFFER DRIVER
M: Antonino Daplas <adaplas@gmail.com>
L: linux-fbdev-devel@lists.sourceforge.net (moderated for non-subscribers)
L: linux-fbdev@vger.kernel.org
S: Maintained
F: drivers/video/riva/
F: drivers/video/nvidia/
......@@ -3828,7 +3904,7 @@ F: sound/soc/omap/
OMAP FRAMEBUFFER SUPPORT
M: Imre Deak <imre.deak@nokia.com>
L: linux-fbdev-devel@lists.sourceforge.net (moderated for non-subscribers)
L: linux-fbdev@vger.kernel.org
L: linux-omap@vger.kernel.org
S: Maintained
F: drivers/video/omap/
......@@ -4334,14 +4410,14 @@ F: include/linux/qnxtypes.h
RADEON FRAMEBUFFER DISPLAY DRIVER
M: Benjamin Herrenschmidt <benh@kernel.crashing.org>
L: linux-fbdev-devel@lists.sourceforge.net (moderated for non-subscribers)
L: linux-fbdev@vger.kernel.org
S: Maintained
F: drivers/video/aty/radeon*
F: include/linux/radeonfb.h
RAGE128 FRAMEBUFFER DISPLAY DRIVER
M: Paul Mackerras <paulus@samba.org>
L: linux-fbdev-devel@lists.sourceforge.net (moderated for non-subscribers)
L: linux-fbdev@vger.kernel.org
S: Maintained
F: drivers/video/aty/aty128fb.c
......@@ -4480,7 +4556,7 @@ F: drivers/net/wireless/rtl818x/rtl8187*
S3 SAVAGE FRAMEBUFFER DRIVER
M: Antonino Daplas <adaplas@gmail.com>
L: linux-fbdev-devel@lists.sourceforge.net (moderated for non-subscribers)
L: linux-fbdev@vger.kernel.org
S: Maintained
F: drivers/video/savage/
......@@ -5643,7 +5719,7 @@ S: Maintained
UVESAFB DRIVER
M: Michal Januszewski <spock@gentoo.org>
L: linux-fbdev-devel@lists.sourceforge.net (moderated for non-subscribers)
L: linux-fbdev@vger.kernel.org
W: http://dev.gentoo.org/~spock/projects/uvesafb/
S: Maintained
F: Documentation/fb/uvesafb.txt
......@@ -5676,7 +5752,7 @@ F: drivers/mmc/host/via-sdmmc.c
VIA UNICHROME(PRO)/CHROME9 FRAMEBUFFER DRIVER
M: Joseph Chan <JosephChan@via.com.tw>
M: Scott Fang <ScottFang@viatech.com.cn>
L: linux-fbdev-devel@lists.sourceforge.net (moderated for non-subscribers)
L: linux-fbdev@vger.kernel.org
S: Maintained
F: drivers/video/via/
......
Makefile
浏览文件 @ bcd6acd5
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 32
EXTRAVERSION = -rc8
EXTRAVERSION =
NAME = Man-Eating Seals of Antiquity
# *DOCUMENTATION*
......@@ -379,6 +379,7 @@ export RCS_TAR_IGNORE := --exclude SCCS --exclude BitKeeper --exclude .svn --exc
PHONY += scripts_basic
scripts_basic:
$(Q)$(MAKE) $(build)=scripts/basic
$(Q)rm -f .tmp_quiet_recordmcount
# To avoid any implicit rule to kick in, define an empty command.
scripts/basic/%: scripts_basic ;
......
arch/Kconfig
浏览文件 @ bcd6acd5
......@@ -83,6 +83,13 @@ config KRETPROBES
def_bool y
depends on KPROBES && HAVE_KRETPROBES
config USER_RETURN_NOTIFIER
bool
depends on HAVE_USER_RETURN_NOTIFIER
help
Provide a kernel-internal notification when a cpu is about to
switch to user mode.
config HAVE_IOREMAP_PROT
bool
......@@ -126,4 +133,13 @@ config HAVE_DMA_API_DEBUG
config HAVE_DEFAULT_NO_SPIN_MUTEXES
bool
config HAVE_HW_BREAKPOINT
bool
depends on HAVE_PERF_EVENTS
select ANON_INODES
select PERF_EVENTS
config HAVE_USER_RETURN_NOTIFIER
bool
source "kernel/gcov/Kconfig"
arch/alpha/include/asm/cacheflush.h
浏览文件 @ bcd6acd5
......@@ -9,6 +9,7 @@
#define flush_cache_dup_mm(mm) do { } while (0)
#define flush_cache_range(vma, start, end) do { } while (0)
#define flush_cache_page(vma, vmaddr, pfn) do { } while (0)
#define ARCH_IMPLEMENTS_FLUSH_DCACHE_PAGE 0
#define flush_dcache_page(page) do { } while (0)
#define flush_dcache_mmap_lock(mapping) do { } while (0)
#define flush_dcache_mmap_unlock(mapping) do { } while (0)
......
arch/alpha/include/asm/socket.h
浏览文件 @ bcd6acd5
......@@ -67,6 +67,8 @@
#define SO_TIMESTAMPING 37
#define SCM_TIMESTAMPING SO_TIMESTAMPING
#define SO_RXQ_OVFL 40
/* O_NONBLOCK clashes with the bits used for socket types. Therefore we
* have to define SOCK_NONBLOCK to a different value here.
*/
......
arch/alpha/include/asm/thread_info.h
浏览文件 @ bcd6acd5
......@@ -61,21 +61,24 @@ register struct thread_info *__current_thread_info __asm__("$8");
/*
* Thread information flags:
* - these are process state flags and used from assembly
* - pending work-to-be-done flags come first to fit in and immediate operand.
* - pending work-to-be-done flags come first and must be assigned to be
* within bits 0 to 7 to fit in and immediate operand.
* - ALPHA_UAC_SHIFT below must be kept consistent with the unaligned
* control flags.
*
* TIF_SYSCALL_TRACE is known to be 0 via blbs.
*/
#define TIF_SYSCALL_TRACE 0 /* syscall trace active */
#define TIF_SIGPENDING 1 /* signal pending */
#define TIF_NEED_RESCHED 2 /* rescheduling necessary */
#define TIF_POLLING_NRFLAG 3 /* poll_idle is polling NEED_RESCHED */
#define TIF_DIE_IF_KERNEL 4 /* dik recursion lock */
#define TIF_UAC_NOPRINT 5 /* see sysinfo.h */
#define TIF_UAC_NOFIX 6
#define TIF_UAC_SIGBUS 7
#define TIF_MEMDIE 8
#define TIF_RESTORE_SIGMASK 9 /* restore signal mask in do_signal */
#define TIF_NOTIFY_RESUME 10 /* callback before returning to user */
#define TIF_NOTIFY_RESUME 1 /* callback before returning to user */
#define TIF_SIGPENDING 2 /* signal pending */
#define TIF_NEED_RESCHED 3 /* rescheduling necessary */
#define TIF_POLLING_NRFLAG 8 /* poll_idle is polling NEED_RESCHED */
#define TIF_DIE_IF_KERNEL 9 /* dik recursion lock */
#define TIF_UAC_NOPRINT 10 /* see sysinfo.h */
#define TIF_UAC_NOFIX 11
#define TIF_UAC_SIGBUS 12
#define TIF_MEMDIE 13
#define TIF_RESTORE_SIGMASK 14 /* restore signal mask in do_signal */
#define TIF_FREEZE 16 /* is freezing for suspend */
#define _TIF_SYSCALL_TRACE (1<<TIF_SYSCALL_TRACE)
......@@ -94,7 +97,7 @@ register struct thread_info *__current_thread_info __asm__("$8");
#define _TIF_ALLWORK_MASK (_TIF_WORK_MASK \
| _TIF_SYSCALL_TRACE)
#define ALPHA_UAC_SHIFT 6
#define ALPHA_UAC_SHIFT 10
#define ALPHA_UAC_MASK (1 << TIF_UAC_NOPRINT | 1 << TIF_UAC_NOFIX | \
1 << TIF_UAC_SIGBUS)
......
arch/alpha/include/asm/unistd.h
浏览文件 @ bcd6acd5
......@@ -433,10 +433,11 @@
#define __NR_signalfd 476
#define __NR_timerfd 477
#define __NR_eventfd 478
#define __NR_recvmmsg 479
#ifdef __KERNEL__
#define NR_SYSCALLS 479
#define NR_SYSCALLS 480
#define __ARCH_WANT_IPC_PARSE_VERSION
#define __ARCH_WANT_OLD_READDIR
......
arch/alpha/kernel/core_marvel.c
浏览文件 @ bcd6acd5
......@@ -1103,6 +1103,8 @@ marvel_agp_info(void)
* Allocate the info structure.
*/
agp = kmalloc(sizeof(*agp), GFP_KERNEL);
if (!agp)
return NULL;
/*
* Fill it in.
......
arch/alpha/kernel/core_titan.c
浏览文件 @ bcd6acd5
......@@ -757,6 +757,8 @@ titan_agp_info(void)
* Allocate the info structure.
*/
agp = kmalloc(sizeof(*agp), GFP_KERNEL);
if (!agp)
return NULL;
/*
* Fill it in.
......
arch/alpha/kernel/irq.c
浏览文件 @ bcd6acd5
......@@ -92,7 +92,7 @@ show_interrupts(struct seq_file *p, void *v)
for_each_online_cpu(j)
seq_printf(p, "%10u ", kstat_irqs_cpu(irq, j));
#endif
seq_printf(p, " %14s", irq_desc[irq].chip->typename);
seq_printf(p, " %14s", irq_desc[irq].chip->name);
seq_printf(p, " %c%s",
(action->flags & IRQF_DISABLED)?'+':' ',
action->name);
......
arch/alpha/kernel/irq_alpha.c
浏览文件 @ bcd6acd5
......@@ -228,7 +228,7 @@ struct irqaction timer_irqaction = {
};
static struct irq_chip rtc_irq_type = {
.typename = "RTC",
.name = "RTC",
.startup = rtc_startup,
.shutdown = rtc_enable_disable,
.enable = rtc_enable_disable,
......
arch/alpha/kernel/irq_i8259.c
浏览文件 @ bcd6acd5
......@@ -84,7 +84,7 @@ i8259a_end_irq(unsigned int irq)
}
struct irq_chip i8259a_irq_type = {
.typename = "XT-PIC",
.name = "XT-PIC",
.startup = i8259a_startup_irq,
.shutdown = i8259a_disable_irq,
.enable = i8259a_enable_irq,
......
arch/alpha/kernel/irq_pyxis.c
浏览文件 @ bcd6acd5
......@@ -71,7 +71,7 @@ pyxis_mask_and_ack_irq(unsigned int irq)
}
static struct irq_chip pyxis_irq_type = {
.typename = "PYXIS",
.name = "PYXIS",
.startup = pyxis_startup_irq,
.shutdown = pyxis_disable_irq,
.enable = pyxis_enable_irq,
......
arch/alpha/kernel/irq_srm.c
浏览文件 @ bcd6acd5
......@@ -49,7 +49,7 @@ srm_end_irq(unsigned int irq)
/* Handle interrupts from the SRM, assuming no additional weirdness. */
static struct irq_chip srm_irq_type = {
.typename = "SRM",
.name = "SRM",
.startup = srm_startup_irq,
.shutdown = srm_disable_irq,
.enable = srm_enable_irq,
......
arch/alpha/kernel/sys_alcor.c
浏览文件 @ bcd6acd5
......@@ -90,7 +90,7 @@ alcor_end_irq(unsigned int irq)
}
static struct irq_chip alcor_irq_type = {
.typename = "ALCOR",
.name = "ALCOR",
.startup = alcor_startup_irq,
.shutdown = alcor_disable_irq,
.enable = alcor_enable_irq,
......
arch/alpha/kernel/sys_cabriolet.c
浏览文件 @ bcd6acd5
......@@ -72,7 +72,7 @@ cabriolet_end_irq(unsigned int irq)
}
static struct irq_chip cabriolet_irq_type = {
.typename = "CABRIOLET",
.name = "CABRIOLET",
.startup = cabriolet_startup_irq,
.shutdown = cabriolet_disable_irq,
.enable = cabriolet_enable_irq,
......
arch/alpha/kernel/sys_dp264.c
浏览文件 @ bcd6acd5
......@@ -199,7 +199,7 @@ clipper_set_affinity(unsigned int irq, const struct cpumask *affinity)
}
static struct irq_chip dp264_irq_type = {
.typename = "DP264",
.name = "DP264",
.startup = dp264_startup_irq,
.shutdown = dp264_disable_irq,
.enable = dp264_enable_irq,
......@@ -210,7 +210,7 @@ static struct irq_chip dp264_irq_type = {
};
static struct irq_chip clipper_irq_type = {
.typename = "CLIPPER",
.name = "CLIPPER",
.startup = clipper_startup_irq,
.shutdown = clipper_disable_irq,
.enable = clipper_enable_irq,
......
arch/alpha/kernel/sys_eb64p.c
浏览文件 @ bcd6acd5
......@@ -70,7 +70,7 @@ eb64p_end_irq(unsigned int irq)
}
static struct irq_chip eb64p_irq_type = {
.typename = "EB64P",
.name = "EB64P",
.startup = eb64p_startup_irq,
.shutdown = eb64p_disable_irq,
.enable = eb64p_enable_irq,
......
arch/alpha/kernel/sys_eiger.c
浏览文件 @ bcd6acd5
......@@ -81,7 +81,7 @@ eiger_end_irq(unsigned int irq)
}
static struct irq_chip eiger_irq_type = {
.typename = "EIGER",
.name = "EIGER",
.startup = eiger_startup_irq,
.shutdown = eiger_disable_irq,
.enable = eiger_enable_irq,
......
arch/alpha/kernel/sys_jensen.c
浏览文件 @ bcd6acd5
......@@ -119,7 +119,7 @@ jensen_local_end(unsigned int irq)
}
static struct irq_chip jensen_local_irq_type = {
.typename = "LOCAL",
.name = "LOCAL",
.startup = jensen_local_startup,
.shutdown = jensen_local_shutdown,
.enable = jensen_local_enable,
......
arch/alpha/kernel/sys_marvel.c
浏览文件 @ bcd6acd5
......@@ -170,7 +170,7 @@ marvel_irq_noop_return(unsigned int irq)
}
static struct irq_chip marvel_legacy_irq_type = {
.typename = "LEGACY",
.name = "LEGACY",
.startup = marvel_irq_noop_return,
.shutdown = marvel_irq_noop,
.enable = marvel_irq_noop,
......@@ -180,7 +180,7 @@ static struct irq_chip marvel_legacy_irq_type = {
};
static struct irq_chip io7_lsi_irq_type = {
.typename = "LSI",
.name = "LSI",
.startup = io7_startup_irq,
.shutdown = io7_disable_irq,
.enable = io7_enable_irq,
......@@ -190,7 +190,7 @@ static struct irq_chip io7_lsi_irq_type = {
};
static struct irq_chip io7_msi_irq_type = {
.typename = "MSI",
.name = "MSI",
.startup = io7_startup_irq,
.shutdown = io7_disable_irq,
.enable = io7_enable_irq,
......
arch/alpha/kernel/sys_mikasa.c
浏览文件 @ bcd6acd5
......@@ -69,7 +69,7 @@ mikasa_end_irq(unsigned int irq)
}
static struct irq_chip mikasa_irq_type = {
.typename = "MIKASA",
.name = "MIKASA",
.startup = mikasa_startup_irq,
.shutdown = mikasa_disable_irq,
.enable = mikasa_enable_irq,
......
arch/alpha/kernel/sys_noritake.c
浏览文件 @ bcd6acd5
......@@ -74,7 +74,7 @@ noritake_end_irq(unsigned int irq)
}
static struct irq_chip noritake_irq_type = {
.typename = "NORITAKE",
.name = "NORITAKE",
.startup = noritake_startup_irq,
.shutdown = noritake_disable_irq,
.enable = noritake_enable_irq,
......
arch/alpha/kernel/sys_rawhide.c
浏览文件 @ bcd6acd5
......@@ -136,7 +136,7 @@ rawhide_end_irq(unsigned int irq)
}
static struct irq_chip rawhide_irq_type = {
.typename = "RAWHIDE",
.name = "RAWHIDE",
.startup = rawhide_startup_irq,
.shutdown = rawhide_disable_irq,
.enable = rawhide_enable_irq,
......
arch/alpha/kernel/sys_ruffian.c
浏览文件 @ bcd6acd5
......@@ -66,7 +66,7 @@ ruffian_init_irq(void)
common_init_isa_dma();
}
#define RUFFIAN_LATCH ((PIT_TICK_RATE + HZ / 2) / HZ)
#define RUFFIAN_LATCH DIV_ROUND_CLOSEST(PIT_TICK_RATE, HZ)
static void __init
ruffian_init_rtc(void)
......
arch/alpha/kernel/sys_rx164.c
浏览文件 @ bcd6acd5
......@@ -73,7 +73,7 @@ rx164_end_irq(unsigned int irq)
}
static struct irq_chip rx164_irq_type = {
.typename = "RX164",
.name = "RX164",
.startup = rx164_startup_irq,
.shutdown = rx164_disable_irq,
.enable = rx164_enable_irq,
......
arch/alpha/kernel/sys_sable.c
浏览文件 @ bcd6acd5
......@@ -502,7 +502,7 @@ sable_lynx_mask_and_ack_irq(unsigned int irq)
}
static struct irq_chip sable_lynx_irq_type = {
.typename = "SABLE/LYNX",
.name = "SABLE/LYNX",
.startup = sable_lynx_startup_irq,
.shutdown = sable_lynx_disable_irq,
.enable = sable_lynx_enable_irq,
......
arch/alpha/kernel/sys_takara.c
浏览文件 @ bcd6acd5
......@@ -75,7 +75,7 @@ takara_end_irq(unsigned int irq)
}
static struct irq_chip takara_irq_type = {
.typename = "TAKARA",
.name = "TAKARA",
.startup = takara_startup_irq,
.shutdown = takara_disable_irq,
.enable = takara_enable_irq,
......
arch/alpha/kernel/sys_titan.c
浏览文件 @ bcd6acd5
......@@ -195,7 +195,7 @@ init_titan_irqs(struct irq_chip * ops, int imin, int imax)
}
static struct irq_chip titan_irq_type = {
.typename = "TITAN",
.name = "TITAN",
.startup = titan_startup_irq,
.shutdown = titan_disable_irq,
.enable = titan_enable_irq,
......
arch/alpha/kernel/sys_wildfire.c
浏览文件 @ bcd6acd5
......@@ -158,7 +158,7 @@ wildfire_end_irq(unsigned int irq)
}
static struct irq_chip wildfire_irq_type = {
.typename = "WILDFIRE",
.name = "WILDFIRE",
.startup = wildfire_startup_irq,
.shutdown = wildfire_disable_irq,
.enable = wildfire_enable_irq,
......
arch/alpha/kernel/systbls.S
浏览文件 @ bcd6acd5
......@@ -497,6 +497,7 @@ sys_call_table:
.quad sys_signalfd
.quad sys_ni_syscall
.quad sys_eventfd
.quad sys_recvmmsg
.size sys_call_table, . - sys_call_table
.type sys_call_table, @object
......
arch/arm/Kconfig
浏览文件 @ bcd6acd5
......@@ -433,6 +433,17 @@ config ARCH_L7200
If you have any questions or comments about the Linux kernel port
to this board, send e-mail to <sjhill@cotw.com>.
config ARCH_DOVE
bool "Marvell Dove"
select PCI
select GENERIC_GPIO
select ARCH_REQUIRE_GPIOLIB
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
select PLAT_ORION
help
Support for the Marvell Dove SoC 88AP510
config ARCH_KIRKWOOD
bool "Marvell Kirkwood"
select CPU_FEROCEON
......@@ -702,6 +713,16 @@ config ARCH_BCMRING
help
Support for Broadcom's BCMRing platform.
config ARCH_U8500
bool "ST-Ericsson U8500 Series"
select CPU_V7
select ARM_AMBA
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
select COMMON_CLKDEV
help
Support for ST-Ericsson's Ux500 architecture
endchoice
source "arch/arm/mach-clps711x/Kconfig"
......@@ -747,6 +768,9 @@ source "arch/arm/mach-orion5x/Kconfig"
source "arch/arm/mach-kirkwood/Kconfig"
source "arch/arm/mach-dove/Kconfig"
source "arch/arm/plat-samsung/Kconfig"
source "arch/arm/plat-s3c24xx/Kconfig"
source "arch/arm/plat-s3c64xx/Kconfig"
source "arch/arm/plat-s3c/Kconfig"
......@@ -787,6 +811,7 @@ source "arch/arm/mach-at91/Kconfig"
source "arch/arm/plat-mxc/Kconfig"
source "arch/arm/mach-nomadik/Kconfig"
source "arch/arm/plat-nomadik/Kconfig"
source "arch/arm/mach-netx/Kconfig"
......@@ -804,12 +829,16 @@ source "arch/arm/mach-w90x900/Kconfig"
source "arch/arm/mach-bcmring/Kconfig"
source "arch/arm/mach-ux500/Kconfig"
# Definitions to make life easier
config ARCH_ACORN
bool
config PLAT_IOP
bool
select GENERIC_CLOCKEVENTS
select GENERIC_TIME
config PLAT_ORION
bool
......@@ -955,10 +984,10 @@ source "kernel/time/Kconfig"
config SMP
bool "Symmetric Multi-Processing (EXPERIMENTAL)"
depends on EXPERIMENTAL && (REALVIEW_EB_ARM11MP || REALVIEW_EB_A9MP ||\
MACH_REALVIEW_PB11MP || MACH_REALVIEW_PBX || ARCH_OMAP4)
MACH_REALVIEW_PB11MP || MACH_REALVIEW_PBX || ARCH_OMAP4 || ARCH_U8500)
depends on GENERIC_CLOCKEVENTS
select USE_GENERIC_SMP_HELPERS
select HAVE_ARM_SCU if (ARCH_REALVIEW || ARCH_OMAP4)
select HAVE_ARM_SCU if (ARCH_REALVIEW || ARCH_OMAP4 || ARCH_U8500)
help
This enables support for systems with more than one CPU. If you have
a system with only one CPU, like most personal computers, say N. If
......@@ -1027,9 +1056,9 @@ config HOTPLUG_CPU
config LOCAL_TIMERS
bool "Use local timer interrupts"
depends on SMP && (REALVIEW_EB_ARM11MP || MACH_REALVIEW_PB11MP || \
REALVIEW_EB_A9MP || MACH_REALVIEW_PBX || ARCH_OMAP4)
REALVIEW_EB_A9MP || MACH_REALVIEW_PBX || ARCH_OMAP4 || ARCH_U8500)
default y
select HAVE_ARM_TWD if (ARCH_REALVIEW || ARCH_OMAP4)
select HAVE_ARM_TWD if (ARCH_REALVIEW || ARCH_OMAP4 || ARCH_U8500)
help
Enable support for local timers on SMP platforms, rather then the
legacy IPI broadcast method. Local timers allows the system
......
arch/arm/Kconfig.debug
浏览文件 @ bcd6acd5
......@@ -83,6 +83,14 @@ config DEBUG_ICEDCC
It does include a timeout to ensure that the system does not
totally freeze when there is nothing connected to read.
config OC_ETM
bool "On-chip ETM and ETB"
select ARM_AMBA
help
Enables the on-chip embedded trace macrocell and embedded trace
buffer driver that will allow you to collect traces of the
kernel code.
config DEBUG_DC21285_PORT
bool "Kernel low-level debugging messages via footbridge serial port"
depends on DEBUG_LL && FOOTBRIDGE
......
arch/arm/Makefile
浏览文件 @ bcd6acd5
......@@ -122,6 +122,7 @@ machine-$(CONFIG_ARCH_AT91) := at91
machine-$(CONFIG_ARCH_BCMRING) := bcmring
machine-$(CONFIG_ARCH_CLPS711X) := clps711x
machine-$(CONFIG_ARCH_DAVINCI) := davinci
machine-$(CONFIG_ARCH_DOVE) := dove
machine-$(CONFIG_ARCH_EBSA110) := ebsa110
machine-$(CONFIG_ARCH_EP93XX) := ep93xx
machine-$(CONFIG_ARCH_GEMINI) := gemini
......@@ -166,6 +167,7 @@ machine-$(CONFIG_ARCH_SHARK) := shark
machine-$(CONFIG_ARCH_STMP378X) := stmp378x
machine-$(CONFIG_ARCH_STMP37XX) := stmp37xx
machine-$(CONFIG_ARCH_U300) := u300
machine-$(CONFIG_ARCH_U8500) := ux500
machine-$(CONFIG_ARCH_VERSATILE) := versatile
machine-$(CONFIG_ARCH_W90X900) := w90x900
machine-$(CONFIG_FOOTBRIDGE) := footbridge
......@@ -176,11 +178,12 @@ machine-$(CONFIG_ARCH_MXC91231) := mxc91231
plat-$(CONFIG_ARCH_MXC) := mxc
plat-$(CONFIG_ARCH_OMAP) := omap
plat-$(CONFIG_PLAT_IOP) := iop
plat-$(CONFIG_PLAT_NOMADIK) := nomadik
plat-$(CONFIG_PLAT_ORION) := orion
plat-$(CONFIG_PLAT_PXA) := pxa
plat-$(CONFIG_PLAT_S3C24XX) := s3c24xx s3c
plat-$(CONFIG_PLAT_S3C64XX) := s3c64xx s3c
plat-$(CONFIG_PLAT_S5PC1XX) := s5pc1xx s3c
plat-$(CONFIG_PLAT_S3C24XX) := s3c24xx s3c samsung
plat-$(CONFIG_PLAT_S3C64XX) := s3c64xx s3c samsung
plat-$(CONFIG_PLAT_S5PC1XX) := s5pc1xx s3c samsung
plat-$(CONFIG_ARCH_STMP3XXX) := stmp3xxx
ifeq ($(CONFIG_ARCH_EBSA110),y)
......
arch/arm/boot/compressed/head.S
浏览文件 @ bcd6acd5
......@@ -743,6 +743,12 @@ proc_types:
W(b) __armv4_mmu_cache_off
W(b) __armv6_mmu_cache_flush
.word 0x560f5810 @ Marvell PJ4 ARMv6
.word 0xff0ffff0
W(b) __armv4_mmu_cache_on
W(b) __armv4_mmu_cache_off
W(b) __armv6_mmu_cache_flush
.word 0x000f0000 @ new CPU Id
.word 0x000f0000
W(b) __armv7_mmu_cache_on
......
arch/arm/common/dmabounce.c
浏览文件 @ bcd6acd5
......@@ -342,6 +342,22 @@ dma_addr_t dma_map_single(struct device *dev, void *ptr, size_t size,
}
EXPORT_SYMBOL(dma_map_single);
/*
* see if a mapped address was really a "safe" buffer and if so, copy
* the data from the safe buffer back to the unsafe buffer and free up
* the safe buffer. (basically return things back to the way they
* should be)
*/
void dma_unmap_single(struct device *dev, dma_addr_t dma_addr, size_t size,
enum dma_data_direction dir)
{
dev_dbg(dev, "%s(ptr=%p,size=%d,dir=%x)\n",
__func__, (void *) dma_addr, size, dir);
unmap_single(dev, dma_addr, size, dir);
}
EXPORT_SYMBOL(dma_unmap_single);
dma_addr_t dma_map_page(struct device *dev, struct page *page,
unsigned long offset, size_t size, enum dma_data_direction dir)
{
......@@ -366,8 +382,7 @@ EXPORT_SYMBOL(dma_map_page);
* the safe buffer. (basically return things back to the way they
* should be)
*/
void dma_unmap_single(struct device *dev, dma_addr_t dma_addr, size_t size,
void dma_unmap_page(struct device *dev, dma_addr_t dma_addr, size_t size,
enum dma_data_direction dir)
{
dev_dbg(dev, "%s(ptr=%p,size=%d,dir=%x)\n",
......@@ -375,7 +390,7 @@ void dma_unmap_single(struct device *dev, dma_addr_t dma_addr, size_t size,
unmap_single(dev, dma_addr, size, dir);
}
EXPORT_SYMBOL(dma_unmap_single);
EXPORT_SYMBOL(dma_unmap_page);
int dmabounce_sync_for_cpu(struct device *dev, dma_addr_t addr,
unsigned long off, size_t sz, enum dma_data_direction dir)
......
arch/arm/configs/am3517_evm_defconfig 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/configs/at91rm9200dk_defconfig
浏览文件 @ bcd6acd5
......@@ -120,6 +120,7 @@ CONFIG_ARCH_AT91RM9200DK=y
# CONFIG_MACH_CARMEVA is not set
# CONFIG_MACH_KB9200 is not set
# CONFIG_MACH_ATEB9200 is not set
CONFIG_MACH_ECO920=y
#
# AT91RM9200 Feature Selections
......
arch/arm/configs/cm_t35_defconfig 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/configs/cm_x300_defconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/configs/dove_defconfig 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/configs/ezx_defconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/configs/h3600_defconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/configs/htcherald_defconfig 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/configs/igep0020_defconfig 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/configs/mx3_defconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/configs/nuc950_defconfig 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/configs/nuc960_defconfig 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/configs/omap3_beagle_defconfig
浏览文件 @ bcd6acd5
......@@ -52,8 +52,8 @@ CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_RT_GROUP_SCHED is not set
CONFIG_USER_SCHED=y
# CONFIG_CGROUP_SCHED is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_SYSFS_DEPRECATED=y is not set
# CONFIG_SYSFS_DEPRECATED_V2=y is not set
# CONFIG_RELAY is not set
# CONFIG_NAMESPACES is not set
CONFIG_BLK_DEV_INITRD=y
......
arch/arm/configs/omap3_defconfig 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/configs/omap3_evm_defconfig
浏览文件 @ bcd6acd5
......@@ -59,8 +59,8 @@ CONFIG_FAIR_GROUP_SCHED=y
CONFIG_USER_SCHED=y
# CONFIG_CGROUP_SCHED is not set
# CONFIG_CGROUPS is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_SYSFS_DEPRECATED=y is not set
# CONFIG_SYSFS_DEPRECATED_V2=y is not set
# CONFIG_RELAY is not set
# CONFIG_NAMESPACES is not set
CONFIG_BLK_DEV_INITRD=y
......@@ -617,8 +617,8 @@ CONFIG_MII=y
# CONFIG_DM9000 is not set
# CONFIG_ENC28J60 is not set
# CONFIG_ETHOC is not set
CONFIG_SMC911X=y
# CONFIG_SMSC911X is not set
# CONFIG_SMC911X is not set
CONFIG_SMSC911X=y
# CONFIG_DNET is not set
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
......@@ -676,13 +676,19 @@ CONFIG_INPUT_EVDEV=y
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5588 is not set
# CONFIG_KEYBOARD_ATKBD is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_QT2160 is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_GPIO is not set
# CONFIG_KEYBOARD_MATRIX is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_GPIO is not set
# CONFIG_KEYBOARD_SUNKBD is not set
CONFIG_KEYBOARD_TWL4030=y
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
......@@ -1126,7 +1132,7 @@ CONFIG_MMC_BLOCK_BOUNCE=y
#
# CONFIG_MMC_SDHCI is not set
# CONFIG_MMC_OMAP is not set
CONFIG_MMC_OMAP_HS=m
CONFIG_MMC_OMAP_HS=y
# CONFIG_MMC_SPI is not set
# CONFIG_MEMSTICK is not set
# CONFIG_ACCESSIBILITY is not set
......
arch/arm/configs/omap3_pandora_defconfig
浏览文件 @ bcd6acd5
......@@ -51,8 +51,9 @@ CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_RT_GROUP_SCHED is not set
CONFIG_USER_SCHED=y
# CONFIG_CGROUP_SCHED is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_SYSFS_DEPRECATED=y is not set
# CONFIG_SYSFS_DEPRECATED_V2=y is not set
# CONFIG_RELAY is not set
# CONFIG_NAMESPACES is not set
CONFIG_BLK_DEV_INITRD=y
......
arch/arm/configs/omap_3630sdp_defconfig 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/configs/omap_4430sdp_defconfig
浏览文件 @ bcd6acd5
......@@ -52,8 +52,8 @@ CONFIG_FAIR_GROUP_SCHED=y
CONFIG_USER_SCHED=y
# CONFIG_CGROUP_SCHED is not set
# CONFIG_CGROUPS is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_SYSFS_DEPRECATED=y is not set
# CONFIG_SYSFS_DEPRECATED_V2=y is not set
# CONFIG_RELAY is not set
# CONFIG_NAMESPACES is not set
CONFIG_BLK_DEV_INITRD=y
......
arch/arm/configs/omap_ldp_defconfig
浏览文件 @ bcd6acd5
......@@ -49,8 +49,8 @@ CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_RT_GROUP_SCHED is not set
CONFIG_USER_SCHED=y
# CONFIG_CGROUP_SCHED is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_SYSFS_DEPRECATED=y is not set
# CONFIG_SYSFS_DEPRECATED_V2=y is not set
# CONFIG_RELAY is not set
# CONFIG_NAMESPACES is not set
CONFIG_BLK_DEV_INITRD=y
......
arch/arm/configs/omap_zoom3_defconfig 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/configs/overo_defconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/configs/rx51_defconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/configs/u8500_defconfig 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/include/asm/cacheflush.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/include/asm/dma-mapping.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/include/asm/hardware/cache-tauros2.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/include/asm/hardware/coresight.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/include/asm/kmap_types.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/include/asm/memory.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/include/asm/pgtable.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/include/asm/socket.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/include/asm/swab.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/include/asm/system.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/kernel/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/kernel/calls.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/kernel/etm.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/kernel/head-nommu.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/kernel/head.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/kernel/isa.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/kernel/signal.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/kernel/vmlinux.lds.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-at91/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-at91/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-at91/board-eco920.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-at91/cpuidle.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-at91/pm.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-at91/pm.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-bcmring/arch.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/Kconfig 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/Makefile 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/Makefile.boot 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/addr-map.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/common.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/common.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/dove-db-setup.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/include/mach/bridge-regs.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/include/mach/debug-macro.S 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/include/mach/dove.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/include/mach/entry-macro.S 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/include/mach/gpio.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/include/mach/hardware.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/include/mach/io.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/include/mach/irqs.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/include/mach/memory.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/include/mach/pm.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/include/mach/system.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/include/mach/timex.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/include/mach/uncompress.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/include/mach/vmalloc.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/irq.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-dove/pcie.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ep93xx/core.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-iop13xx/iq81340mc.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-iop13xx/iq81340sc.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-iop32x/em7210.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-iop32x/glantank.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-iop32x/iq31244.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-iop32x/iq80321.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-iop32x/n2100.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-iop33x/iq80331.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-iop33x/iq80332.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-kirkwood/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-kirkwood/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-kirkwood/ts41x-setup.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-kirkwood/tsx1x-common.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-kirkwood/tsx1x-common.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mmp/aspenite.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mmp/clock.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mmp/clock.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mmp/pxa168.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mmp/pxa910.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mmp/ttc_dkb.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx2/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx2/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx2/clock_imx21.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx2/clock_imx27.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx2/devices.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx2/devices.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx2/mxt_td60.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx2/pca100.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx3/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx3/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx3/armadillo5x0.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx3/clock-imx35.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx3/clock.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx3/cpu.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx3/devices.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx3/devices.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx3/kzmarm11.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx3/mx31lilly-db.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx3/mx31lilly.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx3/mx31lite-db.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx3/mx31lite.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx3/mx31moboard.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx3/mx35pdk.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-mx3/pcm043.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-nomadik/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-nomadik/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/board-fsample.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/board-generic.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/board-h2-mmc.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/board-h2.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/board-h3-mmc.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/board-h3.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/board-htcherald.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/board-osk.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/board-palmte.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/board-palmtt.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/board-palmz71.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/board-sx1-mmc.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/board-sx1.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/clock.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/clock.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/devices.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/fpga.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/id.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/include/mach/clkdev.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/include/mach/debug-macro.S 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/include/mach/entry-macro.S 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/include/mach/gpio.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/include/mach/hardware.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/include/mach/io.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/include/mach/irqs.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/include/mach/memory.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/include/mach/smp.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/include/mach/system.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/include/mach/timex.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/include/mach/uncompress.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/include/mach/vmalloc.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/io.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/irq.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/leds.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/mailbox.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/mcbsp.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/mux.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/pm.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/pm.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/serial.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/sleep.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap1/timer32k.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/board-2430sdp.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/board-3430sdp.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/board-3630sdp.c 0 → 100755
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/board-4430sdp.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/board-am3517evm.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/board-apollon.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/board-cm-t35.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/board-generic.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/board-h4.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/board-igep0020.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/board-ldp.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/board-n8x0.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/board-overo.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/board-rx51-sdram.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/board-rx51.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/board-zoom-peripherals.c 0 → 100755
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/board-zoom2.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/board-zoom3.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/clock.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/clock.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/clock24xx.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/clock34xx.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/clock34xx.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/clockdomain.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/clockdomains.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/cm.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/control.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/cpuidle34xx.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/devices.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/emu.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/gpmc-onenand.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/gpmc-smc91x.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/gpmc.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/id.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/include/mach/board-zoom.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/include/mach/clkdev.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/include/mach/gpio.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/include/mach/hardware.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/include/mach/io.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/include/mach/irqs.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/include/mach/memory.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/include/mach/smp.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/include/mach/system.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/include/mach/timex.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/include/mach/uncompress.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/io.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/iommu2.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/irq.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/mailbox.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/mcbsp.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/mmc-twl4030.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/mux.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/omap-smp.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/omap3-iommu.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/omap_hwmod.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/pm-debug.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/pm.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/pm24xx.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/pm34xx.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/powerdomain.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/powerdomains.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/prcm.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/prm.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/sdram-hynix-h8mbx00u0mer-0em.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/sdrc.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/sdrc.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/sdrc2xxx.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/serial.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/sleep24xx.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/sleep34xx.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/sram242x.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/sram243x.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/timer-gp.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/usb-ehci.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/usb-musb.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-omap2/usb-tusb6010.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/balloon3.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/cm-x2xx.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/cm-x300.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/colibri-pxa270.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/colibri-pxa300.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/colibri-pxa320.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/colibri-pxa3xx.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/corgi.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/corgi_pm.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/cpufreq-pxa2xx.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/cpufreq-pxa3xx.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/csb726.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/devices.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/e330.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/e350.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/e400.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/e740.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/e750.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/e800.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/em-x270.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/ezx.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/generic.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/gumstix.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/h5000.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/himalaya.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/hx4700.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/idp.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/imote2.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/include/mach/palmtreo.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/include/mach/regs-u2d.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/include/mach/treo680.h 已删除 100644 → 0
浏览文件 @ 11c34c7d
此差异已折叠。
arch/arm/mach-pxa/littleton.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/lpd270.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/lubbock.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/magician.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/mainstone.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/mioa701.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/mp900.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/palmld.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/palmt5.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/palmtc.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/palmte2.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/palmtx.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/palmz72.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/pcm027.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/poodle.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/pxa25x.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/pxa27x.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/pxa3xx.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/saar.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/sharpsl.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/sharpsl_pm.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/spitz.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/spitz_pm.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/ssp.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/stargate2.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/tavorevb.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/tosa.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/trizeps4.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/viper.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/xcep.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-pxa/zylonite.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2410/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2410/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2410/bast-irq.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2410/cpu-freq.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2410/mach-bast.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2410/mach-h1940.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2410/mach-n30.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2410/mach-qt2410.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2410/mach-vr1000.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2410/pll.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2410/usb-simtec.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2412/mach-jive.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2412/mach-vstms.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2440/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2440/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2440/irq.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2440/mach-anubis.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2440/mach-osiris-dvs.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2440/mach-osiris.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2440/mach-rx3715.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c2442/mach-gta02.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c6400/s3c6400.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c6410/cpu.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s3c6410/mach-hmt.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s5pc100/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s5pc100/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s5pc100/cpu.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s5pc100/include/mach/regs-fb.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-s5pc100/setup-sdhci.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-sa1100/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-sa1100/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-sa1100/assabet.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-sa1100/badge4.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-sa1100/cerf.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-sa1100/collie.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-sa1100/generic.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-sa1100/generic.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-sa1100/h3100.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-sa1100/h3600.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-sa1100/h3xxx.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-sa1100/hackkit.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-sa1100/include/mach/h3600.h 已删除 100644 → 0
浏览文件 @ 11c34c7d
此差异已折叠。
arch/arm/mach-sa1100/include/mach/h3xxx.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-sa1100/jornada720.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-sa1100/lart.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-sa1100/pleb.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-sa1100/shannon.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-sa1100/simpad.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-u300/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-u300/i2c.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-u300/mmc.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-u300/regulator.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/Kconfig 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/Makefile 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/Makefile.boot 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/board-mop500.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/clock.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/cpu-u8500.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/headsmp.S 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/include/mach/clkdev.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/include/mach/debug-macro.S 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/include/mach/entry-macro.S 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/include/mach/hardware.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/include/mach/io.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/include/mach/irqs.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/include/mach/memory.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/include/mach/setup.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/include/mach/smp.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/include/mach/system.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/include/mach/timex.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/include/mach/uncompress.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/include/mach/vmalloc.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/localtimer.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-ux500/platsmp.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mach-w90x900/dev.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mm/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mm/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mm/cache-l2x0.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mm/cache-tauros2.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mm/copypage-v6.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mm/dma-mapping.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mm/fault-armv.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mm/flush.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mm/mm.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mm/mmu.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mm/proc-v6.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mm/proc-xsc3.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mm/vmregion.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/mm/vmregion.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-iop/time.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-mxc/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-mxc/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-mxc/audmux-v1.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-mxc/audmux-v2.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-mxc/dma-mx1-mx2.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-mxc/gpio.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-mxc/include/mach/audmux.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-mxc/include/mach/board-kzmarm11.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-mxc/include/mach/ulpi.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-mxc/iomux-v3.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-mxc/ulpi.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-nomadik/Kconfig 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-nomadik/Makefile 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/clock.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/common.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/cpu-omap.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/debug-devices.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/debug-leds.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/devices.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/dma.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/dmtimer.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/fb.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/gpio.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/i2c.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/include/plat/omap7xx.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/io.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/iommu-debug.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/iommu.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/iovmm.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/mailbox.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/mcbsp.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/mux.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/omap-pm-noop.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/omap_device.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/sram.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-omap/usb.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c/clock.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c/dev-hsmmc2.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c/dev-i2c0.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c/dev-i2c1.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c/dev-nand.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c/dma.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c/include/plat/fb.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c/include/plat/regs-fb-v4.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c/pm-check.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c/pm.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c24xx/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c24xx/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c24xx/clock-dclk.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c24xx/common-smdk.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c24xx/cpu-freq.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c24xx/dma.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c24xx/irq-pm.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c24xx/irq.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c24xx/pm-simtec.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c24xx/pm.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c24xx/s3c244x-irq.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c24xx/simtec-audio.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c64xx/cpu.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c64xx/cpufreq.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c64xx/dev-audio.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c64xx/gpiolib.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s3c64xx/irq-eint.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s5pc1xx/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s5pc1xx/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s5pc1xx/clock.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s5pc1xx/cpu.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s5pc1xx/gpio-config.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s5pc1xx/gpiolib.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s5pc1xx/include/plat/gpio-cfg-s5pc1xx.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s5pc1xx/include/plat/gpio-ext.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s5pc1xx/include/plat/regs-gpio.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s5pc1xx/include/plat/regs-power.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s5pc1xx/irq-eint.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s5pc1xx/irq-gpio.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s5pc1xx/irq.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s5pc1xx/setup-fb-24bpp.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s5pc1xx/setup-i2c0.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s5pc1xx/setup-i2c1.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-s5pc1xx/setup-sdhci-gpio.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-samsung/Kconfig 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/plat-samsung/Makefile 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/arm/tools/mach-types
浏览文件 @ bcd6acd5
此差异已折叠。
arch/avr32/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/avr32/include/asm/bug.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/avr32/include/asm/cacheflush.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/avr32/include/asm/socket.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/avr32/kernel/syscall_table.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/blackfin/kernel/bfin_dma_5xx.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/blackfin/kernel/process.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/blackfin/kernel/ptrace.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/blackfin/mach-bf561/atomic.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/blackfin/mach-common/entry.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/blackfin/mach-common/smp.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/cris/include/asm/cacheflush.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/cris/include/asm/socket.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/frv/include/asm/cacheflush.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/frv/include/asm/socket.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/frv/kernel/pm.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/frv/kernel/sysctl.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/h8300/include/asm/cacheflush.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/h8300/include/asm/socket.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/ia64/ia32/ia32_entry.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/ia64/ia32/sys_ia32.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/ia64/include/asm/cacheflush.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/ia64/include/asm/kvm.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/ia64/include/asm/kvm_host.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/ia64/include/asm/socket.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/ia64/include/asm/swiotlb.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/ia64/include/asm/unistd.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/ia64/kernel/crash.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/ia64/kernel/entry.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/ia64/kernel/pci-swiotlb.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/ia64/kernel/perfmon.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/ia64/kvm/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/ia64/kvm/kvm-ia64.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/m32r/include/asm/cacheflush.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/m32r/include/asm/socket.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/m68k/include/asm/ptrace.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/m68k/include/asm/socket.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/m68k/kernel/entry.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/m68k/kernel/process.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/m68k/kernel/ptrace.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/m68k/kernel/vmlinux-std.lds
浏览文件 @ bcd6acd5
此差异已折叠。
arch/m68k/kernel/vmlinux-sun3.lds
浏览文件 @ bcd6acd5
此差异已折叠。
arch/m68knommu/kernel/ptrace.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/microblaze/include/asm/prom.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/microblaze/kernel/head.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/microblaze/kernel/prom.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/mips/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/mips/include/asm/bug.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/mips/include/asm/cacheflush.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/mips/include/asm/mman.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/mips/include/asm/socket.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/mips/include/asm/system.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/mips/include/asm/unistd.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/mips/kernel/linux32.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/mips/kernel/scall32-o32.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/mips/kernel/scall64-64.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/mips/kernel/scall64-n32.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/mips/kernel/scall64-o32.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/mips/kernel/syscall.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/mips/lasat/sysctl.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/mips/rb532/devices.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/mn10300/include/asm/socket.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/parisc/include/asm/socket.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/parisc/kernel/sys_parisc32.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/parisc/kernel/syscall_table.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/parisc/kernel/unwind.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/parisc/kernel/vmlinux.lds.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/Kconfig.debug
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/include/asm/hvcall.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/include/asm/prom.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/include/asm/reg.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/include/asm/socket.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/include/asm/trace.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kernel/align.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kernel/entry_64.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kernel/idle.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kernel/irq.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kernel/perf_event.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kernel/power5+-pmu.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kernel/power5-pmu.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kernel/power6-pmu.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kernel/power7-pmu.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kernel/ppc970-pmu.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kernel/prom.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kernel/setup-common.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kernel/setup_32.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kernel/setup_64.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kernel/sys_ppc32.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kernel/time.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kernel/traps.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kvm/powerpc.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/kvm/timing.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/powerpc/lib/copypage_64.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/s390/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/s390/appldata/appldata_base.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/s390/include/asm/bug.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/s390/include/asm/cacheflush.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/s390/include/asm/kvm.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/s390/include/asm/socket.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/s390/include/asm/spinlock.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/s390/kernel/compat_linux.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/s390/kernel/compat_linux.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/s390/kernel/compat_wrapper.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/s390/kernel/debug.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/s390/kernel/ftrace.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/s390/kvm/kvm-s390.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/s390/kvm/sigp.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/s390/mm/cmm.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/score/include/asm/cacheflush.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sh/boards/mach-hp6xx/setup.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sh/boards/mach-se/7724/setup.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sh/include/asm/cacheflush.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sh/include/asm/sh_eth.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sh/kernel/syscalls_64.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sh/kernel/traps_64.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/include/asm/btext.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/include/asm/leon.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/include/asm/prom.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/include/asm/rwsem.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/include/asm/smp_32.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/include/asm/socket.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/include/asm/unistd.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/apc.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/auxio_32.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/btext.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/cpu.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/entry.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/head_32.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/ioport.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/irq_64.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/leon_kernel.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/leon_smp.c 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/pci_msi.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/setup_64.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/smp_32.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/sys_sparc32.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/systbls_32.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/systbls_64.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/time_32.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/kernel/trampoline_32.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/mm/init_64.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/sparc/mm/srmmu.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/Kconfig
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/Kconfig.cpu
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/Kconfig.debug
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/Makefile_32.cpu
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/boot/compressed/head_64.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/boot/video.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/ia32/ia32entry.S
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/ia32/sys_ia32.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/Kbuild
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/a.out-core.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/acpi.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/alternative.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/amd_iommu.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/amd_iommu_proto.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/apic.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/apicdef.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/apicnum.h 已删除 100644 → 0
浏览文件 @ 11c34c7d
此差异已折叠。
arch/x86/include/asm/bug.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/cache.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/cacheflush.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/calgary.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/cmpxchg_32.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/cmpxchg_64.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/debugreg.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/device.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/dma-mapping.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/e820.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/elf.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/entry_arch.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/gart.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/hardirq.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/hw_breakpoint.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/hw_irq.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/inat.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/inat_types.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/insn.h 0 → 100644
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/iommu.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/irq.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/irq_vectors.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/k8.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/kvm.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/kvm_emulate.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/kvm_host.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/mce.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/microcode.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/mpspec.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/msr.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/page_types.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/perf_event.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/pgtable.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/processor.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/proto.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/ptrace.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/sections.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/string_32.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/svm.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/swiotlb.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/sys_ia32.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/system.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/thread_info.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/uaccess.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/uaccess_32.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/uaccess_64.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/unistd_32.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/unistd_64.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/uv/uv_irq.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/vmx.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/include/asm/x86_init.h
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/kernel/Makefile
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/kernel/acpi/processor.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/kernel/acpi/sleep.c
浏览文件 @ bcd6acd5
此差异已折叠。
arch/x86/kernel/amd_iommu.c
浏览文件 @ bcd6acd5
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或