On Wed, Apr 12, 2017 at 05:27:22PM +0100, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in DRM_DEBUG_ATOMIC debug message
>
> Signed-off-by: Colin Ian King
Applied for 4.13 (4.12 feature cutoff is already gone).
Thanks, Daniel
> ---
> drivers/gpu/drm/drm_atomic
On Wed, Apr 12, 2017 at 12:12:01PM -0700, Eric Anholt wrote:
> If we follow the typical pattern of the base class being the first
> member, we can use the default dma_fence_free function.
>
> Signed-off-by: Eric Anholt
On 3&4: Reviewed-by: Daniel Vetter
> Cc: Lucas Stach
> Cc: Russell King
>
Hi Chen-Yu,
On Thu, Apr 13, 2017 at 10:13:52AM +0800, Chen-Yu Tsai wrote:
> In common PLL designs, changes to the dividers take effect almost
> immediately, while changes to the multipliers (implemented as
> dividers in the feedback loop) take a few cycles to work into
> the feedback loop for the
From: Sean Wang
Document the devicetree bindings for Mediatek random number
generator which could be found on MT7623 SoC or other similar
Mediatek SoCs.
Signed-off-by: Sean Wang
---
Documentation/devicetree/bindings/rng/mtk-rng.txt | 18 ++
1 file changed, 18 insertions(+)
cre
From: Sean Wang
This patch adds support for hardware random generator on MT7623 SoC
and should also work on other similar Mediatek SoCs. Currently,
the driver is already tested successfully with rng-tools.
Signed-off-by: Sean Wang
---
drivers/char/hw_random/Kconfig | 16 +++-
drivers/char/h
From: Sean Wang
This patchset introduces support for Mediatek hardware random generator (RNG)
Currently, the driver is already tested successfully with rng-tools on MT7623
SoC. And it should also be workable on other similar Mediatek SoCs.
SoC that also works on other similar SoCs.
Sean Wang (2
Signed-off-by: Christoph Hellwig
---
kernel/irq/manage.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
index a4afe5cc5af1..391cb738b2db 100644
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -1557,7 +1557,7 @@ void remove_irq(
This allows callers to get back at them instead of having to store
it in another variable.
Signed-off-by: Christoph Hellwig
---
include/linux/interrupt.h | 2 +-
kernel/irq/manage.c | 13 ++---
2 files changed, 11 insertions(+), 4 deletions(-)
diff --git a/include/linux/interrupt
PCI drivers that support multiple MSI or MSI-X vectors currently have a
lot of boileplate code to generate names for each vector (or simply use
the same name for all of them, which isn't nice either). This series
adds new helpers that allocate and free a name based on a format string
passed to the
Hi Jeffy,
[auto build test ERROR on drm/drm-next]
[also build test ERROR on v4.11-rc6 next-20170413]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Jeffy-Chen/drm-Unplug-drm-device-when
Signed-off-by: Christoph Hellwig
---
drivers/nvme/host/pci.c | 30 +-
1 file changed, 13 insertions(+), 17 deletions(-)
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 26a5fd05fe88..925997127a6b 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/n
These are small wrappers around request_threaded_irq and free_irq,
which dynamically allocate space for the device name so that drivers
don't need to keep static buffers for these around. Additionally it
works with device-relative vector numbers to make the usage easier,
and force the IRQF_SHARED
On Wed, Apr 12, 2017 at 05:21:20PM -0700, Kees Cook wrote:
> Hrm? This is what the patch already does. It adds them for both
> __port_action and struct bfa_module_s.
For __port_action it only uses designated initializers for the
structures in the array, not the array itself.
>>
>> Yes. It was derived from TASK_SIZE :
>>
>> http://lxr.free-electrons.com/source/arch/powerpc/include/asm/processor.h#L105
>>
>
> That is getting update to 128TB by default and conditionally to 512TB
>
Since this is compile time, we should probably keep the scope to 128TB
for now and see if w
Looks fine,
Reviewed-by: Christoph Hellwig
On Thu, 13 Apr 2017 09:29:23 +0300
Mathias Nyman wrote:
> On 12.04.2017 10:47, Ralph Sennhauser wrote:
> > Hi Guoqing Zhang,
> >
> > Commit a6ff6cbf1fabe7500d8ac25e133e3346db0a0fca ("usb: xhci: Add
> > helper function xhci_set_power_on().") causes a null pointer
> > dereference on an armada-385.
On Wed, Apr 12, 2017 at 12:12:02PM -0700, Eric Anholt wrote:
> This is needed for proper synchronization with display on another DRM
> device (pl111 or tinydrm) with buffers produced by vc4 V3D. Fixes the
> new igt vc4_dmabuf_poll testcase, and rendering of one of the glmark2
> desktop tests on pl
> On Fri, Apr 07, 2017 at 03:07:07PM +0200, Micha?? K??pie?? wrote:
> > This patch series cleans up parts of fujitsu-laptop responsible for
> > handling LED class devices. It was tested on a Lifebook E744. It
> > depends on the previous patch series I submitted for fujitsu-laptop and
> > should b
On Thu, Apr 13, 2017 at 11:59:20AM +0900, Minchan Kim wrote:
> Johannes Thumshirn reported system goes the panic when using NVMe over
> Fabrics loopback target with zram.
>
> The reason is zram expects each bvec in bio contains a single page
> but nvme can attach a huge bulk of pages attached to t
On Thu, 13 Apr 2017 16:27:34 +1000
Michael Neuling wrote:
> On Thu, 2017-04-13 at 14:12 +1000, Benjamin Herrenschmidt wrote:
> > On Thu, 2017-04-13 at 09:28 +0530, Aneesh Kumar K.V wrote:
> > > > #endif
> > > > mtctr r12
> > > > bctrl
> > > > +/*
> > > > + * cur_cpu_spec->cpu_
Dear Robert,
Thank you for your reply.
On 2017-04-12 23:49, Moore, Robert wrote:
On 2017-04-12 17:54, Moore, Robert wrote:
> And probably the dmesg if error messages appear in there.
Linux doesn’t log any messages, as the `tpm` module doesn’t load.
Please
find the output of `sudo acpidump
On 13 April 2017 at 04:58, Gary Lin wrote:
> This commit adds the new config options to allow the user to modify the
> following fields in the PE-COFF header.
>
> UINT16 MajorOperatingSystemVersion
> UINT16 MinorOperatingSystemVersion
> UINT16 MajorImageVersion
> UINT16 MinorImageVersion
>
> Those
Hi David,
On Wednesday 12 April 2017 19:15:20 David Miller wrote:
> [...]
> >> Please note: the "MDIO managed mode" driver part isn't tested yet. I
> >> have used and tested the "I2C managed mode" only.
> >
> > Series applied, thank you.
>
> Actually, this doesn't even build. Please fix this and
> Hi All,
>
> There are a few parallel efforts involving the Windows Management
> Instrumentation (WMI)[1] and dependent/related drivers. I'd like to have a
> round of
> discussion among those of you that have been involved in this space before we
> decide on a direction.
>
> The WMI support in
After unbinding drm, the user space may still owns the drm dev fd, and
may still be able to call drm ioctl.
We're using an unplugged state to prevent something like that, so let's
reuse it here.
Also drop drm_unplug_dev, because it would be unused after other changes.
Verified on rk3399 chromebo
Fix this by moving the mdp component nodes up a level such that they are
siblings of mdp and all other SoC subsystems. This also simplifies the
device tree.
Daniel Kurtz (2):
arm64: dts: mt8173: Fix mdp device tree
media: mtk-mdp: Fix mdp device tree
Minghsiu Tsai (1):
dt-bindings: mt8173:
From: Daniel Kurtz
If the mdp_* nodes are under an mdp sub-node, their corresponding
platform device does not automatically get its iommu assigned properly.
Fix this by moving the mdp component nodes up a level such that they are
siblings of mdp and all other SoC subsystems. This also simplifie
On Wednesday 12 April 2017 16:08:54 Darren Hart wrote:
> In Windows, applications interact with WMI more or less directly. We don't do
> this in Linux currently, although it has been discussed in the past [3]. Some
> vendors will work around this by performing SMI/SMM, which is inefficient at
> bes
From: Daniel Kurtz
If the mdp_* nodes are under an mdp sub-node, their corresponding
platform device does not automatically get its iommu assigned properly.
Fix this by moving the mdp component nodes up a level such that they are
siblings of mdp and all other SoC subsystems. This also simplifie
To define the outgoing port and to discover the incoming port a regular
VLAN tag is used by the LAN9303. But its VID meaning is 'special'.
This tag handler/filter depends on some hardware features which must be
enabled in the device to provide and make use of this special VLAN tag
to control the d
When the LAN9303 device is in MDIO manged mode, all register accesses must
be done via MDIO.
Please note: this code is compile time tested only due to the absence of such
configured hardware. It is based on a patch from Stefan Roese from 2014.
Signed-off-by: Juergen Borleis
Reviewed-by: Andrew L
In this mode the switch device and the internal phys will be managed via
I2C interface. The MDIO interface is still supported, but for the
(emulated) CPU port only.
Signed-off-by: Juergen Borleis
Reviewed-by: Andrew Lunn
CC: devicet...@vger.kernel.org
CC: robh...@kernel.org
CC: mark.rutl...@arm.
The LAN9303 is a three port 10/100 ethernet switch with integrated phys
for the two external ethernet ports. The third port is an RMII/MII
interface to a host master network interface (e.g. fixed link).
While the LAN9303 device itself supports offload packet processing, this
driver does not make u
The SMSC/Microchip LAN9303 is an ethernet switch device with one CPU port
and two external ethernet ports with built-in phys.
This driver uses the DSA framework, but is currently only capable of
separating the two external ports. There is no offload support yet.
Signed-off-by: Juergen Borleis
Re
On Thu, Apr 13, 2017 at 3:02 PM, Maxime Ripard
wrote:
> Hi Chen-Yu,
>
> On Thu, Apr 13, 2017 at 10:13:52AM +0800, Chen-Yu Tsai wrote:
>> In common PLL designs, changes to the dividers take effect almost
>> immediately, while changes to the multipliers (implemented as
>> dividers in the feedback lo
If the mdp_* nodes are under an mdp sub-node, their corresponding
platform device does not automatically get its iommu assigned properly.
Fix this by moving the mdp component nodes up a level such that they are
siblings of mdp and all other SoC subsystems. This also simplifies the
device tree.
S
On Wed, Apr 12, 2017 at 01:26:01PM +0100, David Woodhouse wrote:
> From: David Woodhouse
>
> Signed-off-by: David Woodhouse
For the CRIS part:
Acked-by: Jesper Nilsson
> ---
> arch/cris/arch-v32/drivers/pci/bios.c | 23 ---
> arch/cris/include/asm/pci.h | 1 +
On Tue, 11 Apr 2017 13:23:53 +0200
Gerd Hoffmann wrote:
> Hi,
>
> > > Just let know what you need tested, I should be able to turn it around
> > > within a couple of days.
> >
> > That's part of my problem. I don't really know what should be tested.
> > What do people do with their BE machi
On Wed, 12 Apr 2017 19:11:21 +0200
Thierry Reding wrote:
> On Sun, Apr 09, 2017 at 08:09:27PM +0200, Ralph Sennhauser wrote:
> > From: Andrew Lunn
> >
> > Armada 370/XP devices can 'blink' GPIO lines with a configurable on
> > and off period. This can be modelled as a PWM.
> >
> > However, the
On Thu, Apr 13, 2017 at 12:28 PM, Aneesh Kumar K.V
wrote:
>
>
> On Thursday 13 April 2017 12:22 PM, Bhupesh Sharma wrote:
>>
>> Hi Aneesh,
>>
>> On Thu, Apr 13, 2017 at 12:06 PM, Aneesh Kumar K.V
>> wrote:
>>>
>>> Bhupesh Sharma writes:
>>>
powerpc arch_mmap_rnd() currently uses hard-coded
On Thu, Apr 13, 2017 at 08:26:04AM +0100, Ard Biesheuvel wrote:
> On 13 April 2017 at 04:58, Gary Lin wrote:
> > This commit adds the new config options to allow the user to modify the
> > following fields in the PE-COFF header.
> >
> > UINT16 MajorOperatingSystemVersion
> > UINT16 MinorOperatingS
On Wed, 12 Apr 2017 19:16:56 +0200
Thierry Reding wrote:
> On Sun, Apr 09, 2017 at 08:09:26PM +0200, Ralph Sennhauser wrote:
> > Hi Therry,
> >
> > Resending this as v5 with some minor changes since v4. What is
> > missing is an ACK from you so Linus can merge the driver and
> > Gregory the dts
On Wed, Apr 12, 2017 at 09:46:05AM -0700, Stephen Boyd wrote:
> On 03/21, Peter De Schrijver wrote:
> > Whenever a user change its min or max rate limit of a clock, we need to
> > re-evaluate the current clock rate and possibly change it if the new limits
> > require so. To do this clk_set_rate_ran
This patch extends the device tree support for the pca9532 by adding
the leds 'default-state' property.
Signed-off-by: Felix Brack
---
.../devicetree/bindings/leds/leds-pca9532.txt | 10
drivers/leds/leds-pca9532.c| 27 +-
include/linux/l
Hi Steven,
I just found this patch in linux-next commit 8aaf1ee70e19 with
scripts/checkkconfigsymbols.py complaining about an undefined
CONFIG_PREEMPT_DEBUG (see below). I guess it's just a typo, since
there is a symbol named DEBUG_PREEMPT.
If you want to, I can send a trivial patch to rename bot
thermal_zone_device_check --> thermal_zone_device_update -->
handle_thermal_trip --> handle_critical_trips --> orderly_poweroff
The above sequence happens every 250/500 mS based on the configuration.
The orderly_poweroff function is getting called every 250/500 mS.
With a full fledged file system
orderly_poweroff is triggered when a graceful shutdown
of system is desired. This may be used in many critical states of the
kernel such as when subsystems detects conditions such as critical
temperature conditions. However, in certain conditions in system
boot up sequences like those in the middle
Doing a mkfs.btrfs on a (qemu emulated) PCIe NVMe causes a kernel panic
in nvme_setup_prps() because the dma_len will drop below zero but the
length not.
A git bisect tracked the behaviour down to commit 729204ef49ec ("block:
relax check on sg gap"). Since commit 729204ef49ec a bio's offsets are n
On Wed, Apr 12, 2017 at 09:27:31PM -0700, Cong Wang wrote:
> On Wed, Apr 12, 2017 at 7:21 AM, Wolfgang Bumiller
> wrote:
> > If memory allocation for nla_memdup_cookie() fails
> > module_put has to be guarded by the same condition as it was
> > before the TCA_ACT_COOKIE has been added as stated in
On 06/04/2017 18:50, Davidlohr Bueso wrote:
> On Thu, 06 Apr 2017, Laurent Dufour wrote:
>
>> How is 'seqnum' wrapping handled here ?
>> I'd rather see something like time_before() here, isn't it ?
>
> Its a 64bit counter, no overflows.
I should have miss something, what prevents this 64bit coun
On Wed, Apr 12, 2017 at 11:15:59AM -0400, Sven Van Asbroeck wrote:
> + pm_runtime_set_active(&client->dev);
> + /* enable will put the chip into suspend, which is what we
> + * want as all outputs are disabled at this point
> + */
This comment should also be in the standard block
The mmustat_enable sysfs file accessor functions must run code on the
target CPU. This is achieved by temporarily setting the affinity of the
calling user space thread to the requested CPU and reset it to the original
affinity afterwards.
That's racy vs. concurrent affinity settings for that threa
Gemini Lake is a Goldmont core based Apollo Lake successor with better
CPU performance. Currently there is no hardware cache events available
if checking with "perf list cache" on Gemini Lake. Perf hardware cache
event test always fail because of this.
This patch adds INTEL_FAM6_ATOM_GEMINI_LAKE c
spu_queue_register() needs to invoke setup functions on a particular
CPU. This is achieved by temporarily setting the affinity of the
calling user space thread to the requested CPU and reset it to the original
affinity afterwards.
That's racy vs. CPU hotplug and concurrent affinity settings for th
On (04/13/17 14:50), Sergey Senozhatsky wrote:
[..]
> On (04/12/17 01:19), Sergey Senozhatsky wrote:
> [..]
> > it does offloading after X printed lines by the same process.
> > if we reschedule, then the counter resets. which is probably OK,
> > we don't really want any process, except for printk_
spu_queue_register() needs to invoke setup functions on a particular
CPU. This is achieved by temporarily setting the affinity of the
calling user space thread to the requested CPU and reset it to the original
affinity afterwards.
That's racy vs. CPU hotplug and concurrent affinity settings for th
Am Donnerstag, 13. April 2017, 12:00:19 CEST schrieb Kever Yang:
> Hi Heiko,
>
> On 04/12/2017 09:29 PM, Heiko Stuebner wrote:
> > Hi Kever,
> >
> > Am Montag, 10. April 2017, 11:50:13 CEST schrieb Kever Yang:
> >> Firefly-rk3399 is a bord from T-Firefly, you can find detail about
> >> it here:
>
The access to the HBIRD_ESTAR_MODE register in the cpu frequency control
functions must happen on the target CPU. This is achieved by temporarily
setting the affinity of the calling user space thread to the requested CPU
and reset it to the original affinity afterwards.
That's racy vs. CPU hotplug
Hi Guochun,
Le 13/04/2017 à 04:40, Guochun Mao a écrit :
> Hi Cyrille,
>
> On Wed, 2017-04-12 at 22:57 +0200, Cyrille Pitchen wrote:
>> Hi Guochun,
>>
>> Le 05/04/2017 à 10:37, Guochun Mao a écrit :
>>> When nor's size larger than 16MByte, nor's address width maybe
>>> set to 3 or 4, and controll
On Thu, Apr 13, 2017 at 11:25:39AM +0800, Jin, Yao wrote:
SNIP
> >
> > Now it works without my patch and it runs with latest perf/core branch.
> > So it looks like a regression issue.
> >
> > Thanks
> > Jin Yao
> >
> >
>
> I have tested, the regression issue is happened after this commit:
>
On Wed, Apr 12, 2017 at 11:23:01AM -0700, David Carrillo-Cisneros wrote:
> From: Stephane Eranian
>
> (This is a patch has been sitting in the Intel CQM/CMT driver series
> for a while, despite not depend on it. Sending it now independently
> since the series is being discarded.)
>
> When an e
On 2017/4/12 6:55, Douglas Anderson wrote:
According to the SDIO standard interrupts are normally signalled in a
very complicated way. They require the card clock to be running and
require the controller to be paying close attention to the signals
coming from the card. This simply can't happe
Hi Sebastian,
> Here is the fourth revision of the nokia bluetooth patchset. Compared
> to the previous one the following things have changed:
>
> * Drop patch 1-8 (applied by Marcel) and update Cc/To for patchset
> * Order includes in the driver alphabetically
> * Explicitly include in the noki
On 04/11/2017 at 04:47 AM, Daniel Bristot de Oliveira wrote:
> On 04/10/2017 11:22 AM, Xunlei Pang wrote:
>> I was testing Daniel's changes with his test case in the commit
>> df8eac8cafce ("sched/deadline: Throttle a constrained deadline
>> task activated after the deadline"), and tweaked it a lit
Do you need a loan to pay up bill or to start a business? Email Us
On Thu 13-04-17 10:07:48, Laurent Dufour wrote:
> On 06/04/2017 18:50, Davidlohr Bueso wrote:
> > On Thu, 06 Apr 2017, Laurent Dufour wrote:
> >
> >> How is 'seqnum' wrapping handled here ?
> >> I'd rather see something like time_before() here, isn't it ?
> >
> > Its a 64bit counter, no overflows
On Wed, 2017-04-12 at 14:47 -0700, Tony Luck wrote:
> On Wed, Apr 12, 2017 at 5:26 AM, David Woodhouse wrote:
> >
> > From: David Woodhouse
> >
> > Now that we eliminated the different behaviour in separately-reviewable
> > commits, we can switch IA64 to the generic implementation.
> >
> > Sig
On Thu, 2017-04-13 at 09:37 +0200, Jesper Nilsson wrote:
> On Wed, Apr 12, 2017 at 01:26:01PM +0100, David Woodhouse wrote:
> >
> > From: David Woodhouse
> >
> > Signed-off-by: David Woodhouse
> For the CRIS part:
>
> Acked-by: Jesper Nilsson
Thanks. I actually had that once before but it ha
Hi Sean,
Mostly looks good, have few minor comments.
On 13 April 2017 at 12:35, wrote:
> +static bool mtk_rng_wait_ready(struct hwrng *rng, bool wait)
> +{
> + struct mtk_rng *priv = to_mtk_rng(rng);
> + int ready;
> +
> + ready = readl(priv->base + RNG_CTRL) & RNG_READY;
> +
On Wed, Apr 12, 2017 at 02:27:44PM -0400, Steven Rostedt wrote:
> + * schedule_idle() is similar to schedule_preempt_disable() except
> + * that it never enables preemption.
That's not right. The primary distinction is that it doesn't call
sched_submit_work().
And because that function is a no-op
Alexei Starovoitov wrote:
> this will obviously break the program.
Yeah. But if it allows one to twiddle the kernel image or gain access to
crypto material...
> How about disabling loading tracing programs during the lockdown completely?
Interesting thought. I'm not sure how much would actua
Hi Milan,
On 10 April 2017 at 19:30, Milan Broz wrote:
Thank you for the reply.
> Well, it is good that there is no performance degradation but it
> would be nice to have some user of it that proves it is really
> working for your hw.
I have been able to get access to a hardware with IV genera
Hi Xiuqi,
On 2017/3/30 18:31, Xie XiuQi wrote:
> Error Synchronization Barrier (ESB; part of the ARMv8.2 Extensions)
> is used to synchronize Unrecoverable errors. That is, containable errors
> architecturally consumed by the PE and not silently propagated.
>
> With ESB it is generally possible t
Excerpts from Masami Hiramatsu's message of April 13, 2017 10:04:
On Wed, 12 Apr 2017 16:28:27 +0530
"Naveen N. Rao" wrote:
This helper will be used in a subsequent patch to emulate instructions
on re-entering the kprobe handler. No functional change.
In this case, please merge this patch in
On Wed, Apr 12, 2017 at 07:30:22PM +0200, Christoph Hellwig wrote:
> > shows some have been done. I wonder whether marking
> > pci_enable_msix_exact() would cause a lot of warnings though. An
> > allyesconfig build would tell...
>
> It would cause lots of warnings. The problem with __deprecated i
Currently, the __iommu_dma_{map/free} functions call iova_{offset/align}
making them unsuitable for use with iommu_domains having an IOMMU_DMA_MSI
cookie since the cookie's iova_domain member, iovad, is uninitialized.
Now that iommu_dma_get_msi_page() calls __iommu_dma_map() regardless
of cookie t
On 13/04/2017 10:38, Jan Kara wrote:
> On Thu 13-04-17 10:07:48, Laurent Dufour wrote:
>> On 06/04/2017 18:50, Davidlohr Bueso wrote:
>>> On Thu, 06 Apr 2017, Laurent Dufour wrote:
>>>
How is 'seqnum' wrapping handled here ?
I'd rather see something like time_before() here, isn't it ?
>>>
On Wed, Apr 12, 2017 at 10:56:07PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt (VMware)
>
> During my tests, I see this in my dmesg:
>
> "Scheduler tracepoints stat_sleep, stat_iowait, stat_blocked and
> stat_runtime require the kernel parameter schedstats=enabled or
> kernel.sched_sched
Enable the xHCI plat runtime PM for parent device to suspend/resume
xHCI. Also call pm_runtime_forbid() in probe() function to force users
to explicitly enable runtime pm using power/control in sysfs, in case
some parent devices didn't implement runtime PM callbacks.
Signed-off-by: Baolin Wang
--
On Thu, Apr 13, 2017 at 11:00:05AM +0200, Peter Zijlstra wrote:
> On Wed, Apr 12, 2017 at 10:56:07PM -0400, Steven Rostedt wrote:
> > From: Steven Rostedt (VMware)
> >
> > During my tests, I see this in my dmesg:
> >
> > "Scheduler tracepoints stat_sleep, stat_iowait, stat_blocked and
> > stat_r
On Wed, Apr 12, 2017 at 10:07:26PM +0200, Thomas Gleixner wrote:
> While dealing with the fallout of the scheduler cleanups on RT, we found
> several racy usage sites of the following scheme:
>
> cpumask_copy(&save_cpus_allowed, ¤t->cpus_allowed);
> set_cpus_allowed_ptr(current, cpumas
On Wed, Apr 12, 2017 at 09:40:14AM -0700, Paul E. McKenney wrote:
> This commit updates the "Early Boot" section of the RCU requirements
> to describe how synchronous RCU grace periods are now legal throughout
> the boot process.
You mean people would come an arrest you for doing it before? ;-)
On Mon, Apr 10, 2017 at 02:15:44PM +0200, Tobias Regnery wrote:
> The ccu-sun9i-a80 driver uses the ccu_mult_ops struct, but unlike the other
> users it doesen't select the corresponding Kconfig symbol under which the
> struct is compiled in.
>
> This results in the following link error with CONFI
On Wed, Apr 12, 2017 at 09:55:37AM -0700, Paul E. McKenney wrote:
> A group of Linux kernel hackers reported chasing a bug that resulted
> from their assumption that SLAB_DESTROY_BY_RCU provided an existence
> guarantee, that is, that no block from such a slab would be reallocated
> during an RCU r
On Wed, Apr 12, 2017 at 09:55:38AM -0700, Paul E. McKenney wrote:
> This commit changes lockdep splats to begin lines with "WARNING" and
> to use pr_warn() instead of printk(). This change eases scripted
> analysis of kernel console output.
>
> Reported-by: Dmitry Vyukov
> Reported-by: Ingo Moln
On Tue, Apr 11, 2017 at 10:34:27AM +0100, Richard Fitzgerald wrote:
> On Mon, 2017-04-10 at 15:17 -0500, Rob Herring wrote:
> > On Fri, Apr 07, 2017 at 01:38:44PM +0100, Charles Keepax wrote:
> > > The Arizona devices only maintain the state of output GPIOs whilst the
> > > CODEC is active, this ca
On Wed, Apr 12, 2017 at 09:55:40AM -0700, Paul E. McKenney wrote:
> If you set RCU_FANOUT_LEAF too high, you can get lock contention
> on the leaf rcu_node, and you should boot with the skew_tick kernel
> parameter set in order to avoid this lock contention. This commit
> therefore upgrades the RC
The struct cpudl passed to cpudl_init() is already initialized to zero.
Don't do that again.
Signed-off-by: Viresh Kumar
---
kernel/sched/cpudeadline.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/kernel/sched/cpudeadline.c b/kernel/sched/cpudeadline.c
index fba235c7d026..bdf448b6556f 1006
There are only two callers of init_rootdomain(). One of them passes a
global to it and another one sends dynamically allocated root-domain.
There is no need to memset the root-domain in the first case as the
structure is already reset.
Update alloc_rootdomain() to allocate the memory with kzalloc
The struct cpupri passed to cpupri_init() is already initialized to
zero. Don't do that again.
Signed-off-by: Viresh Kumar
---
kernel/sched/cpupri.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/kernel/sched/cpupri.c b/kernel/sched/cpupri.c
index 981fcd7dc394..2511aba36b89 100644
--- a/ke
Hi,
Avoid reinitializing memory which is already set to zero.
V1->V2:
- Don't remove field initializers from 2nd and 3rd patch.
- Drop 4th patch (sched: core: drop useless expression from sched_init()).
--
viresh
Viresh Kumar (3):
sched: topology: drop memset() from init_rootdomain()
sched:
On 12/04/17 19:43, Marc Zyngier wrote:
On 12/04/17 17:19, Andrey Konovalov wrote:
Hi Andrey,
Apparently this wasn't fixed, I've got this report again on
linux-next-c4e7b35a3 (Apr 11), which includes 8b3405e34 "kvm:
arm/arm64: Fix locking for kvm_free_stage2_pgd".
This looks like a different
On Wed, Apr 12, 2017 at 09:55:43AM -0700, Paul E. McKenney wrote:
> However, a little future-proofing is a good thing,
> especially given that smp_mb__before_atomic() is only required to
> provide acquire semantics rather than full ordering. This commit
> therefore adds smp_mb__after_atomic() afte
The madvise_behavior_valid() function should be called before
acting upon the behavior parameter. Hence move up the function.
This also includes MADV_SOFT_OFFLINE and MADV_HWPOISON options
as valid behavior parameter for the system call madvise().
Signed-off-by: Anshuman Khandual
---
This applies
On Wed, Apr 12, 2017 at 10:39:46AM -0700, Paul E. McKenney wrote:
> Currently, IPIs are used to force other CPUs to invalidate their TLBs
> in response to a kernel virtual-memory mapping change. This works, but
> degrades both battery lifetime (for idle CPUs) and real-time response
> (for nohz_ful
David Woodhouse wrote:
> + vma->vm_pgoff += (pci_resource_start(pdev, bar) >> PAGE_SHIFT);
> +vma->vm_ops = &pci_phys_vm_ops;
Whitespace error.
David
David Woodhouse wrote:
> From: David Woodhouse
>
> This was setting vma->vm_flags |= VM_LOCKED. Not sure why...
>
> Signed-off-by: David Woodhouse
Reviewed-by: David Howells
On Wed, Apr 12, 2017 at 10:39:47AM -0700, Paul E. McKenney wrote:
> CONFIG_ARCH_WEAK_RELACQ Kconfig option.
Naming in the changelog and patch don't match.
> +config ARCH_WEAK_RELEASE_ACQUIRE
> + bool
> +
On Tue, 11 Apr 2017 13:31:16 +0300 Adrian Hunter wrote:
> On 11/04/17 13:20, Jisheng Zhang wrote:
> > We found one issue on BG4CT platforms with GPIO for sdcar card detect
> > interrupt: remove sdcard when there's read write access to the sdcard,
> > sometimes the card remove event can't be handle
This resolves a checkpatch warning that "Single statement macros should
not use a do {} while (0) loop" by removing the loop and adjusting line
length accordingly.
Signed-off-by: Craig Inches
---
Changes in v2:
- Kept statements together
- Kept operator on previous line
.../lustre/inclu
1 - 100 of 830 matches
Mail list logo
