This patch creates a mechanism that skip memcg allocations during
certain pieces of our core code. It basically works in the same way
as preempt_disable()/preempt_enable(): By marking a region under
which all allocations will be accounted to the root memcg.
We need this to prevent races in early
When we create caches in memcgs, we need to display their usage
information somewhere. We'll adopt a scheme similar to /proc/meminfo,
with aggregate totals shown in the global file, and per-group
information stored in the group itself.
For the time being, only reads are allowed in the per-group
With all the infrastructure in place, we can now have slabinfo_show
done from slab_common.c. A cache-specific function is called to grab
information about the cache itself, since that is still heavily
dependent on the implementation. But with the values produced by it, all
the printing and
Allow a memcg parameter to be passed during cache creation. When the slub
allocator is being used, it will only merge caches that belong to the same
memcg.
Default function is created as a wrapper, passing NULL to the memcg version. We
only merge caches that belong to the same memcg.
A helper
After the slab/slub/slob merge, we are deleting the element from the
slab_cache lists, and then if the destruction fail, we add it back
again. This behavior was present in some caches, but not in others, if
my memory doesn't fail me.
I, however, see no reason why we need to do so, since we are
Signed-off-by: Glauber Costa glom...@parallels.com
CC: Christoph Lameter c...@linux.com
CC: Pekka Enberg penb...@cs.helsinki.fi
CC: Michal Hocko mho...@suse.cz
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Johannes Weiner han...@cmpxchg.org
CC: Suleiman Souhlal sulei...@google.com
CC:
This enables us to remove all the children of a kmem_cache being
destroyed, if for example the kernel module it's being used in
gets unloaded. Otherwise, the children will still point to the
destroyed parent.
Signed-off-by: Suleiman Souhlal sulei...@google.com
Signed-off-by: Glauber Costa
In the slub allocator, when the last object of a page goes away, we
don't necessarily free it - there is not necessarily a test for empty
page in any slab_free path.
This means that when we destroy a memcg cache that happened to be empty,
those caches may take a lot of time to go away: removing
The header format is highly similar between slab and slub. The main
difference lays in the fact that slab may optionally have statistics
added here in case of CONFIG_SLAB_DEBUG, while the slub will stick them
somewhere else.
By making sure that information conditionally lives inside a
This patch implements destruction of memcg caches. Right now,
only caches where our reference counter is the last remaining are
deleted. If there are any other reference counters around, we just
leave the caches lying around until they go away.
When that happen, a destruction function is called
We are able to match a cache allocation to a particular memcg. If the
task doesn't change groups during the allocation itself - a rare event,
this will give us a good picture about who is the first group to touch a
cache page.
This patch uses the now available infrastructure by calling
This patch moves all the common machinery to slabinfo processing
to slab_common.c. We can do better by noticing that the output is
heavily common, and having the allocators to just provide finished
information about this. But after this first step, this can be done
easier.
Signed-off-by: Glauber
Hello Andrew and Oleg,
Andrew, what do you think about this patch? I reworked it according
with your comments to the previous version.
Oleg, could you send Ack in this version, if it's ok for you.
Thanks.
2012/10/12 Andrew Vagin ava...@openvz.org:
'struct pid' is a variable sized struct - a
On Thu, 2012-10-18 at 11:32 +0400, Vladimir Davydov wrote:
1) Do you agree that the problem exists and should be sorted out?
This is two questions.. yes it exists, I'm absolutely sure I pointed it
out as soon as people even started talking about this nonsense (bw
cruft).
Should it be sorted,
SLAB allows us to tune a particular cache behavior with tunables.
When creating a new memcg cache copy, we'd like to preserve any tunables
the parent cache already had.
This could be done by an explicit call to do_tune_cpucache() after the
cache is created. But this is not very convenient now
Every cache that is considered a root cache (basically the original caches,
tied to the root memcg/no-memcg) will have an array that should be large enough
to store a cache pointer per each memcg in the system.
Theoreticaly, this is as high as 1 sizeof(css_id), which is currently in the
64k
SLUB allows us to tune a particular cache behavior with sysfs-based
tunables. When creating a new memcg cache copy, we'd like to preserve
any tunables the parent cache already had.
This can be done by tapping into the store attribute function provided
by the allocator. We of course don't need to
Mike,
Thank you for reviewing my patch.
Here is my comment.
- Write callback
- Check if there are enough spaces to write logs with
QueryVariableInfo()
to avoid handling out of space situation. (It is suggested by
Matthew Garrett.)
I would prefer to see the exposing
The page allocator is able to bind a page to a memcg when it is
allocated. But for the caches, we'd like to have as many objects as
possible in a page belonging to the same cache.
This is done in this patch by calling memcg_kmem_get_cache in the
beginning of every allocation function. This
On 10/19/2012 07:24 PM, Johannes Weiner wrote:
On Fri, Oct 19, 2012 at 04:25:47PM +0530, Srivatsa S. Bhat wrote:
Move the check for populated_zone() to the control statement of the
'for' loop and get rid of the odd looking if/else block.
Signed-off-by: Srivatsa S. Bhat
Dear kernel guys,
I got a bug report here, hope all the info is correct.
[1.] One line summary of the problem:
The integrated webcam in my Lenovo Thinkpad SL510 is not working in kernels
later than 3.5.
[2.] Full description of the problem/report:
After upgrading to 3.6 and following I
On Thu, 2012-10-18 at 09:40 -0400, Steven Rostedt wrote:
Peter,
There was a little conflict with my merge of 3.4.14 due to the backport
of this patch:
commit 947ca1856a7e60aa6d20536785e6a42dff25aa6e
Author: Michael Wang wang...@linux.vnet.ibm.com
Date: Wed Sep 5 10:33:18 2012 +0800
ehci_fsl_setup_phy is supposed to return an int, but had a void return
value in the case of controller_ver being invalid.
Signed-off-by: Ben Collins be...@servergy.com
Cc: Shengzhou Liu shengzhou@freescale.com
---
drivers/usb/host/ehci-fsl.c |2 +-
1 file changed, 1 insertion(+), 1
From: Joseph Salisbury joseph.salisb...@canonical.com
Signed-off-by: Joseph Salisbury joseph.salisb...@canonical.com
---
sound/pci/hda/patch_realtek.c |1 +
1 file changed, 1 insertion(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 739f968..18fce01
From: Joseph Salisbury joseph.salisb...@canonical.com
BugLink: https://bugs.launchpad.net/bugs/1060372
This patch is to enable audio on T430 Thinkpads. There is no audo from the
headphone jack without this patch. This patch adds a quirk for the T430 model.
== Test Case ==
A test kernel
On Thu, Oct 18, 2012 at 08:53:33AM -0700, Alexander Duyck wrote:
On 10/18/2012 05:41 AM, Konrad Rzeszutek Wilk wrote:
On Mon, Oct 15, 2012 at 08:43:28AM -0700, Alexander Duyck wrote:
On 10/13/2012 05:52 AM, Hillf Danton wrote:
Hi Alexander,
On Fri, Oct 12, 2012 at 4:34 AM, Alexander
On Fri, 2012-10-19 at 09:51 -0400, Johannes Weiner wrote:
Of course I'm banging my head into a wall for not seeing earlier
through the existing migration path how easy this could be.
There's a reason I keep promoting the idea of 'someone' rewriting all
that page-migration code :-) I forever
On 10/19/2012 04:53 AM, Paweł Sikora wrote:
Hi,
on the new opteron server i'm observing an oops during matrox video
initialization.
here's the dmesg from pure 3.6.2 kernel:
I haven't owned a G200 based Matrox in years, but based on code
analysis and your output, it looks to me like the
On Tue, 9 Oct 2012 16:21:24 -0700 (PDT)
Hugh Dickins hu...@google.com wrote:
I am seriously tempted to switch to pure software dirty bits by using
page protection for writable but clean pages. The worry is the number of
additional protection faults we would get. But as we do software
On Fri, 2012-10-19 at 09:51 -0400, Johannes Weiner wrote:
Right now, unlike the traditional migration path, this breaks COW for
every migration, but maybe you don't care about shared pages in the
first place. And fixing that should be nothing more than grabbing the
anon_vma lock and using
On Fri, 2012-10-19 at 09:51 -0400, Johannes Weiner wrote:
It's slightly ugly that migrate_page_copy() actually modifies the
existing page (deactivation, munlock) when you end up having to revert
back to it.
The worst is actually calling copy_huge_page() on a THP.. it seems to
work though ;-)
I've hit this twice in the last two days while fuzz testing.
(Both times on i686 only, my x86-64 tests aren't hitting it
for some reason).
BUG: unable to handle kernel paging request at 6b6b6ce3
IP: [c10b52fe] module_put+0x1e/0x160
*pdpt = 25a4b001 *pde =
Oops:
Hi Lars,
2012/10/19 Lars-Peter Clausen l...@metafoo.de:
On 10/19/2012 01:41 AM, Marcos Paulo de Souza wrote:
With this we can remove a lot of checks.
Signed-off-by: Marcos Paulo de Souza marcos.souza@gmail.com
This one is a bit more tricky and the driver currently gets it (partially
On Fri, 19 Oct 2012, Venu Byravarasu wrote:
NVIDIA produces several Tegra SoCs viz Tegra20, Tegra30 etc.
In order to support USB PHY drivers on these SoCs, existing
PHY driver is split into SoC agnostic common USB PHY driver
and Tegra20-specific USB phy driver. This will facilitate
easy
Tested-by: Jean Nicolas Graux jean-nicolas.gr...@stericsson.com
Le 10/19/2012 03:05 PM, Linus WALLEIJ a écrit :
From: Linus Walleijlinus.wall...@linaro.org
This switches the way that pins are reserved for multiplexing:
We used to do this when the map was parsed, at the creation of
the
On 19 Oct 2012, at 14:58, Sangho Yi antir...@gmail.com wrote:
kfree(NULL) is safe so I removed the if statements for NULL check.
Signed-off-by: Sangho Yi antir...@gmail.com
---
drivers/mmc/core/bus.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
On Thu, Oct 18, 2012 at 02:20:53PM -0700, Tejun Heo wrote:
Hey, Vivek.
On Thu, Oct 18, 2012 at 09:31:49AM -0400, Vivek Goyal wrote:
Tejun, for the sake of readability, are you fine with keeping the original
check and original patch which I had acked.
Can you please send another patch to
On 19.10.2012 14:10, Tetsuo Handa wrote:
Yann E. MORIN wrote:
So, switch to using TAILQ instead, which are more portable.
[...]
Excuse me, but your patch does not solve my problem because kconfig started
using macros which does not exist in @(#)queue.h 8.3 (Berkeley) 12/13/93.
Kconfig still
From: Stephane Eranian eran...@gmail.com
The following patch set enforces exclusive PMU access for
Intel SandyBridge INST_REITRED:PREC_DIST event when used
with PEBS as described in the SDM Vol 3b. Without this,
the sample distribution may not be correct.
The kernel now rejects PEBS +
This patch adds the x modifier for events. It allows users to
request exclusive PMU access (attr-exclusive):
perf stat -e cycles:x ..
or
perf stat -e cpu/cycles/x
Exclusive mode is a feature of perf_events which was not yet
supported by the perf tool. Some events may require exclusive
On all Intel SandyBridge processors, the INST_RETIRED:PREC_DIST
when used with PEBS must be measured alone. That means no other
event can be active on the PMU at the same time as per Intel SDM
Vol3b. This is what the exclusive mode of perf_events provides.
However, it was not enforced for that
From: Linus Walleij linus.wall...@linaro.org
Since in the DT case, the linear domain path will not allocate
descriptors for the IRQs, we need to use irq_create_mapping()
for mapping hwirqs to Linux IRQs, so these descriptors get
created on-the-fly in this case.
Cc: Lee Jones lee.jo...@linaro.org
On Fri, 2012-10-19 at 16:52 +0200, Stephane Eranian wrote:
-modifier_event [ukhpGH]{1,8}
+modifier_event [ukhpGHx]{1,8}
wouldn't the max modifier sting length grow by adding another possible
modifier?
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
On Thu, Oct 18 2012 at 9:14pm -0400,
Tejun Heo t...@kernel.org wrote:
Hello,
On Mon, Oct 15, 2012 at 01:08:34PM -0700, Kent Overstreet wrote:
Since last time - split bio integrity stuff out into its own 2 patch series.
Also changed bio_advance() a bit - it now explicitly special cases
On Fri, Oct 19, 2012 at 5:13 PM, Peter Zijlstra pet...@infradead.org wrote:
On Fri, 2012-10-19 at 16:52 +0200, Stephane Eranian wrote:
-modifier_event [ukhpGH]{1,8}
+modifier_event [ukhpGHx]{1,8}
wouldn't the max modifier sting length grow by adding another possible
modifier?
That's what I
On Fri, Oct 19, 2012 at 12:20:54PM +0900, HATAYAMA Daisuke wrote:
[..]
Instead of capturing the dump of whole memory, isn't it more efficient
to capture the crash dump of VM in question and then if need be just
take filtered crash dump of host kernel.
I think that trying to take
I would like to summarize progress I have made on this issue in the past
few days, and then appeal for help in evaluating the options. Matthew
and H. Peter Anvin, I would appreciate your additional input especially.
The general idea under consideration here is to avoid access to the
legacy
On Fri, Oct 19, 2012 at 05:17:57PM +0200, Stephane Eranian wrote:
On Fri, Oct 19, 2012 at 5:13 PM, Peter Zijlstra pet...@infradead.org wrote:
On Fri, 2012-10-19 at 16:52 +0200, Stephane Eranian wrote:
-modifier_event [ukhpGH]{1,8}
+modifier_event [ukhpGHx]{1,8}
wouldn't the max modifier
On Fri, 19 Oct 2012, Peter Zijlstra wrote:
Could you just confirm that my fix is correct.
We forever keep getting that issue wrong it seems.. so I'd not put too
much trust into whatever my sleep addled brain thinks today :/
I wasn't expecting a reply till next week ;-)
Looks about
I don't think DMI checking is going to work, since (a) as you say,
there's a risk that the ID will inadvertantly change over the lifecycle
of the machine, and (b) there may be other machines. So if it's not
possible to handle this by catching the MCE, I think we have two
options:
1) Declare
On 19 October 2012 18:22, Linus Walleij linus.wall...@linaro.org wrote:
No, which defconfig shall I use for this driver?
mxs_defconfig
Shawn
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Fri, 19 Oct 2012, Peter Zijlstra wrote:
On Thu, 2012-10-18 at 15:28 -0400, Mikulas Patocka wrote:
On Thu, 18 Oct 2012, Oleg Nesterov wrote:
Ooooh. And I just noticed include/linux/percpu-rwsem.h which does
something similar. Certainly it was not in my tree when I started
On Fri, Oct 19, 2012 at 10:43:51AM -0400, Dave Jones wrote:
I've hit this twice in the last two days while fuzz testing.
(Both times on i686 only, my x86-64 tests aren't hitting it
for some reason).
BUG: unable to handle kernel paging request at 6b6b6ce3
IP: [c10b52fe]
On 10/19/2012 08:30 AM, Matthew Garrett wrote:
I don't think DMI checking is going to work, since (a) as you say,
there's a risk that the ID will inadvertantly change over the lifecycle
of the machine, and (b) there may be other machines. So if it's not
possible to handle this by catching the
Thank you for the answer.
On Oct 19, 2012, at 6:24 PM, Peter Zijlstra wrote:
its a quick hack similar to existing hacks done for rt, preferably we'd
do smarter things though.
If you have any ideas how to fix this in a better way, please share.
--
To unsubscribe from this list: send the line
Hi,
On Fri, Oct 19, 2012 at 04:08:05PM +0530, Venu Byravarasu wrote:
NVIDIA produces several Tegra SoCs viz Tegra20, Tegra30 etc.
In order to support USB PHY drivers on these SoCs, existing
PHY driver is split into SoC agnostic common USB PHY driver
and Tegra20-specific USB phy driver. This
That's what I thought too, but then I don't understand why it was at
eight before and not
seven: One instance of each letter, + a second for pp (precise=2). Or
am I missing
something here?
The number is pretty useless imho (it's unlikely to catch any real user error)
and most likely
On Fri, Oct 19, 2012 at 5:23 PM, Jiri Olsa jo...@redhat.com wrote:
On Fri, Oct 19, 2012 at 05:17:57PM +0200, Stephane Eranian wrote:
On Fri, Oct 19, 2012 at 5:13 PM, Peter Zijlstra pet...@infradead.org wrote:
On Fri, 2012-10-19 at 16:52 +0200, Stephane Eranian wrote:
-modifier_event
On Thu, Oct 18, 2012 at 04:24:04PM -0700, Tejun Heo wrote:
Hello, Vivek.
On Wed, Oct 17, 2012 at 09:49:45AM -0400, Vivek Goyal wrote:
Can you explain a bit more. Whe do you mean by total number queued. I
think throttle.io_queued will total number of bios queued in the cgroup
at the time
On 10/18/2012 11:58 PM, Mark Zhang wrote:
Define pinmux for DDC. The DDC pinmux in Ventana is 2 pins in I2C2.
+++ b/arch/arm/boot/dts/tegra20-ventana.dts
- ddc {
- nvidia,pins = ddc, owc, spdi, spdo,
- uac;
On Tue, Oct 16, 2012 at 11:35:08PM +0100, Al Viro wrote:
1. Basic rules for process lifetime.
Except for the initial process (init_task, eventual idle thread on the boot
CPU) all processes are created by do_fork(). There are three classes of
those: kernel threads, userland processes
+ /*
+ * for INST_RETIRED.PREC_DIST to work correctly with PEBS, it must
+ * be measured alone on SNB (exclusive PMU access) as per Intel SDM.
+ */
+ if ((cfg INTEL_ARCH_EVENT_MASK) == 0x01c0 !event-attr.exclusive) {
+ pr_info(perf: INST_RETIRED.PREC_DIST
2012/10/12 Frederic Weisbecker fweis...@gmail.com:
Hi,
So here is a proposition on what we can do to make printk
correctly working on a tickless CPU.
Although it's targeted to be part of the adaptive tickmess
implemetation, it's pretty standalone and generic and also
works for printk()
Commit-ID: 5bc66170dc486556a1e36fd384463536573f4b82
Gitweb: http://git.kernel.org/tip/5bc66170dc486556a1e36fd384463536573f4b82
Author: Borislav Petkov borislav.pet...@amd.com
AuthorDate: Thu, 18 Oct 2012 15:10:56 +0200
Committer: Borislav Petkov borislav.pet...@amd.com
CommitDate: Fri,
On Fri, Oct 19, 2012 at 05:47:11PM +0200, Stephane Eranian wrote:
On Fri, Oct 19, 2012 at 5:23 PM, Jiri Olsa jo...@redhat.com wrote:
On Fri, Oct 19, 2012 at 05:17:57PM +0200, Stephane Eranian wrote:
On Fri, Oct 19, 2012 at 5:13 PM, Peter Zijlstra pet...@infradead.org
wrote:
On Fri,
Hi Andrea, Peter,
I have a question on page refcounting in your NUMA
page migration code.
In Peter's case, I wonder why you introduce a new
MIGRATE_FAULT migration mode. If the normal page
migration / compaction logic can do without taking
an extra reference count, why does your code need it?
On Fri, 19 Oct 2012, Konrad Rzeszutek Wilk wrote:
diff --git a/include/xen/interface/physdev.h
b/include/xen/interface/physdev.h
index 9ce788d..3b9d5b6 100644
--- a/include/xen/interface/physdev.h
+++ b/include/xen/interface/physdev.h
@@ -258,6 +258,16 @@ struct
On 10/19/2012 03:10 AM, Laxman Dewangan wrote:
On Friday 19 October 2012 04:11 AM, Stephen Warren wrote:
On 10/18/2012 04:56 AM, Laxman Dewangan wrote:
Add slink controller details in the dts file of
Tegra20 and Tegra30.
diff --git a/arch/arm/boot/dts/tegra20.dtsi
On Fri, Oct 19, 2012 at 5:49 PM, Andi Kleen a...@linux.intel.com wrote:
+ /*
+ * for INST_RETIRED.PREC_DIST to work correctly with PEBS, it must
+ * be measured alone on SNB (exclusive PMU access) as per Intel SDM.
+ */
+ if ((cfg INTEL_ARCH_EVENT_MASK) == 0x01c0
On Fri, Oct 19, 2012 at 5:53 PM, Jiri Olsa jo...@redhat.com wrote:
On Fri, Oct 19, 2012 at 05:47:11PM +0200, Stephane Eranian wrote:
On Fri, Oct 19, 2012 at 5:23 PM, Jiri Olsa jo...@redhat.com wrote:
On Fri, Oct 19, 2012 at 05:17:57PM +0200, Stephane Eranian wrote:
On Fri, Oct 19, 2012 at
On 10/19/2012 03:13 AM, Laxman Dewangan wrote:
On Friday 19 October 2012 04:13 AM, Stephen Warren wrote:
+OF_DEV_AUXDATA(nvidia,tegra20-slink, TEGRA_SLINK1_BASE,
spi-tegra-slink.0, NULL),
Here, can't we just use the existing device names in the clock files...
So we can completely drop
On 10/19/2012 03:20 AM, Tony Prisk wrote:
On Fri, 2012-10-19 at 18:06 +0900, Alexandre Courbot wrote:
Make use of the power sequences specified in the device tree or platform
data to control how the backlight is powered on and off.
Tony, please do cut down the amount of the patch that you
paravirtualized architectures out there which are perfectly well
documented and supportable, but Xen has resisted doing that for
years, and all we ever get are vague future promises.
There is no resistance - and it is being done. Every month we document
various APIs, man-pages, etc so that
On 19.10.2012, Greg Kroah-Hartman wrote:
3.6-stable review patch. If anyone has any objections, please let me know.
While 3.6.2 is fine. 3.6.3-rc1 crashes my machine (Asus U45-JC) at
boot. A screenshot of the output is here:
http://www.fritha.org/crash.jpg
Reverting this one fixes it:
Ben
On Fri, Oct 19, 2012 at 4:59 AM, Florian Fainelli ffaine...@freebox.fr wrote:
From: Maxime Bizon mbi...@freebox.fr
record_size / console_size / ftrace_size can be 0 (this is how you
disable the feature), but rounddown_pow_of_two(0) is undefined. This problem
has been present since commit
On Wed 17-10-12 18:23:34, gaoqiang wrote:
I looked up nothing useful with google,so I'm here for help..
when this happens: I use memcg to limit the memory use of a
process,and when the memcg cgroup was out of memory,
the process was oom-killed however,it cannot really complete the
On 10/19/2012 04:44 PM, Marcos Souza wrote:
Hi Lars,
2012/10/19 Lars-Peter Clausen l...@metafoo.de:
On 10/19/2012 01:41 AM, Marcos Paulo de Souza wrote:
With this we can remove a lot of checks.
Signed-off-by: Marcos Paulo de Souza marcos.souza@gmail.com
This one is a bit more tricky
On Fri, Oct 19, 2012 at 08:46:10AM -0700, Andi Kleen wrote:
That's what I thought too, but then I don't understand why it was at
eight before and not
seven: One instance of each letter, + a second for pp (precise=2). Or
am I missing
something here?
The number is pretty useless imho
KVM_PV_REASON_PAGE_NOT_PRESENT kicks cpu out of idleness, but we haven't
marked that spot as an exit from idleness.
Not doing so can cause RCU warnings such as:
[ 732.788386] ===
[ 732.789803] [ INFO: suspicious RCU usage. ]
[ 732.790032] 3.7.0-rc1-next-20121019
On 10/19/2012 04:54 AM, Linus Walleij wrote:
The Tegra driver tries to do the work of irq_domain_add_linear()
by reserving a bunch of descriptors somewhere and keeping track
of the base offset, then calling irq_domain_add_legacy(). Let's
stop doing that and simply use the linear IRQ domain.
I fixed the following check item (via checkpatch.pl --strict option):
CHECK: Alignment should match open parenthesis
Signed-off-by: Sangho Yi antir...@gmail.com
---
drivers/devfreq/exynos4_bus.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/devfreq/exynos4_bus.c
On 10/19/2012 07:05 AM, Linus Walleij wrote:
From: Linus Walleij linus.wall...@linaro.org
This switches the way that pins are reserved for multiplexing:
We used to do this when the map was parsed, at the creation of
the settings inside the pinctrl handle, in pinmux_map_to_setting().
On 10/19/2012 07:18 AM, Konrad Rzeszutek Wilk wrote:
On Thu, Oct 18, 2012 at 08:53:33AM -0700, Alexander Duyck wrote:
end to be physical instead of virtual. I reviewed the code and realized
that I wasn't saving anything by removing it since the overall code was
larger as a result so I just
On 10/19/2012 09:09 AM, Linus Walleij wrote:
From: Linus Walleij linus.wall...@linaro.org
Since in the DT case, the linear domain path will not allocate
descriptors for the IRQs, we need to use irq_create_mapping()
for mapping hwirqs to Linux IRQs, so these descriptors get
created
On Thu, 18 Oct 2012, Yinghai Lu wrote:
Get pgt_buf early from BRK, and use it to map PMD_SIZE from top at first.
then use mapped pages to map more range below, and keep looping until
all pages get mapped.
alloc_low_page will use page from BRK at first, after that buff is used up,
will use
On Thu, Oct 18, 2012 at 12:01:17AM +0200, Krzysztof Halasa wrote:
...
Unfortunately, as I already explained to you in
https://lkml.org/lkml/2012/9/29/37, my resources for IXP4xx are very
limited (and this isn't a paid job) and I'm in no way able to do what
you require. This, coupled with my
On Fri, 2012-10-19 at 16:52 +0200, Stephane Eranian wrote:
+static int intel_pebs_aliases_snb(struct perf_event *event)
+{
+ u64 cfg = event-hw.config;
+ /*
+* for INST_RETIRED.PREC_DIST to work correctly with PEBS, it must
+* be measured alone on SNB (exclusive
On Friday 19 of October 2012 18:03:57 we...@cn.fujitsu.com wrote:
From: Wen Congyang we...@cn.fujitsu.com
The patch-set implements a framework for hot removing memory.
The memory device can be removed by 2 ways:
1. send eject request by SCI
2. echo 1 /sys/bus/pci/devices/PNP0C80:XX/eject
ACPI
M: Len Brown l...@kernel.org
+M: Rafael J. Wysocki r...@sisk.pl
Acked-by: Len Brown len.br...@intel.com
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On 10/19/2012 09:35 AM, Felipe Balbi wrote:
Hi,
On Fri, Oct 19, 2012 at 04:08:05PM +0530, Venu Byravarasu wrote:
NVIDIA produces several Tegra SoCs viz Tegra20, Tegra30 etc. In
order to support USB PHY drivers on these SoCs, existing PHY
driver is split into SoC agnostic common USB PHY
On Fri, Oct 19, 2012 at 6:27 PM, Peter Zijlstra pet...@infradead.org wrote:
On Fri, 2012-10-19 at 16:52 +0200, Stephane Eranian wrote:
+static int intel_pebs_aliases_snb(struct perf_event *event)
+{
+ u64 cfg = event-hw.config;
+ /*
+* for INST_RETIRED.PREC_DIST to work
Hi Dave,
On Fri, Oct 19, 2012 at 11:34:52AM -0400, Dave Jones wrote:
On Fri, Oct 19, 2012 at 10:43:51AM -0400, Dave Jones wrote:
I've hit this twice in the last two days while fuzz testing.
(Both times on i686 only, my x86-64 tests aren't hitting it
for some reason).
BUG: unable
On Fri, Oct 19, 2012 at 09:00:59AM -0400, Konrad Rzeszutek Wilk wrote:
On Thu, Oct 18, 2012 at 11:03:38AM +0100, David Vrabel wrote:
From: David Vrabel david.vra...@citrix.com
Backend drivers shouldn't transistion to CLOSED unless the frontend is
CLOSED. If a backend does transition to
(cc list trimmed)
On Fri, 2012-10-19 at 11:55 -0400, Pavel Roskin wrote:
On Fri, 19 Oct 2012 09:04:14 +0200
Eric Dumazet eric.duma...@gmail.com wrote:
Yes they are some names discrepancies, thats a big deal.
And we have alloc_skb() / kfree_skb() / skb_clone()
Why not skb_alloc()
On Fri, 2012-10-19 at 11:53 -0400, Rik van Riel wrote:
If we do need the extra refcount, why is normal
page migration safe? :)
Its mostly a matter of how convoluted you make the code, regular page
migration is about as bad as you can get
Normal does:
follow_page(FOLL_GET) +1
On Fri, Oct 19, 2012 at 01:45:27PM +0800, Tang Chen wrote:
cmci_rediscover() is only called by the CPU_POST_DEAD event handler,
which means the corresponding cpu has already dead. As a result, it
won't be accessed in the for_each_online_cpu loop.
So, we could change the if(cpu == dying)
On Fri, Oct 19, 2012 at 9:24 AM, Stefano Stabellini
stefano.stabell...@eu.citrix.com wrote:
On Thu, 18 Oct 2012, Yinghai Lu wrote:
Get pgt_buf early from BRK, and use it to map PMD_SIZE from top at first.
then use mapped pages to map more range below, and keep looping until
all pages get
On Fri, Oct 19, 2012 at 01:45:28PM +0800, Tang Chen wrote:
cmci_rediscover() used set_cpus_allowed_ptr() to change the current process's
running cpu, and migrate itself to the dest cpu. But worker processes are not
allowed to be migrated. If current is a worker, the worker will be migrated to
On Fri, Oct 19, 2012 at 12:02:42PM +, Bedia, Vaibhav wrote:
On Fri, Oct 19, 2012 at 16:45:58, Porter, Matt wrote:
On Fri, Oct 19, 2012 at 10:26:20AM +, Bedia, Vaibhav wrote:
[...]
I didn't see all the patches that you posted on edma-dmaengine-v3
but I do seem them on
Hi Viresh,
On Fri, Oct 19, 2012 at 7:14 PM, Viresh Kumar viresh.ku...@linaro.org wrote:
On 19 October 2012 15:45, Shiraz Hashim shiraz.has...@st.com wrote:
diff --git a/Documentation/devicetree/bindings/pwm/spear-pwm.txt
b/Documentation/devicetree/bindings/pwm/spear-pwm.txt
+pwm:
801 - 900 of 1116 matches
Mail list logo
