On 05/07/2015 09:14 PM, NeilBrown wrote:
> On Wed, 6 May 2015 23:34:17 -0700 Ming Lin wrote:
>
>> If a read request fits entirely in a chunk, it will be passed directly to the
>> underlying device (providing it hasn't failed of course). If it doesn't fit,
>> the slightly less efficient path
For ARM, when tracing with tracepoint events, the IP and cpsr are set
to 0, preventing the perf code parsing the callchain and resolving the
symbols correctly.
./perf record -e sched:sched_switch -g --call-graph dwarf ls
[ perf record: Captured and wrote 0.006 MB perf.data ]
./perf report
On 05/07/2015 20:52, Nicholas Krause wrote:
> This fixes the make error when building the ip32_defconfig
> configuration due to using sgio2_cmos_devinit rather then
> the correct function,sgio2_rtc_devinit in a device_initcall
> below this function's definition.
>
> Signed-off-by: Nicholas Krause
For arm & arm64, when tracing with tracepoint events, the IP and cpsr
are set to 0, preventing the perf code parsing the callchain and
resolving the symbols correctly.
These two patches fix this by implementing perf_arch_fetch_caller_regs
for arm and arm64, which fills several necessary
For ARM64, when tracing with tracepoint events, the IP and pstate are set
to 0, preventing the perf code parsing the callchain and resolving the
symbols correctly.
./perf record -e sched:sched_switch -g --call-graph dwarf ls
[ perf record: Captured and wrote 0.146 MB perf.data ]
./perf
Consider "(u64)insn1.imm << 32 | imm" in the arm64 JIT. Since imm is
signed 32-bit, it is sign-extended to 64-bit, losing the high 32 bits.
The fix is to convert imm to u32 first and zero-extend it to u64.
Also extend test_bpf to catch this JIT bug; the interpreter is correct.
Before:
test_bpf:
Al,
I was wondering about the struct page rules of
iov_iter_get_pages_alloc(), used in various places. There's no
documentation whatsoever in lib/iov_iter.c, nor in
include/linux/uio.h, and the changelog that introduced it only says:
commit 91f79c43d1b54d7154b118860d81b39bad07dfff
Author:
Hi all,
Changes since 20150507:
New tree : rtc
The ext4 tree still had its build failure so I used the version from
next-20150506.
Non-merge commits (relative to Linus' tree): 2631
2535 files changed, 117241 insertions(+), 49326 deletions
On Fri, May 08, 2015 at 03:28:00PM +1000, NeilBrown wrote:
> On Wed, 6 May 2015 17:45:49 +0800 Yuanhan Liu
> wrote:
>
> > Move the code that put one idle sh(hot in cache, but happens to be
> > zero referenced) back to active stage to __find_stripe(). Because
> > that's what need to do every
On Thursday 07 May 2015 11:49 AM, Heikki Krogerus wrote:
TUSB1210 ULPI PHY has vendor specific register for eye
diagram tuning. On some platforms the system firmware has
set optimized value to it. In order to not loose the
optimized value, the driver stores it during probe and
restores it
On Friday 08 May 2015 12:25 AM, Felipe Balbi wrote:
On Thu, May 07, 2015 at 09:19:31AM +0300, Heikki Krogerus wrote:
ULPI PHYs need to be bound to their controllers with a
lookup. This adds helpers that the ULPI drivers can use to
do both, the registration of the PHY and the lookup, at the
EP-2DAD0AFA905A4ACB804C4F82A001242F
Hi Andrew,
Presently in oom_kill.c we calculate badness score of the victim task as per
the present RSS counter value of the task.
RSS counter value for any task is usually '[Private (Dirty/Clean)] + [Shared
(Dirty/Clean)]' of the task.
We have encountered a
Update FALLOC_FL_INSERT_RANGE flag in fallocate.
Signed-off-by: Namjae Jeon
Signed-off-by: Ashish Sangwan
---
man2/fallocate.2 | 89
1 file changed, 84 insertions(+), 5 deletions(-)
diff --git a/man2/fallocate.2 b/man2/fallocate.2
index
> -Original Message-
> From: Sergei Shtylyov [mailto:sergei.shtyl...@cogentembedded.com]
> Sent: Thursday, May 07, 2015 6:32 PM
> To: Mehresh Ramneek-B31383; linux-kernel@vger.kernel.org
> Cc: ba...@ti.com; linux-...@vger.kernel.org; st...@rowland.harvard.edu;
>
On Wed, 6 May 2015 17:45:49 +0800 Yuanhan Liu
wrote:
> Move the code that put one idle sh(hot in cache, but happens to be
> zero referenced) back to active stage to __find_stripe(). Because
> that's what need to do every time you invoke __find_stripe().
>
> Moving it there avoids duplicate
On Thu, May 07, 2015 at 09:27:45PM -0700, Doug Anderson wrote:
> If you've got code that does this in a tight loop
> 1. Open watchdog
> 2. Send 'expect close'
> 3. Close watchdog
> ...you'll eventually trigger a watchdog reset. You can reproduce this
> by using daisydog (1) and running:
>
On Tue, May 05, 2015 at 12:46:32PM +0100, Srinivas Kandagatla wrote:
> Hi Stephen,
>
> Sorry I took so long to reply.
>
>
> On 09/04/15 15:45, Stephen Boyd wrote:
> >On 04/07, Srinivas Kandagatla wrote:
> >>On 07/04/15 19:45, Stephen Boyd wrote:
> >>>On 03/30, Srinivas Kandagatla wrote:
> >>>
>
On Thu, May 07, 2015 at 09:27:44PM -0700, Doug Anderson wrote:
> Right now the dw_wdt uses a spinlock to protect dw_wdt_open(). The
> problem is that while holding the spinlock we call:
> -> dw_wdt_set_top()
>-> dw_wdt_top_in_seconds()
> -> clk_get_rate()
> ->
It seems odd to me to use BUG() for what you appear to be using it for..
not that I know exactly what that it mind you, but when you said when
some other gizmo in your box has a problem you crash the kernel, my head
tilted to the side - surely there's a more controlled response possible
than
On Thu, May 07, 2015 at 08:18:43PM +0100, One Thousand Gnomes wrote:
> > We could keep heap metadata as R/O and only make it R/W inside of
> > malloc() itself to catch corruption more quickly.
>
> If you implement multiple malloc pools you can chop up lots of stuff.
>
> In library land it isn't
Hi Walleij,
Acked-by: Sonic Zhang
Sonic
On Thu, May 7, 2015 at 5:53 PM, Linus Walleij wrote:
> While the pinmux_ops are ideally just a vtable for pin mux
> calls, the "strict" setting belongs so intuitively with the
> pin multiplexing that we should move it here anyway. Putting
> it in the
I've had reports of UEFI platforms failing iSCSI boot in various
configurations, that ended up being caused by network initialization
scripts getting tripped up by unexpected null addresses (0.0.0.0) being
reported for gateways, dhcp servers, and dns servers.
The tianocore EDK2 iSCSI driver
On Fri, 2015-05-08 at 04:16 +, Oza (Pawandeep) Oza wrote:
> So Mike, is this reason strong enough for you ?
Nope. I think you did the right thing in removing your dependency on
jiffies reliability in a dying box. You don't have to convince me of
anything though, CC timer subsystem
On 4 May 2015 at 14:24, Shilpasri G Bhat wrote:
> This patchset intends to add frequency throttle reporting mechanism
> to powernv-cpufreq driver when OCC throttles the frequency. OCC is an
> On-Chip-Controller which takes care of the power and thermal safety of
> the chip. The CPU frequency can
bdi_unregister() now contains very little functionality.
It contains a "WARN_ON" if bdi->dev is NULL. This warning is of no
real consequence as bdi->dev isn't needed by anything else in the function,
and it triggers if
blk_cleanup_queue() -> bdi_destroy()
is called before bdi_unregister,
Dear Kernel Maintainer,
Submitting the following information for kernel bug review.
[1.] Lenovo SL510 will not resume from suspend
[2.] When using the following three steps to suspend the laptop the will
not resume from suspend. The suspend light flash rapidly instead of slowly.
1. systemctl
On Thu, 7 May 2015 21:27:44 -0700
Doug Anderson wrote:
> Right now the dw_wdt uses a spinlock to protect dw_wdt_open(). The
> problem is that while holding the spinlock we call:
> -> dw_wdt_set_top()
>-> dw_wdt_top_in_seconds()
> -> clk_get_rate()
> -> clk_prepare_lock()
>
> -Original Message-
> From: Alan Stern [mailto:st...@rowland.harvard.edu]
> Sent: Thursday, May 07, 2015 8:16 PM
> To: Mehresh Ramneek-B31383
> Cc: linux-kernel@vger.kernel.org; ba...@ti.com; linux-...@vger.kernel.org;
> gre...@linuxfoundation.org
> Subject: Re: [PATCH 02/10]
* One Thousand Gnomes wrote:
> On Thu, 7 May 2015 21:26:20 +0200
> Ingo Molnar wrote:
>
> >
> > * One Thousand Gnomes wrote:
> >
> > > > We could keep heap metadata as R/O and only make it R/W inside of
> > > > malloc() itself to catch corruption more quickly.
> > >
> > > If you
On 05/07/2015 09:27 PM, Doug Anderson wrote:
Right now the dw_wdt uses a spinlock to protect dw_wdt_open(). The
problem is that while holding the spinlock we call:
-> dw_wdt_set_top()
-> dw_wdt_top_in_seconds()
-> clk_get_rate()
-> clk_prepare_lock()
->
On Wednesday 29 April 2015 10:38 PM, Steven Rostedt wrote:
> On Wed, 29 Apr 2015 21:28:38 +0530
> Shreyas B Prabhu wrote:
>
>>
>>
>> On Wednesday 29 April 2015 08:48 PM, Steven Rostedt wrote:
>>> On Wed, 29 Apr 2015 20:19:28 +0530
>>> Shreyas B Prabhu wrote:
>>>
IIUC there is no existing
On Sat, Apr 11, 2015 at 09:40:32PM +0200, Robert Jarzmik wrote:
> Document the new design of the pxa dma driver.
>
> Signed-off-by: Robert Jarzmik
> ---
> Documentation/dmaengine/pxa_dma.txt | 157
>
> 1 file changed, 157 insertions(+)
> create mode 100644
This is a new one I think, I hit it on the haswell machine running
4.1-rc2.
The backtrace is complex enough I'm not really sure what's going on here.
The fuzzer has been having weird issues where it's been getting
overflow signals from invalid fds. This seems to happen
when an overflow
* Hemant Kumar wrote:
> # perf kvm stat report -p 60515
> Analyze events for pid(s) 60515, all VCPUs:
>
>VM-EXITSamples Samples% Time%Min Time Max
> Time Avg time
>
> H_DATA_STORAGE 500635.30% 0.13% 1.94us 49.46us
>
If you've got code that does this in a tight loop
1. Open watchdog
2. Send 'expect close'
3. Close watchdog
...you'll eventually trigger a watchdog reset. You can reproduce this
by using daisydog (1) and running:
while true; do daisydog -c > /dev/null; done
The problem is that each time
Right now the dw_wdt uses a spinlock to protect dw_wdt_open(). The
problem is that while holding the spinlock we call:
-> dw_wdt_set_top()
-> dw_wdt_top_in_seconds()
-> clk_get_rate()
-> clk_prepare_lock()
-> mutex_lock()
Locking a mutex while holding a spinlock is
On Thu, May 07, 2015 at 10:04:32PM +0200, Greg Kroah-Hartman wrote:
> On Thu, May 07, 2015 at 03:06:52PM +0530, Sudip Mukherjee wrote:
> > the previous patch of the series made this variable unused.
>
> What do you mean? There was only one other patch in this series, never
> send a patch that
On Thu, 7 May 2015, Peter Zijlstra wrote:
> Indeed so; and we can make an analogous argument for hwc. However:
>
> > I think it is more likely related to the bitmask (idxmsk). But then
> > it is always allocated with the constraint even with the HT bug
> > workaround. So most, likely the index
On Thu, May 07, 2015 at 10:18:49AM +0200, Paul Bolle wrote:
> Just a nit: a license mismatch.
>
> On Wed, 2015-05-06 at 01:37 -0700, Gregory Fong wrote:
> > --- /dev/null
> > +++ b/drivers/gpio/gpio-brcmstb.c
>
> > + * This program is free software; you can redistribute it and/or
> > + * modify
On Fri, 1 May 2015, Ingo Molnar wrote:
> So fffe corresponds to 2 events left until overflow,
> right? And on Haswell we don't set x86_pmu.limit_period AFAICS, so we
> allow these super short periods.
>
> Maybe like on Broadwell we need a quirk on Nehalem/Haswell as well,
> one
So Mike, is this reason strong enough for you ?
I understand your point: solve the BUG, and I do tend to agree with you.
But by design and implementation, the BUG() is just a beginning of the end for
dying kernel.
And what happens in between this 'the beginning' and 'the end' is not less
On Wed, 6 May 2015 23:34:17 -0700 Ming Lin wrote:
> If a read request fits entirely in a chunk, it will be passed directly to the
> underlying device (providing it hasn't failed of course). If it doesn't fit,
> the slightly less efficient path that uses the stripe_cache is used.
> Requests
On 5/7/15 5:37 PM, Suravee Suthikulpanit wrote:
Currently, device drivers, which support both OF and ACPI,
need to call two separate APIs, of_dma_is_coherent() and
acpi_dma_is_coherent()) to determine device coherency attribute.
This patch simplifies this process by introducing a new device
Initial commit for a new SoC family, UniPhier, developed by
Socionext Inc. (formerly, System LSI Business Division of
Panasonic Corporation).
This commit includes a minimal set of components for booting the
kernel, including SMP support.
Signed-off-by: Masahiro Yamada
---
Changes in v7: None
Initial device trees for UniPhier SoCs: PH1-sLD3, PH1-LD4, PH1-Pro4,
and PH1-sLD8.
Signed-off-by: Masahiro Yamada
---
Changes in v7:
- Remove redundant "fifo-size" from the 16550A uart node
Changes in v6:
- Remove redundant interrupt-parent property from timer nodes.
Changes in v5: None
Signed-off-by: Masahiro Yamada
---
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 1939513..3c31a27 100644
---
Hi Dave,
Thanks for your comment!
On Fri, May 8, 2015 at 6:20 AM, Dave Chinner wrote:
> On Thu, May 07, 2015 at 08:32:39PM +0800, Ming Lei wrote:
>> On Thu, May 7, 2015 at 3:24 PM, Christoph Hellwig wrote:
>> >> @@ -441,6 +500,12 @@ static void do_loop_switch(struct loop_device *lo,
>> >>
Add UniPhier, a new citizen in the ARM multi platform.
Signed-off-by: Masahiro Yamada
---
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff
This is an initial series for supporting Socionext UniPhier SoCs,
based on ARM Cortex-A9, mainly used for digital TVs, video recorders, etc.
Masahiro Yamada (4):
ARM: UniPhier: add basic support for UniPhier architecture
ARM: multi_v7_defconfig: enable UniPhier SoC family
ARM: dts:
On 08.05.2015 13:01, Anand Moon wrote:
> Hi Krysztof,
>
> Actually the patch is based on https://lkml.org/lkml/2015/4/3/389
> I don't know how to measure the energy consumption when compared to
> cpufreq-exynos.
It does not have to be energy consumption. It may be something else
visible, like
The port.type has already been set by of_platform_serial_setup()
called from a few lines above.
Setting it to the same value is redundant.
Signed-off-by: Masahiro Yamada
---
drivers/tty/serial/of_serial.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/tty/serial/of_serial.c
Hi Krysztof,
Actually the patch is based on https://lkml.org/lkml/2015/4/3/389
I don't know how to measure the energy consumption when compared to
cpufreq-exynos.
I will update the commit log and resend it with you review.
-Anand Moon
On 8 May 2015 at 05:44, Krzysztof Kozlowski wrote:
>
Hi,
On Thu, May 7, 2015 at 6:47 PM, Guenter Roeck wrote:
> On 05/07/2015 03:09 PM, Doug Anderson wrote:
>>
>> Right now the dw_wdt uses a spinlock to protect dw_wdt_open(). The
>> problem is that while holding the spinlock we call:
>> -> dw_wdt_set_top()
>> -> dw_wdt_top_in_seconds()
>>
On 05/08/2015 02:29 AM, Rafael J. Wysocki wrote:
> On Thursday, May 07, 2015 05:49:22 PM Preeti U Murthy wrote:
>> On 05/05/2015 02:11 PM, Preeti U Murthy wrote:
>>> On 05/05/2015 12:03 PM, Shilpasri G Bhat wrote:
Hi Preeti,
On 05/05/2015 09:30 AM, Preeti U Murthy wrote:
> Hi
On Wed, May 06, 2015 at 12:13:42PM +0200, Maxime Ripard wrote:
> On Wed, May 06, 2015 at 11:31:31AM +0200, Jens Kuske wrote:
> > The H3 SoC has the same dma engine as the A31 (sun6i), with a
> > reduced amount of endpoints and physical channels. Add the proper
> > config data and compatible string
On Thu, May 07, 2015 at 12:48:34PM +0300, Peter Ujfalusi wrote:
> On 05/04/2015 08:38 AM, Vinod Koul wrote:
> > On Thu, Apr 09, 2015 at 12:35:49PM +0300, Peter Ujfalusi wrote:
> >> +int omap_dmaxbar_init(void)
> >> +{
> >> + return platform_driver_register(_dma_xbar_driver);
> >> +}
> >>
On May 8, 2015 8:11 AM, "Dave Chinner" wrote:
>
> On Thu, May 07, 2015 at 10:20:53AM -0700, Zach Brown wrote:
> > On Thu, May 07, 2015 at 10:26:17AM +1000, Dave Chinner wrote:
> > > On Wed, May 06, 2015 at 03:00:12PM -0700, Zach Brown wrote:
> > > > Add the O_NOMTIME flag which prevents mtime
On Thu, May 7, 2015 at 9:21 AM, H.J. Lu wrote:
> On Thu, May 7, 2015 at 4:52 AM, Jan Beulich wrote:
> On 07.05.15 at 08:02, wrote:
>>> AFAICT gas will produce relocations for jumps to global labels in the
>>> same file. This doesn't seem directly harmful to me, except that, on
>>> x86, it
In glibc 2.21 (and several previous), a call to opendir() will
result in a 32K (BUFSIZ*4) buffer being allocated and passed to
getdents.
However a call to fdopendir() results in an 'fstat' request to
determine block size and a matching buffer allocated for subsequent
use with getdents. This
On 2015/5/8 10:29, Yun Wu (Abel) wrote:
> Hi Gerry,
> On 2015/5/4 11:15, Jiang Liu wrote:
>
>> NUMA node information is per-irq instead of per-irqchip, so move it into
>> struct irq_common_data.
>>
>> Signed-off-by: Jiang Liu
>> ---
>> arch/sh/kernel/irq.c |2 +-
>>
On Thu, 2015-05-07 at 13:31 -0700, Jacob Pan wrote:
> On Fri, 8 May 2015 03:39:04 +0930
> Anand Moon wrote:
>
> > To install tmon we issue "make install" which produces bellow error.
> >
> looks good, there is no config file for now.
>
> Thanks for the fix.
> Acked-by: Jacob Pan
>
patch
This patch adds a driver to support the ktd2692 flash LEDs.
ktd2692 can control flash current by ExpressWire interface.
Signed-off-by: Ingi Kim
Acked-by: Seung-Woo Kim
Reviewed-by: Varka Bhadram
---
drivers/leds/Kconfig| 9 +
drivers/leds/Makefile | 1 +
This patch adds vendor prefix for Kinetic technologies
Signed-off-by: Ingi Kim
Acked-by: Rob Herring
Acked-by: Seung-Woo Kim
Reviewed-by: Varka Bhadram
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
This patch adds ktd2692 Flash LED driver with LED Flash class
Change in v8:
- Add led-max-microamp mandatory property for LEDs current
base on Jacek's patch [1]
patch [1] [PATCH v6] DT: leds: Improve description of
flash LEDs related properties
- Fix
This patch adds the device tree bindings for ktd2692 flash LEDs.
Add Optional properties of child node for Flash LED
Signed-off-by: Ingi Kim
Acked-by: Seung-Woo Kim
Reviewed-by: Varka Bhadram
---
.../devicetree/bindings/leds/leds-ktd2692.txt | 50 ++
1 file changed,
Currently, a fill-up partition (indicated by '-') must be the last
partition, and no other partitions can go after it. Change the
cmdlinepart parsing code to allow a fill-up partition at any point.
This is useful, for example, if you want to reserve a partition at the
end of the flash where the
On 04/30/2015 07:36 PM, Paolo Bonzini wrote:
smep_andnot_wp is initialized in kvm_init_shadow_mmu and shadow pages
should not be reused for different values of it. Thus, it has to be
added to the mask in kvm_mmu_pte_write.
Good catch!
Reviewed-by: Xiao Guangrong
--
To unsubscribe from
On Thu, 7 May 2015 15:09:24 -0700
Doug Anderson wrote:
> If you've got code that does this in a tight loop
> 1. Open watchdog
> 2. Send 'expect close'
> 3. Close watchdog
> ...you'll eventually trigger a watchdog reset. You can reproduce this
> by using daisydog (1) and running:
> while
On Thu, May 07, 2015 at 12:53:46PM -0700, Andy Lutomirski wrote:
> On Thu, May 7, 2015 at 12:09 PM, Richard Weinberger
> wrote:
> > On Thu, May 7, 2015 at 7:20 PM, Zach Brown wrote:
> >> On Thu, May 07, 2015 at 10:26:17AM +1000, Dave Chinner wrote:
> >>> On Wed, May 06, 2015 at 03:00:12PM -0700,
On Thu, 7 May 2015 15:09:23 -0700
Doug Anderson wrote:
> Right now the dw_wdt uses a spinlock to protect dw_wdt_open(). The
> problem is that while holding the spinlock we call:
> -> dw_wdt_set_top()
>-> dw_wdt_top_in_seconds()
> -> clk_get_rate()
> -> clk_prepare_lock()
>
On Thu, May 07, 2015 at 10:20:53AM -0700, Zach Brown wrote:
> On Thu, May 07, 2015 at 10:26:17AM +1000, Dave Chinner wrote:
> > On Wed, May 06, 2015 at 03:00:12PM -0700, Zach Brown wrote:
> > > Add the O_NOMTIME flag which prevents mtime from being updated which can
> > > greatly reduce the IO
On a system that has multiple devices on the mmc bus the host can
block on the mutex that protects access to the bus. Some operations
require the status of the device to be polled to see when the device
finishes executing the previous command that was sent to it (if
there is no busy detection in
On 2015/5/4 11:15, Jiang Liu wrote:
[...]
> diff --git a/include/linux/irqdesc.h b/include/linux/irqdesc.h
> index dd1109fb241e..3010e99abf3e 100644
> --- a/include/linux/irqdesc.h
> +++ b/include/linux/irqdesc.h
> @@ -47,6 +47,7 @@ struct pt_regs;
> * @name:flow handler name for
Hi Gerry,
On 2015/5/4 11:15, Jiang Liu wrote:
> NUMA node information is per-irq instead of per-irqchip, so move it into
> struct irq_common_data.
>
> Signed-off-by: Jiang Liu
> ---
> arch/sh/kernel/irq.c |2 +-
> arch/x86/kernel/apic/vector.c |8
>
On Thu, May 07, 2015 at 11:06:06AM -0400, Dan Streetman wrote:
>
> The crypto 842-nx has (significant) code in it to handle any alignment
> and length input buffers, to match them to what the driver requires.
> Would it be better to move that into the crypto code, so that any
> crypto compression
If a wakeup source is found to be pending in the last stage of suspend
after syscore suspend then the device doesn't suspend but the error is
not propogated which causes an error in the accounting for the number
of suspend aborts and successful suspends.
Signed-off-by: Ruchi Kandoi
---
On Thu, May 07, 2015 at 11:25:29AM +0200, Arnd Bergmann wrote:
> On Wednesday 06 May 2015 14:18:47 Ray Jui wrote:
> > On 5/6/2015 2:05 PM, Brian Norris wrote:
> > > On Wed, May 06, 2015 at 09:17:36PM +0200, Arnd Bergmann wrote:
> > >> You had mentioned previously that there might be an endianess
ct results (with openrisc):
groeck@server:~/src/linux-next$ git bisect log
# bad: [55a92d585bd9150b7bd06882e0579a943a22c356] Add linux-next specific files
for 20150507
# good: [5ebe6afaf0057ac3eaeb98defd5456894b446d22] Linux 4.1-rc2
git bisect start 'HEAD' 'v4.1-rc2'
# good: [3ef136d5df42c848c119a0
On 05/07/2015 03:09 PM, Doug Anderson wrote:
If you've got code that does this in a tight loop
1. Open watchdog
2. Send 'expect close'
3. Close watchdog
...you'll eventually trigger a watchdog reset. You can reproduce this
by using daisydog (1) and running:
while true; do daisydog
Linus,
The newly added ftrace_print_array_seq() function had a bug in it. Luckily,
the only user of it didn't make the 4.1 merge window. But the helper
function should be fixed before 4.2 when the users start coming in.
Please pull the latest trace-fixes-v4.1-rc2 tree, which can be found at:
On 05/07/2015 03:09 PM, Doug Anderson wrote:
Right now the dw_wdt uses a spinlock to protect dw_wdt_open(). The
problem is that while holding the spinlock we call:
-> dw_wdt_set_top()
-> dw_wdt_top_in_seconds()
-> clk_get_rate()
-> clk_prepare_lock()
->
On Thu, May 07, 2015 at 04:47:15PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150506:
>
> The ext4 tree gained a build failure so I used the version from
> next-20150506.
>
> The vfs tree gained a conflict against the f2fs tree.
>
> The rcu tree gained conflicts against the
Hello!
On May 7, 2015, at 8:09 AM, Dan Carpenter wrote:
>>> Clean up spacing in some variable declarations, to be more consistent.
>>>
>>> It's small, but I need to start somewhere. Please let me know if I'm not
>>> adhering to proper procedure for trivial cleanups.
>>
>> It's actually Lustre
- Original Message -
> On Tue, 5 May 2015 07:54:46 -0700
> Drew Richardson wrote:
>
> > CLOCK_MONOTONIC_RAW will advance more constantly than CLOCK_MONOTONIC.
> >
> > Imagine someone is trying to optimize a particular program to reduce
> > instructions executed for a given workload
> -Original Message-
> From: Sergey Senozhatsky [mailto:sergey.senozhat...@gmail.com]
> Sent: Thursday, May 07, 2015 4:24 AM
> To: Konduru, Chandra
> Cc: Daniel Vetter; Sergey Senozhatsky; David Airlie; Vetter, Daniel; intel-
> g...@lists.freedesktop.org; dri-de...@lists.freedesktop.org;
==
ANNOUNCEMENT AND CALL FOR PARTICIPATION
LINUX SECURITY SUMMIT 2015
20-21 AUGUST
SEATTLE WA, USA
On 7 May 2015 at 02:56, Boris Brezillon
wrote:
> Luis, Tyler,
>
> On Thu, 7 May 2015 09:55:53 +0100
> Luis Henriques wrote:
>
>> On Wed, May 06, 2015 at 10:25:17PM -0700, Tyler Baker wrote:
>> >
>> > Locally I've reverted c67881fc890916206e723329e774391c6ed354ce on top
>> > of v3.19.7 and
On 05/08/2015 04:47 AM, Greg Kroah-Hartman wrote:
On Thu, May 07, 2015 at 10:18:15AM +0800, Lu Baolu wrote:
This patch implements device_suspend/device_resume entries for xHC driver.
device_suspend will be called when a USB device is about to suspend. It
will issue a stop endpoint command for
On Thu, May 7, 2015 at 9:01 PM, Sage Weil wrote:
> On Thu, 7 May 2015, Zach Brown wrote:
>> On Thu, May 07, 2015 at 10:26:17AM +1000, Dave Chinner wrote:
>> > On Wed, May 06, 2015 at 03:00:12PM -0700, Zach Brown wrote:
>> > > The criteria for using O_NOMTIME is the same as for using O_NOATIME:
>>
On 05/07/15 at 10:25am, Don Dutile wrote:
> On 05/07/2015 10:00 AM, Dave Young wrote:
> >On 04/07/15 at 10:12am, Don Dutile wrote:
> >>On 04/06/2015 11:46 PM, Dave Young wrote:
> >>>On 04/05/15 at 09:54am, Baoquan He wrote:
> On 04/03/15 at 05:21pm, Dave Young wrote:
> >On 04/03/15 at
Just to avoid compiling errors on arm.
Signed-off-by: AKASHI Takahiro
---
arch/arm/include/asm/kvm_asm.h |1 +
arch/arm/include/asm/kvm_host.h | 12
arch/arm/include/asm/kvm_mmu.h |5 +
arch/arm/kvm/init.S |6 ++
4 files changed, 24 insertions(+)
This patch allows cpu cores to be up and down by adding
kvm_arch_hardware_enable/isable(). This way, especially in kexec case,
cores are reset to initial states and kexec can gracefully shutdown the
system and reboot a new kernel from EL2.
Signed-off-by: AKASHI Takahiro
---
By indroducing cpu kvm hotplug, this dependency is not needed any more.
Signed-off-by: AKASHI Takahiro
---
arch/arm64/kvm/Kconfig |1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/kvm/Kconfig b/arch/arm64/kvm/Kconfig
index 30ae7a7..f5590c8 100644
--- a/arch/arm64/kvm/Kconfig
+++
Cpu must be put back into its initial state, at least, in the
following cases in order to shutdown the system and/or re-initialize cpus
later on:
1) kexec/kdump
2) cpu hotplug (offline)
3) removing kvm as a module
To address those issues in later patches, this patch adds a tear-down
function,
This patch set addresses KVM issue described in Geoff's kexec patch set[1].
See "Changes" below.
Initially, I used reboot notifier hook to shut down cpu cores, but in this
version, kvm cpu hotplug is implemented after Mark's comment.
I confirmed that it works with kexec under the following
On 05/07/2015 10:34 PM, Alan Stern wrote:
On Thu, 7 May 2015, Lu, Baolu wrote:
+ void(*device_suspend)(struct usb_hcd *, struct usb_device *udev,
+ pm_message_t msg);
+ void(*device_resume)(struct usb_hcd *, struct usb_device *udev,
+
Expose the NMI safe accessor to the monotonic raw clock to the
tracer. The mono clock was added with commit
1b3e5c0936046e7e023149ddc8946d21c2ea20eb. Although the monotonic raw
clock cannot be used to compare time between different machines, it is
not perturbed by ntp.
Signed-off-by: Drew
powerpc provides hcall events that also provide insights into guest
behaviour. Enhance perf kvm to record and analyze hcall events.
- To trace hcall events :
perf kvm stat record
- To show the results :
perf kvm stat report --event=hcall
The result shows the number of hypervisor calls
From: Srikar Dronamraju
perf kvm can be used to analyze guest exit reasons. This support already
exists in x86. Hence, porting it to powerpc.
- To trace KVM events :
perf kvm stat record
If many guests are running, we can track for a specific guest by using
--pid as in : perf kvm stat
Use perf_probe_event.target field for the target binary
instead of passing it as an argument.
Signed-off-by: Masami Hiramatsu
---
tools/perf/builtin-probe.c|1 -
tools/perf/util/probe-event.c | 55 +++--
tools/perf/util/probe-event.h |4 +--
3
1 - 100 of 2182 matches
Mail list logo
