On Mon, Aug 13, 2012 at 9:49 PM, Michal Hocko wrote:
>
> I will leave it as an excersise for the careful reader...
Is it too late for you to prepare a redelivery?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On Mon 13-08-12 21:24:36, Hillf Danton wrote:
> On Mon, Aug 13, 2012 at 9:09 PM, Michal Hocko wrote:
> > On Mon 13-08-12 20:10:41, Hillf Danton wrote:
> >> On Sun, Aug 12, 2012 at 5:31 PM, Michal Hocko wrote:
> >> > From d07b88a70ee1dbcc96502c48cde878931e7deb38 Mon Sep 17 00:00:00 2001
> >> >
On Mon, Aug 13, 2012 at 03:09:31PM +0200, Linus Walleij wrote:
> On Sun, Aug 5, 2012 at 10:43 PM, Anthony Olech
> > +#include
> If you're using regmap you better select it in Kconfig
> too, but it appears you don't. You should be using regmap in the
> main MFD driver in this case (I haven't
On Mon, Aug 13, 2012 at 12:57:03PM +0530, Bitan Biswas wrote:
> Hi Guenter,
>
> Thank you for the guidance.
>
> >>
> >>But looking at the hwmon linux documentation, seems the sensor
> >>kernel drivers should report only raw readings.
> >>The raw readings can be converted into required output,
>
On Mon, Aug 13, 2012 at 11:50 AM, IAN CHEN wrote:
> For several MoviNAND, there are some known issue with secure option.
> For these specific MoviNAND device, we skip secure option.
OK..
> diff --git a/include/linux/mmc/card.h b/include/linux/mmc/card.h
> index 111aca5..4505a30 100644
> ---
Afaics the usage of update_debugctlmsr() and TIF_BLOCKSTEP in
step.c was always very wrong.
1. update_debugctlmsr() was simply unneeded. The child sleeps
TASK_TRACED, __switch_to_xtra(next_p => child) should notice
TIF_BLOCKSTEP and set/clear DEBUGCTLMSR_BTF after resume if
needed.
2.
No functional changes, preparation for the next fix and for uprobes
single-step fixes.
Move the code playing with TIF_BLOCKSTEP/DEBUGCTLMSR_BTF into the
new helper, set_task_blockstep().
Signed-off-by: Oleg Nesterov
---
arch/x86/kernel/step.c | 41 +
1
On Sun, Aug 12, 2012 at 11:56:45PM -0700, Eric W. Biederman wrote:
> Fengguang Wu writes:
>
> > Hi Geert,
> >
> > This is the build error I get, on Eric's userns tree.
> >
> > tree:
> > git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
> > userns-always-map-user-v45
>
Hello.
The subject says "ptrace:", but we need these changes for uprobes.
Although I think this fix makes sense by itself. I am really
surprised how many problems this simple code has, or I am
totally confused (this is very possible).
Could someone review 2/2 ?
The next step will change
On Thu, Aug 9, 2012 at 5:00 PM, Otavio Salvador wrote:
> Hello,
>
> One of machines we have freeze during initialization from time to time:
>
> freeze at: http://download.ossystems.com.br/~otavio/geode-freeze.jpg
> works at: http://download.ossystems.com.br/~otavio/geode-working-dmesg.txt
>
>
On Mon, 13 Aug 2012, Peter Zijlstra wrote:
> OK, I like this.. Thanks guys! Will will you send a final and complete
> patch?
Here it is:
--- >8
Date: Fri, 10 Aug 2012 15:22:09 +0100
From: Will Deacon
Subject: [PATCH] mutex: place lock in contended state after fastpath_lock
failure
ARM
On Thu, Aug 9, 2012 at 1:38 PM, Alan Cox wrote:
>> Maybe tty can do this, but want to have all modem related separately.
>> There are many such hardware and many drivers coming up in near future.
>
> tty can't do all this. We have similar things with stuff like CAIF. Modem
> has gone from
KY Srinivasan writes:
> In the interim, I have submitted a patch that conforms to the MSFT guidelines
> for generating guest IDs for non-MSFT operating systems on Hyper-V.
Oh, sorry. I missed that. Found it now. Thanks
Including distro info in a driver interface looks a bit weird to me, but
Tejun Heo wrote:
> Convert delayed_work users doing cancel_delayed_work() followed by
> queue_delayed_work() to mod_delayed_work().
>
> Most conversions are straight-forward. Ones worth mentioning are,
>
> * drivers/edac/edac_mc.c: edac_mc_workq_setup() converted to always
> use
On 08/09, Sebastian Andrzej Siewior wrote:
>
> v1..v2: re-use auprobe->fixups for fixups
Yes, but
> @@ -46,6 +46,8 @@ struct arch_uprobe_task {
> #ifdef CONFIG_X86_64
> unsigned long saved_scratch_register;
> #endif
> +#define UPROBE_CLEAR_TF (1 <<
On Mon, Aug 13, 2012 at 09:20:55AM -0400, Steven Rostedt wrote:
> When I did a compile of perf using a relative path for the output
> directory, the build failed when it tried to compile libtraceevent. This
> is because it continues to use the same relative path when the new
> working directory is
On Mon, Aug 13, 2012 at 9:09 PM, Michal Hocko wrote:
> On Mon 13-08-12 20:10:41, Hillf Danton wrote:
>> On Sun, Aug 12, 2012 at 5:31 PM, Michal Hocko wrote:
>> > From d07b88a70ee1dbcc96502c48cde878931e7deb38 Mon Sep 17 00:00:00 2001
>> > From: Michal Hocko
>> > Date: Fri, 10 Aug 2012 15:03:07
* Oleg Nesterov [2012-08-08 19:37:49]:
> Now that we have uprobe_dup_mmap() we can fold uprobe_reset_state()
> into the new hook and remove it. mmput()->uprobe_clear_state() can't
> be called before dup_mmap().
>
> Signed-off-by: Oleg Nesterov
Acked-by: Srikar Dronamraju
--
To unsubscribe
* Oleg Nesterov [2012-08-08 19:37:47]:
> Add the new MMF_HAS_UPROBES flag. It is set by install_breakpoint()
> and it is copied by dup_mmap(), uprobe_pre_sstep_notifier() checks
> it to avoid the slow path if the task was never probed. Perhaps it
> makes sense to check it in
* Oleg Nesterov [2012-08-08 19:37:44]:
> -EEXIST from install_breakpoint() no longer makes sense, all
> callers should simply treat it as "success". Change the code
> to return zero and simplify register_for_each_vma().
>
> Signed-off-by: Oleg Nesterov
> ---
Acked-by: Srikar Dronamraju
--
To
* Oleg Nesterov [2012-08-08 19:37:42]:
> Once install_breakpoint() fails uprobe_mmap() "ignores" all other
> uprobes and returns the error.
>
> It was never really needed to to stop after the first error, and
> in fact it was always wrong at least in -ENOTSUPP case.
>
> Change uprobe_mmap() to
* Oleg Nesterov [2012-08-08 19:37:39]:
> 1. Kill dup_mmap()->uprobe_mmap(), it was only needed to calculate
>new_mm->uprobes_state.count removed by the previous patch.
>
>If the forking process has a pending uprobe (int3) in vma, it will
>be copied by copy_page_range(), note that it
When I did a compile of perf using a relative path for the output
directory, the build failed when it tried to compile libtraceevent. This
is because it continues to use the same relative path when the new
working directory is in a different path.
SUBDIR ../lib/traceevent/
/bin/sh: line 0:
On 08/09, Sebastian Andrzej Siewior wrote:
>
> * Oleg Nesterov | 2012-08-08 15:14:57 [+0200]:
>
> >> What I miss right now is an interface to tell the user/gdb that there is a
> >> program that hit a global breakpoint and is waiting for further
> >> instructions.
> >> A "tail -f trace" does not
On Fri, 3 Aug 2012, Jiri Kosina wrote:
> Historically, the top three bytes of personality have been used for things
> such as ADDR_NO_RANDOMIZE, which made sense only for specific
> architectures.
>
> We now, however, have a flag there that is general no matter the
> architecture (UNAME26);
* Oleg Nesterov [2012-08-08 19:37:37]:
> uprobes_state->count is only needed to avoid the slow path in
> uprobe_pre_sstep_notifier(). It is also checked in uprobe_munmap()
> but ironically its only goal to decrement this counter. However,
> it is very broken. Just some examples:
>
> -
Directly comparing current->personality against PER_LINUX32 doesn't work
in cases when any of the personality flags stored in the top three bytes
are used.
Directly forcefully setting personality to PER_LINUX32 or PER_LINUX
discards any flags stored in the top three bytes
Use personality()
On Mon, 2012-08-13 at 20:40 +0800, Huacai Chen wrote:
> When SWIOTLB is configured, if without this patch kernel compilation
> fails with such error messages:
>
> drivers/gpu/drm/radeon/radeon_ttm.c: In function 'radeon_ttm_tt_populate':
> drivers/gpu/drm/radeon/radeon_ttm.c:606:2: error:
Driver throw the warning message if dt node does not
have the info for VMBCH-Threshold and VMBCH2-Threshold.
These properties are optional property and hence it
is not mandatory to have these on DT node and in this case
it should not throw the warning message.
It creates noise from driver as
On Mon 13-08-12 12:05:38, Glauber Costa wrote:
> On 08/10/2012 10:54 PM, Michal Hocko wrote:
> > On Thu 09-08-12 17:01:10, Glauber Costa wrote:
> >> From: Suleiman Souhlal
> >>
> >> mem_cgroup_do_charge() was written before kmem accounting, and expects
> >> three cases: being called for 1 page,
Hi Anthony, sorry for delayed reply...
On Sun, Aug 5, 2012 at 10:43 PM, Anthony Olech
wrote:
> This is the GPIO component driver of the Dialog DA9058 PMIC.
> This driver is just one component of the whole DA9058 PMIC driver.
> It depends on the core DA9058 MFD driver.
OK
> +config GPIO_DA9058
On Mon 13-08-12 20:10:41, Hillf Danton wrote:
> On Sun, Aug 12, 2012 at 5:31 PM, Michal Hocko wrote:
> > From d07b88a70ee1dbcc96502c48cde878931e7deb38 Mon Sep 17 00:00:00 2001
> > From: Michal Hocko
> > Date: Fri, 10 Aug 2012 15:03:07 +0200
> > Subject: [PATCH] hugetlb: do not use
On Monday 13 August 2012, wei_w...@realsil.com.cn wrote:
> From: Wei WANG
>
> Realtek PCI-E SD/MMC card host driver is used to access SD/MMC card,
> with the help of Realtek PCI-E card reader MFD driver.
>
> Signed-off-by: Wei WANG
Acked-by: Arnd Bergmann
--
To unsubscribe from this list:
On Monday 13 August 2012, wei_w...@realsil.com.cn wrote:
> From: Wei WANG
>
> Realtek PCI-E card reader driver adapts requests from upper-level
> sdmmc/memstick layer to the real physical card reader.
>
> Signed-off-by: Wei WANG
Hi,
This looks pretty good overall, I'm generally happy with
> -Original Message-
> From: Bjørn Mork [mailto:bj...@mork.no]
> Sent: Monday, August 13, 2012 9:00 AM
> To: Greg KH
> Cc: KY Srinivasan; Paolo Bonzini; de...@linuxdriverproject.org; linux-
> ker...@vger.kernel.org
> Subject: Re: [PATCH] drivers: hv: use Linux version in guest ID
>
>
On Mon, 2012-08-13 at 10:03 +0200, Peter Zijlstra wrote:
> > +void perf_trace_event_submit(void *raw_data, struct ftrace_event_call
> > *event_call,
> > +struct perf_trace_event *pe)
> > +{
> > + struct hlist_head *head;
> > +
> > + head =
Hi. Ian.
known issue ? Would you explain more ?
Thanks.
2012/8/13 IAN CHEN :
> From 5c60eb8be04c7440d6e33b8f72ea2046a3657ac4 Mon Sep 17 00:00:00 2001
> From: ian.cy.chen
> Date: Mon, 13 Aug 2012 10:53:55 +0900
> Subject: [PATCH] mmc: card: Skip secure option for MoviNAND.
>
> For several
Greg KH writes:
> On Fri, Jul 20, 2012 at 04:02:44PM +, KY Srinivasan wrote:
>> > On Fri, Jul 20, 2012 at 10:03:08AM +0200, Bjørn Mork wrote:
>> >
>> > > +/* Linux vendor ID allocated by Microsoft */
>> > > +#define HV_LINUX_GUEST_ID_VENDOR0xB16B
>> > > +
>> > > +/* Creating a guest
Peter,
Ok, that should fix the problem that IBS would not work correctly in
per-thread mode.
I realized I was looking at an older kernel which did not have the
split between ibs
op and fetch. And there, the .task_nr_context was not initialized at all.
Your proposal solves the problem, though it
When poweroff machine, kernel_power_off() call disable_nonboot_cpus().
And if we have HOTPLUG_CPU configured, disable_nonboot_cpus() is not an
empty function but attempt to actually disable the nonboot cpus. Since
system state is SYSTEM_POWER_OFF, play_dead() won't be called and thus
Hey,
Op 11-08-12 21:39, Daniel Vetter schreef:
> +
> + if (!ret) {
> + cb->base.flags = 0;
> + cb->base.func = __dma_fence_wake_func;
> + cb->base.private = priv;
> + cb->fence = fence;
> + cb->func =
When SWIOTLB is configured, if without this patch kernel compilation
fails with such error messages:
drivers/gpu/drm/radeon/radeon_ttm.c: In function 'radeon_ttm_tt_populate':
drivers/gpu/drm/radeon/radeon_ttm.c:606:2: error: implicit declaration of
function 'swiotlb_nr_tbl'
This is a cleanup patch. The assignment is redundant.
---
ipc/msg.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/ipc/msg.c b/ipc/msg.c
index 7385de2..f3bfbb8 100644
--- a/ipc/msg.c
+++ b/ipc/msg.c
@@ -787,7 +787,6 @@ long do_msgrcv(int msqid, long *pmtype, void __user
On 07/27/2012 04:32 PM, Peter Zijlstra wrote:
> On Fri, 2012-07-27 at 09:47 +0800, Alex Shi wrote:
>
>> From 610515185d8a98c14c7c339c25381bc96cd99d93 Mon Sep 17 00:00:00 2001
>> From: Alex Shi
>> Date: Thu, 26 Jul 2012 08:55:34 +0800
>> Subject: [PATCH 1/3] sched: recover SD_WAKE_AFFINE in
v4:
1) If MSG_COPY flag is specified, then "mtype" is not a type, but message
number to copy.
2) MSG_SET_COPY logic for sys_msgctl() was removed.
v3:
1) Copy messages to user-space under spinlock was replaced by allocation of
dummy message before queue lock and then copy of desired message to the
This test is a part of CRIU development test suit.
---
tools/testing/selftests/ipc/msgque.c | 151 ++
1 files changed, 151 insertions(+), 0 deletions(-)
create mode 100644 tools/testing/selftests/ipc/msgque.c
diff --git a/tools/testing/selftests/ipc/msgque.c
This patch is required for checkpoint/restore in userspace.
IOW, c/r requires some way to get all pending IPC messages without deleting
them from the queue (checkpoint can fail and in this case tasks will be resumed,
so queue have to be valid).
To achive this, new operation flag MSG_COPY for
New SHM_SET command will be interpreted exactly as IPC_SET, but also will
update key, cuid and cgid values. IOW, it allows to change existent key value.
The fact, that key is not used is checked before update. Otherwise -EEXIST is
returned.
Signed-off-by: Stanislav Kinsbursky
Signed-off-by:
This patch moves all message related manipulation into one function msg_fill().
Actually, two functions because of the compat one.
Signed-off-by: Stanislav Kinsbursky
Signed-off-by: Cyrill Gorcunov
Conflicts:
arch/tile/kernel/compat.c
include/linux/compat.h
---
New SEM_SET command will be interpreted exactly as IPC_SET, but also will
update key, cuid and cgid values. IOW, it allows to change existent key value.
The fact, that key is not used is checked before update. Otherwise -EEXIST is
returned.
Signed-off-by: Stanislav Kinsbursky
Signed-off-by:
New MSG_SET command will be interpreted exactly as IPC_SET, but also will
update key, cuid and cgid values. IOW, it allows to change existent key value.
The fact, that key is not used is checked before update. Otherwise -EEXIST is
returned.
Signed-off-by: Stanislav Kinsbursky
Signed-off-by:
This patch introduces existent segment key changing infrastructure.
New function ipc_update_key() can be used change segment key, cuid, cgid
values. It checks for that new key is not used (except IPC_PRIVATE) prior to
set it on existent.
To make this possible, added copying of this fields from
This patch introduces new IPC resource get request flag IPC_PRESET, which
should be interpreted as a request to try to allocate IPC slot with number,
starting from value resented by key. IOW, kernel will try
allocate new segment in specified slot. If slot is not emply, them -EEXIST
returned.
On Fri, Aug 10, 2012 at 09:33:44AM +0800, Axel Lin wrote:
> This is not required after commit f7df20ec
> "regulator: core: Use list_voltage() to read single voltage regulators"
applied 2-6.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Sat, Aug 11, 2012 at 10:22:54AM +0800, Axel Lin wrote:
> We do have such case in drivers/regulator/max1586.c
They should have a read operation implemented.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On Mon, Aug 13, 2012 at 08:14:35PM +0800, Alex Shi wrote:
> commit cfd19c5a9ec (mm: only set page->pfmemalloc when
> ALLOC_NO_WATERMARKS was used) try to narrow down page->pfmemalloc
> setting, but it missed some places the pfmemalloc should be set.
>
> So, in __slab_alloc, the unalignment
On Fri, Aug 10, 2012 at 01:56:27PM -0700, Guenter Roeck wrote:
> The call to spi_unregister_master() in the device remove function frees device
> memory, and with it any device local data. However, device local data is still
> accessed after the call to spi_unregister_master().
Applied, thanks.
Since there is no power saving consideration in scheduler CFS, I has a
very rough idea for enabling a new power saving schema in CFS.
It bases on the following assumption:
1, If there are many task crowd in system, just let few domain cpus
running and let other cpus idle can not save power. Let
On Sun, Aug 12, 2012 at 11:23:59PM -0700, John Fastabend wrote:
> >OK clearly I screwed it up thanks for reviewing Al. How about this.
> >
> > fdt = files_fdtable(files);
> > for (fd = 0; fd < fdt->max_fds; fd++) {
> > struct socket *sock;
>
commit cfd19c5a9ec (mm: only set page->pfmemalloc when
ALLOC_NO_WATERMARKS was used) try to narrow down page->pfmemalloc
setting, but it missed some places the pfmemalloc should be set.
So, in __slab_alloc, the unalignment pfmemalloc and ALLOC_NO_WATERMARKS
cause incorrect deactivate_slab() on
On Mon, 13 Aug 2012 15:37:31 +0400
Stanislav Kinsbursky wrote:
> v2:
> 1) rpc_clnt_set_nodename() prototype updated.
> 2) fixed errors in comment.
>
> When child reaper exits, it can destroy mount namespace it belongs to, and if
> there are NFS mounts inside, then it will try to umount them.
On Sun, Aug 12, 2012 at 5:31 PM, Michal Hocko wrote:
> From d07b88a70ee1dbcc96502c48cde878931e7deb38 Mon Sep 17 00:00:00 2001
> From: Michal Hocko
> Date: Fri, 10 Aug 2012 15:03:07 +0200
> Subject: [PATCH] hugetlb: do not use vma_hugecache_offset for
> vma_prio_tree_foreach
>
> 0c176d5 (mm:
>>> On 13.08.12 at 13:43, "Kirill A. Shutemov"
>>> wrote:
> On Thu, Aug 09, 2012 at 04:22:04PM +0100, Jan Beulich wrote:
>> >>> On 09.08.12 at 17:03, "Kirill A. Shutemov"
>> >>> wrote:
>
> ...
>
>> > ---
>> > arch/x86/include/asm/page.h |2 ++
>> >
On Sun, Jul 29, 2012 at 4:55 AM, Axel Lin wrote:
> gpio_chip.can_sleep is 0, but current code uses mutex in pch_gpio_set
> pch_gpio_get and pch_gpio_direction_input functions.
> Thus those functions are not callable from interrupt context.
> This patch converts mutex into spinlock.
>
>
A performance counter of e500mc processor core generates an overflow
interrupt when the counter value reaches to 0x8000. In order to
set up a sampling counter, the kernel sets the counter value to
0x8000 - to cause an interrupt right after
are incremented.
In the current code, the
On Sun, Jul 29, 2012 at 4:54 AM, Axel Lin wrote:
> gpio_chip.can_sleep is 0, but current code uses mutex in ioh_gpio_set,
> ioh_gpio_get and ioh_gpio_direction_input functions.
> Thus those functions are not callable from interrupt context.
> This patch converts mutex into spinlock.
>
>
Correct spelling typo in drivers/mfd
Signed-off-by: Masanari Iida
---
drivers/mfd/ab8500-gpadc.c| 2 +-
drivers/mfd/rc5t583.c | 2 +-
drivers/mfd/rdc321x-southbridge.c | 2 +-
drivers/mfd/tps65911-comparator.c | 2 +-
include/linux/mfd/max8998.h | 2 +-
5 files
On Wed, Aug 08, 2012 at 10:08:20PM +0200, Peter Zijlstra wrote:
> On Wed, 2012-08-08 at 21:50 +0200, Mike Galbraith wrote:
> > 32bit built do_div()
> > and div64_u64() both sucked equally compared to 64bit
>
> /me peeks at div64_u64 fallback implementation and sees why, it still
> does a single
On Thu, Aug 09, 2012 at 05:46:38PM -0700, Casey Schaufler wrote:
> On 12/20/2011 11:20 PM, Jarkko Sakkinen wrote:
> > Allow SIGCHLD to be passed to child process without
> > explicit policy. This will help to keep the access
> > control policy simple and easily maintainable with
> > complex
On Thu, Aug 09, 2012 at 04:22:04PM +0100, Jan Beulich wrote:
> >>> On 09.08.12 at 17:03, "Kirill A. Shutemov"
> >>> wrote:
...
> > ---
> > arch/x86/include/asm/page.h |2 ++
> > arch/x86/include/asm/string_32.h |5 +
> > arch/x86/include/asm/string_64.h |5
Sourav,
On Mon, Aug 13, 2012 at 3:35 PM, Sourav Poddar wrote:
>
> The following patch series add i2c support for omap5.
> As well as enable I2C based devices like pressure and temperature
> through device tree. Also add onchip keypad dts data.
>
> Cc: Benoit Cousson
> Cc: Felipe Balbi
> Cc:
v2:
1) rpc_clnt_set_nodename() prototype updated.
2) fixed errors in comment.
When child reaper exits, it can destroy mount namespace it belongs to, and if
there are NFS mounts inside, then it will try to umount them. But in this
point current->nsproxy is set to NULL and all namespaces will be
Thanks, Jeff. Will fix.
13.08.2012 15:35, Jeff Layton пишет:
On Mon, 13 Aug 2012 15:21:56 +0400
Stanislav Kinsbursky wrote:
When child reaper exits, it can destroy mount namespace it belong to, and if
there are NFS mounts inside, then it will try to umount them. But in this
point
On Tue, 2012-08-07 at 18:12 +0200, Sebastian Andrzej Siewior wrote:
> By setting an uprobe tracepoint, one learns whenever a certain point
> within a program is reached / passed. This is recorded and the
> application continues.
> This patch adds the ability to hold the program once this point has
On Mon, 13 Aug 2012 15:21:56 +0400
Stanislav Kinsbursky wrote:
> When child reaper exits, it can destroy mount namespace it belong to, and if
> there are NFS mounts inside, then it will try to umount them. But in this
> point current->nsproxy is set to NULL and all namespaces will be destroyed
When child reaper exits, it can destroy mount namespace it belong to, and if
there are NFS mounts inside, then it will try to umount them. But in this
point current->nsproxy is set to NULL and all namespaces will be destroyed one
by one. I.e. we can't dereference current->nsproxy to obtain uts
From: Dongjin Kim
This patch adds the clock controls for the audio subsystem channel 0,
and fixes invalid clock gating for i2s.0.
Signed-off-by: Dongjin Kim
---
arch/arm/mach-exynos/clock-exynos4.c | 254 +++-
arch/arm/mach-exynos/common.c |
On Sun, Aug 12, 2012 at 10:55:17PM -0700, John Fastabend wrote:
> On 8/12/2012 6:53 PM, Al Viro wrote:
> > Ladies and gentlemen, who the devil had reviewed that little gem?
> >
> >commit 406a3c638ce8b17d9704052c07955490f732c2b8
> >Author: John Fastabend
> >Date: Fri Jul 20 10:39:25 2012
Hi Linus,
please pull from the 'for-linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus
to receive some s390 patches on top of 3.6-rc1.
Included are bug fixes and a patch to enable system call filtering with BPF.
Heiko Carstens (4):
s390/mm:
On Mon, Aug 13, 2012 at 07:13:16PM +0800, Xiao Guangrong wrote:
> THP_COLLAPSE_ALLOC is double counted if NUMA is disabled since it has
> already been calculated in khugepaged_alloc_hugepage
>
> Signed-off-by: Xiao Guangrong
Acked-by: Kirill A. Shutemov
> ---
> mm/huge_memory.c |2 +-
>
Use khugepaged_enabled to see whether thp is enabled
Signed-off-by: Xiao Guangrong
---
mm/huge_memory.c | 11 ++-
1 files changed, 2 insertions(+), 9 deletions(-)
diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index 6ddf671..6becf6c 100644
--- a/mm/huge_memory.c
+++
Since it is called in start_khugepaged
Signed-off-by: Xiao Guangrong
---
mm/huge_memory.c |5 -
1 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index 6becf6c..6533956 100644
--- a/mm/huge_memory.c
+++ b/mm/huge_memory.c
@@ -225,9 +225,6
Merge khugepaged_loop into khugepaged
Signed-off-by: Xiao Guangrong
---
mm/huge_memory.c | 14 --
1 files changed, 4 insertions(+), 10 deletions(-)
diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index 82f6cce..6ddf671 100644
--- a/mm/huge_memory.c
+++ b/mm/huge_memory.c
@@
They are used to abstract the difference between NUMA enabled and NUMA disabled
to make the code more readable
Signed-off-by: Xiao Guangrong
---
mm/huge_memory.c | 166 --
1 files changed, 98 insertions(+), 68 deletions(-)
diff --git
If NUMA is enabled, we can release the page in the page pre-alloc operation,
then the CONFIG_NUMA dependent code can be reduced
Signed-off-by: Xiao Guangrong
---
mm/huge_memory.c | 19 +++
1 files changed, 7 insertions(+), 12 deletions(-)
diff --git a/mm/huge_memory.c
There are two pre-alloc operations in these two function, the different is:
- it allows to sleep if page alloc fail in khugepaged_loop
- it exits immediately if page alloc fail in khugepaged_do_scan
Actually, in khugepaged_do_scan, we can allow the pre-alloc to sleep on the
first failure, then
If NUMA is disabled, hpage is used as page pre-alloc, so there are
two cases for hpage:
- it is !NULL, means the page is not consumed otherwise,
- the page has been consumed
If NUMA is enabled, hpage is just used as alloc-fail indicator which
is not a real page, NULL means not fail triggered.
Add the check of kthread_should_stop() to the conditions which are used
to wakeup on khugepaged_wait, then kthread_stop is enough to let the
thread exit
Signed-off-by: Xiao Guangrong
---
mm/huge_memory.c | 35 +--
1 files changed, 21 insertions(+), 14
Now, khugepaged creation and cancel are completely serial under the
protection of khugepaged_mutex, it is impossible that many khugepaged
entities are running
Signed-off-by: Xiao Guangrong
---
mm/huge_memory.c |5 +
1 files changed, 1 insertions(+), 4 deletions(-)
diff --git
Currently, hugepaged_mutex is used really complexly and hard to understand,
actually, it is just used to serialize start_khugepaged and khugepaged for
these reasons:
- khugepaged_thread is shared between them
- the thp disable path (echo never > transparent_hugepage/enabled) is
nonblocking, so
The check is unnecessary since if mm_slot_cache or mm_slots_hash initialize
failed, no sysfs interface will be created
Signed-off-by: Xiao Guangrong
---
mm/huge_memory.c |7 ++-
1 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index
THP_COLLAPSE_ALLOC is double counted if NUMA is disabled since it has
already been calculated in khugepaged_alloc_hugepage
Signed-off-by: Xiao Guangrong
---
mm/huge_memory.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index
khugepaged_mutex is used very complexly and there are too many small pieces
of the code depend on CONFIG_NUMA, they make the code very hardly understand
This patchset try to optimize use of khugepaged_mutex and reduce dependence
of CONFIG_NUMA, after the patchset, the code is more readable
--
To
On Fri, Aug 10, 2012 at 11:03:58AM +, Arnd Bergmann wrote:
> On Thursday 09 August 2012, Russell King - ARM Linux wrote:
> > On Wed, Aug 08, 2012 at 11:27:57PM +0200, Arnd Bergmann wrote:
> > > ARMv3 support was removed in 357c9c1f07 "ARM: Remove support for ARMv3
> > > ARM610 and ARM710
Resending to correct Jeremy's address.
On Wed, Aug 08, 2012 at 03:50:46PM -0700, David Miller wrote:
> From: Mel Gorman
> Date: Tue, 7 Aug 2012 09:55:55 +0100
>
> > Commit [c48a11c7: netvm: propagate page->pfmemalloc to skb] is responsible
> > for the following bug triggered by a xen network
We validate irq pin number when routing is setup, so
code handling illegal irq # in pic and ioapic on each injection
is never called.
Drop it.
Signed-off-by: Michael S. Tsirkin
---
Reposting, applies without changes to kvm/next.
arch/x86/kvm/i8259.c | 16 +++-
virt/kvm/ioapic.c
On Mon, Aug 13, 2012 at 1:20 AM, Peter Zijlstra wrote:
> On Tue, 2012-08-07 at 00:25 -0700, Michel Lespinasse wrote:
>> a faster worst-case complexity of O(k+log N) for stabbing queries in a
>> well-balanced prio tree, vs O(k*log N) for interval trees (where k=number
>> of matches, N=number of
12.08.2012 13:48, Manfred Spraul пишет:
I would keep it simple - unless there is a clear use case where "peek
by id" is useful.
Or - since MSG_COPY is linux specific anyway:
What about storing the number of the message that should be returned in *msgp?
Store it as "int64", just to avoid any
Embed block device name in struct block_device, thus we can replace
the following code:
char b[BDEVNAME_SIZE];
printk(KERN_XXX "...%s..\n", bdevname(bdev, b);
with a much simpler and less stack usage version:
printk(KERN_XXX "...%s..\n", bdev->bd_name);
This is a RFC
Since we embeded block device name into struct block_device, we don't
need call a function bdevname() to get the name any more.
Here this patch replace all the code using bdevname() in vfs layer to
bdev->bd_name.
This patch servers as an example of using embeded block device name.
It makes the
601 - 700 of 1532 matches
Mail list logo
