Since hisi_sas_itct format is different between v1
and v2 hw, give more general names for some fields.
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas.h | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/drivers/scsi/hisi_sas/hisi_sas.h b/drivers/scsi/
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 92 ++
1 file changed, 92 insertions(+)
diff --git a/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
b/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
index 2c6a753..8b51acf 100644
--- a/drivers/scsi/hisi_sas/h
These patches add support for the Cooling Method feature found in most
Toshiba laptops, allowing userspace to control the desired cooling method,
which are the following:
0 - Maximum Performance
1 - Peformance
2 - Battery Optimized
The Cooling Method feature basically controls the speed of the sys
So it appears it broke somewhere between v4.0 and v4.1, as the v4.0 install
displays:
16,244,802,268 instructions ( +- 23.01% )
2.108676769 seconds time elapsed
( +- 0.86% )
[a few minutes later]
Bisected it down to:
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 421 +
1 file changed, 421 insertions(+)
diff --git a/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
b/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
index cea0b36..481aff9 100644
--- a/drivers/scsi/hisi_sas/
This patchset introduces support for the HiSi SAS v2 hw.
The major difference between v1 and v2 hw is support
for SATA/STP.
Known limitation:
- We cannot connect a SATA disk through an expander
which enables DMA setup auto-activate, as our controller
does not support this feature. Directly con
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 49 ++
1 file changed, 49 insertions(+)
diff --git a/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
b/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
index a7b83bd..35ce7b6 100644
--- a/drivers/scsi/hisi_sas/h
Since the error record structure is different for
v2 hw, make hisi_sas_err_record opaque and add
hisi_sas_err_record_v1.
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas.h | 12 +---
drivers/scsi/hisi_sas/hisi_sas_v1_hw.c | 17 +++--
2 files changed, 16 inse
Also include slot_complete_v2_hw handler
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 190 +
1 file changed, 190 insertions(+)
diff --git a/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
b/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
index c4a887c..0
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 237 +
1 file changed, 237 insertions(+)
diff --git a/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
b/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
index 0f7f2af..31e4fdc 100644
--- a/drivers/scsi/hisi_sas/
On 01/23/2016 07:05 AM, mika.pentt...@nextfour.com wrote:
From: Mika Penttilä
Not related to this oops, but while at it, fix incorrect bounds check.
Signed-off-by: Mika Penttilä mika.pentt...@nextfour.com
---
arch/arm/mm/pageattr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
dif
From: Colin Ian King
_show_port_gid_attr performs a va_end on some unused va_list args.
Clean this up by removing the args completely.
Fixes: 470be516a226e8 ("IB/core: Add gid attributes to sysfs")
Signed-off-by: Colin Ian King
---
drivers/infiniband/core/sysfs.c | 2 --
1 file changed, 2 dele
This adds helpers for each of the four currently-specified INVPCID
modes.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/tlbflush.h | 41 +
1 file changed, 41 insertions(+)
diff --git a/arch/x86/include/asm/tlbflush.h b/arch/x86/include/asm/tlbfl
Ingo, before applying this, please apply these two KASAN fixes:
http://lkml.kernel.org/g/1452516679-32040-2-git-send-email-aryabi...@virtuozzo.com
http://lkml.kernel.org/g/1452516679-32040-3-git-send-email-aryabi...@virtuozzo.com
Without those fixes, this series will trigger a KASAN bug.
This is
On my Skylake laptop, INVPCID function 2 (flush absolutely
everything) takes about 376ns, whereas saving flags, twiddling
CR4.PGE to flush global mappings, and restoring flags takes about
539ns.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/tlbflush.h | 9 +
1 file changed, 9 i
> Are you interested in a bit of software optimisation for the implementation
> of the function "xc_load_fw_and_init_tuner"?
To be clear, absolutely none of the code in question is performance
sensitive (i.e. saving a couple of extra CPU cycles has no value in
this case). Hence given that I'm ass
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 171 +
1 file changed, 171 insertions(+)
diff --git a/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
b/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
index 1990d65..a7b83bd 100644
--- a/drivers/scsi/hisi_sas/
Add the dt bindings for HiSi SAS controller v2 HW.
The main difference in the controller from dt perspective
is interrupts. The v2 controller does not have dedicated
fatal and broadcast interrupts - they are multiplexed on
the channel interrupt.
Each SAS v2 controller can issue upto 64 commands
(
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/hisi_sas/hisi_sas.h b/drivers/scsi/hisi_sas/hisi_sas.h
index f00b55b..9f08c0c 100644
--- a/drivers/scsi/hisi_sas/hisi_sas.h
+++ b/drivers/scsi/hisi_sas/h
This also includes broadcast handler. Unlike v1 hw,
broadcast does not have its own dedicated interrupt.
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 79 ++
1 file changed, 79 insertions(+)
diff --git a/drivers/scsi/hisi_sas/hisi_sas_v2_
* Mel Gorman wrote:
> On Mon, Jan 25, 2016 at 04:46:35PM +0100, Ingo Molnar wrote:
> > > Of course, it'll be our luck that tracking the data for these
> > > tracepoints is the most expensive part of schedstats ...
> > >
> > > Ingo?
> >
> > IIRC it needed only a small subset of schedstats to ma
Relocate DEV_IS_EXPANDER to hisi_sas.h as
it will be required for v2 hw support.
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas.h | 4
drivers/scsi/hisi_sas/hisi_sas_main.c | 4
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/scsi/hisi_sas/hisi
On Mon, Jan 25, 2016 at 06:38:06PM +, Colin King wrote:
> From: Colin Ian King
>
> _show_port_gid_attr performs a va_end on some unused va_list args.
> Clean this up by removing the args completely.
>
> Fixes: 470be516a226e8 ("IB/core: Add gid attributes to sysfs")
> Signed-off-by: Colin Ian
Since v2 hardware permits different numbers of
commands to v1, set this as configurable in
hisi_sas_hw.
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas.h | 2 +-
drivers/scsi/hisi_sas/hisi_sas_main.c | 24
drivers/scsi/hisi_sas/hisi_sas_v1_hw.c | 3
Since v2 hw only supports 2048 itct entries,
as opposed to 4096 for v1 hw, set the max itct
entries to the lower of the two.
It is not anticipated that any device with v1
will ever require to connect > 2048 devices.
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas.h | 2 +-
1 file c
Include code to prep ssp frame and deliver
to hardware.
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 185 +
1 file changed, 185 insertions(+)
diff --git a/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
b/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
i
On 01/23/2016 07:05 AM, mika.pentt...@nextfour.com wrote:
From: Mika Penttilä
This makes set_memory_xx() consistent with x86.
Signed-off-by: Mika Penttilä mika.pentt...@nextfour.com
---
arch/arm/mm/pageattr.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/mm/pageattr.c b/a
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 71 ++
1 file changed, 71 insertions(+)
diff --git a/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
b/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
index ab6ea25..2c6a753 100644
--- a/drivers/scsi/hisi_sas/h
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 100 +
1 file changed, 100 insertions(+)
diff --git a/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
b/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
index 5af2069..c4a887c 100644
--- a/drivers/scsi/hisi_sas/
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas.h | 4 +
drivers/scsi/hisi_sas/hisi_sas_main.c | 8 ++
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 162 +
3 files changed, 174 insertions(+)
diff --git a/drivers/scsi/hisi_sas/hisi_sas.h b/driver
Add code to initialise the hardware.
Support is also added to deal with the
"am-max-transmissions" (amt) limitation in hip06
controller #1. This is how many connection requests
we can send on the system bus before waiting for a
response.
Due to chip bus design, controller #1 is limited to
32 amt,
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 23 +++
1 file changed, 23 insertions(+)
diff --git a/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
b/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
index 481aff9..58e1956 100644
--- a/drivers/scsi/hisi_sas/hisi_sas_v2_
On Monday 25 Jan 2016 16:36:40 John Crispin wrote:
> Hi,
>
> On 25/01/2016 13:41, Lee Jones wrote:
> > Please honour the subject format of the subsystem you are contributing
> > to.
> >
> > `git log --oneline -- $subsystem` gives you this.
> >
> > On Mon, 25 Jan 2016, John Crispin wrote:
> >> Si
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 40 ++
1 file changed, 40 insertions(+)
diff --git a/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
b/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
index da9c375..6f05333 100644
--- a/drivers/scsi/hisi_sas/h
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 49 ++
1 file changed, 49 insertions(+)
diff --git a/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
b/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
index 6f05333..1990d65 100644
--- a/drivers/scsi/hisi_sas/h
Just add enough to build and init the module.
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/Makefile | 2 +-
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 48 ++
2 files changed, 49 insertions(+), 1 deletion(-)
create mode 100644 drivers/scsi/hisi_sas/h
On 01/23/2016 07:05 AM, mika.pentt...@nextfour.com wrote:
From: Mika Penttilä
This makes set_memory_xx() consistent with x86.
Signed-off-by: Mika Penttilä mika.pentt...@nextfour.com
---
arch/arm64/mm/pageattr.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/mm/pageattr.c
Hello,
On Mon, Jan 25, 2016 at 04:44:50PM +0100, Petr Mladek wrote:
> timer_pending() checks whether the list of callbacks is empty.
> Each callback is removed from the list before it is called,
> see call_timer_fn() in __run_timers().
>
> Sometimes we need to make sure that the callback has fini
From: Martin Roth
Date: Sun, 24 Jan 2016 00:56:19 +0200
> This is an additional patch to the one already submitted recently.
> The previous patch was not complete, and the FCC port lock-up scenario
> has been reproduced in lab.
> I had an opportunity to check the current patch in lab and the FCC
On Sun, Jan 24, 2016 at 1:28 AM, Borislav Petkov wrote:
> From: Borislav Petkov
>
> ... and simplify and speed up a tad.
This function is only used when initializing CPUs, so the "tad" is
very small indeed.
If there are systems for which some cpus support rdtscp and some
don't, then this patch
On Mon, Jan 25, 2016 at 05:38:30PM +0100, Mario Kleiner wrote:
> Readding Daniel, which somehow got dropped from the cc.
>
> On 01/25/2016 03:53 PM, Ville Syrjälä wrote:
> >On Mon, Jan 25, 2016 at 02:44:53PM +0100, Mario Kleiner wrote:
> >>
> >>
> >>On 01/25/2016 02:23 PM, Ville Syrjälä wrote:
> >
Hi,
On Mon, Jan 25, 2016 at 9:08 AM, Thierry Reding
wrote:
> I really don't understand this design decision. I presume that the PWM
> controlling this system-critical logic is driven by the SoC? So if the
> regulator is system-critical, doesn't that make it a chicken and egg
> problem? How can th
On Sun, Jan 24, 2016 at 2:22 PM, Andy Lutomirski wrote:
> On Fri, Jan 22, 2016 at 7:02 PM, Eric W. Biederman
> wrote:
>> Kees Cook writes:
>>
>>> There continues to be unexpected side-effects and security exposures
>>> via CLONE_NEWUSER. For many end-users running distro kernels with
>>> CONFIG_
From: Sudip Mukherjee
Date: Mon, 25 Jan 2016 11:43:09 +0530
> We are getting build warning about:
> macb.c:2889:13: warning: 'tx_clk' may be used uninitialized in this function
> macb.c:2888:11: warning: 'hclk' may be used uninitialized in this function
>
> In reality they are not used uninitial
On Sun, Jan 24, 2016 at 2:20 PM, Andy Lutomirski wrote:
> On Sun, Jan 24, 2016 at 12:59 PM, Kees Cook wrote:
>> On Fri, Jan 22, 2016 at 4:59 PM, Ben Hutchings wrote:
>>> On Fri, 2016-01-22 at 15:00 -0800, Kees Cook wrote:
On Fri, Jan 22, 2016 at 2:55 PM, Robert Święcki wrote:
> 2016-0
From: Haiyang Zhang
Date: Mon, 25 Jan 2016 09:49:31 -0800
> Since eliminating send_completion_tid from struct hv_netvsc_packet, we
> haven't add proper book keeping for the skb of the batched packet. This
> patch fixes this issue and allows the previous skb is properly freed.
> Otherwise, a panic
On Mon, Jan 25, 2016 at 6:19 AM, Ard Biesheuvel
wrote:
> This v4 of my kallsyms base relative implementation is now a 3 piece series,
> since it caused some problems due to the way absolute symbols are handled
> by the absolute per cpu code. As it turns out, that code was probably wrong
> in the s
On Mon, Jan 25, 2016 at 10:51 AM, Kees Cook wrote:
> On Sun, Jan 24, 2016 at 2:22 PM, Andy Lutomirski wrote:
>> On Fri, Jan 22, 2016 at 7:02 PM, Eric W. Biederman
>> wrote:
>>> Kees Cook writes:
>>>
There continues to be unexpected side-effects and security exposures
via CLONE_NEWUSER
From: Vitaly Kuznetsov
Date: Mon, 25 Jan 2016 16:00:41 +0100
> Recent changes to 'struct flow_keys' (e.g commit d34af823ff40 ("net: Add
> VLAN ID to flow_keys")) introduced a performance regression in netvsc
> driver. Is problem is, however, not the above mentioned commit but the
> fact that netv
From: Sudip Mukherjee
Date: Mon, 25 Jan 2016 13:05:20 +0530
> We are getting many build warnings about:
> 'bar_start' may be used uninitialized
> and
> 'bar_len' may be used uninitialized
>
> They are not actually uninitialized as dfx_get_bars() will initialize
> them properly. But still lets ha
On Mon, Jan 25, 2016 at 04:44:53PM +0100, Petr Mladek wrote:
> +struct kthread_worker *
> +create_kthread_worker_on_cpu(int cpu, const char namefmt[])
> +{
> + if (cpu < 0 || cpu > num_possible_cpus())
> + return ERR_PTR(-EINVAL);
Comparing cpu ID to num_possible_cpus() doesn't mak
On 01/22/2016 02:27 AM, John Ogness wrote:
> The DMA-enabled OMAP UART driver in its current form queues 48 bytes for a
> DMA-RX transfer. After the transfer is complete, a new transfer of 48 bytes
> is queued. The DMA completion callback runs in tasklet context, so a
> reschedule with context swit
Hi Arnd,
On Mon, Jan 25, 2016 at 04:45:50PM +0100, Arnd Bergmann wrote:
> When CONFIG_DEBUG_VM is set, the various VM_BUG_ON() confuse gcc to
> the point where it cannot remember that 'memcg' is known to be initialized:
>
> mm/memcontrol.c: In function 'mem_cgroup_can_attach':
> mm/memcontrol.c:4
On Mon, 2016-01-25 at 18:02 +, Elliott, Robert (Persistent Memory)
wrote:
>
>
> > -Original Message-
> > From: James Bottomley [mailto:james.bottom...@hansenpartnership.com
> > ]
> > Sent: Saturday, January 23, 2016 10:44 AM
> > To: Andy Shevchenko ; Matt
> > Fleming
> > ; Thomas Glei
On Mon, Jan 25, 2016 at 10:53 AM, Andy Lutomirski wrote:
> On Mon, Jan 25, 2016 at 10:51 AM, Kees Cook wrote:
>> On Sun, Jan 24, 2016 at 2:22 PM, Andy Lutomirski wrote:
>>> On Fri, Jan 22, 2016 at 7:02 PM, Eric W. Biederman
>>> wrote:
Kees Cook writes:
> There continues to be une
* Andy Lutomirski wrote:
> Ingo, before applying this, please apply these two KASAN fixes:
>
> http://lkml.kernel.org/g/1452516679-32040-2-git-send-email-aryabi...@virtuozzo.com
> http://lkml.kernel.org/g/1452516679-32040-3-git-send-email-aryabi...@virtuozzo.com
>
> Without those fixes, this s
On Mon, Jan 25, 2016 at 04:44:56PM +0100, Petr Mladek wrote:
> +static void insert_kthread_work_sanity_check(struct kthread_worker *worker,
> +struct kthread_work *work)
> +{
> + lockdep_assert_held(&worker->lock);
> + WARN_ON_ONCE(!irqs_disabled(
We discussed this on IRC, here's the gist:
On Mon, Jan 25, 2016 at 10:45:30AM -0800, Andy Lutomirski wrote:
> On Sun, Jan 24, 2016 at 1:28 AM, Borislav Petkov wrote:
> > From: Borislav Petkov
> >
> > ... and simplify and speed up a tad.
>
> This function is only used when initializing CPUs, so
On 25/01/2016 19:44, Matthias Brugger wrote:
> On Monday 25 Jan 2016 16:36:40 John Crispin wrote:
>> Hi,
>>
>> On 25/01/2016 13:41, Lee Jones wrote:
>>> Please honour the subject format of the subsystem you are contributing
>>> to.
>>>
>>> `git log --oneline -- $subsystem` gives you this.
>>>
>>>
Hi Mans,
[auto build test ERROR on asoc/for-next]
[also build test ERROR on v4.5-rc1 next-20160125]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Mans-Rullgard/ASoC-mxs-saif-add-mclk-enable
Hi Daniel,
On Monday 25 January 2016 08:29:38 Daniel Vetter wrote:
> On Mon, Jan 25, 2016 at 12:19:27AM +0200, Laurent Pinchart wrote:
> > On Friday 15 January 2016 11:17:30 Daniel Vetter wrote:
> >> On Fri, Jan 15, 2016 at 01:13:05AM +0200, Laurent Pinchart wrote:
> >>> On Thursday 14 January 201
Signed-off-by: Andy Lutomirski
---
Documentation/kernel-parameters.txt | 2 ++
arch/x86/kernel/cpu/common.c| 16
2 files changed, 18 insertions(+)
diff --git a/Documentation/kernel-parameters.txt
b/Documentation/kernel-parameters.txt
index 742f69d18fc8..b34e55e00bae 10
Add a reset-controller driver for performing reset management of
various devices present on the SoC, with the reset registers shared
between devices in a common register memory space. This driver uses
the syscon/regmap frameworks to actually implement the various reset
functionalities needed by the
Some SoCs contain reset controls for modules that are memory-mapped to
areas shared with other module configuration settings. This requires
synchronization across all drivers accessing this memory area. This
series adds a generic SYSCON reset driver to allow resets toggled
by bits in memory-mapped
Add syscon reset controller binding. This will hook to the reset
framework and use syscon/regmap to set reset bits. This allows
reset control of individual SoC subsytems and devices with
memory-mapped reset registers in a common register memory
space.
Signed-off-by: Andrew F. Davis
[s-a...@ti.com
Hello,
On Mon, Jan 25, 2016 at 04:44:57PM +0100, Petr Mladek wrote:
> +/*
> + * Returns true when there is a pending operation for this work.
> + * In particular, it checks if the work is:
> + * - queued
> + * - a timer is running to queue this delayed work
> + *
> + * This function must be ca
On 01/25, Sasha Levin wrote:
>
> A random wakeup can get us out of sigsuspend() without TIF_SIGPENDING
> being set.
and TIF_RESTORE_SIGMASK is just wrong in this case. I'd say this is the
bugfix, not work-around ;)
> Avoid that by making sure we were signaled, like sys_pause() does.
>
> Signed-of
The WinSystems EBC-C384 has an onboard watchdog timer. The timeout range
supported by the watchdog timer is 1 second to 255 minutes. Timeouts
under 256 seconds have a 1 second resolution, while the rest have a 1
minute resolution.
This driver adds watchdog timer support for this onboard watchdog t
On Mon, 25 Jan 2016, Brian Norris wrote:
> > > + res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> > > + if (!res) {
> > > + dev_err(dev, "invalid resource\n");
> > > + return -EINVAL;
> > > + }
> > > + if (!devm_request_mem_region(dev, res->start, resource_size(res),
> > > +
Hi Chao,
On Mon, Jan 25, 2016 at 05:49:06PM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> > -Original Message-
> > From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> > Sent: Sunday, January 24, 2016 4:16 AM
> > To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> > linux-f2fs-de...@l
Hi Arnd,
On Mon, Jan 25, 2016 at 05:02:49PM +0100, Arnd Bergmann wrote:
> The Tegra clocksource implementation uses the clocksource_mmio helper
> functions, but currently can be configured without them, which fails:
>
> drivers/clocksource/built-in.o: In function `tegra20_init_timer':
> :(.init.t
On 25/01/16 16:44, Will Deacon wrote:
> On Mon, Jan 25, 2016 at 04:37:39PM +, Marc Zyngier wrote:
>> On 25/01/16 16:26, Will Deacon wrote:
>>> On Mon, Jan 25, 2016 at 03:53:34PM +, Marc Zyngier wrote:
ARMv8.1 comes with the "Virtualization Host Extension" (VHE for
short), which en
Hello,
On Mon, Jan 25, 2016 at 04:44:58PM +0100, Petr Mladek wrote:
> @@ -574,6 +575,7 @@ EXPORT_SYMBOL_GPL(__init_kthread_worker);
> static inline bool kthread_work_pending(const struct kthread_work *work)
> {
> return !list_empty(&work->node) ||
> +work->canceling ||
>
On Tue, Jan 05, 2016 at 11:54:28AM -0700, Toshi Kani wrote:
> This patch-set enhances the iomem table and its search interfacs, and
> then changes EINJ to support NVDIMM.
>
> - Patches 1-2 add a new System RAM type, IORESOURCE_SYSTEM_RAM, and
>make the iomem search interfaces work with resour
Hi Chao,
On Mon, Jan 25, 2016 at 05:42:40PM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> > -Original Message-
> > From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> > Sent: Sunday, January 24, 2016 4:16 AM
> > To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> > linux-f2fs-de...@l
On Mon, Jan 25, 2016 at 04:44:59PM +0100, Petr Mladek wrote:
> +bool mod_delayed_kthread_work(struct kthread_worker *worker,
> + struct delayed_kthread_work *dwork,
> + unsigned long delay)
> +{
> + struct kthread_work *work = &dwork->work;
>
On Mon, Jan 25, 2016 at 04:45:00PM +0100, Petr Mladek wrote:
> @@ -556,6 +556,7 @@ void __init_kthread_worker(struct kthread_worker *worker,
> const char *name,
> struct lock_class_key *key)
> {
> + worker->flags = 0;
> spin_loc
alloc_etherdev() calls alloc_netdev_mqs(), which
already uses kzalloc/vzalloc.
This clears a sparse warning :
drivers/staging/unisys/visornic/visornic_main.c:1366:15: warning: memset with
byte count of 1460112
Signed-off-by: Hugo Camboulive
---
drivers/staging/unisys/visornic/visornic_main.c |
On Mon, Jan 25, 2016 at 09:21:53AM +0100, Christian Borntraeger wrote:
> >> Let's go back to the original default and reverse the command
> >> line parameter to allow disabling the feature.
> >
> > Default disable is requested by Andrew and I agreed that.
> >
> > https://lkml.org/lkml/2014
Hi,
On Mon, Jan 25, 2016 at 7:36 AM, Arend van Spriel wrote:
> On 25-01-16 11:47, Sjoerd Simons wrote:
>> On a Radxa Rock2 board with a Ampak AP6335 (Broadcom 4339 core) it seems
>> the card responds very quickly most of the time, unfortunately during
>> initialisation it sometimes seems to take
On Mon, Jan 25, 2016 at 8:56 PM, James Bottomley
wrote:
> On Mon, 2016-01-25 at 18:02 +, Elliott, Robert (Persistent Memory)
> wrote:
> Using ffs leads to precision runaway
How exactly?!
> and
> exporting an array from string_helpers.c is simply the wrong way to do
> it.
This part I didn'
> +static int ebc_c384_wdt_set_timeout(struct watchdog_device *wdev, unsigned t)
> +{
> + /* resolution is in minutes for timeouts greater than 255 seconds */
> + if (t > 255) {
> + /* truncate second resolution to minute resolution */
> + t /= 60;
> + wd
On 01/25/2016 09:50 AM, Stefan Agner wrote:
> Hi Marcel,
>
> [also added Lucas]
>
> On 2015-12-30 19:12, Marcel Ziswiler wrote:
>> Continuing on the Apalis iMX6 mainlining work started by Petr Štetiar I
>> noticed that it only boots when rebooting from NXP's downstream 3.14.28
>> kernel or mainli
On Mon, Jan 25, 2016 at 07:15:49PM +, Maciej W. Rozycki wrote:
> On Mon, 25 Jan 2016, Brian Norris wrote:
>
> > > > + res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> > > > + if (!res) {
> > > > + dev_err(dev, "invalid resource\n");
> > > > + retu
On 01/25/2016 07:51 PM, Daniel Vetter wrote:
On Mon, Jan 25, 2016 at 05:38:30PM +0100, Mario Kleiner wrote:
Readding Daniel, which somehow got dropped from the cc.
On 01/25/2016 03:53 PM, Ville Syrjälä wrote:
On Mon, Jan 25, 2016 at 02:44:53PM +0100, Mario Kleiner wrote:
On 01/25/2016 02:
On Tue, Jan 26, 2016 at 01:21:50AM +0800, j00310691 wrote:
> From: John Garry
>
> Add the dt bindings for HiSi SAS controller v2 HW.
>
> The main difference in the controller from dt perspective
> is interrupts. The v2 controller does not have dedicated
> fatal and broadcast interrupts - they ar
On Mon, Jan 25, 2016 at 08:09:15PM +0100, Oleg Nesterov wrote:
> On 01/25, Sasha Levin wrote:
> >
> > A random wakeup can get us out of sigsuspend() without TIF_SIGPENDING
> > being set.
>
> and TIF_RESTORE_SIGMASK is just wrong in this case. I'd say this is the
> bugfix, not work-around ;)
Agree
On Mon, Jan 25, 2016 at 10:37:30AM -0600, Andrew F. Davis wrote:
> Add binding for generic parallel-in/serial-out shift register devices
> used as GPIO.
>
> Signed-off-by: Andrew F. Davis
> ---
> .../devicetree/bindings/gpio/gpio-pisosr.txt | 34
> ++
> 1 file changed,
Hello, Christoph.
On Mon, Jan 25, 2016 at 09:49:42AM +0100, Christoph Hellwig wrote:
> FYI, my use case was also related to percpu-ref. The percpu ref API
> is unfortunately really hard to use and will almost always involve
> a work queue due to the complex interaction between percpu_ref_kill
> a
On Mon, Jan 25, 2016 at 02:22:10PM -0500, Dave Jones wrote:
> > A default mode would be ok for me as it makes things obvious. Will send
> > a patch.
>
> The messaging around changing a default like this was really poor.
> When we do behaviour changes like this, we typically rename the CONF
On Sat, 5 Dec 2015 17:50:10 -0200
Diego Viola wrote:
> Signed-off-by: Diego Viola
OK, I've applied this (the original version) to the docs tree, sorry for
the delay. In the future, though, when a maintainer asks you to relax,
please don't respond by sending five more messages :)
jon
From: Aravind Gopalakrishnan
In mce_amd_feature_init() we take decisions based on mce_flags being set
or not. So the feature detection using CPUID should naturally be ordered
before we call mce_amd_feature_init().
Fix that here.
Signed-off-by: Aravind Gopalakrishnan
Cc: linux-edac
Cc: Tony Lu
From: Aravind Gopalakrishnan
It is required for the OS to acknowledge that it is using the MCAX
register set and its associated fields by setting the 'McaXEnable' bit
in each bank's MCi_CONFIG register. If it is not set, then all UC errors
will cause a system panic.
Signed-off-by: Aravind Gopala
From: Aravind Gopalakrishnan
For processor families with the Scalable MCA feature, the LVT offset for
threshold interrupts is configured only in MSR 0xC410 and not in
each per bank MISC register as was done in earlier families.
Obtain the LVT offset from the correct MSR for those families.
From: Huaitong Han
Most of magic numbers of x86_capability have been converted to enum
cpuid_leafs, and this patch does update the remaining part.
Signed-off-by: Huaitong Han
Cc: Alexander Kuleshov
Cc: Andrew Morton
Cc: Andy Lutomirski
Cc: Boris Ostrovsky
Cc: Brian Gerst
Cc: David Vrabel
From: Borislav Petkov
Hi,
here's the first pile. It contains mainly the RAS pile for 4.6 and a
couple of small cleanups.
Please apply,
thanks.
Alexander Kuleshov (1):
x86/traps.c: Refactor preemption and interrupt flag handling
Aravind Gopalakrishnan (5):
x86/mce: Fix order of AMD MCE in
From: Aravind Gopalakrishnan
>From Fam17h onwards, the number of extended MCx_MISC register blocks is
reduced to 4. It is an architectural change from what we had on earlier
processors.
Although theoritically the total number of extended MCx_MISC registers
was 8 in earlier processor families, in
Em Mon, Jan 25, 2016 at 07:35:11PM +0100, Ingo Molnar escreveu:
>
> So it appears it broke somewhere between v4.0 and v4.1, as the v4.0 install
> displays:
>
> 16,244,802,268 instructions ( +- 23.01% )
>
>2.108676769 seconds time elapsed
From: Alexander Kuleshov
Make the preemption and interrupt flag handling more readable by
removing preempt_conditional_sti() and preempt_conditional_cli() helpers
and using preempt_disable() and preempt_enable_no_resched() instead.
Rename contitional_sti() and conditional_cli() to the more
under
From: Aravind Gopalakrishnan
Fam17h and above should not require a check to see if a bank is shared
or not. For shared banks, there will always be only one core that has
visibility over the MSRs and only that particular core will be allowed
to write to the MSRs.
Fix the code to return early if w
901 - 1000 of 1350 matches
Mail list logo
