On 02/12/2013 17:10, Nicolas Ferre wrote:
Acked-by Boris BREZILLON
Signed-off-by: Nicolas Ferre
---
arch/arm/boot/dts/sama5d3_uart.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/sama5d3_uart.dtsi
b/arch/arm/boot/dts/sama5d3_uart.dtsi
index
On 12/2/13, 2:33 AM, Pekka Enberg wrote:
I'm seeing rather large "sch delay" numbers on Fedora 19's default
kernel that seem like a data error of some sort:
4500.663117 [02] fix_client[7216] 0.007
18446744073708.033 1.786
Does this address the large numbers for you?
David
On Mon, Dec 02, 2013 at 11:31:01AM +0100, leroy christophe wrote:
>
> Le 01/12/2013 20:38, Guenter Roeck a écrit :
> >On 11/30/2013 07:33 AM, Christophe Leroy wrote:
> >>Convert mpc8xxx_wdt.c to the new watchdog API.
> >>
> >>Signed-off-by: Christophe Leroy
> >>
> >>diff -ur
Signed-off-by: Nicolas Ferre
---
arch/arm/boot/dts/sama5d3.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/sama5d3.dtsi b/arch/arm/boot/dts/sama5d3.dtsi
index f520b0236671..f5fd111b5ee6 100644
--- a/arch/arm/boot/dts/sama5d3.dtsi
+++
From: srinivas kandagatla
Date: Mon, 2 Dec 2013 10:48:32 +
> Do you have any plans to take this series?
They aren't queued up in "Under Review" state in patchwork, so no.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
From: "David Laight"
Date: Mon, 2 Dec 2013 10:04:49 -
> I know you like ethernet drivers to work this way, but requiring enough
> descriptors for a maximally fragmented packet requires a difficult
> calculation and will cause the tx queue to be stopped unnecessarily.
...
> Isn't there also
Signed-off-by: Nicolas Ferre
---
arch/arm/boot/dts/sama5d3_uart.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/sama5d3_uart.dtsi
b/arch/arm/boot/dts/sama5d3_uart.dtsi
index 49d4d76ca6f4..a9fa75e41652 100644
--- a/arch/arm/boot/dts/sama5d3_uart.dtsi
+++
On Sat, Nov 30, 2013 at 04:45:40PM +0100, Christophe Leroy wrote:
> MPC8xx watchdog is enabled at startup by HW.
> If the bootloader disables it, it cannot be reenabled.
>
> Signed-off-by: Christophe Leroy
>
Reviewed-by: Guenter Roeck
> diff -ur a/drivers/watchdog/mpc8xxx_wdt.c
On Thu, Nov 28, 2013 at 1:17 PM, Souvik Banerjee wrote:
> When I run `dkms install vboxhost/4.3.2` it fails to build with the
> following error:
> -
>
> DKMS make.log for vboxhost-4.3.2 for kernel
>
On Sat, Nov 30, 2013 at 1:08 PM, Linus Torvalds
wrote:
>
> I still don't see what could be wrong with the pipe_inode_info thing,
> but the fact that it's been so consistent in your traces does make me
> suspect it really is *that* particular slab.
I think I finally found it.
I've spent waaayy
>
> That would be kind of OK, if the driver's .suspend_late() only invoked its own
> .runtime_suspend(), what you did below.
>
> But, in the Ulf's approach the driver calls .runtime_suspend() from
> its *subsystem* in the hope that it will all work out properly (or
> perhaps based on the knowledge
On Mon, Dec 2, 2013 at 9:38 AM, Vlad Yasevich wrote:
> On 11/27/2013 11:03 PM, Sun Paul wrote:
>> How LKSCTP select which source address to use for the INIT_ACK or
>> HB_ACK? below is the testing result where a router is located in the
>> middle.
>>
>> Before starting the application. the packet
* Peter Zijlstra wrote:
> Subject: sched: Revert 14a40ffccd61 ("sched: replace PF_THREAD_BOUND with
> PF_NO_SETAFFINITY")
>
> PF_NO_SETAFFINITY, which crudely turns off affinity control and cgroups
> access to tasks, and which is in use by every workqueue thread in Linux (!),
> is
On Fri, Nov 29, 2013 at 11:10:48AM +0800, Baoquan He wrote:
[..]
> > +void *arch_kexec_kernel_image_load(struct kimage *image, char *kernel,
> > + unsigned long kernel_len, char *initrd,
> > + unsigned long initrd_len, char *cmdline,
> > +
Since Ubuntu 13.10 "Saucy Salamander" uses the 3.11 kernel, the Ubuntu
kernel team will pick up stable maintenance where Greg KH left off[1]
with 3.11.10 (thanks a lot, Greg!).
The Ubuntu kernel team is pleased to announce that we will be
providing extended stable support for the Linux 3.11
2013-12-02 (월), 13:57 +0100, Ingo Molnar:
> So basically, in the end I think it should be possible to have the
> following behavior:
>
>perf record -a -e cycles sleep 1
>
>perf report stat # Reports as if we ran: 'perf stat -a -e
> cycles sleep 1'
>perf report
On Thu, Nov 28, 2013 at 07:35:14PM +0800, Baoquan He wrote:
[..]
> > +void *bzImage64_load(struct kimage *image, char *kernel,
> > + unsigned long kernel_len,
> > + char *initrd, unsigned long initrd_len,
> > + char *cmdline, unsigned long cmdline_len)
> > +{
> > +
>
On Mon, Dec 02, 2013 at 07:55:21PM +0530, Kamala R wrote:
> The behaviour of blackhole and prohibit routes has been corrected by setting
> the input and output pointers of the dst variable appropriately. For
> blackhole routes, they are set to dst_discard and to ip6_pkt_discard and
>
setlocalversion script was testing the presence of .git directory in order to
find out
if git is used as SCM to track the current kernel project. However in some
cases, .git
is not a directory but can be a file: when the kernel is a git submodule part
of a git
super project for example.
This
On 12/02, Oleg Nesterov wrote:
>
> The lockless while_each_thread() is racy and broken, almost
> every user can loop forever.
> ...
> Another problem with while_each_thread() is that it is very easy
> to use it wrongly, and oom_kill.c is the good example.
Forgot to mention, it is not necessarily
Hi Thomas,
On 11/29/2013 05:28 PM, Thomas Gleixner wrote:
> On Fri, 29 Nov 2013, Preeti U Murthy wrote:
>> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
>> index b44b52c..cafa788 100644
>> --- a/arch/powerpc/Kconfig
>> +++ b/arch/powerpc/Kconfig
>> @@ -129,6 +129,8 @@ config PPC
>>
On Thu, Nov 28, 2013 at 07:28:16PM +0800, Baoquan He wrote:
[..]
> > +int crash_copy_backup_region(struct kimage *image)
> > +{
>
> Why need this func be called, backup region has been added into crash
> segment by kexec_add_buffer, and then buffer copy is done in
> kimage_load_crash_segment. I
Logging and tracking firmware bugs in the kernel has long been an issue
for system administrators. The current kernel does not have a good
uniform method of reporting firmware bugs and the code in the kernel is a
mix of printk's and WARN_ONs. This causes problems for both system
administrators
Logging and tracking firmware bugs in the kernel has long been an issue
for system administrators. The current kernel does not have a good
uniform method of reporting firmware bugs and the code in the kernel is a
mix of printk's and WARN_ONs. This causes problems for both system
administrators
Logging and tracking firmware bugs in the kernel has long been an issue
for system administrators. The current kernel does not have a good
uniform method of reporting firmware bugs and the code in the kernel is a
mix of printk's and WARN_ONs. This causes problems for both system
administrators
Subject: sched: Revert 14a40ffccd61 ("sched: replace PF_THREAD_BOUND with
PF_NO_SETAFFINITY")
PF_NO_SETAFFINITY, which crudely turns off affinity control and cgroups
access to tasks, and which is in use by every workqueue thread in Linux (!),
is conceptually wrong on many levels:
- We should
On Thu, Nov 28, 2013 at 05:48:02PM +0900, HATAYAMA Daisuke wrote:
> Hello Vivek,
>
> Here is a patch set for mmap failure for /proc/vmcore.
> Could you try to use this on the problematic system?
>
> This patch doesn't copy partial pages to the 2nd kernel, only prepares
> vmcore objects for
On 11/29/13 at 11:10am, Baoquan He wrote:
> On 11/20/13 at 12:50pm, Vivek Goyal wrote:
> > diff --git a/arch/x86/kernel/machine_kexec_64.c
> > b/arch/x86/kernel/machine_kexec_64.c
> > index 4eabc16..fb41b73 100644
> > --- a/arch/x86/kernel/machine_kexec_64.c
> > +++
On Mon, Dec 02, 2013 at 11:56:17AM +, Mark Brown wrote:
> On Sat, Nov 16, 2013 at 12:25:29AM +0800, Nicolin Chen wrote:
> > The normal mode of SSI allows it to send/receive data to/from the first
> > slot of each period. So we can use this normal mode to trick I2S signal
> > by puting/getting
while_each_thread() and next_thread() should die, almost every
lockless usage is wrong.
1. Unless g == current, the lockless while_each_thread() is not safe.
while_each_thread(g, t) can loop forever if g exits, next_thread()
can't reach the unhashed thread in this case. Note that this can
1. Change oom_kill.c to use for_each_thread() rather than the racy
while_each_thread() which can loop forever if we race with exit.
Note also that most users were buggy even if while_each_thread()
was fine, the task can exit even _before_ rcu_read_lock().
Fortunately the new
Sorry for late response to these threads. Holiday weekend in the US.
On 11/29/2013 06:14 AM, Viresh Kumar wrote:
On some systems we can't really say what frequency we're running at the moment
and so for these we shouldn't check if we are running at a frequency present in
frequency table. For
Hello.
This was reported several times, I believe the first report is
http://marc.info/?l=linux-kernel=127688978121665. Hmm, 3 years
ago. The lockless while_each_thread() is racy and broken, almost
every user can loop forever.
Recently people started to report they actually hit this problem in
> Something like below? user space supply buffer for error string.
That would work, although I was thinking of making it a more
generic mechanism (store it into task_struct, have a extra
syscall to retrieve)
-Andi
>
> jirka
>
>
> ---
> diff --git a/include/uapi/linux/perf_event.h
>
> Well, to be honest, I'd never put a call to pm_runtime_get_sync() into
> a driver's system suspend callback.
Nevertheless, the PM core allows it to happen and there are not only
subsystem-level code but also drivers that use it, for whatever
reasons.
>
> Subsystem callbacks are a different
Ming Lei writes:
> blk_mq_alloc_request_pinned() may return NULL request in case of
> !__GFP_WAIT, so cause its callers to derefence NULL pointer for
> releasing current context.
>
> This patch introduces two flags to address the issue.
Hi, Ming,
Good catch, but your patch seems overly
On Sat, Nov 23, 2013 at 04:37:10PM +0100, Frederic Weisbecker wrote:
> Ingo, Thomas,
>
> Please pull the timers/posix-timers-for-tip branch that can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> timers/posix-timers-for-tip
>
> HEAD:
On 12/02/2013 04:16 PM, Michal Marek wrote:
> On 2.12.2013 16:14, Franck Bui-Huu wrote:
>> On 12/02/2013 03:57 PM, Michal Marek wrote:
>>> On 2.12.2013 14:21, Franck Bui-Huu wrote:
diff --git a/scripts/setlocalversion b/scripts/setlocalversion
index 0b5ccf3..c16e65d 100755
---
Logging and tracking firmware bugs in the kernel has long been an issue
for system administrators. The current kernel does not have a good
uniform method of reporting firmware bugs and the code in the kernel is a
mix of printk's and WARN_ONs. This causes problems for both system
administrators
On 2.12.2013 16:14, Franck Bui-Huu wrote:
> On 12/02/2013 03:57 PM, Michal Marek wrote:
>> On 2.12.2013 14:21, Franck Bui-Huu wrote:
>>> diff --git a/scripts/setlocalversion b/scripts/setlocalversion
>>> index 0b5ccf3..c16e65d 100755
>>> --- a/scripts/setlocalversion
>>> +++
Hi,
During 3.13-rc1 testing, I have found out that the mvmdio driver would report
timeouts on the kernel console:
[ 11.011334] orion-mdio orion-mdio: Timeout: SMI busy for too long
The hardware is a MV88F6281 Kirkwood CPU. The mvmdio driver is using the irq
line 46 (ge00_err).
I am
On 12/02/2013 03:57 PM, Michal Marek wrote:
> On 2.12.2013 14:21, Franck Bui-Huu wrote:
>> diff --git a/scripts/setlocalversion b/scripts/setlocalversion
>> index 0b5ccf3..c16e65d 100755
>> --- a/scripts/setlocalversion
>> +++ b/scripts/setlocalversion
>> @@ -43,7 +43,8 @@ scm_version()
>> fi
On 12/02/2013 04:03 PM, Sebastian Andrzej Siewior wrote:
> On 12/02/2013 02:44 PM, Roger Quadros wrote:
>> "Errata id: i660
>> DESCRIPTION
>> In the following configuration :
>> • USBHOST module is set to smart-idle mode
>> • PRCM asserts idle_req to the USBHOST module. (This typically happens
Hi Thomas,
On 11/29/2013 08:09 PM, Thomas Gleixner wrote:
> On Fri, 29 Nov 2013, Preeti U Murthy wrote:
>> +static enum hrtimer_restart handle_broadcast(struct hrtimer *hrtimer)
>> +{
>> +struct clock_event_device *bc_evt = _timer;
>> +ktime_t interval, next_bc_tick, now;
>> +
>> +now
Hi Ingo,
2013-12-02 (월), 13:45 +0100, Ingo Molnar:
> * Namhyung Kim wrote:
>
> > From: Namhyung Kim
> >
> > It's sometimes useful to see total sampling or elapsed time with
> > normal performance result. To do that, record first and last sample
> > time for each evsel and to display it in
On Mon, 2 Dec 2013, Joonsoo Kim wrote:
> Now, the size of the freelist for the slab management diminish,
> so that the on-slab management structure can waste large space
> if the object of the slab is large.
Hmmm.. That is confusing to me. "Since the size of the freelist has shrunk
significantly
Linus,
please pull the latest irq-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
irq-urgent-for-linus
* Correction of fuzzy and fragile IRQ_RETVAL macro
* IRQ related resume fix affecting only XEN
* ARM/GIC fix for chained GIC controllers
On 12/1/13, 10:59 PM, Masami Hiramatsu wrote:
> (2013/12/02 9:07), David Ahern wrote:
>> When requesting a function from a userspace library the error message to
>> the user is less than helpful. e.g.,
>>
>> perf probe -x /lib64/libpthread-2.14.90.so -a
>>
Thanks for the patch Corey.
I am afraid that the system does not have interrupts enabled. It uses polling
mode.
When the error is seen, I know for a fact that in function ipmi_thread()
smi_result is SI_SM_CALL_WITH_DELAY,
I have some logs where in busy_wait always reads as 1. Not sure if it
On 05-11-2013 13:26, Lukasz Majewski wrote:
> This patch provides auto disable/enable operation for boost. It uses already
> present thermal infrastructure to provide boost hysteresis.
> A special set of TMU data has been defined for Exynos4412, which is only
> considered when BOOST is enabled.
Thanks, applying.--b.
On Sat, Nov 30, 2013 at 05:56:44PM +0800, Weng Meiling wrote:
>
> From: Weng Meiling
>
> Signed-off-by: Weng Meiling
> ---
> include/linux/sunrpc/svc.h | 2 +-
> net/sunrpc/xprtsock.c | 7 +++
> 2 files changed, 4 insertions(+), 5 deletions(-)
>
> diff --git
On Mon, 2 Dec 2013, Roger Quadros wrote:
> It won't be done by omap_hwmod as we set HWMOD_INIT_NO_RESET flag in the
> hwmod data [1].
>
> Question is do we do it in the driver of leave it to hwmod?
It should be done by hwmod (or more broadly, some OMAP bus code). That
way the device can be
On 2.12.2013 14:21, Franck Bui-Huu wrote:
> diff --git a/scripts/setlocalversion b/scripts/setlocalversion
> index 0b5ccf3..c16e65d 100755
> --- a/scripts/setlocalversion
> +++ b/scripts/setlocalversion
> @@ -43,7 +43,8 @@ scm_version()
> fi
>
> # Check for git and a git repo.
> -
2013-12-02 (월), 09:39 -0300, Arnaldo Carvalho de Melo:
> Em Mon, Dec 02, 2013 at 03:53:18PM +0900, Namhyung Kim escreveu:
> > From: Namhyung Kim
> >
> > Calculate elapsed time for each sample and record it. The elapsed
> > time is a diff between current sample->time and previous sample->time
>
On Thu, Nov 28, 2013 at 10:34:27AM +0900, HATAYAMA Daisuke wrote:
[..]
> int generic_processor_info(int apicid, int version)
> {
> int cpu, max = nr_cpu_ids;
> - bool boot_cpu_detected = physid_isset(boot_cpu_physical_apicid,
> + /*
> + * boot_cpu_physical_apicid is designed
On Fri, 2013-11-29 at 11:30 +, Matt Fleming wrote:
> > /*
> >* Add an additional efi_memory_desc_t because we're doing an
> >* allocation which may be in a new descriptor region.
> > + * We allocate as EFI_RUNTIME_SERVICES_DATA since this is what
> > + * we want
On Sun, 2013-12-01 at 14:38 -0800, Joe Perches wrote:
> On Sun, 2013-12-01 at 10:35 +0100, Johannes Berg wrote:
> > Good try, but no, now ap_sdata isn't even assigned. :)
>
> Right. Oh well. There's no improving this without
> significant rewrite. Even then, there may not be much
> overall
On 12/1/13, 11:15 PM, Masami Hiramatsu wrote:
> (2013/12/02 9:07), David Ahern wrote:
>> Allow user to specify an address within an executable. This is useful, for
>> example, in probing local functions. If the function name begins with 0x
>> then try to convert the supplied name to an address. If
On Sat, Nov 30, 2013 at 02:59:07PM +0100, Ingo Molnar wrote:
>
> * Frederic Weisbecker wrote:
>
> > Ingo,
> >
> > Please pull the timers/core branch that can be found at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> > timers/core
> >
> > It passed
Free previously allocated map.
Signed-off-by: Stanislav Fomichev
---
tools/perf/util/session.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/perf/util/session.c b/tools/perf/util/session.c
index 4ce146bae552..ee717ee9ca3a 100644
--- a/tools/perf/util/session.c
+++
On Monday, December 02, 2013 02:29:46 AM Rafael J. Wysocki wrote:
> On Sunday, December 01, 2013 02:24:33 AM Rafael J. Wysocki wrote:
> > On Saturday, November 30, 2013 02:27:15 PM Yinghai Lu wrote:
> > > On Sat, Nov 30, 2013 at 1:37 PM, Rafael J. Wysocki
> > > wrote:
> > > > On Saturday,
On Sat, Nov 30, 2013 at 04:53:07AM -0800, tip-bot for Namhyung Kim wrote:
> Commit-ID: ad7ebb9a48f59bad2714b64725653a73d78b686e
> Gitweb: http://git.kernel.org/tip/ad7ebb9a48f59bad2714b64725653a73d78b686e
> Author: Namhyung Kim
> AuthorDate: Tue, 26 Nov 2013 17:51:12 +0900
> Committer:
Linus,
Please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
# HEAD: 96739d6e548e16d76de39d059e1e39e70c187fff sched/doc: Fix generation
of device-drivers
Various smaller fixlets, all over the place.
Hey Linus,
Please git pull the following tag:
git pull git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
stable/for-linus-3.13-rc2-tag
which has three fixes. The signed tag has the details - but it is just
fixes to patches that went in this merge window along with a latent
bug.
Print all CPUs, even if there were no events (use perf header to get number
of CPUs).
This is required to support topology in the next patch.
Signed-off-by: Stanislav Fomichev
---
tools/perf/builtin-timechart.c | 32 ++--
1 file changed, 26 insertions(+), 6
More than two boolean arguments to a function are rather confusing and
error-prone for callers. Let's make the behavior bit flags instead of
triple combos.
A nice suggestion by Borislav Petkov.
Acked-by: Borislav Petkov
Acked-by: Prarit Bhargava
Acked-by: Ming Lei
Signed-off-by: Takashi Iwai
On Mon, 02 Dec 2013 14:32:13 +0100
Tim Sander wrote:
> > If all goes well, this patch will be converted to the next main release
> > on 11/25/2013.
> I don't want to nag you but as this date is in the past i just wanted to know
> if anything has not gone well besides that the non-rc version is
When CONFIG_FW_LOADER_USER_HELPER is set, request_firmware() falls
back to the usermode helper for loading via udev when the direct
loading fails. But the recent udev takes way too long timeout (60
seconds) for non-existing firmware. This is unacceptable for the
drivers like microcode loader
Add -t switch to sort CPUs topologically.
Signed-off-by: Stanislav Fomichev
---
tools/perf/Documentation/perf-timechart.txt | 3 +
tools/perf/builtin-timechart.c | 17 +++-
tools/perf/util/svghelper.c | 132 +++-
Add backtrace info to the CPU usage timechart.
Signed-off-by: Stanislav Fomichev
---
tools/perf/builtin-timechart.c | 10 --
tools/perf/util/svghelper.c| 4 +++-
tools/perf/util/svghelper.h| 2 +-
3 files changed, 12 insertions(+), 4 deletions(-)
diff --git
rootfs was missing its f.
Signed-off-by: Emilio López
---
drivers/base/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/base/Kconfig b/drivers/base/Kconfig
index e373671..ec36e77 100644
--- a/drivers/base/Kconfig
+++ b/drivers/base/Kconfig
@@ -49,7 +49,7 @@
On Sat, Nov 30, 2013 at 03:11:06PM +0100, Ingo Molnar wrote:
>
> * Ingo Molnar wrote:
>
> >
> > * Frederic Weisbecker wrote:
> >
> > > Ingo,
> > >
> > > Please pull the timers/core branch that can be found at:
> > >
> > >
Hi Greg,
this is the revised patchset, just rebased to be applicable cleanly
to 3.13-rc tree. Other than that, there is no change since v3.
[PATCH v4 1/4] firmware: Introduce request_firmware_direct()
[PATCH v4 2/4] microcode: Use request_firmware_direct()
[PATCH v4 3/4] firmware: Use bit
On 28/11/2013 15:49, Boris BREZILLON :
Hello,
This patch series moves sama5d3 SoCs and boards to the new at91 clk framework
(based on common clk framework).
Best Regards,
Whole series:
Acked-by: Nicolas Ferre
and added on top of CCF one for at91-3.14-cleanup
Bye,
Boris
Changes since
On Mon, Dec 2, 2013 at 5:02 AM, Hiroshi Doyu wrote:
> Stephen Warren wrote @ Sun, 1 Dec 2013 20:00:09 +0100:
>
>> On 11/29/2013 04:46 AM, Hiroshi Doyu wrote:
>> ...
>> > Iterating over a property containing a list of phandles with arguments
>> > is a common operation for device drivers. This
The commit [3e358ac2bb5b: firmware: Be a bit more verbose about direct
firmware loading failure] introduced a new warning message about
falling back to user helper, but this isn't true when
CONFIG_FW_LOADER_USER_HELPER isn't set.
In this patch, clear the FW_OPT_FALLBACK flag in the case without
Linus,
Please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
# HEAD: e98a6e59dff885eb387163b1a7abe019a44ba90b Merge tag
'perf-urgent-for-mingo' of
On 11/27/2013 11:03 PM, Sun Paul wrote:
> How LKSCTP select which source address to use for the INIT_ACK or
> HB_ACK? below is the testing result where a router is located in the
> middle.
>
> Before starting the application. the packet on eth1 and eth2 are
>
> eth1
> 0 packets dropped by kernel
Use the new helper, request_firmware_direct(), for avoiding the
lengthy timeout of non-existing firmware loads. Especially the Intel
microcode driver suffers from this problem because each CPU triggers
the f/w loading, thus it ends up taking (literally) hours with many
cores.
Tested-by: Prarit
Add PID to the figures of CPU usage timechart.
Signed-off-by: Stanislav Fomichev
---
tools/perf/builtin-timechart.c | 1 +
tools/perf/util/svghelper.c| 4 ++--
tools/perf/util/svghelper.h| 2 +-
3 files changed, 4 insertions(+), 3 deletions(-)
diff --git
This patch series has the following features:
- adds backtrace info to the CPU overview chart
- adds pid info to the figures on CPU overview chart
- we now read number of CPUs from the perf.data header (this makes CPU overview
more accurate since it shows idle cores)
- adds '-t' option to sort
Hi Arnaldo,
2013-12-02 (월), 09:33 -0300, Arnaldo Carvalho de Melo:
> Em Mon, Dec 02, 2013 at 03:53:19PM +0900, Namhyung Kim escreveu:
> > From: Namhyung Kim
> >
> > The --show-time-info option is for displaying elapsed sampling time
>
> Isn't that too long? Can't we use just --time/-t?
Hmm..
This commit reverts part of the 3e6a147deef9 "perf tools: Separate lbfd
check out of NO_DEMANGLE condition" which always links perf with libbfd.
I'd like to preserve old behavior when NO_DEMAGLE does not link with
it, because some machines may contain different versions of binutils
(hence miss
On 12/2/13, 12:41 AM, Namhyung Kim wrote:
Hi David,
On Sun, 1 Dec 2013 17:23:15 -0700, David Ahern wrote:
Add entry to perf-sched documentation for timehist command and its
options.
[SNIP]
+--max-stack::
+Set the stack depth limit when showing the callchains. Default: 127
Isn't it 5
On Mon, 2 Dec 2013 15:15:37 +0530
Viresh Kumar wrote:
> Binary was written as binay, probably by mistake. Fix it.
This can go through the trivial tree.
Acked-by: Steven Rostedt
-- Steve
>
> Signed-off-by: Viresh Kumar
> ---
> include/linux/tracepoint.h | 2 +-
> 1 file changed, 1
At Mon, 2 Dec 2013 06:32:45 -0800,
Greg Kroah-Hartman wrote:
>
> On Mon, Dec 02, 2013 at 09:44:13AM +0100, Takashi Iwai wrote:
> > At Sat, 16 Nov 2013 06:24:55 +0900,
> > Greg Kroah-Hartman wrote:
> > >
> > > On Fri, Nov 15, 2013 at 04:34:09PM +0100, Takashi Iwai wrote:
> > > > At Tue, 12 Nov
On 12/2/13, 2:33 AM, Pekka Enberg wrote:
On 12/02/2013 02:23 AM, David Ahern wrote:
'perf sched timehist' provides an analysis of scheduling events.
Example usage:
perf sched record -- sleep 1
perf sched timehist
By default it shows the individual schedule events, including the time
On 02/12/13 09:28, Dave Jones wrote:
> On Mon, Dec 02, 2013 at 03:16:24PM +0100, Jiri Kosina wrote:
> > On Sat, 30 Nov 2013, Dave Jones wrote:
> >
> > > > Commit: 4a2c94c9b6c03af61b04993340bd9559e2277de4
> > > > Author: Benjamin Tissoires
> > > > AuthorDate: Wed Nov 20 09:49:41
On Mon, 2 Dec 2013, Dave Jones wrote:
> Commit 4a2c94c9b6 inadvertantly removed a break from the GENIUS_GX_IMPERATOR
> case.
> Spotted by Coverity.
>
> Signed-off-by: Dave Jones
>
> diff --git a/drivers/hid/hid-kye.c b/drivers/hid/hid-kye.c
> index ecb5ca669e97..e77696367591 100644
> ---
On Mon, Dec 02, 2013 at 09:44:13AM +0100, Takashi Iwai wrote:
> At Sat, 16 Nov 2013 06:24:55 +0900,
> Greg Kroah-Hartman wrote:
> >
> > On Fri, Nov 15, 2013 at 04:34:09PM +0100, Takashi Iwai wrote:
> > > At Tue, 12 Nov 2013 13:02:12 +0100,
> > > Takashi Iwai wrote:
> > > >
> > > > Hi,
> > > >
>
Hi,
I have submitted a version 4 of my patch that squashes the above
changes into it as well. Is that the right way to do it ?
Regards,
Kamala
On Sat, Nov 30, 2013 at 11:29 PM, Hannes Frederic Sowa
wrote:
> On Sat, Nov 30, 2013 at 12:51:10PM -0500, David Miller wrote:
>> From: Hannes Frederic
On Mon, Dec 02, 2013 at 03:16:24PM +0100, Jiri Kosina wrote:
> On Sat, 30 Nov 2013, Dave Jones wrote:
>
> > > Commit: 4a2c94c9b6c03af61b04993340bd9559e2277de4
> > > Author: Benjamin Tissoires
> > > AuthorDate: Wed Nov 20 09:49:41 2013 -0500
> > > Committer: Jiri Kosina
> >
On 12/2/13, 12:58 AM, Namhyung Kim wrote:
time cpu task name[tid/pid]b/n time sch delay run time
- - - -
79371.874569 [11] gcc[31949] 0.014 0.000 1.148
79371.874591 [10] gcc[31951]
On Mon, Dec 02, 2013 at 07:25:01PM +0530, Laxman Dewangan wrote:
I think the canonical subject prefix for Tegra is:
ARM: tegra:
Perhaps also mention that you "Add" the header file? Like so:
ARM: tegra: Add header file for pinctrl constants
> Defines pincontrol constants to use
The behaviour of blackhole and prohibit routes has been corrected by setting
the input and output pointers of the dst variable appropriately. For
blackhole routes, they are set to dst_discard and to ip6_pkt_discard and
ip6_pkt_discard_out respectively for prohibit routes.
ipv6:
On Mon, Dec 2, 2013 at 10:53 AM, Paul Bolle wrote:
> On Mon, 2013-12-02 at 08:33 +0100, Daniel Vetter wrote:
>> On Sun, Dec 1, 2013 at 5:57 PM, Paul Bolle wrote:
>> > The WARNING is now gone during suspend and resume (having tested that
>> > thoroughly - ie, twice). But I still see it at boot.
On Sat, 30 Nov 2013, Dave Jones wrote:
> > Commit: 4a2c94c9b6c03af61b04993340bd9559e2277de4
> > Author: Benjamin Tissoires
> > AuthorDate: Wed Nov 20 09:49:41 2013 -0500
> > Committer: Jiri Kosina
> > CommitDate: Thu Nov 21 10:28:58 2013 +0100
> >
> > HID: kye: Add report
On Sat, 30 Nov 2013, Zawullon wrote:
> Issue description: I have two Logitech Dual Action gamepads, both have
> same Vendor/Device id pair. Newest gamepad (A) can switch between old mode
> (HID)
> and XBox gamepad emulation mode. Old gamepad (B) can only work in HID mode.
> In HID mode gamepad A
Hi Mark,
On Wed, 2013-11-27 at 16:28 +, Mark Brown wrote:
> On Wed, Nov 27, 2013 at 04:13:23PM +, Lee Jones wrote:
> > On Wed, 27 Nov 2013, Mark Brown wrote:
>
> > > The usual thing to do is of_get_child_by_name() on the parent to get the
> > > container to search in.
>
> > What do you
On 11/28, Oleg Nesterov wrote:
>
> On 11/28, Michal Hocko wrote:
> >
> > They are both trying to solve the same issue. Neither of them is
> > optimal unfortunately.
>
> yes, but this one doesn't look right.
>
> > Oleg said he would look into this and I have seen
> > some patches but didn't geto
901 - 1000 of 2434 matches
Mail list logo
