On 03/10/2013 03:25 AM, Pekka Enberg wrote:
What is preventing us from making the 64-bit variant also work in flat
mode to make the code consistent and not hiding the differences under
the rug? What am I missing here?
There is no such thing as flat mode in 64-bit mode. We use a #PF
On Thu, Apr 04, 2013 at 09:12:25PM +0200, Borislav Petkov wrote:
On Thu, Apr 04, 2013 at 12:18:04PM -0500, Jacob Shin wrote:
@@ -574,6 +577,45 @@ static struct common_dbs_data od_dbs_cdata = {
.exit = od_exit,
};
+static void od_set_powersave_bias(unsigned int powersave_bias)
On 04/04/2013 01:23 PM, Julien Tinnes wrote:
On Thu, Apr 4, 2013 at 1:19 PM, Julien Tinnes j...@google.com wrote:
On Thu, Apr 4, 2013 at 1:12 PM, H. Peter Anvin h...@zytor.com wrote:
On 04/04/2013 01:07 PM, Kees Cook wrote:
However, the benefits of
this feature in certain environments exceed
On Thu, Apr 04, 2013 at 09:23:23PM +0200, Borislav Petkov wrote:
On Thu, Apr 04, 2013 at 11:19:04AM -0500, Jacob Shin wrote:
Future AMD processors, starting with Family 16h, can provide software
with feedback on how the workload may respond to frequency change --
memory-bound workloads will
I have not tested it yet, but I am pretty sure it won't work. It
looks like the patch changes the BLKRRPART path to go ahead and remove
existing partitions when GENHD_FL_NO_PARTSCAN is set. loop doesn't
issue the BLKRRPART ioctl when !LO_FLAGS_PARTSCAN so this won't help.
I think loop
changed is not initialized in path_power_down_sync, but it is expected
to be false in case no change happened in the loop. So set it to
false.
Signed-off-by: Jiri Slaby jsl...@suse.cz
Cc: Jaroslav Kysela pe...@perex.cz
Cc: Takashi Iwai ti...@suse.de
---
sound/pci/hda/hda_generic.c | 2 +-
1 file
In build, we open a file, read that but do not close it. Fix that by
sticking fclose at the right place.
Signed-off-by: Jiri Slaby jsl...@suse.cz
Cc: H. Peter Anvin h...@zytor.com
Cc: Thomas Gleixner t...@linutronix.de
Cc: Ingo Molnar mi...@redhat.com
Cc: x...@kernel.org
---
ret might be uninitialized and is returned that way when kstrdup of
rbd_dev-spec-snap_name fails. Fix it by returning ENOMEM from that
place.
Signed-off-by: Jiri Slaby jsl...@suse.cz
---
drivers/block/rbd.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
rc_unregister_device already calls rc_free_device to free the passed
device. But in one of ttusbir's probe fail paths, we call
rc_unregister_device _and_ rc_free_device. This is wrong and results
in a double free.
Instead, set rc to NULL resulting in rc_free_device being a noop.
Signed-off-by:
In pointer_press_speed_show, we do
data_pointer = hid_get_drvdata(hdev);
twice in a row. Remove one of those.
Signed-off-by: Jiri Slaby jsl...@suse.cz
Cc: Jiri Kosina jkos...@suse.cz
Cc: linux-in...@vger.kernel.org
---
drivers/hid/hid-lenovo-tpkbd.c | 2 --
1 file changed, 2 deletions(-)
On Thu, Apr 4, 2013 at 2:04 PM, Neil Horman nhor...@tuxdriver.com wrote:
On Thu, Apr 04, 2013 at 10:40:07AM -0700, Yinghai Lu wrote:
On Thu, Apr 4, 2013 at 10:27 AM, Don Dutile ddut...@redhat.com wrote:
You need to move the quirk to early_quirk to append nointremap to
avoid extra rebooting.
tty_port_tty_get might return a tty which is NULL. But it is
dereferenced unconditionally in edge_send. Stop dereferencing that by
sending usb_serial_port pointer around.
Signed-off-by: Jiri Slaby jsl...@suse.cz
Cc: Johan Hovold jhov...@gmail.com
Cc: linux-...@vger.kernel.org
---
On Thu, Apr 4, 2013 at 6:49 PM, Peter Zijlstra pet...@infradead.org wrote:
On Thu, 2013-04-04 at 15:31 +0200, Daniel Vetter wrote:
We've discussed this approach of using (rt-prio, age) instead of just
age
to determine the the oldness of a task for deadlock-breaking with
-EAGAIN. The problem
On Thu, Apr 04, 2013 at 12:12:05PM -0500, Nathan Zimmer wrote:
Ok I am cloning the tree now.
It does look like the patches would conflict.
I'll run some tests and take a deeper look.
FWIW, I've just pushed there a tentative patch that switches to hopefully
saner locking (head should be at
On Thu, 2013-04-04 at 21:44 +0200, Borislav Petkov wrote:
ahci :00:1f.2: DMA-API: device driver maps memory fromstack
[addr=88040df2da50]
I fixed this already.
On Thu, Apr 4, 2013 at 1:21 PM, H. Peter Anvin h...@zytor.com wrote:
I have to admit to being somewhat skeptical toward KASLR with only 8
bits of randomness.
I agree that 8 bits is pretty low and more would be better. However,
even 8 bits provides a 1% chance that any particular guess will be
On Thu, Apr 4, 2013 at 1:27 PM, H. Peter Anvin h...@zytor.com wrote:
On 04/04/2013 01:23 PM, Julien Tinnes wrote:
On Thu, Apr 4, 2013 at 1:19 PM, Julien Tinnes j...@google.com wrote:
On Thu, Apr 4, 2013 at 1:12 PM, H. Peter Anvin h...@zytor.com wrote:
On 04/04/2013 01:07 PM, Kees Cook wrote:
On Tuesday, March 26, 2013 02:34:25 PM Rafael J. Wysocki wrote:
On Tuesday, March 19, 2013 11:41:01 AM Paul Bolle wrote:
Kconfig symbol ACPI_DEBUG_FUNC_TRACE was only used (through its
corresponding macro) in drivers/acpi/acpica/acmacros.h. That macro was
removed from that header in v3.8,
On Thu, Apr 4, 2013 at 1:12 PM, H. Peter Anvin h...@zytor.com wrote:
On 04/04/2013 01:07 PM, Kees Cook wrote:
However, the benefits of
this feature in certain environments exceed the perceived weaknesses[2].
Could you clarify?
I would summarize the discussion of KASLR weaknesses into to two
It seems to me that you are assuming that the attacker is targeting a specific
system, but a bot might as well target 256 different systems and see what
sticks...
Kees Cook keesc...@chromium.org wrote:
On Thu, Apr 4, 2013 at 1:12 PM, H. Peter Anvin h...@zytor.com wrote:
On 04/04/2013 01:07
On Thu, Apr 4, 2013 at 1:58 PM, H. Peter Anvin h...@zytor.com wrote:
It seems to me that you are assuming that the attacker is targeting a
specific system, but a bot might as well target 256 different systems and see
what sticks...
Certainly, but system monitoring will show 255 crashed
Natural evolution: when the cluster is the computer, kernel panics are
recoverable like segfaults in a multi-process OS.
You have a point and 8 bits isn't perfect, but it's already useful
regardless, in certain scenarios.
On Thu, Apr 4, 2013 at 1:58 PM, H. Peter Anvin h...@zytor.com wrote:
It
On Thu, Apr 4, 2013 at 1:58 PM, H. Peter Anvin h...@zytor.com wrote:
It seems to me that you are assuming that the attacker is targeting a
specific system, but a bot might as well target 256 different systems and see
what sticks...
The alarm signal from the ones that don't stick is, in my
What system monitoring? Most systems don't have much...
Kees Cook keesc...@chromium.org wrote:
On Thu, Apr 4, 2013 at 1:58 PM, H. Peter Anvin h...@zytor.com wrote:
It seems to me that you are assuming that the attacker is targeting a
specific system, but a bot might as well target 256
On 04/04/2013 22:45, David Woodhouse wrote:
On Thu, 2013-04-04 at 21:44 +0200, Borislav Petkov wrote:
ahci :00:1f.2: DMA-API: device driver maps memory fromstack
[addr=88040df2da50]
I fixed this already.
When CONFIG_XHCI_HCD_DEBUGGING is activated, the XHCI driver can dump
device and input contexts to the console. The endpoint contexts in that
dump are labeled Endpoint N Context, where N is DCI - 1... this is
very confusing, especially for people who are not that familiar with
the XHCI
On Thu, Apr 4, 2013 at 2:01 PM, H. Peter Anvin h...@zytor.com wrote:
What system monitoring? Most systems don't have much...
The security of an unmonitored system is going to be much lower than
of a well-monitored system. That's true independent of whether kASLR
is deployed.
Kees Cook
Hi Linus,
Please pull from the git repository at
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
pm+acpi-3.9-rc6
to receive ACPI and power management fixes for v3.9-rc6 with top-most commit
6cb437acd93a01fdbd6bac9c78ac8159c644e576
Merge branch 'acpi-fixes' into fixes
on
If an attacker targets multiple distinct systems across a wide range
of system owners, instead of landing the exploit against all of them,
they'll get less than 1% of them, and crash all the rest, removing
them (for a while) from the target pool. Without KASLR, they would
have landed 100% of the
On 04/03/2013 01:47 PM, Linus Walleij wrote:
From: Laurent Meunier laurent.meun...@st.com
This update adds a debugfs interface to modify a pin configuration
for a given state in the pinctrl map. This allows to modify the
configuration for a non-active state, typically sleep state.
This
On Thu, Apr 4, 2013 at 1:33 PM, Bjorn Helgaas bhelg...@google.com wrote:
See my last email to Bjorn. Doing this in early-quirks in such a way that we
can detect an iommu that has interrupt remapping enabled (so we don't just
unilaterally print this quirk all the time) requires that we be able
Quoting Peter De Schrijver (2013-04-04 01:20:44)
On Thu, Apr 04, 2013 at 01:23:05AM +0200, Stephen Warren wrote:
On 04/03/2013 12:27 PM, Stephen Warren wrote:
On 04/03/2013 11:52 AM, Stephen Warren wrote:
On 04/03/2013 08:40 AM, Peter De Schrijver wrote:
This is the nineth version of
On 04/03/2013 08:45 AM, Thierry Reding wrote:
Move the PCIe driver from arch/arm/mach-tegra into the drivers/pci/host
directory. The motivation is to collect various host controller drivers
in the same location in order to facilitate refactoring.
The Tegra PCIe driver has been largely
On 04/04/2013 03:28 PM, Stephen Warren wrote:
On 04/03/2013 08:45 AM, Thierry Reding wrote:
Move the PCIe driver from arch/arm/mach-tegra into the drivers/pci/host
directory. The motivation is to collect various host controller drivers
in the same location in order to facilitate refactoring.
On Thu, Apr 04, 2013 at 03:28:13PM -0500, Jacob Shin wrote:
Ah, okay .. here is the fixup:
From 7236287faa1a499686c9aac1d3f3f224516a7bbf Mon Sep 17 00:00:00 2001
From: Jacob Shin jacob.s...@amd.com
Date: Tue, 2 Apr 2013 09:56:56 -0500
Subject: [PATCH 1/2] cpufreq: ondemand: allow custom
Quoting Tushar Behera (2013-04-02 01:20:40)
In legacy setup, sclk_mmc{0,1,2,3} used PRE_RATIO bit-field (8-bit wide)
instead of RATIO bit-field (4-bit wide) for dividing clock rate.
With current common clock setup, we are using RATIO bit-field which
is creating FIFO read errors while
On Wed, Mar 13, 2013 at 5:28 PM, Yinghai Lu ying...@kernel.org wrote:
After they are put in add-on resources, they will be safely claimed later.
Signed-off-by: Yinghai Lu ying...@kernel.org
---
drivers/pci/quirks.c | 155
+++---
1 file changed,
Calling memcmp() to check the value of the first byte in a string is overkill.
Just use buf[0] == '1' or buf[0] != '1' as appropriate.
Signed-off-by: Tony Luck tony.l...@intel.com
---
[Inspired by a rant on IRC about a different driver doing something similar]
diff --git
From: John W. Linville linvi...@tuxdriver.com
Date: Wed, 3 Apr 2013 14:16:48 -0400
Here are some more fixes intended for the 3.9 stream...
Pulled, thanks John.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More
From: Francois Romieu rom...@fr.zoreil.com
Date: Tue, 2 Apr 2013 23:37:36 +0200
Hayes Wang hayesw...@realtek.com :
It would cause no link after suspending or shutdowning when the
nic changes the speed to 10M and connects to a link partner which
forces the speed to 100M.
Check the link
Francois what is the status of this patch set?
I see there is still some discussion about dependencies between
patch #5 and #6, is that resolved? If so, should I just apply
this series as-is?
Thanks!
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
On 04/04/2013 12:28 PM, Kirill A. Shutemov wrote:
Sasha Levin wrote:
On 04/04/2013 10:30 AM, Kirill A. Shutemov wrote:
Sasha Levin wrote:
Ping? I'm seeing a whole bunch of these with current -next.
Do you have a way to reproduce?
Not really, trinity just manages to make it happen quite
On Tue, 26 Mar 2013 14:07:14 -0400
Sasha Levin sasha.le...@oracle.com wrote:
Not necessarily, we do release everything at the end of the function:
out_unlock_free:
sem_unlock(sma, locknum);
Ow, there's a rcu_read_unlock() in sem_unlock()? This complicates things even
more I
On Thu, 2013-04-04 at 12:20 +0300, Or Gerlitz wrote:
On 04/04/2013 10:24, Nicholas A. Bellinger wrote:
+
+void isert_cq_tx_callback(struct ib_cq *, void *);
+void isert_cq_rx_callback(struct ib_cq *, void *);
+void isert_free_rx_descriptors(struct isert_conn *);
any reason not to have
On Wed, Mar 13, 2013 at 5:27 PM, Yinghai Lu ying...@kernel.org wrote:
Use resource pointer to get index in pci resources array/list.
-v2: export symbol for acpiphp compiling error, found by
Steven Newbury st...@snewbury.org.uk
Signed-off-by: Yinghai Lu ying...@kernel.org
---
This is a refresh for the zswap patchset. I am submitting this as a
candidate for merging in the v3.10 window. Just a few changes vs v7
and rebase to v3.9-rc5 (see Changelog section for details).
zswap greatly improves performance and reduces swap I/O on systems
in a state of VM thrashing (see
swap_writepage() is currently where frontswap hooks into the swap
write path to capture pages with the frontswap_store() function.
However, if a frontswap backend wants to resume the writeback of
a page to the swap device, it can't call swap_writepage() as
the page will simply reenter the backend.
=
DO NOT MERGE, FOR REVIEW ONLY
This patch introduces zsmalloc as new code, however, it already
exists in drivers/staging. In order to build successfully, you
must select EITHER to driver/staging version OR this version.
Once zsmalloc is reviewed in this format (and hopefully accepted),
I
This patch adds the documentation file for the zswap functionality
Signed-off-by: Seth Jennings sjenn...@linux.vnet.ibm.com
---
Documentation/vm/zswap.txt | 82 ++
1 file changed, 82 insertions(+)
create mode 100644 Documentation/vm/zswap.txt
diff
zswap is a thin compression backend for frontswap. It receives
pages from frontswap and attempts to store them in a compressed
memory pool, resulting in an effective partial memory reclaim and
dramatically reduced swap device I/O.
Additionally, in most cases, pages can be retrieved from this
This patch adds support for evicting swap pages that are currently
compressed in zswap to the swap device. This functionality is very
important and make zswap a true cache in that, once the cache is full
or can't grow due to memory pressure, the oldest pages can be moved
out of zswap to the swap
To prevent flooding the swap device with writebacks, frontswap
backends need to count and limit the number of outstanding
writebacks. The incrementing of the counter can be done before
the call to __swap_writepage(). However, the caller must receive
a notification when the writeback completes in
debugfs currently lack the ability to create attributes
that set/get atomic_t values.
This patch adds support for this through a new
debugfs_create_atomic_t() function.
Acked-by: Greg Kroah-Hartman gre...@linuxfoundation.org
Signed-off-by: Seth Jennings sjenn...@linux.vnet.ibm.com
---
This patch adds a documentation file for zsmalloc at
Documentation/vm/zsmalloc.txt
Signed-off-by: Seth Jennings sjenn...@linux.vnet.ibm.com
---
Documentation/vm/zsmalloc.txt | 68 +++
1 file changed, 68 insertions(+)
create mode 100644
Vivek found some problems with old kexec-tools.
We keep the old crashkernel=X to old behavoir, so it will not break
old kexec-tools.
Add crashkernel=X,high to support new kexec-tools that supports loading high.
when high is used, memblock will search from top to low.
if the allocated one is above
Vivek found old kexec-tools does not work new kernel anymore.
So change back crashkernel= back to old behavoir, and add crashkernel_high=
to let user decide if buffer could be above 4G, and also new kexec-tools will
be needed.
-v2: let crashkernel=X override crashkernel_high=
update
We can extend kexec-tools to support multiple Crash kernel in /proc/iomem
instead.
So we can use Crash kernel instead of Crash kernel low in /proc/iomem.
Suggested-by: Vivek Goyal vgo...@redhat.com
Signed-off-by: Yinghai Lu ying...@kernel.org
---
kernel/kexec.c |2 +-
1 file changed, 1
On Thu, 2013-04-04 at 12:45 +0300, Or Gerlitz wrote:
On 04/04/2013 10:24, Nicholas A. Bellinger wrote:
+#define ISER_RECV_DATA_SEG_LEN 8192
+#define ISER_RX_PAYLOAD_SIZE(ISER_HEADERS_LEN + ISER_RECV_DATA_SEG_LEN)
[...]
+#define ISER_RX_PAD_SIZE (16384 - (ISER_RX_PAYLOAD_SIZE + \
Per hpa, use crashkernel=XM;high crashkernel=YM;low instead of
crashkernel_hign=XM crashkernel_low=YM. As that could be extensible.
-v2: according to Vivek, change delimiter to ;
-v3: let hign and low only handle simple form and it conforms to
description in kernel-parameters.txt
On Wed, Mar 13, 2013 at 5:27 PM, Yinghai Lu ying...@kernel.org wrote:
From: Ram Pai linux...@us.ibm.com
Currently pci_dev structure holds an array of 17 PCI resources; six base
BARs, one ROM BAR, four BRIDGE BARs, six sriov BARs. This is wasteful.
A bridge device just needs the 4 bridge
Chao said that kdump does does work well on his system on 3.8
without extra parameter, even iommu does not work with kdump.
And now have to append crashkernel_low=Y in first kernel to make
kdump work.
We have now modified crashkernel=X to allocate memory beyong 4G (if
available) and do not
On Thursday 14 of March 2013, Arkadiusz Miśkiewicz wrote:
Hi.
Just hit watchdog related oops in 3.8.3 kernel. Unfortunately photos only.
http://ixion.pld-linux.org/~arekm/watchdog-oops-3.8.3/IMG_8942.JPG
http://ixion.pld-linux.org/~arekm/watchdog-oops-3.8.3/IMG_8941.JPG
3.9git from today
On Thu, 2013-04-04 at 12:51 +0300, Or Gerlitz wrote:
On 04/04/2013 10:24, Nicholas A. Bellinger wrote:
+static int
+isert_put_response(struct iscsi_conn *conn, struct iscsi_cmd *cmd)
+{
+ struct isert_cmd *isert_cmd = container_of(cmd,
+ struct
On Wed, Mar 13, 2013 at 5:27 PM, Yinghai Lu ying...@kernel.org wrote:
According to resource pointer find out if the resource is some type resource
like bridge, sriov, or std.
Signed-off-by: Yinghai Lu ying...@kernel.org
---
include/linux/pci.h | 23 +++
1 file
On 04/04/2013 01:12 AM, Stephane Eranian wrote:
On Wed, Apr 3, 2013 at 7:57 PM, John Stultz john.stu...@linaro.org wrote:
I'm not sure I follow this. If perf exported data came with CLOCK_MONOTONIC
timestamps, no correlation would need to be exposed. perf would just have
to do the extra
Regulator drivers may specify regulator_desc-supply_name which
regulator_register() will use to find the supply node for a regulator.
If no supply was specified in the device tree or the supply has yet
to be registered regulator_register() will fail, deferring the probe
of the regulator. In the
On Thursday, April 04, 2013 06:24:08 PM Viresh Kumar wrote:
Hi Rafael,
These are all the remaining patches i have for 3.10. All of them have received
Acks from their maintainers leaving powerpc ones. I have got an additional
patch
for powerpc (18) this time, it was the only driver left out
On Thu, Apr 04, 2013 at 12:01:52PM -0700, Hugh Dickins wrote:
On Thu, 4 Apr 2013, Linus Torvalds wrote:
On Thu, Apr 4, 2013 at 11:35 AM, Hugh Dickins hu...@google.com wrote:
find_vma() can be called by multiple threads with read lock
held on mm-mmap_sem and any of them can update
On 04/04/2013 05:10 PM, Seth Jennings wrote:
swap_writepage() is currently where frontswap hooks into the swap
write path to capture pages with the frontswap_store() function.
However, if a frontswap backend wants to resume the writeback of
a page to the swap device, it can't call
On Thu, 4 Apr 2013, Jiri Slaby wrote:
In pointer_press_speed_show, we do
data_pointer = hid_get_drvdata(hdev);
twice in a row. Remove one of those.
Signed-off-by: Jiri Slaby jsl...@suse.cz
Cc: Jiri Kosina jkos...@suse.cz
Cc: linux-in...@vger.kernel.org
---
Jiri Slaby jsl...@suse.cz writes:
ret might be uninitialized and is returned that way when kstrdup of
rbd_dev-spec-snap_name fails. Fix it by returning ENOMEM from that
place.
Signed-off-by: Jiri Slaby jsl...@suse.cz
---
drivers/block/rbd.c | 4 +++-
1 file changed, 3 insertions(+), 1
Jiri Slaby jsl...@suse.cz writes:
In pointer_press_speed_show, we do
data_pointer = hid_get_drvdata(hdev);
twice in a row. Remove one of those.
Signed-off-by: Jiri Slaby jsl...@suse.cz
Cc: Jiri Kosina jkos...@suse.cz
Cc: linux-in...@vger.kernel.org
---
drivers/hid/hid-lenovo-tpkbd.c
On 04/03/2013 06:34 PM, Stephen Warren wrote:
From: Stephen Warren swar...@nvidia.com
The recent dtc+cpp support allows header files and C pre-processor
defines/macros to be used when compiling device tree files. These
headers will typically define various constants that are part of the
Hi Al,
On Thu, 4 Apr 2013 09:10:11 +0100 Al Viro v...@zeniv.linux.org.uk wrote:
On Thu, Apr 04, 2013 at 12:02:53AM -0700, Andrew Morton wrote:
Well perhaps the vfs tree should start paying some attention to the
rest of the world, particularly after -rc5.
I can't even find this lift
On 04/04/2013 03:05 AM, Prashant Gaikwad wrote:
Correct IDs for cdev1 and cdev2 are 94 and 93 respectively.
I've applied this, split into the two patches I just posted.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
On 04/03/2013 08:40 AM, Peter De Schrijver wrote:
This is the nineth version of the Tegra114 clockframework. It is based on the
next-20130320-fixed branch of ...
I have applied this series to Tegra's for-3.10/clk branch, with patch
10/14 replaced by v9b.
--
To unsubscribe from this list: send
[...]
to give us some idea how much performance we would gain from each
approach? Thoughput should be completely unaffected anyway, since virtio
just coalesces kicks internally.
Latency is dominated by the scheduling latency.
This means virtio-net is not the best benchmark.
So
Now that all external cgroup_lock() users are gone, we can finally
unexport the locking interface and prevent future abuse of
cgroup_mutex.
Make cgroup_[un]lock() and cgroup_lock_live_group() static. Also,
cgroup_attach_task() doesn't have any user left and can't be used
without locking
We don't want controllers to assume that the information is officially
available and do funky things with it.
The only user is task_subsys_state_check() which uses it to verify RCU
access context. We can move cgroup_lock_is_held() inside
CONFIG_PROVE_RCU but that doesn't add meaningful
Now that locking interface is unexported, there's no reason to keep
around these thin wrappers. Kill them and use mutex operations
directly.
Signed-off-by: Tejun Heo t...@kernel.org
---
kernel/cgroup.c | 41 +++--
1 file changed, 11 insertions(+), 30
When a cpuset becomes empty (no CPU or memory), its tasks are
transferred with the nearest ancestor with execution resources. This
is implemented using cgroup_scan_tasks() with a callback which grabs
cgroup_mutex and invokes cgroup_attach_task() on each task.
Both cgroup_mutex and
cgroup_lock_live_group() and cgroup_attach_task() are scheduled to be
made static. Relocate the former and cgroup_attach_task_all() so that
we don't need forward declarations.
This patch is pure relocation.
Signed-off-by: Tejun Heo t...@kernel.org
---
kernel/cgroup.c | 84
Hello,
Most cgroup_mutex abuses outside cgroup core proper have been
eradicated but there's still one use remaining and locking interface
is still exported. This patchset updates the last user and unexports
the locking interface and is composed of the following five patches.
2013/4/4 Dave Hansen d...@sr71.net:
With the 3.9-rcs (and probably much earlier) I'm seeing some weird top
output where the cpu time spent is millions of hours:
445 root 20 0 000 S0 0.0 5124095h kworker/45:1
404 root 20 0 000 S0 0.0 5124095h
David Miller da...@davemloft.net :
[...]
I see there is still some discussion about dependencies between
patch #5 and #6, is that resolved?
Yes.
If so, should I just apply this series as-is ?
Yes.
- the series is imho -stable unfriendly: whoever wants to figure what
should be fed into a
Move node_possible_map handling out of numa_check_memblks to avoid side
changing in numa_check_memblks().
Only set once for successful path instead of resetting in numa_init()
every time.
Suggested-by: Tejun Heo t...@kernel.org
Signed-off-by: Yinghai Lu ying...@kernel.org
---
arch/x86/mm/numa.c
Parsing numa info has been separated to two functions now.
early_initmem_info() only parse info in numa_meminfo and
nodes_parsed. still keep numaq, acpi_numa, amd_numa, dummy
fall back sequence working.
SLIT and numa emulation handling are still left in initmem_init().
Call early_initmem_init
If node with ram is hotplugable, local node mem for page table and vmemmap
should be on that node ram.
This patch is some kind of refreshment of
| commit 1411e0ec3123ae4c4ead6bfc9fe3ee5a3ae5c327
| Date: Mon Dec 27 16:48:17 2010 -0800
|
|x86-64, numa: Put pgtable to local node memory
That
Prepare to put page table on local nodes.
Move calling of init_mem_mapping to early_initmem_init.
Rework alloc_low_pages to alloc page table in following order:
BRK, local node, low range
Still only load_cr3 one time, otherwise we would break xen 64bit again.
Signed-off-by: Yinghai Lu
Now we have arch_pfn_mapped array, and max_low_pfn_mapped should not
be used anymore.
User should use arch_pfn_mapped or just 1UL(32-PAGE_SHIFT) instead.
Only user is ACPI_INITRD_TABLE_OVERRIDE, and it should not use that,
as later accessing is using early_ioremap(). We could change to use
For finding with 32bit, it would be easy to access initrd in 32bit
flat mode, as we don't need to set page table.
That is from head_32.S, and microcode updating already use this trick.
Need to change acpi_initrd_override_find to use phys to access global
variables.
Pass is_phys in the function,
We need to handle slit later, as it need to allocate buffer for distance
matrix. Also we do not need SLIT info before init_mem_mapping.
So move SLIT parsing later.
x86_acpi_numa_init become x86_acpi_numa_init_srat/x86_acpi_numa_init_slit.
It should not break ia64 by replacing acpi_numa_init
early_initmem_init() call early_x86_numa_init() to parse numa info early.
Later will call init_mem_mapping for nodes in it.
Signed-off-by: Yinghai Lu ying...@kernel.org
Cc: Pekka Enberg penb...@kernel.org
Cc: Jacob Shin jacob.s...@amd.com
---
arch/x86/include/asm/page_types.h | 1 +
We could use numa_meminfo directly instead of memblock nid.
So we could move down set memblock nid and only do it one time
for successful path.
-v2: according to tj, separate moving to another patch.
Signed-off-by: Yinghai Lu ying...@kernel.org
---
arch/x86/mm/numa.c | 30
Need to use get_ramdisk_image() with early microcode_updating in other file.
Change it to global.
Also make it to take boot_params pointer, as head_32.S need to access it via
phys address during 32bit flat mode.
Signed-off-by: Yinghai Lu ying...@kernel.org
Acked-by: Tejun Heo t...@kernel.org
---
As request by hpa, add comments for why we choose 5 for
step size shift.
Signed-off-by: Yinghai Lu ying...@kernel.org
---
arch/x86/mm/init.c | 21 ++---
1 file changed, 18 insertions(+), 3 deletions(-)
diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c
index 28b294f..2754e45
Current acpi tables in initrd is limited to 10, that is too small.
64 should be good enough as we have 35 sigs and could have several
SSDT.
Two problems in current code prevent us from increasing limit:
1. that cpio file info array is put in stack, as every element is 32
bytes, could run out
To parse srat early, we need to move acpi table probing early.
acpi_initrd_table_override is before acpi table probing. So we need to
move it early too.
Current code acpi_initrd_table_override is after init_mem_mapping and
relocate_initrd(), so it can scan initrd and copy acpi tables with kernel
Move node_map_pfn_alignment() to arch/x86/mm as no other user for it.
Will update it to use numa_meminfo instead of memblock.
Signed-off-by: Yinghai Lu ying...@kernel.org
---
arch/x86/mm/numa.c | 50 ++
include/linux/mm.h | 1 -
mm/page_alloc.c
head64.c could use #PF handler set page table to access initrd before
init mem mapping and initrd relocating.
head_32.S could use 32bit flat mode to access initrd before init mem
mapping initrd relocating.
That make 32bit and 64 bit more consistent.
-v2: use inline function in header file
501 - 600 of 1434 matches
Mail list logo
