Note: when allocating an index, in the error case,
where the just-allocated index has to be released,
the required locking around the index removal was
not present, so this conversion has the side effect
of adding locking for that error condition. This
should close a possible race condition that
Add support to create thermal zones based on the temperature sensors
provided by the SCP. The thermal zones can be defined using the
thermal DT bindings and should refer to the SCP sensor id to select
the sensor.
Signed-off-by: Punit Agrawal
Acked-by: Guenter Roeck
Cc: Eduardo Valentin
---
Create a driver to add support for SoC sensors exported by the System
Control Processor (SCP) via the System Control and Power Interface
(SCPI). The supported sensor types is one of voltage, temperature,
current, and power.
The sensor labels and values provided by the SCP are exported via the
Building with the attached random configuration file,
warning: (VIDEO_COBALT) selects VIDEO_ADV7511 which has unmet direct
dependencies (MEDIA_SUPPORT && VIDEO_V4L2 && I2C &&
VIDEO_V4L2_SUBDEV_API)
warning: (VIDEO_COBALT) selects VIDEO_ADV7604 which has unmet direct
dependencies (MEDIA_SUPPORT &&
ARM System Control Processor (SCP) provides an API to query and use
the sensors available in the system. Extend the SCPI driver to support
sensor messages.
Signed-off-by: Punit Agrawal
Cc: Sudeep Holla
---
drivers/firmware/arm_scpi.c | 60 +++
The SCP firmware on Juno provides access to SoC sensors via the
SCPI. Add the sensor nodes to the device tree to enable this support.
Signed-off-by: Punit Agrawal
Cc: Rob Herring
Cc: Mark Rutland
Cc: Liviu Dudau
Cc: Sudeep Holla
---
arch/arm64/boot/dts/arm/juno-base.dtsi | 5 +
1 file
The System Control Processor (SCP) provides access to SoC sensors via
the System Control and Power Interface (SCPI) Message Protocol. Add
bindings to allow probing of these sensors. Also support referencing
of the sensors for setting up thermal zones via the thermal DT
bindings.
Signed-off-by:
Signed-off-by: Lee Duncan
---
drivers/mfd/rtsx_pcr.c | 13 +++--
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/drivers/mfd/rtsx_pcr.c b/drivers/mfd/rtsx_pcr.c
index a66540a49079..8ddefb8c5e64 100644
--- a/drivers/mfd/rtsx_pcr.c
+++ b/drivers/mfd/rtsx_pcr.c
@@ -1191,15
Signed-off-by: Lee Duncan
---
drivers/dca/dca-sysfs.c | 19 ---
1 file changed, 4 insertions(+), 15 deletions(-)
diff --git a/drivers/dca/dca-sysfs.c b/drivers/dca/dca-sysfs.c
index 126cf295b198..8930707df295 100644
--- a/drivers/dca/dca-sysfs.c
+++ b/drivers/dca/dca-sysfs.c
@@
Hi,
This series adds support for SCPI based sensors for ARM development
platform. In addition to supporting sensors, when a temperature sensor
is discovered the driver registers the sensor with the thermal
framework.
The sensor patches here have been split out from a longer series
adding support
> Is this an actual problem? Write errors usually indicate that the
There are transaction systems that need to track errors at the level
of the individual IO. So yes we should guarantee that if a particular
sync failed an error is always returned.
-Andi
--
To unsubscribe from this list: send
On Thu, 2015-08-20 at 20:16 +0200, Juergen Groß wrote:
> On 08/18/2015 05:55 PM, Dario Faggioli wrote:
> > Hey everyone,
> >
> > So, as a followup of what we were discussing in this thread:
> >
> > [Xen-devel] PV-vNUMA issue: topology is misinterpreted by the guest
> >
Change log from v1:
o fix wrong pointer assignment
Chang log from v2:
o add one more missing call path: f2fs_encrypted_follow_link
>From 84574dd5c3e8ed9ca9fdfcbd251b354cdbc5ecab Mon Sep 17 00:00:00 2001
From: Jaegeuk Kim
Date: Thu, 3 Sep 2015 13:38:23 -0700
Subject: [PATCH 1/3] f2fs crypto:
Signed-off-by: Lee Duncan
---
drivers/scsi/sd.c | 20
1 file changed, 4 insertions(+), 16 deletions(-)
diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
index 3b2fcb4fada0..60b2ad918208 100644
--- a/drivers/scsi/sd.c
+++ b/drivers/scsi/sd.c
@@ -2948,15 +2948,7 @@ static
Hi,
On Tue, Sep 15, 2015 at 06:41:55PM +0200, Peter Senna Tschudin wrote:
> On Tue, Sep 15, 2015 at 4:33 PM, Felipe Balbi wrote:
> > On Mon, Sep 14, 2015 at 07:50:02PM +0200, Peter Senna Tschudin wrote:
> >> On Mon, Sep 14, 2015 at 5:01 PM, Felipe Balbi wrote:
> >> > On Sat, Sep 12, 2015 at
Signed-off-by: Lee Duncan
---
drivers/block/rsxx/core.c | 16 ++--
1 file changed, 2 insertions(+), 14 deletions(-)
diff --git a/drivers/block/rsxx/core.c b/drivers/block/rsxx/core.c
index d8b2488aaade..dd23a0e85040 100644
--- a/drivers/block/rsxx/core.c
+++
Signed-off-by: Lee Duncan
---
drivers/misc/tifm_core.c | 17 -
1 file changed, 4 insertions(+), 13 deletions(-)
diff --git a/drivers/misc/tifm_core.c b/drivers/misc/tifm_core.c
index a511b2a713b3..46385f828a8f 100644
--- a/drivers/misc/tifm_core.c
+++ b/drivers/misc/tifm_core.c
Signed-off-by: Lee Duncan
---
drivers/memstick/core/memstick.c | 19 ---
1 file changed, 4 insertions(+), 15 deletions(-)
diff --git a/drivers/memstick/core/memstick.c b/drivers/memstick/core/memstick.c
index a0547dbf9806..8f40a3d5108b 100644
---
Signed-off-by: Lee Duncan
---
drivers/base/soc.c | 17 +++--
1 file changed, 3 insertions(+), 14 deletions(-)
diff --git a/drivers/base/soc.c b/drivers/base/soc.c
index 39fca01c8fa1..cf70c3246123 100644
--- a/drivers/base/soc.c
+++ b/drivers/base/soc.c
@@ -122,18 +122,7 @@ struct
Signed-off-by: Lee Duncan
---
drivers/block/mtip32xx/mtip32xx.c | 22 --
1 file changed, 4 insertions(+), 18 deletions(-)
diff --git a/drivers/block/mtip32xx/mtip32xx.c
b/drivers/block/mtip32xx/mtip32xx.c
index 4a2ef09e6704..ccff4119b554 100644
---
On 15/09/2015 15:36, Christian Borntraeger wrote:
> I am wondering why the old code behaved in such fatal ways. Is there
> some interaction between waiting for a reschedule in the
> synchronize_sched writer and some fork code actually waiting for the
> read side to get the lock together with
On Tue, Sep 15, 2015 at 4:33 PM, Felipe Balbi wrote:
> On Mon, Sep 14, 2015 at 07:50:02PM +0200, Peter Senna Tschudin wrote:
>> On Mon, Sep 14, 2015 at 5:01 PM, Felipe Balbi wrote:
>> > On Sat, Sep 12, 2015 at 03:14:50PM +0200, Peter Senna Tschudin wrote:
>> >> >> Should these files be
Signed-off-by: Lee Duncan
---
drivers/md/dm.c | 22 +-
1 file changed, 5 insertions(+), 17 deletions(-)
diff --git a/drivers/md/dm.c b/drivers/md/dm.c
index f331d888e7f5..53d6895eb13d 100644
--- a/drivers/md/dm.c
+++ b/drivers/md/dm.c
@@ -2202,9 +2202,7 @@ static int
Signed-off-by: Lee Duncan
---
drivers/block/nvme-core.c | 14 ++
1 file changed, 2 insertions(+), 12 deletions(-)
diff --git a/drivers/block/nvme-core.c b/drivers/block/nvme-core.c
index d1d6141920d3..ab13833d4fde 100644
--- a/drivers/block/nvme-core.c
+++
This platform driver has a OF device ID table but the OF module
alias information is not created so module autoloading won't work.
Signed-off-by: Luis de Bethencourt
---
drivers/char/ipmi/ipmi_si_intf.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/char/ipmi/ipmi_si_intf.c
Signed-off-by: Lee Duncan
---
drivers/mmc/core/host.c | 14 --
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/drivers/mmc/core/host.c b/drivers/mmc/core/host.c
index 99a9c9011c50..5aa2330f074c 100644
--- a/drivers/mmc/core/host.c
+++ b/drivers/mmc/core/host.c
@@ -40,9
Signed-off-by: Lee Duncan
---
drivers/gpu/drm/virtio/virtgpu_vq.c | 15 ---
1 file changed, 4 insertions(+), 11 deletions(-)
diff --git a/drivers/gpu/drm/virtio/virtgpu_vq.c
b/drivers/gpu/drm/virtio/virtgpu_vq.c
index 1698669f4185..380947dad306 100644
---
Hi Paul,
On Tue, Aug 25, 2015 at 08:25:37PM -0400, Paul Gortmaker wrote:
> In commit f309d4443130bf814e991f836e919dca22df37ae ("platform_device:
> better support builtin boilerplate avoidance") we introduced the
> builtin_driver macro.
>
> Here we use that support and extend it to PCI driver
On 15/09/2015 18:44, Cornelia Huck wrote:
>> > Can you explain why? If there is any non-zero valid length, "wildcard
>> > length" (represented by zero) would also make sense.
> What is a wildcard match supposed to mean in this case? The datamatch
> field contains the queue index for the device
On Tue, Sep 15, 2015 at 10:30:39AM -0600, Jason Gunthorpe wrote:
> On Tue, Sep 15, 2015 at 01:09:56PM +0300, Jarkko Sakkinen wrote:
> > However, for MMIO address the hardware might abort the entire request
> > when trying to do a 64-bit read, which causes the CPU to fill the result
> > with 1's.
>
On Tue, 15 Sep 2015 18:29:49 +0200
Paolo Bonzini wrote:
> On 15/09/2015 18:13, Cornelia Huck wrote:
> > On Tue, 15 Sep 2015 17:07:55 +0200
> > Paolo Bonzini wrote:
> >
> >> On 15/09/2015 08:41, Jason Wang wrote:
> >>> +With KVM_CAP_FAST_MMIO, a zero length mmio eventfd is allowed for
> >>>
ping ;)
Andrew, should I re-send this patch? It was acked by Daniel and Dave
doesn't object.
Dave, I'll appreciate it if you ack it explicitly.
On 08/27, Oleg Nesterov wrote:
>
> It is hardly possible to enumerate all problems with block_all_signals()
> and unblock_all_signals(). Just for
This platform drivers have a OF device ID table but the OF module
alias information is not created so module autoloading won't work.
Signed-off-by: Luis de Bethencourt
---
drivers/char/hw_random/pasemi-rng.c | 1 +
drivers/char/hw_random/ppc4xx-rng.c | 1 +
2 files changed, 2 insertions(+)
Hello,
These patches add the missing MODULE_DEVICE_TABLE() for OF to export
the information so modules have the correct aliases built-in and
autoloading works correctly.
A longer explanation by Javier Canillas can be found here:
https://lkml.org/lkml/2015/7/30/519
Thanks,
Luis
Luis de
[Rather belatedly looping in linux-api]
On Tue, 15 Sep 2015 18:24:28 +0300
Alexander Shishkin wrote:
> Johannes Berg writes:
>
> > On Tue, 2015-09-15 at 17:15 +0300, Alexander Shishkin wrote:
> >>
> >> > It seems to me that current->ext_err_code needs to be cleared on
> >> > each system
On Tue, Sep 15, 2015 at 11:52:10AM -0400, Tejun Heo wrote:
> On Tue, Sep 15, 2015 at 05:45:52PM +0200, Luis de Bethencourt wrote:
> > This platform driver has a OF device ID table but the OF module
> > alias information is not created so module autoloading won't work.
> >
> > Signed-off-by: Luis
On 09/15/2015 05:49 PM, Arnd Bergmann wrote:
> The v4l2 event queue uses a 'struct timespec' to pass monotonic
> timestamps. This is not a problem by itself, but it breaks when user
> space redefines timespec to use 'long long' on 32-bit systems.
>
> To avoid that problem, we define our own
On 09/15/15 at 12:12pm, Steven Rostedt wrote:
> On Wed, 16 Sep 2015 00:00:46 +0800
> Minfei Huang wrote:
>
> > On 09/15/15 at 11:50am, Steven Rostedt wrote:
> > > On Tue, 15 Sep 2015 23:37:39 +0800
> > > Minfei Huang wrote:
> > >
> > >
> > > > I think the variant ftrace_update_time is not
On Tue, 2015-09-15 at 17:04 +0100, Punit Agrawal wrote:
> "Jon Medhurst (Tixy)" writes:
>
> > On Tue, 2015-09-15 at 10:37 +0100, Punit Agrawal wrote:
> >> "Jon Medhurst (Tixy)" writes:
> >>
> >> > On Mon, 2015-09-14 at 15:38 +0100, Punit Agrawal wrote:
> >> >> Mark Rutland writes:
> >> >>
>
Hi,
On Tue, Sep 15, 2015 at 06:15:25PM +0200, Krzysztof Opasiak wrote:
> >>>+ }
> >>>+
> >>>+ return ret;
> >>> }
> >>>
> >>
> >>Personally I don't like this convention. In my opinion usb_ep_disable() &
> >>usb_ep_enable() should fail if ep is already disabled/enabled. Then in
> >>function
This platform driver has a OF device ID table but the OF module
alias information is not created so module autoloading won't work.
This patch adds the missing MODULE_DEVICE_TABLE() for OF to export
that information so modules have the correct aliases built-in and
autoloading works correctly.
On Tue, Sep 15, 2015 at 01:09:56PM +0300, Jarkko Sakkinen wrote:
> However, for MMIO address the hardware might abort the entire request
> when trying to do a 64-bit read, which causes the CPU to fill the result
> with 1's.
Okay, yes, for iomem you can't rely on packed.
packed actually can mess
On Tue, Sep 15, 2015 at 08:34:48AM -0700, Paul E. McKenney wrote:
> On Tue, Sep 15, 2015 at 04:14:39PM +0200, Peter Zijlstra wrote:
> > On Tue, Sep 15, 2015 at 07:09:22AM -0700, Paul E. McKenney wrote:
> > > On Tue, Sep 15, 2015 at 02:48:00PM +0200, Peter Zijlstra wrote:
> > > > On Tue, Sep 15,
On 2015-07-31 16:04, Jan Kiszka wrote:
> On x86, page_fault_* tracepoints report userspace address via kernel
> symbols because all the per-cpu variable offsets are in kallsyms,
> occupying the lower address space. Fix this by skipping over absolute
> addresses while processing kallsyms.
>
>
On 15/09/2015 18:13, Cornelia Huck wrote:
> On Tue, 15 Sep 2015 17:07:55 +0200
> Paolo Bonzini wrote:
>
>> On 15/09/2015 08:41, Jason Wang wrote:
>>> +With KVM_CAP_FAST_MMIO, a zero length mmio eventfd is allowed for
>>> +kernel to ignore the length of guest write and get a possible faster
>>>
On 09/15/2015 07:22 AM, Jiri Slaby wrote:
This is the start of the stable review cycle for the 3.12.48 release.
There are 33 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.
Responses should be made by
On 09/15/2015 05:49 PM, Arnd Bergmann wrote:
> The v4l2 API uses a 'struct timeval' to communicate time stamps to user
> space. This is broken on 32-bit architectures as soon as we have a C library
> that defines time_t as 64 bit, which then changes the structure layout of
> struct v4l2_buffer.
>
On 15/09/15 14:45, Peter Zijlstra wrote:
> On Mon, Sep 14, 2015 at 04:57:35PM +0100, Juri Lelli wrote:
>> On 04/09/15 14:27, Juri Lelli wrote:
>>> So, just to recall what we discussed at LPC (I have Mike's slides
>>> at hand :-)). It seems that key points are:
>>>
>>> 1- we agreed that locking in
On Fri, Sep 04, 2015 at 04:52:39PM +0530, Sudip Mukherjee wrote:
> DM_PARAMS_KMALLOC and DM_PARAMS_VMALLOC should never be set together in
> param_flags. We are setting these flags while allocating so we know that
> there is almost no chance of having these two set together but still we
> can have
On 09/15/2015 05:43 PM, Felipe Balbi wrote:
On Tue, Sep 15, 2015 at 05:37:27PM +0200, Krzysztof Opasiak wrote:
Hello,
On 09/15/2015 04:26 PM, Robert Baldyga wrote:
This patch introduces 'enabled' flag in struct usb_ep, and modifies
usb_ep_enable() and usb_ep_disable() functions to
On Tue, 15 Sep 2015 17:07:55 +0200
Paolo Bonzini wrote:
> On 15/09/2015 08:41, Jason Wang wrote:
> > +With KVM_CAP_FAST_MMIO, a zero length mmio eventfd is allowed for
> > +kernel to ignore the length of guest write and get a possible faster
> > +response. Note the speedup may only work on some
As much as we'd like to live in a world where RELEASE -> ACQUIRE is
always cheaply ordered and can be used to construct UNLOCK -> LOCK
definitions with similar guarantees, the grim reality is that this isn't
even possible on x86 (thanks to Paul for bringing us crashing down to
Earth).
This patch
On Wed, 16 Sep 2015 00:00:46 +0800
Minfei Huang wrote:
> On 09/15/15 at 11:50am, Steven Rostedt wrote:
> > On Tue, 15 Sep 2015 23:37:39 +0800
> > Minfei Huang wrote:
> >
> >
> > > I think the variant ftrace_update_time is not used any more. Previously,
> > > it is used to print the time how
On 09/15/2015 08:22 AM, Jiri Slaby wrote:
> This is the start of the stable review cycle for the 3.12.48 release.
> There are 33 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.
>
> Responses should
On Fri, Sep 11, 2015 at 03:01:14PM -0400, Alan Stern wrote:
> On Fri, 11 Sep 2015, Thierry Reding wrote:
>
> > On Fri, Sep 11, 2015 at 12:08:02AM +0200, Rafael J. Wysocki wrote:
> > > On Thursday, September 10, 2015 12:19:03 PM Thierry Reding wrote:
> > > > From: Thierry Reding
> > > >
> > > >
On Fri, Aug 21, 2015 at 06:51:25PM +0900, Ethan Zhao wrote:
> After commit 4449f079722c ("PCI: Calculate maximum number of buses
> required for VFs"),the initial value of NumVFs register was set to
> non-zero after sriov_init() and no VFs was enabled in device driver.
> this changed the behaviour
Hi Andy,
On Mon, Sep 14, 2015 at 10:52:46AM -0700, Andy Lutomirski wrote:
>
> I'm not sure I entirely like this solution...
Ok. Since we also aren't going to do all the eBPF stuff now, how about
something that looks like this:
struct seccomp_layer {
unsigned int size;
unsigned int type; /*
"Jon Medhurst (Tixy)" writes:
> On Tue, 2015-09-15 at 10:37 +0100, Punit Agrawal wrote:
>> "Jon Medhurst (Tixy)" writes:
>>
>> > On Mon, 2015-09-14 at 15:38 +0100, Punit Agrawal wrote:
>> >> Mark Rutland writes:
>> >>
> [...]
>> >> The way the SCP interface is defined, the sensor identifiers
On 15.09.2015 18:17, Stéphane Graber wrote:
On Tue, Sep 15, 2015 at 06:01:38PM +0300, Konstantin Khlebnikov wrote:
On 15.09.2015 17:27, Eric W. Biederman wrote:
Konstantin Khlebnikov writes:
pid_t getvpid(pid_t pid, pid_t source, pid_t target);
This syscall converts pid from one pid-ns
Hi,
On Tue, Sep 15, 2015 at 05:57:53PM +0200, Robert Baldyga wrote:
> On 09/15/2015 05:43 PM, Felipe Balbi wrote:
> > On Tue, Sep 15, 2015 at 05:37:27PM +0200, Krzysztof Opasiak wrote:
> >> Hello,
> >>
> >> On 09/15/2015 04:26 PM, Robert Baldyga wrote:
> >>> This patch introduces 'enabled' flag
On 09/15/15 at 11:50am, Steven Rostedt wrote:
> On Tue, 15 Sep 2015 23:37:39 +0800
> Minfei Huang wrote:
>
>
> > I think the variant ftrace_update_time is not used any more. Previously,
> > it is used to print the time how long ftrace will spend to update the
> > code in fucntion ftraced.
>
On 09/15/2015 05:43 PM, Felipe Balbi wrote:
> On Tue, Sep 15, 2015 at 05:37:27PM +0200, Krzysztof Opasiak wrote:
>> Hello,
>>
>> On 09/15/2015 04:26 PM, Robert Baldyga wrote:
>>> This patch introduces 'enabled' flag in struct usb_ep, and modifies
>>> usb_ep_enable() and usb_ep_disable() functions
On 09/11/2015 08:44 AM, Peng Fan wrote:
> Check input parameter 'name' for __of_find_property. If name is NULL,
> of_prop_cmp->strcasecmp may trigger panic.
Arguably that could be a feature. Do you have a usecase where name being
NULL is valid and panicking is a problem?
Rob
>
> Signed-off-by:
This platform driver has a OF device ID table but the OF module
alias information is not created so module autoloading won't work.
Signed-off-by: Luis de Bethencourt
---
Hello,
This patch adds the missing MODULE_DEVICE_TABLE() for OF to export
that information so modules have the correct
The dvb demuxer code uses a 'struct timespec' to pass a timeout
as absolute time. This will cause problems on 32-bit architectures
in 2038 when time_t overflows, and it is racy with a concurrent
settimeofday() call.
This patch changes the code to use ktime_get() instead, using
the monotonic time
Commit-ID: 12e14066f4835f5ee1ca795f0309415b54c067a9
Gitweb: http://git.kernel.org/tip/12e14066f4835f5ee1ca795f0309415b54c067a9
Author: Marc Zyngier
AuthorDate: Sun, 13 Sep 2015 12:14:31 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 15 Sep 2015 17:06:29 +0200
irqchip/GIC: Add
On Sat, Sep 12, 2015 at 12:38:19AM +0200, Rafael J. Wysocki wrote:
> On Friday, September 11, 2015 02:03:46 PM Thierry Reding wrote:
> > On Fri, Sep 11, 2015 at 12:08:02AM +0200, Rafael J. Wysocki wrote:
> > > On Thursday, September 10, 2015 12:19:03 PM Thierry Reding wrote:
> > > > From: Thierry
The v4l2 event queue uses a 'struct timespec' to pass monotonic
timestamps. This is not a problem by itself, but it breaks when user
space redefines timespec to use 'long long' on 32-bit systems.
To avoid that problem, we define our own replacement for timespec here,
using 'long' tv_sec and
'struct video_event' is used for the VIDEO_GET_EVENT ioctl, implemented
by drivers/media/pci/ivtv/ivtv-ioctl.c and
drivers/media/pci/ttpci/av7110_av.c. The structure contains a 'time_t',
which will be redefined in the future to be 64-bit wide, causing an
incompatible ABI change for this ioctl.
As
On Tue, Sep 15, 2015 at 05:45:52PM +0200, Luis de Bethencourt wrote:
> This platform driver has a OF device ID table but the OF module
> alias information is not created so module autoloading won't work.
>
> Signed-off-by: Luis de Bethencourt
> ---
>
> Hello,
>
> This patch adds the missing
The systime function uses struct timespec, which we want to stop
using in the kernel because it overflows in 2038. Fortunately,
this use in dibx000_common is in a function that is never called,
so we can just remove it.
Signed-off-by: Arnd Bergmann
---
The v4l2 API uses a 'struct timeval' to communicate time stamps to user
space. This is broken on 32-bit architectures as soon as we have a C library
that defines time_t as 64 bit, which then changes the structure layout of
struct v4l2_buffer.
Fortunately, almost all v4l2 drivers use monotonic
Commit-ID: 157add60cb35913b8a848a3d7e6456b8ed134796
Gitweb: http://git.kernel.org/tip/157add60cb35913b8a848a3d7e6456b8ed134796
Author: Pavel Fedin
AuthorDate: Sun, 13 Sep 2015 12:14:33 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 15 Sep 2015 17:06:29 +0200
irqchip/GICv2m: Fix
Commit-ID: 769b5cf78e6c653c2f513649ee6c4e7a06723872
Gitweb: http://git.kernel.org/tip/769b5cf78e6c653c2f513649ee6c4e7a06723872
Author: Geert Uytterhoeven
AuthorDate: Wed, 9 Sep 2015 13:42:54 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 15 Sep 2015 17:06:29 +0200
Commit-ID: f4e209cdc7a00f934007f40cf885471799073b0d
Gitweb: http://git.kernel.org/tip/f4e209cdc7a00f934007f40cf885471799073b0d
Author: Geert Uytterhoeven
AuthorDate: Tue, 8 Sep 2015 19:00:35 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 15 Sep 2015 17:06:29 +0200
Commit-ID: 6584d84c3e504c76ad291cc2e381bbeed59798ab
Gitweb: http://git.kernel.org/tip/6584d84c3e504c76ad291cc2e381bbeed59798ab
Author: Huang Shijie
AuthorDate: Tue, 1 Sep 2015 10:35:50 +0800
Committer: Thomas Gleixner
CommitDate: Tue, 15 Sep 2015 17:06:30 +0200
genirq: Update the
Hi everyone,
This is a conversion of all subsystem-wide v4l2 code to avoid the
use of types based on time_t. The first five patches should all
be harmless and obvious, so they can get applied for 4.3 after
normal review.
The last two patches are marked RFC for now because their possible
impact
This is a preparation for a change to the type of v4l2 timestamps.
v4l2_get_timestamp() is a helper function that reads the monotonic
time and stores it into a 'struct timeval'. Multiple drivers implement
the same thing themselves for historic reasons.
Changing them all to use
On Tue, 15 Sep 2015 23:37:39 +0800
Minfei Huang wrote:
> I think the variant ftrace_update_time is not used any more. Previously,
> it is used to print the time how long ftrace will spend to update the
> code in fucntion ftraced.
Yes, I know what it measures. It's been on my todo list to
Commit-ID: 4cd7863ecb90010533c178fba6ecc84d5529b402
Gitweb: http://git.kernel.org/tip/4cd7863ecb90010533c178fba6ecc84d5529b402
Author: Geert Uytterhoeven
AuthorDate: Tue, 8 Sep 2015 19:00:36 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 15 Sep 2015 17:06:29 +0200
From: "Suzuki K. Poulose"
Move the kernel pagetable (both swapper and idmap) definitions
from the generic asm/page.h to a new file, asm/kernel-pgtable.h.
This is mostly a cosmetic change, to clean up the asm/page.h to
get rid of the arch specific details which are not needed by the
generic
From: "Suzuki K. Poulose"
We use section maps with 4K page size to create the swapper/idmaps.
So far we have used !64K or 4K checks to handle the case where we
use the section maps.
This patch adds a new symbol, ARM64_SWAPPER_USES_SECTION_MAPS, to
handle cases where we use section maps, instead
Commit-ID: 5a9a8915cb615521b17d70a4342187eae60b
Gitweb: http://git.kernel.org/tip/5a9a8915cb615521b17d70a4342187eae60b
Author: Marc Zyngier
AuthorDate: Sun, 13 Sep 2015 12:14:32 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 15 Sep 2015 17:06:29 +0200
irqchip/gic-v3-its:
On Tue, Sep 15, 2015 at 01:28:13PM +0300, Kirill A. Shutemov wrote:
> Hugh has pointed that compound_head() call can be unsafe in some
> context. There's one example:
>
> CPU0CPU1
>
> isolate_migratepages_block()
> page_count()
> compound_head()
>
Commit-ID: e4084a16bbe07957811c75dfb7c9bf25c5862ba0
Gitweb: http://git.kernel.org/tip/e4084a16bbe07957811c75dfb7c9bf25c5862ba0
Author: Marc Zyngier
AuthorDate: Sun, 13 Sep 2015 13:37:03 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 15 Sep 2015 17:06:29 +0200
platform-msi: Do not
From: "Suzuki K. Poulose"
Now that we can calculate the number of levels required for
mapping a va width, reserve exact number of pages that would
be required to cover the idmap. The idmap should be able to handle
the maximum physical address size supported.
Cc: Ard Biesheuvel
Cc: Mark Rutland
On 09/15/2015 04:26 PM, Robert Baldyga wrote:
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of
On 09/09/2015 08:05, Xiao Guangrong wrote:
> Unify the update in vmx_cpuid_update()
>
> Signed-off-by: Xiao Guangrong
What if we instead start fresh from vmx_secondary_exec_control, like this:
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 4504cbc1b287..98c4d3f1653a 100644
---
From: "Suzuki K. Poulose"
{V}TCR_EL2_TG0 is a 2bit wide field, where:
00 - 4K
01 - 64K
10 - 16K
But we use only 1 bit, which has worked well so far since
we never cared about 16K. Fix it for 16K support.
Cc: Catalin Marinas
Cc: Will Deacon
Cc: Marc Zyngier
Cc: Christoffer Dall
Cc:
From: "Suzuki K. Poulose"
Encountered the following BUG() with 4.3-rc1 on a fast model
for arm64 with NFS root filesystem.
[ cut here ]
kernel BUG at fs/inode.c:1493!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
Modules linked in:
CPU: 2 PID: 1 Comm: swapper/0 Not
From: "Suzuki K. Poulose"
Introduce helpers for finding the number of page table
levels required for a given VA width, shift for a particular
page table level.
Convert the existing users to the new helpers. More users
to follow.
Cc: Ard Biesheuvel
Cc: Mark Rutland
Cc: Catalin Marinas
Cc:
Commit-ID: da92b4eb7e2ec9866f14a0c8f453788e8052dee7
Gitweb: http://git.kernel.org/tip/da92b4eb7e2ec9866f14a0c8f453788e8052dee7
Author: Jiang Liu
AuthorDate: Mon, 1 Jun 2015 16:05:33 +0800
Committer: Thomas Gleixner
CommitDate: Tue, 15 Sep 2015 17:06:28 +0200
powerpc, irq: Use access
The exynos4 fimc capture driver claims to use monotonic
timestamps but calls ktime_get_real_ts(). This is both
an incorrect API use, and a bad idea because of the y2038
problem and the fact that the wall clock time is not reliable
for timestamps across suspend or settimeofday().
This changes the
From: "Suzuki K. Poulose"
Ensure that the selected page size is supported by the
CPU(s).
Cc: Mark Rutland
Cc: Catalin Marinas
Cc: Will Deacon
Signed-off-by: Suzuki K. Poulose
Reviewed-by: Ard Biesheuvel
Tested-by: Ard Biesheuvel
---
arch/arm64/include/asm/sysreg.h |6 ++
Commit-ID: b1370658804510f6a1c0517a8ff1c9534d371edd
Gitweb: http://git.kernel.org/tip/b1370658804510f6a1c0517a8ff1c9534d371edd
Author: Geert Uytterhoeven
AuthorDate: Wed, 9 Sep 2015 13:42:53 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 15 Sep 2015 17:06:29 +0200
From: "Suzuki K. Poulose"
This series enables the 16K page size support on Linux for arm64.
Adds support for 48bit VA(4 level), 47bit VA(3 level) and
36bit VA(2 level) with 16K. 16K was a late addition to the architecture
and is not implemented by all CPUs. Added a check to ensure the
selected
This platform driver has a OF device ID table but the OF module
alias information is not created so module autoloading won't work.
Signed-off-by: Luis de Bethencourt
---
Hello,
This patch adds the missing MODULE_DEVICE_TABLE() for OF to export
that information so modules have the correct
* Felipe Balbi [150914 14:28]:
> On Sat, Sep 12, 2015 at 10:45:51AM -0700, Dmitry Torokhov wrote:
> > Now that the driver respects IRQ trigger settings from device tree, let's
> > fix them up in individual DTSes (note that the driver is still compatible
> > with older DTSes).
> >
> >
From: "Suzuki K. Poulose"
At the moment, we only support maximum of 3-level page table for
swapper. With 48bit VA, 64K has only 3 levels and 4K uses section
mapping. Add support for 4-level page table for swapper, needed
by 16K pages.
Cc: Ard Biesheuvel
Cc: Mark Rutland
Cc: Catalin Marinas
From: "Suzuki K. Poulose"
Update the help text for ARM64_64K_PAGES to reflect the reality
about AArch32 support.
Cc: Mark Rutland
Cc: Catalin Marinas
Cc: Will Deacon
Signed-off-by: Suzuki K. Poulose
Reviewed-by: Ard Biesheuvel
Tested-by: Ard Biesheuvel
---
arch/arm64/Kconfig |4 ++--
301 - 400 of 2190 matches
Mail list logo
