Hi tj, Yinghai,
On 06/19/2013 01:21 AM, Tejun Heo wrote:
Hey, Tang.
On Tue, Jun 18, 2013 at 01:47:16PM +0800, Tang Chen wrote:
[approach]
Parse SRAT earlier before memblock starts to work, because there is a
bit in SRAT specifying which memory is hotpluggable.
I'm not saying this is the best
From: Andrew Vagin
vp_dev->msix_vectors should be initialized before allocating
msix_affinity_masks, otherwise vp_free_vectors will not free these
objects.
unreferenced object 0x88010f969d88 (size 512):
comm "systemd-udevd", pid 158, jiffies 4294673645 (age 80.545s)
hex dump (first 32
On Wed, Jun 19, 2013 at 10:08:53PM +, Luck, Tony wrote:
> > The above question about what to do *without* going to userspace and
> > back is maybe more interesting and we'd need a clean design there...
> > we'll see.
>
> Yes - this case (where the BIOS did all the threshold math and made the
On Wed, Jun 19, 2013 at 03:02:19PM -0700, H. Peter Anvin wrote:
> On 06/19/2013 02:52 PM, Borislav Petkov wrote:
> > On Wed, Jun 19, 2013 at 02:42:49PM -0700, H. Peter Anvin wrote:
> >> There is serious confusion with regards to DR6 about the bits which
> >> are *fixed* (forced to 1) and the ones
Hi,
On Wednesday 19 June 2013 09:19 PM, Sylwester Nawrocki wrote:
Hi,
On 06/13/2013 10:43 AM, Kishon Vijay Abraham I wrote:
+/**
+ * phy_create() - create a new phy
+ * @dev: device that is creating the new phy
+ * @id: id of the phy
+ * @ops: function pointers for performing phy operations
+
On 06/19/2013 07:34:29 AM, Aaro Koskinen wrote:
Documentation for inactive_anon / active_anon was mixed up. Fix that.
Signed-off-by: Aaro Koskinen
Acked-by: Rob Landley
---
Documentation/cgroups/memory.txt |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
From: Yijing Wang
Date: Tue, 18 Jun 2013 16:05:39 +0800
> Pci_enable_device() will set device power state to D0,
> so it's no need to do it again in bnx2x_init_dev().
> Also remove redundant PM Cap find code, because pci core
> has been saved the pci device pm cap value.
>
> Signed-off-by:
From: Yijing Wang
Date: Tue, 18 Jun 2013 16:06:37 +0800
> Pci core has been saved pm cap register offset by pdev->pm_cap in
> pci_pm_init()
> in init path. So we can use pdev->pm_cap instead of using
> pci_find_capability(pdev, PCI_CAP_ID_PM) for better performance and
> simplified code.
>
>
From: Yijing Wang
Date: Tue, 18 Jun 2013 16:12:37 +0800
> Pci core has been saved pm cap register offset by pdev->pm_cap in
> pci_pm_init()
> in init path. So we can use pdev->pm_cap instead of using
> pci_find_capability(pdev, PCI_CAP_ID_PM) for better performance and
> simplified code.
>
>
On 06/19/2013 08:46 PM, Arnd Bergmann wrote:
> On Wednesday 19 June 2013, Soren Brinkmann wrote:
>> I don't know how much a defconfig is supposed to provide, hence as RFC.
>> This patches are needed for booting Zynq into a minimum ramfs based
>> system with a serial console.
>
> In my opinion we
From: "Yuval Mintz"
Date: Tue, 18 Jun 2013 09:37:27 +
>> Pci_enable_device() will set device power state to D0,
>> so it's no need to do it again in bnx2x_init_dev().
>> Also remove redundant PM Cap find code, because pci core
>> has been saved the pci device pm cap value.
>>
>>
On 06/19/2013 04:09:25 AM, Xiao Guangrong wrote:
Document it to Documentation/virtual/kvm/mmu.txt
Why break a change to a single documentation file into 7 pieces.
Are we going to bisect the documentation?
Rob--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On 06/20/2013 05:03 AM, Eric W. Biederman wrote:
> Eric Paris writes:
>
>> On Wed, 2013-06-19 at 16:49 -0400, Aristeu Rozanski wrote:
>>> On Wed, Jun 19, 2013 at 09:53:32AM +0800, Gao feng wrote:
This patchset is first part of namespace support for audit.
in this patchset, the mainly
From: Lubomir Rintel
Date: Tue, 18 Jun 2013 19:30:48 +0200
> Zero pointer in rx_skb or tx_skb is how respective *_deinit() functions find
> out that a skb slot is unallocated. If *_init() functions unsuccessfully
> return
> after the allocation (e.g. when subsequent dma_alloc_coherent() is not
From: Lubomir Rintel
Date: Tue, 18 Jun 2013 19:32:38 +0200
> Zero pointer in rx_skb is how respective rxq_deinit() finds out out that a skb
> slot is unallocated. If rxq_refill() fails (e.g. on OOM condition), subsequent
> teardown would result in an attempt to kfree() invalid pointers.
>
>
From: Lubomir Rintel
Date: Tue, 18 Jun 2013 19:33:28 +0200
> We check the failure status just prior to unmap, since it would be too much of
> a hassle to roll back commands we already started to enqueue if we handled it
> just after the map.
>
> This way we at least avoid a lockup on reclaim,
On 06/19/2013 05:56 PM, Eric Dumazet wrote:
> On Wed, 2013-06-19 at 12:11 +0300, Michael S. Tsirkin wrote:
>
>> Well KVM supports up to 160 VCPUs on x86.
>>
>> Creating a queue per CPU is very reasonable, and
>> assuming cache line size of 64 bytes, netdev_queue seems to be 320
>> bytes, that's
On 19 June 2013 22:42, Lukasz Majewski wrote:
> Boost sysfs attribute is always exported (to support legacy API). By
> default boost is exported as read only. One global attribute is available at:
> /sys/devices/system/cpu/cpufreq/boost.
You asked me and Rafael a question and posted your next
On 19 June 2013 12:46, Lukasz Majewski wrote:
> I would like to clarify the above issue.
>
> When I've discussed with Viresh previous version of this patch, we have
> agreed, that "boost" sysfs attribute [*]:
> /sys/devices/system/cpu/cpufreq/boost
>
> would be only visible when boost_supported
This patches add a read barriers to force the driver to check the interrupt mask
before read_index. Otherwise we may lost a kick to host.
Cc: K. Y. Srinivasan
Cc: Haiyang Zhang
Signed-off-by: Jason Wang
---
drivers/hv/ring_buffer.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
On 18 June 2013 18:56, Rafael J. Wysocki wrote:
> On Tuesday, June 18, 2013 12:12:13 PM Viresh Kumar wrote:
>> On 17 June 2013 19:21, Lukasz Majewski wrote:
>> According to my understanding, boost was important for power
>> saving. In case a high load can be managed by a single cpu with
>>
On 18 June 2013 19:14, Lukasz Majewski wrote:
> On Tue, 18 Jun 2013 15:26:16 +0200, Rafael J. Wysocki wrote:
>> On Tuesday, June 18, 2013 12:12:13 PM Viresh Kumar wrote:
>> > On 17 June 2013 19:21, Lukasz Majewski
>> Well, that's why on x86 turbo is controlled by hardware that takes
>> care of
Hi all,
Today's linux-next merge of the tip tree got a conflict in
arch/arm/kernel/Makefile between commit 4477ca45fb36 ("ARM: ARMv7-M:
Allow the building of new kernel port") from the arm tree and commit
38ff87f77af0 ("sched_clock: Make ARM's sched_clock generic for all
architectures") from the
On 06/20/2013 01:49 AM, Alex Williamson wrote:
> On Thu, 2013-06-20 at 00:50 +1000, Benjamin Herrenschmidt wrote:
>> On Wed, 2013-06-19 at 11:58 +0200, Alexander Graf wrote:
>>
Alex, any objection ?
>>>
>>> Which Alex? :)
>>
>> Heh, mostly Williamson in this specific case but your input is
On Thu, 2013-06-20 at 11:08 +0800, xiaoming gao wrote:
> From: newtongao
> Date: Wed, 19 Jun 2013 14:58:33 +0800
> Subject: [PATCH] net bridge: add null pointer check,fix panic
>
> in kernel 3.0, br_port_get_rcu() may return NULL when network interface be
> deleting from bridge,
> but in
On 6/20/2013 12:40 AM, Linus Walleij wrote:
> On Fri, Jun 14, 2013 at 12:20 PM, Philip Avinash
> wrote:
>
>> From: KV Sujith
>>
>> - Add of_device_id for Davinci GPIO driver.
>> - Add function to populate data from DT.
>> - Modify the probe to read from DT if DT match is found.
>> - Add DT
On 6/20/2013 6:06 AM, Joel A Fernandes wrote:
>>> + /* Clear the xbar mapped channels in unused list */
>>> + xbar_chans = info[j]->xbar_chans;
>>> + if (xbar_chans) {
>>> + for (i = 0; xbar_chans[i][1] != -1; i++) {
>>> +
Hello Samuel,
> -Original Message-
> From: J, KEERTHY
> Sent: Wednesday, June 19, 2013 11:28 AM
> To: linux-o...@vger.kernel.org
> Cc: broo...@kernel.org; J, KEERTHY; ldewan...@nvidia.com;
> sa...@linux.intel.com; grant.lik...@secretlab.ca; swar...@nvidia.com;
>
This patch fixes the below compile warning:
drivers/base/firmware_class.c:1254:12: warning: 'cache_firmware' defined
but not used [-Wunused-function]
static int cache_firmware(const char *fw_name)
^
drivers/base/firmware_class.c:1281:12: warning: 'uncache_firmware'
defined but not
Hi Samuel,
> -Original Message-
> From: Stephen Warren [mailto:swar...@wwwdotorg.org]
> Sent: Wednesday, June 19, 2013 10:39 PM
> To: J, KEERTHY
> Cc: linux-o...@vger.kernel.org; broo...@kernel.org;
> ldewan...@nvidia.com; sa...@linux.intel.com; grant.lik...@secretlab.ca;
>
From: Eric Dumazet
Date: Fri, 14 Jun 2013 05:58:07 -0700
> On Fri, 2013-06-14 at 23:30 +1200, Aydin Arik wrote:
>> MD5 key lookups on a given TCP socket were being performed
>> incorrectly. This fix alters parameter inputs to the MD5
>> lookup function tcp_md5_do_lookup, which is called by
> -Original Message-
> From: Mark Brown [mailto:broo...@kernel.org]
> Sent: Wednesday, June 19, 2013 10:12 PM
> To: J, KEERTHY
> Cc: linux-o...@vger.kernel.org; ldewan...@nvidia.com;
> sa...@linux.intel.com; grant.lik...@secretlab.ca; swar...@nvidia.com;
> linux-kernel@vger.kernel.org;
> -Original Message-
> From: Stephen Warren [mailto:swar...@wwwdotorg.org]
> Sent: Wednesday, June 19, 2013 10:39 PM
> To: J, KEERTHY
> Cc: linux-o...@vger.kernel.org; broo...@kernel.org;
> ldewan...@nvidia.com; sa...@linux.intel.com; grant.lik...@secretlab.ca;
> swar...@nvidia.com;
On 06/18/2013 03:39:54 AM, Suki Buryani wrote:
hi,
i am almost fresh in embedded Linux, i
http://kernelnewbies.org is the community's "where do I start" website.
They have mentoring programs that are likely to provide more attention
than you'll get here.
want to test LDD3 examples,
> -Original Message-
> From: Mark Brown [mailto:broo...@kernel.org]
> Sent: Wednesday, June 19, 2013 10:13 PM
> To: J, KEERTHY
> Cc: linux-o...@vger.kernel.org; ldewan...@nvidia.com;
> sa...@linux.intel.com; grant.lik...@secretlab.ca; swar...@nvidia.com;
> linux-kernel@vger.kernel.org;
On 06/19/2013 06:49 PM, Thomas Gleixner wrote:
>> > But I feel, they are not semantically the same.
> This is not about feelings. This is about facts.
>
Excuse me, my English is not quite well, the reason why I use 'feel' is
to want to say with more polite.
Maybe it is not the correct word for
On Wed, Jun 19, 2013 at 11:45:30PM +0200, Arnd Bergmann wrote:
> On Wednesday 19 June 2013, Guenter Roeck wrote:
> > I have been asked to explore options for adding ARINC 429 support [1]
> > into the Linux kernel, primarily to support devices from Holt Integrated
> > Circuits [2] (the request is
(2013/06/20 5:34), Oleg Nesterov wrote:
> On 06/19, Oleg Nesterov wrote:
>>
>> So. I'll resend this series, will you ack the v2 below?
>
> Also. Could you please review the new patch I am going to include
> into this series?
It looks OK for me. BTW, IIRC, I had reviewed same one previously...
>
Hi Greg,
On Wed, 19 Jun 2013 20:28:12 -0700 Greg KH wrote:
>
> Thanks, that helped out a lot. I've now merged this together, and
> pushed it out to my driver-core-next branch, can you verify that I got
> it all correct?
And I have refetched the driver-core tree for today's linux-next so it
On 20 June 2013 04:19, Rafael J. Wysocki wrote:
> Well, sentences that don't start from upper-case letters don't look like
> separate sentences
s/sequences/sentences for your initial mail.
I misunderstood it as, you want to name cpu{0|1|2} as CPU{1|2|3}..
Obviously sentences must start with
On Thu, Jun 20, 2013 at 11:28 AM, Greg KH wrote:
> On Thu, Jun 20, 2013 at 09:22:13AM +0800, Ming Lei wrote:
>> Hi Stephen,
>>
>> Thanks for your help.
>>
>> On Thu, Jun 20, 2013 at 9:06 AM, Stephen Rothwell
>> wrote:
>>
>> >
>> > Try "git diff-tree --cc
Hi John,
Today's linux-next merge of the wireless-next tree got a conflict in
net/wireless/nl80211.c between commit 3a5a423bb958 ("nl80211: fix attrbuf
access race by allocating a separate one") from the net tree and commit
940d0ac9dbe3 ("cfg80211: fix rtnl leak in wiphy dump error cases") from
From: Li Zefan
This is a leftover after ftrace_regex_lseek() was renamed to
ftrace_filter_lseek() and then ftrace_filter_lseek() was moved
out side of CONFIG_DYNAMIC_FTRACE.
Link: http://lkml.kernel.org/r/51b1a1bd.40...@huawei.com
Signed-off-by: Li Zefan
Signed-off-by: Steven Rostedt
---
From: Steven Rostedt
The function tracer uses preempt_disable/enable_notrace() for
synchronization between reading registered ftrace_ops and unregistering
them.
Most of the ftrace_ops are global permanent structures that do not
require this synchronization. That is, ops may be added and removed
From: Namhyung Kim
There's no point calling it when _alloc() failed.
Link:
http://lkml.kernel.org/r/1370585268-29169-1-git-send-email-namhy...@kernel.org
Signed-off-by: Namhyung Kim
Signed-off-by: Steven Rostedt
---
kernel/trace/trace_events.c |7 +--
1 file changed, 1
From: Wang YanQing
Commit 4f271a2a60c748599b30bb4dafff30d770439b96
(tracing: Add a proc file to stop tracing and free buffer)
implement a method to free up ring buffer in kernel memory
in the release code path of free_buffer's fd.
Then we don't need read/write support for free_buffer,
indeed we
From: "Steven Rostedt (Red Hat)"
Add the "cpudump" command to have the current CPU ftrace buffer dumped
to console if a function is hit. This is useful when debugging a
tripple fault, where you have an idea of a function that is called
just before the tripple fault occurs, and can tell ftrace to
From: Steven Rostedt
There are some cases when filtering on a set flag of a field of a tracepoint
is useful. But currently the only filtering commands for numbered fields
is ==, !=, <, <=, >, >=. This does not help when you just want to trace if
a specific flag is set. For example:
> # sudo
From: Stephen Rothwell
Date: Thu, 20 Jun 2013 12:58:23 +1000
> Today's linux-next merge of the net-next tree got a conflict in
> net/wireless/nl80211.c between commit 3a5a423bb958 ("nl80211: fix attrbuf
> access race by allocating a separate one") from the net tree and commit
> 5fe231e87372
From: "Steven Rostedt (Red Hat)"
b0f1a59a "tracing/filters: Use a different op for glob match" added
glob matching to tracepoint filter strings. It uses the ftrace function
tracing glob matching facility that allows for the wild card character (*)
to be used at the start and/or end of the
From: "Steven Rostedt (Red Hat)"
Add a traceoff_on_warning option in both the kernel command line as well
as a sysctl option. When set, any WARN*() function that is hit will cause
the tracing_on variable to be cleared, which disables writing to the
ring buffer.
This is useful especially when
From: "zhangwei(Jovi)"
Since tp->flags assignment was moved into function enable_trace_probe(),
there is no need to use trace_probe_is_enabled to check flags
in the same function.
Remove the unnecessary checking.
Link: http://lkml.kernel.org/r/51ba7b9e.3040...@huawei.com
Acked-by: Masami
The following patches are queued for 3.11.
Harsh Prateek Bora (1):
tracing/trivial: Consolidate error return condition
Juri Lelli (1):
ftrace: Fix stddev calculation in function profiler
Li Zefan (1):
ftrace: Remove ftrace_regex_lseek()
Namhyung Kim (1):
tracing: Do
From: Harsh Prateek Bora
Consolidate the checks for !enabled and !param to return -EINVAL
in event_enable_func().
Link:
http://lkml.kernel.org/r/1369380137-12452-1-git-send-email-ha...@linux.vnet.ibm.com
Signed-off-by: Harsh Prateek Bora
Signed-off-by: Steven Rostedt
---
From: Juri Lelli
When FUNCTION_GRAPH_TRACER is enabled, ftrace can profile kernel functions
and print basic statistics about them. Unfortunately, running stddev
calculation is wrong. This patch corrects it implementing Welfordâs method:
s^2 = 1 / (n * (n-1)) * (n * \Sum (x_i)^2 -
From: "Steven Rostedt (Red Hat)"
Add the "dump" command to have the ftrace buffer dumped to console if
a function is hit. This is useful when debugging a tripple fault,
where you have an idea of a function that is called just before the
tripple fault occurs, and can tell ftrace to dump its
(2013/06/20 5:30), Oleg Nesterov wrote:
> On 06/18, Oleg Nesterov wrote:
>>
>> On 06/18, Masami Hiramatsu wrote:
>>>
>>> Oh, I agree with removing probe_enable_lock itself :)
>>> I just concerned only about the exceptional case of __init test
>>> function, which can mislead someone to use
Cc: Tejun, and cgroup ML
>> Here are the entries in the cpuset:
>> cgroup.event_control mem_exclusivememory_pressure_enabled
>> notify_on_release tasks
>> cgroup.procs mem_hardwall memory_spread_page release_agent
>> cpu_exclusive memory_migrate
On Thu, Jun 20, 2013 at 09:22:13AM +0800, Ming Lei wrote:
> Hi Stephen,
>
> Thanks for your help.
>
> On Thu, Jun 20, 2013 at 9:06 AM, Stephen Rothwell
> wrote:
>
> >
> > Try "git diff-tree --cc e4b00d75ee3ed3af9fac83970d21e27d1ad4aa8d"
>
> Greg, Stephen, so is sort of below generated patch
On Tue, Jun 18, 2013 at 02:51:13PM +0930, Rusty Russell wrote:
> Tejun Heo writes:
> > Buth yeah, interesting trick. We'll be doing IPIs, flushing TLB and
> > taking faults until it hits zero. It'll all depend on the frequency
> > of preemption but given that branches don't tend to be too
On Wed, Jun 19, 2013 at 09:31:21AM -0700, Sage Weil wrote:
> Hi Li,
>
> There is a version of fsx.c floating around that tests hole punching...
> have you tried running that on top of this patch? Ideally, we should
> build a test (ceph.git/qa/workunits/rbd/hole_punch.sh or similar) that
>
On Tue, Jun 18, 2013 at 02:13:19PM +0100, Will Deacon wrote:
> On Fri, Jun 14, 2013 at 12:21:11AM +0100, Jed Davis wrote:
> > With this change, we no longer lose the innermost entry in the user-mode
> > part of the call chain. See also the x86 port, which includes the ip.
> >
> > It's possible
On Sun, Jun 16, 2013 at 08:51:06PM +0100, Al Viro wrote:
> On Sun, Jun 16, 2013 at 08:51:50PM +0200, Martin Steigerwald wrote:
> > > Seriously, I'm not just making that sh*t up. Google it.
> >
> > I think I will have a look at this.
>
> Look up "sarcasm" as well, while you are at it...
On 06/20/2013 11:02 AM, Gao feng wrote:
> If we don't tie audit to user namespace, there is still one problem.
One more problem. some audit messages are generated by some net subsystem
such as netfilter. If we don't tie audit to user namespace, we have no
idea where these audit messages should
On Wed, 2013-06-19 at 19:43 -0700, David Rientjes wrote:
>
> I'm suspecting that you're referring to enlarged rss because of
> khugepaged's max_ptes_none and because you're abusing the purpose of
> cpusets for containerization.
Why is containerization an abuse? What's wrong with renting
From: newtongao
Date: Wed, 19 Jun 2013 14:58:33 +0800
Subject: [PATCH] net bridge: add null pointer check,fix panic
in kernel 3.0, br_port_get_rcu() may return NULL when network interface be
deleting from bridge,
but in function br_handle_frame and br_handle_local_finish, the pointer didn't
be
With this change, we no longer lose the innermost entry in the user-mode
part of the call chain. See also the x86 port, which includes the ip,
and the corresponding change in arch/arm.
Signed-off-by: Jed Davis
---
arch/arm64/kernel/perf_event.c |1 +
1 file changed, 1 insertion(+)
diff
-...@lists.freedesktop.org
Cc: dri-de...@lists.freedesktop.org
---
drivers/gpu/drm/i915/i915_gem.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20130619.orig/drivers/gpu/drm/i915/i915_gem.c
+++ linux-next-20130619/drivers/gpu/drm/i915/i915_gem.c
@@ -3110,7 +3110,7
On 06/20/2013 04:51 AM, Eric Paris wrote:
> On Wed, 2013-06-19 at 16:49 -0400, Aristeu Rozanski wrote:
>> On Wed, Jun 19, 2013 at 09:53:32AM +0800, Gao feng wrote:
>>> This patchset is first part of namespace support for audit.
>>> in this patchset, the mainly resources of audit system have
>>>
(+)
--- linux-next-20130619.orig/drivers/video/aty/atyfb_base.c
+++ linux-next-20130619/drivers/video/aty/atyfb_base.c
@@ -531,8 +531,10 @@ static int correct_chipset(struct atyfb_
return 0;
}
+#if defined(CONFIG_FB_ATY_GX) || defined(CONFIG_FB_ATY_CT)
static char ram_dram[] = "DRAM"
Mackerras
Cc: Benjamin Herrenschmidt
Cc: linux-fb...@vger.kernel.org
Cc: Jean-Christophe Plagniol-Villard
Cc: Tomi Valkeinen
---
drivers/video/aty/atyfb_base.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-next-20130619.orig/drivers/video/aty
On 2013-06-05 20:50, Stefano Stabellini wrote:
On Wed, 5 Jun 2013, Zhenzhong Duan wrote:
Stefano Stabellini wrote:
On Tue, 21 May 2013, Stefano Stabellini wrote:
On Tue, 21 May 2013, Konrad Rzeszutek Wilk wrote:
Looking at the hypervisor code I couldn't see anything obviously
On Mon, Jun 17, 2013 at 02:20:05PM +0800, Bob Liu wrote:
> Hi Seth,
>
> On Tue, Jun 4, 2013 at 4:33 AM, Seth Jennings
> wrote:
> > zswap is a thin backend for frontswap that takes pages that are in the
> > process
> > of being swapped out and attempts to compress them and store them in a
> >
On Thu, Jun 20, 2013 at 9:43 AM, Lei Wen wrote:
> Hi Alex,
>
> On Mon, Jun 17, 2013 at 11:41 PM, Alex Shi wrote:
>> On 06/17/2013 07:51 PM, Paul Turner wrote:
>>> Can you add something like:
>>>
>>> + /*
>>> +* Task re-woke on same cpu (or else
>>>
On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
> This patch adds device node for TMU controller. There are 3
> instances of the controllers so 3 nodes are created.
>
> Acked-by: Jonghwa Lee
> Acked-by: Kukjin Kim
> Signed-off-by: Amit Daniel Kachhap
Reviewed-by: Eduardo Valentin
> ---
>
On 06/19/13 01:21, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130618:
>
on i386:
drivers/tty/serial/8250/8250_dw.c: In function 'dw8250_serial_inq':
drivers/tty/serial/8250/8250_dw.c:68:2: error: implicit declaration of function
'__raw_readq'
On Thu, Jun 20, 2013 at 02:14:32AM +0200, Christoph Anton Mitterer wrote:
> Well perhaps someone else with enough knowledge has time to look into
> this,... or perhaps someone has some good contacts over at QNAP and is
> able to lobby them to submit their code to the mainline kernel; I tried
> to
On Wed, 19 Jun 2013, Robin Holt wrote:
> cpusets was not for NUMA. It has no preference for "nodes" or anything like
> that. It was for splitting a machine into layered smaller groups. Usually,
> we see one cpuset with contains the batch scheduler. The batch scheduler then
> creates cpusets
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
net/wireless/nl80211.c between commit 3a5a423bb958 ("nl80211: fix attrbuf
access race by allocating a separate one") from the net tree and commit
5fe231e87372 ("cfg80211: vastly simplify locking") from the net-next tree.
I
On Wed, Jun 19, 2013 at 02:23:01PM +0530, Viresh Kumar wrote:
> PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
> should be called or both shouldn't be.
>
> In case we have started PRECHANGE notifier and found an error, we must call
> POSTCHANGE notifier with
On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
> TMU probe function now checks for a device tree defined regulator.
> For compatibility reasons it is allowed to probe driver even without
> this regulator defined.
>
> Acked-by: Jonghwa Lee
> Signed-off-by: Lukasz Majewski
> Signed-off-by:
On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
> This patch updates the documentation to explain the driver model
> and file layout.
>
> Acked-by: Jonghwa Lee
> Acked-by: Kukjin Kim
> Signed-off-by: Amit Daniel Kachhap
Acked-by: Eduardo Valentin
> ---
>
On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
> This patch adds support for h/w mode calibration in the TMU controller.
> soc's like 5440 support this features.
>
> Acked-by: Jonghwa Lee
> Acked-by: Kukjin Kim
> Signed-off-by: Amit Daniel Kachhap
> ---
> drivers/thermal/samsung/exynos_tmu.c
Michael Ellerman [mich...@ellerman.id.au] wrote:
| On Wed, 2013-06-19 at 17:15 +0800, Runzhen Wang wrote:
| > In the Power7 PMU guide:
| >
https://www.power.org/documentation/commonly-used-metrics-for-performance-analysis/
| > PM_BRU_MPRED is referred to as PM_BR_MPRED.
| >
| > This patch fix
> -Original Message-
> From: Samuel Ortiz [mailto:sa...@linux.intel.com]
> Sent: Wednesday, June 19, 2013 4:25 PM
> To: Stephen Rothwell
> Cc: linux-n...@vger.kernel.org; linux-kernel@vger.kernel.org; Chao Xie; Yi
> Zhang
> Subject: Re: linux-next: build failure after merge of the final
On Wed, Jun 19, 2013 at 02:24:07PM -0700, David Rientjes wrote:
> On Wed, 19 Jun 2013, Robin Holt wrote:
>
> > The convenience being that many batch schedulers have added cpuset
> > support. They create the cpuset's and configure them as appropriate
> > for the job as determined by a mixture of
On 06/18/2013 05:16 PM, Aaron Lu wrote:
> On 06/18/2013 02:01 AM, Tejun Heo wrote:
>> On Mon, Jun 17, 2013 at 09:50:20AM +0800, Aaron Lu wrote:
>>> On 06/15/2013 11:02 AM, Liu Jiang wrote:
From: Liu Jiang
Commit 30dcf76acc69 "libata: migrate ACPI code over to new bindings"
Hello,
On Thu, Jun 20, 2013 at 10:29:51AM +0930, Rusty Russell wrote:
> Now seems to get abused by lazy coders who blame users for their own
> broken APIs. And Ubuntu, who turn it on by default in their gcc when
> optimizing. Yeah, it's a sore point :)
How is the API broken? It is a function
The wakeuped migrated task will __synchronize_entity_decay(se); in
migrate_task_rq_fair, then it needs to set
`se->avg.last_runnable_update -= (-se->avg.decay_count) << 20'
before update_entity_load_avg, in order to avoid slept time is updated
twice for se.avg.load_avg_contrib in both
They are the base values in load balance, update them with rq runnable
load average, then the load balance will consider runnable load avg
naturally.
We also try to include the blocked_load_avg as cpu load in balancing,
but that cause kbuild performance drop 6% on every Intel machine, and
To get the latest runnable info, we need do this cpuload update after
task_tick.
Signed-off-by: Alex Shi
Reviewed-by: Paul Turner
---
kernel/sched/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index c78a9e2..ee0225e 100644
On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
> This patch sets the second point trimming value according to the platform
> data if the register value is 0.
>
> Acked-by: Jonghwa Lee
> Acked-by: Kukjin Kim
> Signed-off-by: Amit Daniel Kachhap
Acked-by: Eduardo Valentin
> ---
>
Since tg->load_avg is smaller than tg->load_weight, we don't need a
atomic64_t variable for load_avg in 32 bit machine.
The same reason for cfs_rq->tg_load_contrib.
The atomic_long_t/unsigned long variable type are more efficient and
convenience for them.
Signed-off-by: Alex Shi
Tested-by:
Like as runnable_load_avg, blocked_load_avg variable, long type is
enough for removed_load in 64 bit or 32 bit machine.
Then we avoid the expensive atomic64 operations on 32 bit machine.
Signed-off-by: Alex Shi
Reviewed-by: Paul Turner
Tested-by: Vincent Guittot
---
kernel/sched/fair.c | 10
Based-on-patch-by: Fengguang Wu
Signed-off-by: Alex Shi
Tested-by: Vincent Guittot
---
kernel/sched/proc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/proc.c b/kernel/sched/proc.c
index ce5cd48..16f5a30 100644
--- a/kernel/sched/proc.c
+++
The following 2 variables only used under CONFIG_SMP, so better to move
their definiation into CONFIG_SMP too.
atomic64_t load_avg;
atomic_t runnable_avg;
Signed-off-by: Alex Shi
---
kernel/sched/sched.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kernel/sched/sched.h
On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
> This patch adds configuration data for exynos5440 soc. Also register
> definations for the controller are added.
>
> Acked-by: Jonghwa Lee
> Acked-by: Kukjin Kim
> Signed-off-by: Amit Daniel Kachhap
> ---
> drivers/thermal/samsung/exynos_tmu.c
We need initialize the se.avg.{decay_count, load_avg_contrib} for a
new forked task.
Otherwise random values of above variables cause mess when do new task
enqueue:
enqueue_task_fair
enqueue_entity
enqueue_entity_load_avg
and make forking balancing imbalance since
Tejun Heo writes:
> On Wed, Jun 19, 2013 at 12:25:14PM +0930, Rusty Russell wrote:
>> But it's quite OK to ignore OOM errors in builtin init functions.
>
> I think it'd be cleaner to let those use cases use BUG_ON() around it.
> We really want most users to be checking its return value.
Yeah,
Since the 'u64 runnable_load_avg, blocked_load_avg' in cfs_rq struct are
smaller than 'unsigned long' cfs_rq->load.weight. We don't need u64
vaiables to describe them. unsigned long is more efficient and convenience.
Signed-off-by: Alex Shi
Reviewed-by: Paul Turner
Tested-by: Vincent Guittot
1 - 100 of 1728 matches
Mail list logo
