提交 · ed402af3c23a4804b3f8899263e8d0f97c62ab49 · OpenHarmony / kernel_linux

20 10月, 2008 22 次提交

kdump: make elfcorehdr_addr independent of CONFIG_PROC_VMCORE · 57cac4d1

由 Vivek Goyal 提交于 10月 18, 2008

o elfcorehdr_addr is used by not only the code under CONFIG_PROC_VMCORE
  but also by the code which is not inside CONFIG_PROC_VMCORE.  For
  example, is_kdump_kernel() is used by powerpc code to determine if
  kernel is booting after a panic then use previous kernel's TCE table.
  So even if CONFIG_PROC_VMCORE is not set in second kernel, one should be
  able to correctly determine that we are booting after a panic and setup
  calgary iommu accordingly.

o So remove the assumption that elfcorehdr_addr is under
  CONFIG_PROC_VMCORE.

o Move definition of elfcorehdr_addr to arch dependent crash files.
  (Unfortunately crash dump does not have an arch independent file
  otherwise that would have been the best place).

o kexec.c is not the right place as one can Have CRASH_DUMP enabled in
  second kernel without KEXEC being enabled.

o I don't see sh setup code parsing the command line for
  elfcorehdr_addr.  I am wondering how does vmcore interface work on sh.
  Anyway, I am atleast defining elfcoredhr_addr so that compilation is not
  broken on sh.
Signed-off-by: NVivek Goyal <vgoyal@redhat.com>
Acked-by: N"Eric W. Biederman" <ebiederm@xmission.com>
Acked-by: NSimon Horman <horms@verge.net.au>
Acked-by: NPaul Mundt <lethal@linux-sh.org>
Cc: Ingo Molnar <mingo@elte.hu>
Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>

57cac4d1

container freezer: implement freezer cgroup subsystem · dc52ddc0

由 Matt Helsley 提交于 10月 18, 2008

This patch implements a new freezer subsystem in the control groups
framework.  It provides a way to stop and resume execution of all tasks in
a cgroup by writing in the cgroup filesystem.

The freezer subsystem in the container filesystem defines a file named
freezer.state.  Writing "FROZEN" to the state file will freeze all tasks
in the cgroup.  Subsequently writing "RUNNING" will unfreeze the tasks in
the cgroup.  Reading will return the current state.

* Examples of usage :

   # mkdir /containers/freezer
   # mount -t cgroup -ofreezer freezer  /containers
   # mkdir /containers/0
   # echo $some_pid > /containers/0/tasks

to get status of the freezer subsystem :

   # cat /containers/0/freezer.state
   RUNNING

to freeze all tasks in the container :

   # echo FROZEN > /containers/0/freezer.state
   # cat /containers/0/freezer.state
   FREEZING
   # cat /containers/0/freezer.state
   FROZEN

to unfreeze all tasks in the container :

   # echo RUNNING > /containers/0/freezer.state
   # cat /containers/0/freezer.state
   RUNNING

This is the basic mechanism which should do the right thing for user space
task in a simple scenario.

It's important to note that freezing can be incomplete.  In that case we
return EBUSY.  This means that some tasks in the cgroup are busy doing
something that prevents us from completely freezing the cgroup at this
time.  After EBUSY, the cgroup will remain partially frozen -- reflected
by freezer.state reporting "FREEZING" when read.  The state will remain
"FREEZING" until one of these things happens:

	1) Userspace cancels the freezing operation by writing "RUNNING" to
		the freezer.state file
	2) Userspace retries the freezing operation by writing "FROZEN" to
		the freezer.state file (writing "FREEZING" is not legal
		and returns EIO)
	3) The tasks that blocked the cgroup from entering the "FROZEN"
		state disappear from the cgroup's set of tasks.

[akpm@linux-foundation.org: coding-style fixes]
[akpm@linux-foundation.org: export thaw_process]
Signed-off-by: NCedric Le Goater <clg@fr.ibm.com>
Signed-off-by: NMatt Helsley <matthltc@us.ibm.com>
Acked-by: NSerge E. Hallyn <serue@us.ibm.com>
Tested-by: NMatt Helsley <matthltc@us.ibm.com>
Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>

dc52ddc0

sh: Move SH-4 CPU headers down one more level. · 40e24c40

由 Paul Mundt 提交于 10月 20, 2008

These accidentally got placed in to cpu-sh4 instead of cpu-sh4/cpu, push
them down one more level.
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

40e24c40

sh: Only build in gpio.o when CONFIG_GENERIC_GPIO is selected. · ebf9c118

由 Paul Mundt 提交于 10月 20, 2008

The pinmux management is tied in to this code, while it is presently only
used by platforms that select GENERIC_GPIO. The asm/gpio.h definitions
are not referenced when GENERIC_GPIO is disabled, resulting in a build
failure for all of the platforms that don't select it.
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

ebf9c118

P
sh: Migrate common board headers to mach-common/. · 7639a454
由 Paul Mundt 提交于 10月 20, 2008
```
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
```
7639a454
P
sh: Move the CPU definition headers from asm/ to cpu/. · f7275650
由 Paul Mundt 提交于 10月 20, 2008
```
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
```
f7275650

sh: remove consistent alloc cruft · 77137187

由 Magnus Damm 提交于 10月 09, 2008

Remove left overs from the generic declared coherent rework.
Signed-off-by: NMagnus Damm <damm@igel.co.jp>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

77137187

sh: add dynamic crash base address support · 4aeaa223

由 Magnus Damm 提交于 10月 09, 2008

Add support for dynamic crash kernel base address.
Signed-off-by: NMagnus Damm <damm@igel.co.jp>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

4aeaa223

sh: reduce Migo-R smc91x overruns · a30c89ad

由 Magnus Damm 提交于 10月 09, 2008

Improve Migo-R ethernet performance by reducing smc91x overruns.
This is done by enabling SMC91X_NOWAIT and optimizing CS4 setup.
Signed-off-by: NMagnus Damm <damm@igel.co.jp>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

a30c89ad

P
sh: Fix up some merge damage. · 9a19eb2a
由 Paul Mundt 提交于 10月 20, 2008
```
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
```
9a19eb2a

Fix debugfs_create_file's error checking method for arch/sh/mm/ · 25627c7f

由 Zhaolei 提交于 10月 17, 2008

debugfs_create_file() returns NULL if an error occurs, returns -ENODEV
when debugfs is not enabled in the kernel.
Signed-off-by: NZhao Lei <zhaolei@cn.fujitsu.com>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

25627c7f

Fix debugfs_create_dir's error checking method for arch/sh/kernel/ · 9986b311

由 Zhaolei 提交于 10月 17, 2008

debugfs_create_dir() returns NULL if an error occurs, returns -ENODEV
when debugfs is not enabled in the kernel.
Signed-off-by: NZhao Lei <zhaolei@cn.fujitsu.com>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

9986b311

sh: ap325rxa: Add support RTC RX-8564LC in AP325RXA board · a3e02706

由 Nobuhiro Iwamatsu 提交于 10月 17, 2008

Renesas AP325RXA board has Epson RX-8564LC of RTC.
This patch supports RTC of this board.
Signed-off-by: NNobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

a3e02706

sh: Use sh7720 GPIO on magicpanelr2 board · 843284d0