On Tue, Jan 13, 2015 at 11:22:40PM -0800, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.14.29 release.
> There are 77 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know
On Fri, Jan 09, 2015 at 08:40:56PM +0800, Wang, Yalin wrote:
> Oh, I see,
> How about change like this:
> + select HAVE_ARCH_BITREVERSE if ((CPU_V7M || CPU_V7) && !CPU_V6 &&
> !CPU_V6K)
> I am not sure if I also need add some older CPU types like !CPU_ARM9TDMI &&
> !CPU_ARM940T ?
>
> Another
debugfs_remove_recursive() is NULL-aware, thus, we may safely remove the check
here. There is no need to assing NULL to variable since it will be not used
anywhere.
Signed-off-by: Andy Shevchenko
Acked-by: Aubrey Li
---
arch/x86/kernel/pmc_atom.c | 4
1 file changed, 4 deletions(-)
diff -
Couple of clean ups and one feature enhancement (expose PSS register in the
debug fs).
Changes since v4:
- address one Thomas' comment (patch 1/5 was added)
- rebased on recent linux-next
Changes since v3:
- rebase on top of recent linux-next
- resend to better place for review and push
Changes
The PSS register reflects the power state of each island on SoC. It would be
useful to know which of the islands is on or off at the momemnt.
Signed-off-by: Andy Shevchenko
Acked-by: Aubrey Li
---
arch/x86/include/asm/pmc_atom.h | 22 +++
arch/x86/kernel/pmc_atom.c | 61 +++
pmc_dbgfs_unregister() will be called when pmc->dbgfs_dir is unconditionally
NULL on error path in pmc_dbgfs_register(). To prevent this we move an
assignment to where is should be.
Fixes: f855911c1f48 (x86/pmc_atom: Expose PMC device state and platform sleep
state)
Reported-by: Thomas Gleixner
There is no need to use err variable.
Signed-off-by: Andy Shevchenko
Acked-by: Aubrey Li
---
arch/x86/kernel/pmc_atom.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git a/arch/x86/kernel/pmc_atom.c b/arch/x86/kernel/pmc_atom.c
index 6b62f55..f8becc4 100644
--- a/arch
DRIVER_NAME seems unused. This patch just removes it. There is no functional
change.
Signed-off-by: Andy Shevchenko
---
arch/x86/kernel/pmc_atom.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/x86/kernel/pmc_atom.c b/arch/x86/kernel/pmc_atom.c
index 1dd6c62..6b62f55 100644
--- a/arch
On 01/14/2015 06:24 AM, Arnd Bergmann wrote:
On Tuesday 13 January 2015 19:47:00 Jon Masters wrote:
Hi Folks,
TLDR: I would like to consider the value of adding something like
"cluster_siblings" or similar in sysfs to describe ARM topology.
A quick question on intended data representation in /
On Tue, Jan 13, 2015 at 02:26:01PM -0500, Paul Clements wrote:
> On Tue, Jan 13, 2015 at 11:14 AM, Andrey Utkin
> wrote:
> > Hi Paul,
> > could you please describe
>
> > - how wide is NBD usage today (any estimation is ok),
>
> It depends somewhat on who you consider to be users. There are two
>
Le 14/01/2015 14:20, Peter Rosin a écrit :
> From: Peter Rosin
>
> The DDRSDR controller (on the ATSAMA5D31) fails miserably to put LPDDR1
> memories in self-refresh. Force the controller to think it has DDR2
> memories during the self-refresh period, as the DDR2 self-refresh spec
> is equivalent
On 01/14/2015, 05:37 PM, Guenter Roeck wrote:
> On Tue, Jan 13, 2015 at 11:22:40PM -0800, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 3.14.29 release.
>> There are 77 patches in this series, all will be posted as a response
>> to this one. If anyone has any is
On Wed 14-01-15 17:06:59, Vinayak Menon wrote:
[...]
> In one such instance, zone_page_state(zone, NR_ISOLATED_FILE)
> had returned 14, zone_page_state(zone, NR_INACTIVE_FILE)
> returned 92, and GFP_IOFS was set, and this resulted
> in too_many_isolated returning true. But one of the CPU's
> pagese
On Wed, 31 Dec, at 06:37:39PM, Matt Fleming wrote:
> On Wed, 17 Dec, at 08:54:56AM, Andy Lutomirski wrote:
> > > As far as I know, the only way to have continuously functional interrupt
> > > handling across a long mode transition is to install an interrupt vector
> > > table and hope that CPUs act
Dave noticed that unprivileged process can allocate significant amount
of memory -- >500 MiB on x86_64 -- and stay unnoticed by oom-killer and
memory cgroup. The trick is to allocate a lot of PMD page tables. Linux
kernel doesn't account PMD tables to the process, only PTE.
The use-cases below use
On Mon, Jan 12, 2015 at 11:23:12AM -0800, Yinghai Lu wrote:
> Some bios put range that is not fully coverred by root bus resources.
> Try to clip them and update them in pci bridge bars.
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=85491
> Reported-by: Marek Kordik
> Tested-by: Marek Kor
On Sun, Dec 21, 2014 at 1:47 AM, Geert Uytterhoeven
wrote:
> Hi Mike, Stephen,
>
> On Sun, Dec 21, 2014 at 2:14 AM, Linux Kernel Mailing List
> wrote:
>> Gitweb:
>> http://git.kernel.org/linus/;a=commit;h=baeb0d9b98c3450e22f8f8e4a6619b8b1d5106ff
>> Commit: baeb0d9b98c3450e22f8f8e4a6619b8
On Wed, Jan 14, 2015 at 10:40:01AM -0500, Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> If the function graph tracer traces a jprobe callback, the system will
> crash. This can easily be demonstrated by compiling the jprobe
> sample module that is in the kernel tree, loading it and
Hi,
On 14/01/2015 at 16:21:50 +, Russell King - ARM Linux wrote :
> On Wed, Jan 14, 2015 at 04:46:03PM +0100, Alexandre Belloni wrote:
> > Hi,
> >
> > This patch set hasn't moved since while. We actually need patch 4 to
> > properly configure prefetch on sama5d4. What would be needed to come
These are 4 of probably many examples of what could be changed if the proposed
sign_extend8, 16 and 64 are added to bitops.h, now as real patches.
Again, keep in mind, only take them if "PATCH v2 add sign_exted8, 16 and 64"
is included first.
--
To unsubscribe from this list: send the line "unsub
Signed-off-by: Martin Kepplinger
---
drivers/rtc/rtc-x1205.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/rtc/rtc-x1205.c b/drivers/rtc/rtc-x1205.c
index b1de58e..3ec0b95 100644
--- a/drivers/rtc/rtc-x1205.c
+++ b/drivers/rtc/rtc-x1205.c
@@ -22,6 +22,7 @@
#incl
Signed-off-by: Martin Kepplinger
---
drivers/input/tablet/gtco.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/drivers/input/tablet/gtco.c b/drivers/input/tablet/gtco.c
index 8580456..25b3834 100644
--- a/drivers/input/tablet/gtco.c
+++ b/drivers/input/tablet/gtc
Signed-off-by: Martin Kepplinger
Reviewed-by: Guenter Roeck
---
drivers/hwmon/jc42.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/hwmon/jc42.c b/drivers/hwmon/jc42.c
index 388f8bc..d0582a3 100644
--- a/drivers/hwmon/jc42.c
+++ b/drivers/hwmon/jc42.c
@@ -31,6
2015-01-14 01:27+, Wu, Feng:
> > the new
> > > hardware even doesn't consider the TPR for lowest priority interrupts
> > delivery.
> >
> > A bold move ... what hardware was the first to do so?
>
> I think it was starting with Nehalem.
Thanks, (Could be that QPI can't inform about TPR change
Signed-off-by: Martin Kepplinger
---
drivers/media/dvb-frontends/stb0899_algo.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/media/dvb-frontends/stb0899_algo.c
b/drivers/media/dvb-frontends/stb0899_algo.c
index 93596e0..7bbcfde 100644
--- a/drivers/media/dvb-f
On Wed, Jan 14, 2015 at 12:47:00AM +, Jon Masters wrote:
> Hi Folks,
>
> TLDR: I would like to consider the value of adding something like
> "cluster_siblings" or similar in sysfs to describe ARM topology.
>
> A quick question on intended data representation in /sysfs topology
> before I ask
2015-01-14 18:44 GMT+02:00 Sudip Mukherjee :
> studied the driver code. looks like the driver is simple and the main work is
> being done by the nbd-client and nbd-server.
> i was thinking of putting in my name for consideration, but being a newbie in
> lkml (have worked with drivers and server-c
Hi,
On Wed, Jan 14, 2015 at 03:08:43PM +0800, Sneeker Yeh wrote:
> Hi Felipe:
>
> thanks for suggestion,
>
> 2015-01-13 1:20 GMT+08:00 Felipe Balbi :
>
> > Hi,
> >
> > On Sun, Jan 11, 2015 at 11:19:55PM +0800, Sneeker Yeh wrote:
> > > > > > enable the quirk only for you. Isn't there a better wa
Hello,
On Wed, Jan 14, 2015 at 11:07:31PM +0800, Xunlei Pang wrote:
> Cc Uwe Kleine-Koenig
Thanks, that was useful.
>
> On 13 January 2015 at 23:44, Xunlei Pang wrote:
> > From: Xunlei Pang
> >
> > This driver has a number of y2038/y2106 issues.
> >
> > This patch resolves them by:
> > - Repl
On 01/14/2015 02:18 AM, Bart Tanghe wrote:
To probe the bcm2835-pwm driver properly, this dts bindings has to be added
to the bcm2835 dtsi file.
In expectation of a bcm2835 clock driver, I've added fixed-clock clock binding.
---
Changes in v3:
- node added by reg value
The pwm node still seem
On Wed, 14 Jan 2015 17:55:37 +0100
Borislav Petkov wrote:
> Err, stupid question: marking the jprobe handler "notrace" doesn't help?
>
A few reasons.
One, that would require all users to make their handler as "notrace".
That's not very reliable. Not to mention, I still work at Red Hat and
we
2015-01-13 21:26 GMT+02:00 Paul Clements :
>> - what are critical bugs or important issues requiring work, if there are
>> any.
>
> There is a network timeout issue, which is probably one of the more
> important fixes to get in:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770479
Looking
On Vi, 2014-12-26 at 11:13 +, Jonathan Cameron wrote:
> On 18/12/14 16:51, Lars-Peter Clausen wrote:
> > Adding V4L folks to Cc for more input.
> Thanks Lars - we definitely would need the v4l guys to agree to a driver like
> this going in IIO. (not that I'm convinced it should!)
> >
> > On 12
Since lapic timer handler only wakes up a simple waitqueue,
it can be executed from hardirq context.
Reduces average cyclictest latency by 3us.
Signed-off-by: Marcelo Tosatti
---
arch/x86/kvm/lapic.c | 42 +++---
1 file changed, 39 insertions(+), 3 deletio
The problem:
On -RT, an emulated LAPIC timer instances has the following path:
1) hard interrupt
2) ksoftirqd is scheduled
3) ksoftirqd wakes up vcpu thread
4) vcpu thread is scheduled
This extra context switch introduces unnecessary latency in the
LAPIC path for a KVM guest.
The solution:
Al
Against v3.14-rt branch of
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
The problem:
On -RT, an emulated LAPIC timer instance has the following path:
1) hard interrupt
2) ksoftirqd is scheduled
3) ksoftirqd wakes up vcpu thread
4) vcpu thread is scheduled
This extra con
On Tue, Jan 13, 2015 at 09:03:37PM +0100, Geert Uytterhoeven wrote:
> If asoc_simple_card_probe() fails, asoc_simple_card_unref() may be
> called before dev_set_drvdata(), causing a NULL pointer dereference in
> asoc_simple_card_unref():
Applied, thanks.
signature.asc
Description: Digital signat
On 01/14/2015 12:00 PM, Mark Rutland wrote:
> On Wed, Jan 14, 2015 at 12:47:00AM +, Jon Masters wrote:
>> Hi Folks,
>>
>> TLDR: I would like to consider the value of adding something like
>> "cluster_siblings" or similar in sysfs to describe ARM topology.
>>
>> A quick question on intended data
On Wed, Jan 14, 2015 at 04:34:25PM +0100, Michal Hocko wrote:
> On Thu 08-01-15 23:15:04, Johannes Weiner wrote:
> [...]
> > @@ -2353,6 +2353,22 @@ done_restock:
> > css_get_many(&memcg->css, batch);
> > if (batch > nr_pages)
> > refill_stock(memcg, batch - nr_pages);
> > + /*
On 01/13/2015 07:15 PM, Michael Ellerman wrote:
> On Tue, 2015-01-13 at 17:16 -0700, Shuah Khan wrote:
>> Please add a commit log.
>
> What does it need to say?
Explain the change the patch is making. Please see
Documentation/SubmittingPatches for details.
Looks like this patch is no longer nee
On a 32 bit ARM architecture with LPAE extension physical addresses
cannot fit into unsigned long variable.
This patch fixes the ioremap_page, __map_ioremap_pfn_caller,
__arm_ioremap and __arm_ioremap_exec functions.
Signed-off-by: Vitaly Andrianov
Acked-by: Murali Karicheri
---
arch/arm/inclu
On Mon, Jan 12, 2015 at 01:13:59PM +1000, Ken Wilson wrote:
> This commit changes spi-orion to provide setup, set_cs, and transfer_one
> functions instead of transfer_one_message. This allows chip select support
> for both native and GPIO chip selects to be added.
Applied, thanks.
signature.asc
Ping?
On Tue, Dec 30, 2014 at 05:52:28PM -0200, Marcelo Tosatti wrote:
>
> Commit "timers: do not raise softirq unconditionally", allows for timer
> wheel processing (__run_timers) to be delayed for long periods of time.
>
> The effect is that
>
> loops = jiffies - base->timer_jiffies
>
> Ca
On Wed, 14 Jan 2015 10:09:05 +0900
Namhyung Kim wrote:
> > >> +
> > >> +void __init trace_event_init(void)
> > >> +{
> > >> +event_trace_memsetup();
> > >> +init_ftrace_syscalls();
> > >> +event_trace_enable();
> > >> +}
> > >> +
> > >
> > > init_ftrace_syscalls() get ca
On Wed, Jan 14, 2015 at 04:31:44PM +0100, Stephan Mueller wrote:
> Am Mittwoch, 14. Januar 2015, 22:00:11 schrieb Herbert Xu:
>
> Hi Herbert,
>
> > On Wed, Jan 14, 2015 at 04:46:31AM -0500, Neil Horman wrote:
> > > On Wed, Jan 14, 2015 at 04:52:29AM +0100, Stephan Mueller wrote:
> > > > Hi,
> > >
Some devices might not implement config space access
(e.g. remoteproc used not to - before 3.9).
virtio/scsi needs config space access so make it
fail gracefully if not there.
Signed-off-by: Michael S. Tsirkin
---
drivers/scsi/virtio_scsi.c | 6 ++
1 file changed, 6 insertions(+)
diff --git
Changes since v2:
handling for devices without config space (e.g. rng)
reduce # of mappings for VQs
These patches seem to work fine on my virtio-1.0 qemu branch.
There haven't been any bugs since v2: just minor cleanups
and enhancements.
QEMU side is still undergoing polishing, but
Some devices might not implement config space access
(e.g. remoteproc used not to - before 3.9).
virtio/blk needs config space access so make it
fail gracefully if not there.
Signed-off-by: Michael S. Tsirkin
---
drivers/block/virtio_blk.c | 6 ++
1 file changed, 6 insertions(+)
diff --git
Some devices might not implement config space access
(e.g. remoteproc used not to - before 3.9).
virtio/net needs config space access so make it
fail gracefully if not there.
Signed-off-by: Michael S. Tsirkin
---
drivers/net/virtio_net.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/
Virtio drivers should map the part of the BAR they need, not necessarily
all of it.
Cc: Bjorn Helgaas
Cc: linux-...@vger.kernel.org
Acked-by: Arnd Bergmann
Signed-off-by: Michael S. Tsirkin
Signed-off-by: Rusty Russell
---
Bjorn, can you please ack this for merging through the virtio tree?
pci-iomap.c was (apparently, mistakenly) reintroduced as part of
commit 83c2dc15ce824450e7044b9f90cd529c25747ae0
MN10300: Handle cacheable PCI regions in pci_iomap()
probably as side-effect of forward-porting the patch
from an old kernel.
It's not really needed: the generic pci_iomap does the
Lightly tested against qemu.
One thing *not* implemented here is separate mappings
for descriptor/avail/used rings. That's nice to have,
will be done later after we have core support.
This also exposes the PCI layout to userspace, and
adds macros for PCI layout offsets:
QEMU wants it, so why not
Virtio 1.0 spec lists device config as optional.
Set get/set callbacks to NULL. Drivers can check that
and fail gracefully.
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/virtio_pci_modern.c | 21 +++--
1 file changed, 19 insertions(+), 2 deletions(-)
diff --git a/drivers/
From: Rusty Russell
QEMU wants it, so why not? Trust, but verify.
Signed-off-by: Rusty Russell
Signed-off-by: Michael S. Tsirkin
---
include/uapi/linux/virtio_pci.h| 30
drivers/virtio/virtio_pci_modern.c | 58 +-
2 files changed,
From: Rusty Russell
Based on patches by Michael S. Tsirkin , but I found it
hard to follow so changed to use structures which are more
self-documenting.
Signed-off-by: Rusty Russell
Signed-off-by: Michael S. Tsirkin
---
include/uapi/linux/virtio_pci.h | 62
We don't know the # of VQs that drivers are going to use so it's hard to
predict how much memory we'll need to map. However, the relevant
capability does give us an upper limit.
If that's below a page, we can reduce the number of required
mappings by mapping it all once ahead of the time.
Signed-o
Most of initialization is device-independent.
Let's move it to common.
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/virtio_pci_common.h | 5 +--
drivers/virtio/virtio_pci_common.c | 69 +-
drivers/virtio/virtio_pci_legacy.c | 76 --
Virtio drivers should map the part of the range they need, not
necessarily all of it.
To this end, support mapping ranges within BAR on s390.
Since multiple ranges can now be mapped within a BAR, we keep track of
the number of mappings created, and only clear out the mapping for a BAR
when this num
Some devices might not implement config space access
(e.g. remoteproc used not to - before 3.9).
virtio/9p needs config space access so make it
fail gracefully if not there.
Signed-off-by: Michael S. Tsirkin
---
net/9p/trans_virtio.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/net/
Some devices might not implement config space access
(e.g. remoteproc used not to - before 3.9).
virtio/console needs config space access so make it
fail gracefully if not there.
Signed-off-by: Michael S. Tsirkin
---
drivers/char/virtio_console.c | 6 ++
1 file changed, 6 insertions(+)
diff
Some devices might not implement config space access
(e.g. remoteproc used not to - before 3.9).
virtio/balloon needs config space access so make it
fail gracefully if not there.
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/virtio_balloon.c | 6 ++
1 file changed, 6 insertions(+)
di
virtio_pci does not depend on virtio_config:
let's not include it, users can pull it in as necessary.
Signed-off-by: Michael S. Tsirkin
---
include/uapi/linux/virtio_pci.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/uapi/linux/virtio_pci.h b/include/uapi/linux/vir
On 14/01/2015 18:12, Marcelo Tosatti wrote:
> Against v3.14-rt branch of
> git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
>
> The problem:
>
> On -RT, an emulated LAPIC timer instance has the following path:
>
> 1) hard interrupt
> 2) ksoftirqd is scheduled
> 3) ksoftirq
Hello, Arnd,
As you asked, here's a pull request.
This has been in linux-next apparently with no ill effects.
The following changes since commit 99975cc6ada0d5f2675e83abecae05aba5f437d2:
vhost/net: length miscalculation (2015-01-07 12:22:00 +0200)
are available in the git repository at:
git
On Wed, Jan 14, 2015 at 05:21:57PM +0100, Alexandre Belloni wrote:
> From: Boris Brezillon
>
> The driver is requesting clock by their global name (those declared in the
> clk_lookup list), but this only works with !CCF kernels.
>
> Now that all SoCs have moved to CCF, fix the driver to use loca
On Wed, Jan 14, 2015 at 05:21:58PM +0100, Alexandre Belloni wrote:
> From: Boris Brezillon
>
> Now that at91 system clocks forward set_rate request to their parent we
> can remove the uclk clock and directly call clk_set_rate on fclk.
>
> Signed-off-by: Boris Brezillon
Acked-by: Felipe Balbi
On Wed, Jan 14, 2015 at 05:22:00PM +0100, Alexandre Belloni wrote:
> From: Boris Brezillon
>
> Since non-DT board support has been removed from the at91 architecture we
> can safely remove non-DT handling code.
>
> Signed-off-by: Boris Brezillon
> ---
> drivers/usb/gadget/udc/Kconfig| 1 +
On Wed, Jan 14, 2015 at 05:22:02PM +0100, Alexandre Belloni wrote:
> From: Boris Brezillon
>
> cpu_is_at91xxx are a set of macros defined in mach/cpu.h and are here used
> to detect the SoC we are booting on.
> Use compatible string + a caps structure to replace those cpu_is_xxx tests.
>
> Remov
On Wed, Jan 14, 2015 at 05:22:01PM +0100, Alexandre Belloni wrote:
> From: Boris Brezillon
>
> Make use of devm_ functions to simplify probe and remove code.
>
> Signed-off-by: Boris Brezillon
Acked-by: Felipe Balbi
> ---
> drivers/usb/gadget/udc/at91_udc.c | 116
> +---
On Wed, Jan 14, 2015 at 05:22:04PM +0100, Alexandre Belloni wrote:
> From: Boris Brezillon
>
> Allocate udc structure instead of relying on the statically declared
> object.
>
> Signed-off-by: Boris Brezillon
Acked-by: Felipe Balbi
> ---
> drivers/usb/gadget/udc/at91_udc.c | 96
> +
On Wed, Jan 14, 2015 at 12:22:34PM -0500, Vitaly Andrianov wrote:
> On a 32 bit ARM architecture with LPAE extension physical addresses
> cannot fit into unsigned long variable.
>
> This patch fixes the ioremap_page, __map_ioremap_pfn_caller,
> __arm_ioremap and __arm_ioremap_exec functions.
This
On Wed, 14 Jan 2015 15:21:47 -0200
Marcelo Tosatti wrote:
>
> Ping?
>
Sorry, I've fallen behind since the holidays and still trying to catch
up. I'll try to look at this this week.
-- Steve
> On Tue, Dec 30, 2014 at 05:52:28PM -0200, Marcelo Tosatti wrote:
> >
> > Commit "timers: do not rai
On a 32 bit ARM architecture with LPAE extension physical addresses
cannot fit into unsigned long variable.
This patch fixes the ioremap_page function.
Signed-off-by: Vitaly Andrianov
Acked-by: Murali Karicheri
- Fixing the commit log and resending
---
arch/arm/include/asm/mach/map.h | 2 +-
On Wed, Jan 14, 2015 at 12:44:12PM -0500, Vitaly Andrianov wrote:
> On a 32 bit ARM architecture with LPAE extension physical addresses
> cannot fit into unsigned long variable.
>
> This patch fixes the ioremap_page function.
>
> Signed-off-by: Vitaly Andrianov
> Acked-by: Murali Karicheri
>
>
Hi Daniel,
Am Mittwoch, 14. Januar 2015, 17:10:24 schrieb Daniel Lezcano:
> On 01/13/2015 12:20 AM, Heiko Stübner wrote:
> >> +- clock-frequency: the frequency the timer is running
> >> +
> >> +Example:
> >> + timer: timer@ff81 {
> >> + compatible = "rockchip,rk3288-timer";
> >> +
2015-01-09 15:37+0100, Radim Krčmář:
> Lowest priority should take the task priority into account.
>
> SDM 10.6.2.4 Lowest Priority Delivery Mode.
> (Too long to quote; second and last paragraphs are relevant.)
>
> Before this patch, we strived to have the same amount of handled
> lowest-priority
Hi Greg,
Alright, 3 more fixes for v3.19-rc and my queue is finally clean.
All three fixes are rather obvious, two of them just took longer
to sort out all the stable rules details and I ended up having
to fix all that, otherwise we would miss the time frame.
Please condiser merging to your greg
On 01/14/2015 12:44 PM, Russell King - ARM Linux wrote:
On Wed, Jan 14, 2015 at 12:44:12PM -0500, Vitaly Andrianov wrote:
On a 32 bit ARM architecture with LPAE extension physical addresses
cannot fit into unsigned long variable.
This patch fixes the ioremap_page function.
Signed-off-by: Vit
On 01/13, Rik van Riel wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 01/13/2015 01:30 PM, Oleg Nesterov wrote:
> > On 01/13, Oleg Nesterov wrote:
> >>
> >> But yes, I think we need the per-cpu "in_kernel_fpu" and
> >> irq_fpu_usable() must die. Please look at
> >> http://marc.in
On Wed, 2015-01-14 at 11:57 +, Bogdan Purcareata wrote:
> The readback is necessary in order to handle PCI posted
> writes,
That is unclear.
> or when the MPIC is handling interrupts in a loop
> (ppc_md.get_irq).
I'm questioning this one as well -- if reading WHOAMI is sufficient to
sync wi
On Tue, Jan 13, 2015 at 6:43 PM, Chris Zhong wrote:
> After we set the GET_TIME bit, the rtc time couldn't be read immediately,
> we should wait up to 31.25 us, about one cycle of 32khz. Otherwise reading
> RTC time will return a old time. If clear the GET_TIME bit after setting,
> the time of i2c
On Wed, 14 Jan 2015 09:35:17 +1100
Michael Ellerman wrote:
> In commit 5f893b2639b2 "tracing: Move enabling tracepoints to just after
> rcu_init()", tracing was enabled earlier in boot.
>
> This broke tracing of the raw_syscall tracepoints from boot using the
> trace_event kernel parameter.
>
>
On Wed, Jan 14, 2015 at 05:48:54PM +0100, Jiri Slaby wrote:
> On 01/14/2015, 05:37 PM, Guenter Roeck wrote:
> > On Tue, Jan 13, 2015 at 11:22:40PM -0800, Greg Kroah-Hartman wrote:
> >> This is the start of the stable review cycle for the 3.14.29 release.
> >> There are 77 patches in this series, al
Hi Paul,
On Tue, Jan 13, 2015 at 09:45:27AM -0500, Paul Clements wrote:
> All,
>
> I've maintained the NBD driver since 2003, but alas, I no longer have
> the time and energy to continue maintaining it. If someone would like
> to take over, let me know.
Quite a long time of maintaining the drive
From: Ashish Sangwan
We have hit a race condition while parallely accessing device's uevent
and rmmoding device's driver. In dev_uevent() first dev->driver is checked if
present which becomes true but before calling add_uevent_var
dev->driver is set to NULL and driver is freed in __device_releas
On Wed, Jan 14, 2015 at 04:06:17PM +, One Thousand Gnomes wrote:
> and I think you effectively have the user usage covered here for such
> things. It much like GPIO pins - we can describe them but we can also
> declare they are not visible to the user.
A missing element in mainline is a kind
On Tue, Jan 13, 2015 at 4:16 PM, Mark Salyzyn wrote:
> A secured user-space accessible pstore object. Writes
> to /dev/pmsg0 are appended to the buffer, on reboot
> the persistent contents are available in
> /sys/fs/pstore/pmsg-ramoops-[ID].
>
> One possible use is syslogd, or other daemon, can
>
Hi,
Expect something tonight should the latest tests run okay. I needed to include
an EPROBE_DEFER to address the unavailibity of the pci driver needed in order to
request the lock during probe of the i2c device. This due to the lock now being
requested during probe because of the hang.
Dave
On
On 01/14/2015 12:12 PM, Marcelo Tosatti wrote:
> The problem:
>
> On -RT, an emulated LAPIC timer instances has the following path:
>
> 1) hard interrupt
> 2) ksoftirqd is scheduled
> 3) ksoftirqd wakes up vcpu thread
> 4) vcpu thread is scheduled
>
> This extra context switch introduces unneces
On 01/14/2015 12:12 PM, Marcelo Tosatti wrote:
> Since lapic timer handler only wakes up a simple waitqueue,
> it can be executed from hardirq context.
>
> Reduces average cyclictest latency by 3us.
>
> Signed-off-by: Marcelo Tosatti
Acked-by: Rik van Riel
--
To unsubscribe from this list: se
On Wed, Jan 14, 2015 at 06:51:56PM +0200, Kirill A. Shutemov wrote:
> Dave noticed that unprivileged process can allocate significant amount
> of memory -- >500 MiB on x86_64 -- and stay unnoticed by oom-killer and
> memory cgroup. The trick is to allocate a lot of PMD page tables. Linux
> kernel d
On Wed, Jan 14, 2015 at 8:51 AM, Matt Fleming wrote:
> On Wed, 31 Dec, at 06:37:39PM, Matt Fleming wrote:
>> On Wed, 17 Dec, at 08:54:56AM, Andy Lutomirski wrote:
>> > > As far as I know, the only way to have continuously functional interrupt
>> > > handling across a long mode transition is to ins
On Wed, Jan 14, 2015 at 04:07:53PM +0100, Lukasz Majewski wrote:
> Hi Eduardo,
>
> > On Mon, Dec 22, 2014 at 05:27:42PM +0100, Lukasz Majewski wrote:
> > > Odroid U3 fan can work without being registered as OF cooling device
> > > (with CONFIG_THERMAL_OF disabled).
> > > In this situation it can b
On Wed, Jan 14, 2015 at 08:38:03AM +, Stoidner, Christoph wrote:
>
> Hi Paul,
>
> > Two things to try:
> >
> > 1. alt-sysreq-t to get all tasks' stacks, or
>
> I am not able to do that since I am working on an embedded system which
> has no real tty, just a serial connected terminal.
On Wed, Jan 14, 2015 at 04:01:06PM +0100, Lukasz Majewski wrote:
> Hi Eduardo,
>
> > On Fri, Jan 02, 2015 at 02:54:28PM -0400, Eduardo Valentin wrote:
> > > On Mon, Dec 22, 2014 at 05:27:41PM +0100, Lukasz Majewski wrote:
> > > > Odroid U3 fan can work without being registered as OF cooling
> > >
On Wed, Jan 7, 2015 at 10:12 AM, John Stultz wrote:
> Hey Ingo, Thomas,
>
> Here are two mult overflow validation fixes from Sasha for
> tip/timers/urgent that I didn't manage to send out before the holidays.
>
> For v2 I've added the mili->micro fix Andy noticed.
>
> Let me know if you have any
On 14/01/2015 at 11:38:12 -0600, Felipe Balbi wrote :
> On Wed, Jan 14, 2015 at 05:22:00PM +0100, Alexandre Belloni wrote:
> > From: Boris Brezillon
> >
> > Since non-DT board support has been removed from the at91 architecture we
> > can safely remove non-DT handling code.
> >
> > Signed-off-by
On Wed, Jan 14, 2015 at 10:27:47AM -0800, Andy Lutomirski wrote:
> How are you manually triggering an MCE? I've been playing with some
> MCE stuff recently, but the only reasonably reliable way I know of to
> trigger an MCE is using WHEA, and I don't have a box with WHEA, and I
> assume your ASUS
On Wed, Jan 14, 2015 at 11:29:41AM +, Stefano Stabellini wrote:
> On Tue, 13 Jan 2015, Luis R. Rodriguez wrote:
> > On Mon, Dec 15, 2014 at 02:58:26PM +, Stefano Stabellini wrote:
> > > On Tue, 9 Dec 2014, Luis R. Rodriguez wrote:
> > > > From: "Luis R. Rodriguez"
> > > >
> > > > This let
On 01/11, r...@redhat.com wrote:
>
> If the next task still has its FPU state present in the FPU registers,
> there is no need to restore it from memory.
Another patch I can't understand...
> --- a/arch/x86/include/asm/fpu-internal.h
> +++ b/arch/x86/include/asm/fpu-internal.h
> @@ -435,13 +435,9
501 - 600 of 911 matches
Mail list logo
