Simplify netvsvc pointer graph by getting rid of the redundant ndev
pointer. We can always get a pointer to struct net_device from somewhere
else.
Signed-off-by: Vitaly Kuznetsov
---
drivers/net/hyperv/hyperv_net.h | 5 +--
drivers/net/hyperv/netvsc.c | 36 +++-
drivers/net/
We have the following structures keeping netvsc adapter state:
- struct net_device
- struct net_device_context
- struct netvsc_device
- struct rndis_device
- struct hv_device
and there are pointers/dependencies between them:
- struct net_device_context is contained in struct net_device
- struct hv_
Crash in netvsc_send() is observed when netvsc device is re-created on
mtu change/set channels. The crash is caused by dereferencing of NULL
channel pointer which comes from chn_table. The root cause is a mixture
of two facts:
- we set nvdev pointer in net_device_context in alloc_net_device()
bef
netvsc_link_change() can race with netvsc_change_mtu() or
netvsc_set_channels() as these functions destroy struct netvsc_device and
rndis filter. Use start_remove flag for syncronization. As
netvsc_change_mtu()/netvsc_set_channels() are called with rtnl lock held
we need to take it before checking
Changes since v1:
- Rebased to net-next [Haiyang Zhang]
Original description:
MTU change and set channels operations are implemented as netvsc device
re-creation destroying internal structures (struct net_device stays). This
is really unfortunate but there is no support from Hyper-V host to do it
On Tue, Apr 26, 2016 at 01:01:05PM -0500, Andreas Dannenberg wrote:
> On Tue, Apr 26, 2016 at 06:29:36PM +0100, Mark Brown wrote:
> > Is the device actually going to mess up if someone sends it something
> > else or is it just going to ignore the extra bits (given that it's doing
> > autodetection
When netvsc device is removed during mtu change or channels setup we get
into troubles as both paths are trying to remove the device. Synchronize
them with start_remove flag and rtnl lock.
Signed-off-by: Vitaly Kuznetsov
---
drivers/net/hyperv/netvsc_drv.c | 9 +++--
1 file changed, 7 insert
struct netvsc_device is destroyed on mtu change so keeping the
protection flag there is not a good idea. Move it to struct
net_device_context which is preserved.
Signed-off-by: Vitaly Kuznetsov
---
drivers/net/hyperv/hyperv_net.h | 4 +++-
drivers/net/hyperv/netvsc.c | 3 +--
drivers/net/h
On Fri 13-05-16 11:52:30, Sebastian Frias wrote:
> Hi,
>
> On 05/13/2016 10:44 AM, Mason wrote:
> > On 13/05/2016 10:04, Michal Hocko wrote:
> >
> >> On Tue 10-05-16 13:56:30, Sebastian Frias wrote:
> >> [...]
> >>> NOTE: I understand that the overcommit mode can be changed dynamically
> >>> thr
This series is to improve the pxa168_eth driver performance by using
{readl|writel}_relaxed or appropriate memory barriers.
Jisheng Zhang (2):
net: pxa168_eth: use {readl|writel}_relaxed instead of readl/writel
net: pxa168_eth: Use dma_wmb/rmb where appropriate
drivers/net/ethernet/marvell/p
Since appropriate memory barriers are already there, use the relaxed
version to improve performance a bit.
Signed-off-by: Jisheng Zhang
---
drivers/net/ethernet/marvell/pxa168_eth.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/marvell/pxa168_eth.c
Update the mv643xx_eth driver to use the dma_rmb/wmb calls instead of
the full barriers in order to improve performance.
Signed-off-by: Jisheng Zhang
---
drivers/net/ethernet/marvell/mv643xx_eth.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/net/ethernet
Hi Krzysztof,
On 10/05/16 21:09, Krzysztof Kozlowski wrote:
Hi,
Patchset adds necessary clocks, reorganizes existing stuff and finally
adds Odroid XU support.
Changes since v2
1. Got global-ack from Stephen for the clock changes. I think merging
everything through arm-soc
Update the pxa168_eth driver to use the dma_rmb/wmb calls instead of the
full barriers in order to improve performance: reduced 97ns/39ns on
average in tx/rx path on Marvell BG4CT platform.
Signed-off-by: Jisheng Zhang
---
drivers/net/ethernet/marvell/pxa168_eth.c | 8
1 file changed, 4
This series is to improve the mv643xx_eth driver performance by using
{readl|writel}_relaxed or appropriate memory barriers.
Since I have no mv643xx_eth platforms, tests are appreciated!
Jisheng Zhang (2):
net: mv643xx_eth: use {readl|writel}_relaxed instead of readl/writel
net: mv643xx_eth:
Since appropriate memory barriers are already there, use the relaxed
version to improve performance a bit.
Signed-off-by: Jisheng Zhang
---
drivers/net/ethernet/marvell/mv643xx_eth.c | 33 +++---
1 file changed, 17 insertions(+), 16 deletions(-)
diff --git a/drivers/net/
On Wed 05-11-16 09:53:00, Michal Hocko wrote:
> Yes I think this makes sense. The only case where it would be suboptimal
> is when the pagevec was already full and then we just created a single
> page pvec to drain it. This can be handled better though by:
>
> diff --git a/mm/swap.c b/mm/swap.c
>
On Fri 13-05-16 10:23:31, Vlastimil Babka wrote:
> On 05/12/2016 06:20 PM, Michal Hocko wrote:
> > On Tue 10-05-16 09:35:56, Vlastimil Babka wrote:
> > [...]
> > > diff --git a/include/linux/gfp.h b/include/linux/gfp.h
> > > index 570383a41853..0cb09714d960 100644
> > > --- a/include/linux/gfp.h
>
debug_stat sysfs is read-only and represents various debugging
data that zram developers may need. This file is not meant to be
used by anyone else: its content is not documented and will change
any time w/o any notice. Therefore, the output of debug_stat file
contains a version string. To avoid an
Add the macro _GNU_SOURCE, so that compilation does not terminate.
Signed-off-by: Muhammad Falak R Wani
---
tools/testing/selftests/intel_pstate/run.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/intel_pstate/run.sh
b/tools/testing/selftests/intel
On Friday 13 May 2016 19:59:19 Jisheng Zhang wrote:
> /* port register accessors
> **/
> static inline u32 rdl(struct mv643xx_eth_private *mp, int offset)
> {
> - return readl(mp->shared->base + offset);
> + return readl_relaxed(mp->shared
Hi,
Baolin Wang writes:
>>> diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h
>>> index 6254b2f..dada5c6 100644
>>> --- a/drivers/usb/dwc3/core.h
>>> +++ b/drivers/usb/dwc3/core.h
>>> @@ -734,6 +734,9 @@ struct dwc3_scratchpad_array {
>>> * 1 - -3.5dB de-emphasis
>>> *
On 05/13/2016 02:03 PM, Robin Murphy wrote:
> Hi Krzysztof,
>
> On 10/05/16 21:09, Krzysztof Kozlowski wrote:
>> Hi,
>>
>> Patchset adds necessary clocks, reorganizes existing stuff and finally
>> adds Odroid XU support.
>>
>>
>> Changes since v2
>>
>> 1. Got global-ack from Steph
On Fri, May 6, 2016 at 2:45 PM, Andrey Ryabinin wrote:
> When bogus memory access happens in mem[set,cpy,move]() it's usually
> caller's fault. So don't blame mem[set,cpy,move]() in bug report, blame
> the caller instead.
>
> Before:
> BUG: KASAN: out-of-bounds access in memset+0x23/0x40 a
Greetings!
It is my pleasure to meet your acquaintance and hope your are in good health.
This is to inform you that Bear Medic Corporation Ltd requires immediate
services of an efficient Individual/Company Representative in your area. This
is a work from home/office job opportunity(a job you
On 13/05/2016 13:44, Michal Hocko wrote:
> Anyway, this is my laptop where I do not run anything really special
> (xfce, browser, few consoles, git, mutt):
> $ grep Commit /proc/meminfo
> CommitLimit: 3497288 kB
> Committed_AS:3560804 kB
>
> I am running with the default overcommit setup
On Fri, May 13, 2016 at 01:22:38PM +0530, Purna Chandra Mandal wrote:
Thanks for resolving the remaining issues. As per discussion of the
last version I've now queued the entire series for 4.7.
One step closer to full PIC32MZDA in-tree support!
Ralf
On Fri, May 6, 2016 at 2:45 PM, Andrey Ryabinin wrote:
> Memory access coded in an assembly won't be seen by KASAN as a compiler
> can instrument only C code. Add kasan_check_[read,write]() API
> which is going to be used to check a certain memory range.
>
> Signed-off-by: Andrey Ryabinin
> Cc: A
On Fri, May 13, 2016 at 02:37:21PM +0300, Adrian Hunter wrote:
> + cc some Marvell people because they added this code
>
> On 13/05/16 12:27, Ludovic Desroches wrote:
> > Activating wakeup event is not enough to get a wakeup signal. The
> > corresponding events have to be enabled in the Interrupt
From: Jan Kara
Currently, printk() sometimes waits for message to be printed to console
and sometimes it does not (when console_sem is held by some other
process). In case printk() grabs console_sem and starts printing to
console, it prints messages from kernel printk buffer until the buffer
is e
From: Jan Kara
Offload printing of scheduler deferred messages from IRQ context
to a schedulable printing kthread, when possible (the same way we
do it in vprintk_emit()). Otherwise, the CPU can spend unbounded
amount of time doing printing in console_unlock() from IRQ.
Signed-off-by: Sergey Sen
Change `synchronous' printk param to be RW, so user space
can change printk mode back and forth to/from sync mode
(which is considered to be more reliable).
Signed-off-by: Sergey Senozhatsky
Reviewed-by: Jan Kara
Reviewed-by: Petr Mladek
---
kernel/printk/printk.c | 56
stead of 'direct' printing the actual print
job is performed by a dedicated kthread. This has the advantage
that printing always happens from a schedulable context and thus
we don't lockup any particular CPU or even interrupts.
against next-20160513
v12:
-- rename printk_kthre
Dear Arnd,
On Fri, 13 May 2016 14:09:43 +0200 Arnd Bergmann wrote:
> On Friday 13 May 2016 19:59:19 Jisheng Zhang wrote:
> > /* port register accessors
> > **/
> > static inline u32 rdl(struct mv643xx_eth_private *mp, int offset)
> > {
> > - r
On 11/05/16 18:59, Javier Martinez Canillas wrote:
> The IS_ENABLED() macro checks if a Kconfig symbol has been enabled either
> built-in or as a module, use that macro instead of open coding the same.
>
> Signed-off-by: Javier Martinez Canillas
> ---
>
> drivers/video/fbdev/via/accel.c| 2
When the DMA configuration fails, there is a log reporting that we can't
use DMA and indicating the error number. When booting the kernel, it is
annoying to see this error number. Moreover, people can think something
is going wrong. It is not the case, it means that DMA can't be used but
it doesn't
Le 12/05/2016 16:54, Ludovic Desroches a écrit :
> An unexpected value of CUBC can lead to a corrupted residue. A more
> complex sequence is needed to detect an inaccurate value for NCA or CUBC.
>
> Signed-off-by: Ludovic Desroches
> Fixes: e1f7c9eee707 ("dmaengine: at_xdmac: creation of the atme
Le 12/05/2016 16:54, Ludovic Desroches a écrit :
> Having descriptors aligned on 64 bits allows update CNDA and CUBC in an
> atomic way.
>
> Signed-off-by: Ludovic Desroches
> Fixes: e1f7c9eee707 ("dmaengine: at_xdmac: creation of the atmel
> eXtended DMA Controller driver")
> Cc: sta...@vger.ker
Le 12/05/2016 16:54, Ludovic Desroches a écrit :
> Due to the way CUBC register is updated, a double flush is needed to
> compute an accurate residue. First flush aim is to get data from the DMA
> FIFO and second one ensures that we won't report data which are not in
> memory.
>
> Signed-off-by: L
If c->cdev->use_os_string flag is not set,
don't need to invoke ffs_do_os_descs() in _ffs_func_bind.
So uninitialized ext_compat_id pointer won't be accessed by
__ffs_func_bind_do_os_desc to cause kernel panic.
Signed-off-by: Jim Lin
---
drivers/usb/gadget/function/f_fs.c | 18 ++
On 13 May 2016 at 20:09, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h
index 6254b2f..dada5c6 100644
--- a/drivers/usb/dwc3/core.h
+++ b/drivers/usb/dwc3/core.h
@@ -734,6 +734,9 @@ struct dwc3_scratchpad
Hi Enric!
On Fri, May 06, 2016 at 11:02:34PM +0200, Enric Balletbo i Serra wrote:
> A host device that supports write protection should refuse to write to
> an SD card that is designated read-only when write-protect is set. This
> is an optional feature of the SD specification.
Does it ever work
On Tue 10-05-16 09:35:57, Vlastimil Babka wrote:
> In the context of direct compaction, for some types of allocations we would
> like the compaction to either succeed or definitely fail while trying as hard
> as possible. Current async/sync_light migration mode is insufficient, as there
> are heuri
The patch
spi: pic32-sqi: Fix linker error, undefined reference to `bad_dma_ops'.
has been applied to the spi tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
Hi Michal,
On 05/13/2016 02:00 PM, Michal Hocko wrote:
> On Fri 13-05-16 11:52:30, Sebastian Frias wrote:
>>
>> By the way, do you know what's the rationale to allow this setting to
>> be controlled by the userspace dynamically? Was it for testing only?
>
> Dunno, but I guess the default might b
(Adding linux-wireless)
Rafał Miłecki writes:
> On 26 January 2016 at 16:06, Andreas Ziegler wrote:
>> your commit 399500da18f7 ("ssb: pick PCMCIA host code support from b43
>> driver") removed the Kconfig option B43_PCMCIA from Kconfig, but left
>> one reference to it in b43/main.c, inside the
Hi,
Baolin Wang writes:
why does it need restart? Why is dwc3 powered off? Who powers it off?
>>>
>>> Because when the dwc3 Vbus is off (no cable pluging in now),
>>> especially for some mobile device, the system need to power off the
>>> dwc3 to save power in this situation.
>>
>> but dwc3
On 13/05/16 15:19, Ludovic Desroches wrote:
> On Fri, May 13, 2016 at 02:37:21PM +0300, Adrian Hunter wrote:
>> + cc some Marvell people because they added this code
>>
>> On 13/05/16 12:27, Ludovic Desroches wrote:
>>> Activating wakeup event is not enough to get a wakeup signal. The
>>> correspon
Hello.
On 5/13/2016 8:56 AM, Ethan Zhao wrote:
Allocating 64 Tx/Rx as default doesn't benefit perfomrnace when less
Performance.
CPUs were assigned. especially when DCB is enabled, so we should take
num_online_cpus() as top limit, and aslo to make sure every TC has
Also.
at least
On Fri, 2016-05-13 at 16:19 +0800, Yisen Zhuang wrote:
> From: Kejian Yan
>
> hns-mdio needs to register itself to mii-bus. The info of the device
> can
> be read by both OF and ACPI.
> HNS tries to call Linux PHY driver to help access PHY-devices, the HNS
> hardware topology is as below. The MDI
On Fri, 2016-05-13 at 16:19 +0800, Yisen Zhuang wrote:
> From: Kejian Yan
>
> As device_node is only used by OF case, it is expected to find uniform
> ways. So fwnode_handle is the suitable method.
Yeah, and this is part of conversion to fwnode, see previous comment.
>
> Signed-off-by: Kejian
Em Fri, May 13, 2016 at 07:55:58AM +, Wang Nan escreveu:
> Extract event reader to __perf_evlist__mmap_read(). Future commit will
> feed it with manually computed 'head' and 'old' pointers.
why not use the perf_mmap__read() directly then?
- Arnaldo
> Signed-off-by: Wang Nan
> Cc: Arnaldo C
Em Fri, May 13, 2016 at 07:55:59AM +, Wang Nan escreveu:
> In this commit sereval helpers are introduced to support the principle
several
> of channel. Channels hold different groups of evsels which configured
> differently. It will be used for overwritable evsels, which allo
On Fri, 2016-05-13 at 16:19 +0800, Yisen Zhuang wrote:
> From: Kejian Yan
>
> As device_node is only used by OF case, HNS needs to treat the others
> cases including ACPI. It needs to use uniform ways to handle both of
> OF and ACPI. This patch chooses phy_device, and of_phy_connect and
> of_phy_
Em Fri, May 13, 2016 at 07:56:06AM +, Wang Nan escreveu:
> Detect avalibility of write_backward and save the result into
> record_opts. With write_backward the start pointer of a ring
> buffer mapped read only can be found reliably.
We have perf_missing_features for that, please try to use it.
On Tue 10-05-16 09:35:58, Vlastimil Babka wrote:
> Async compaction detects contention either due to failing trylock on
> zone->lock
> or lru_lock, or by need_resched(). Since 1f9efdef4f3f ("mm, compaction:
> khugepaged should not give up due to need_resched()") the code got quite
> complicated to
On 2016-05-13 08:39, Sebastian Frias wrote:
On 05/13/2016 02:00 PM, Michal Hocko wrote:
On Fri 13-05-16 11:52:30, Sebastian Frias wrote:
From what I remember, one of the LTP maintainers said that it is
highly unlikely people test (or run LTP for that matter) with
different settings for overcom
On Monday 09 May 2016 02:42 PM, Jose Abreu wrote:
> Can you apply this to arc-next? Main driver was already merged into clk-next.
> We
> still have to check how to deal with the parent clock frequency that will
> change
> in the next firmware release.
Done ! although note that this might *not* b
Having multiple loadable modules with the same name cannot work
with modprobe, and having both net/qrtr/smd.ko and drivers/soc/qcom/smd.ko
results in a (somewhat cryptic) build error:
ERROR: "qcom_smd_driver_unregister" [net/qrtr/smd.ko] undefined!
ERROR: "qcom_smd_driver_register" [net/qrtr/smd.k
On Fri, 2016-05-13 at 16:19 +0800, Yisen Zhuang wrote:
> From: Kejian Yan
>
> Dsaf needs to get configuration parameter by ACPI, so this patch add
> support of ACPI.
>
Looks like at some point better to split driver to core part, and PCI
and ACPI/DT/platform code.
Too many changes where IS_ENA
Em Fri, May 13, 2016 at 07:56:05AM +, Wang Nan escreveu:
> There's no need to receive events from overwritable ring buffer. Instead,
> perf should make them run background until something happen. This patch
> makes normal events from overwrite ring buffer ignored.
>
> Signed-off-by: Wang Nan
On Fri, 2016-05-13 at 16:19 +0800, Yisen Zhuang wrote:
> From: Hanjun Guo
>
> acpi_match_device_ids() will be used for drivers to match
> different hardware versions, it will be compiled in non-ACPI
> case, but acpi_match_device_ids() in acpi_bus.h and it can
> only be used in ACPI case, so move
Activating wakeup event is not enough to get a wakeup signal. The
corresponding events have to be enabled in the Interrupt Status Enable
Register too.
Signed-off-by: Ludovic Desroches
---
Hi,
I just updated sdhci_enable_irq_wakeups() not sdhci_disable_irq_wakeups()
because I don't think it is ne
Activating wakeup event is not enough to get a wakeup signal. The
corresponding events have to be enabled in the Interrupt Status Enable
Register too. It follows the specification and is needed at least by
sdhci-of-at91.
Signed-off-by: Ludovic Desroches
---
drivers/mmc/host/sdhci.c | 15
Mistake while sending v2, sorry for the noise.
On Fri, May 13, 2016 at 03:14:46PM +0200, Ludovic Desroches wrote:
> Activating wakeup event is not enough to get a wakeup signal. The
> corresponding events have to be enabled in the Interrupt Status Enable
> Register too.
>
> Signed-off-by: Ludovic
On Fri, May 13, 2016 at 10:09:52AM +0200, Borislav Petkov wrote:
> Try this one better - it fixes an unitialized var.
Instead, or in addiiton?
Greetings
Marc
--
-
Marc Haber | "I don't trust Computers. They | Ma
On Tue 10-05-16 09:35:59, Vlastimil Babka wrote:
> A recent patch has added whole_zone flag that compaction sets when scanning
> starts from the zone boundary, in order to report that zone has been fully
> scanned in one attempt. For allocations that want to try really hard or cannot
> fail, we wil
On 2016-05-13 06:18, Mason wrote:
On 13/05/2016 11:52, Michal Hocko wrote:
On Fri 13-05-16 10:44:30, Mason wrote:
On 13/05/2016 10:04, Michal Hocko wrote:
On Tue 10-05-16 13:56:30, Sebastian Frias wrote:
[...]
NOTE: I understand that the overcommit mode can be changed dynamically thru
sysctl
On Fri, May 13, 2016 at 09:28:03AM +, Catalin Marinas wrote:
> > >On Thu, May 12, 2016 at 03:20:00AM +0300, Yury Norov wrote:
> > >>I debugged preadv02 and pwritev02 failures and found very weird bug.
> > >>Test passes {iovec_base = 0x, iovec_len = 64} as one element
> > >>>
Hi Austin,
On 05/13/2016 03:11 PM, Austin S. Hemmelgarn wrote:
> On 2016-05-13 08:39, Sebastian Frias wrote:
>> Well, a more urgent problem would be that in that case overcommit=never is
>> not really well tested.
> I know more people who use overcommit=never than overcommit=always. I use it
>
From: Steven Rostedt
The introduction of switch_mm_irqs_off() brought back an old bug
regarding the use of preempt_enable_no_resched:
As part of 62b94a08da1b ("sched/preempt: Take away
preempt_enable_no_resched() from modules"), the definition of
preempt_enable_no_resched() is only available in
Hi Austin,
On 05/13/2016 03:11 PM, Austin S. Hemmelgarn wrote:
> On 2016-05-13 08:39, Sebastian Frias wrote:
>>
>> My point is that it seems to be possible to deal with such conditions in a
>> more controlled way, ie: a way that is less random and less abrupt.
> There's an option for the OOM-kill
On Tue 10-05-16 09:36:01, Vlastimil Babka wrote:
> During reclaim/compaction loop, it's desirable to get a final answer from
> unsuccessful compaction so we can either fail the allocation or invoke the OOM
> killer. However, heuristics such as deferred compaction or pageblock skip bits
> can cause
Hi Arnaldo,
On Fri, May 13, 2016 at 08:48:48AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, May 13, 2016 at 03:01:01PM +0900, Namhyung Kim escreveu:
> > The commit 140aeadc1fb5 ("perf stat: Abstract stat metrics printing")
> > changed way to print shadow metrics, but it missed to update the wi
On 05/12/2016 10:49 PM, Huacai Chen wrote:
I'll send a patch, but it seems be ignored by maintainer.
https://patchwork.linux-mips.org/patch/13136/
It is marked as accepted, so it should be in Ralf's queue.
Thanks,
Guenter
Huacai
On Fri, May 13, 2016 at 11:46 AM, Guenter Roeck wrote:
On 0
On Thursday 12 May 2016 23:32:18 John Youn wrote:
>
> Hi Arnd,
>
> The capitalization issue is still there in this patch.
>
> There's also a few checkpatch issues.
Fixed now, thanks. I'll send a v4 in a bit.
> And should the barrier be moved after the write like it says in the
> comment? That
On 12.05.2016 16:06, Konstantin Khlebnikov wrote:
On 10.05.2016 20:20, Konstantin Khlebnikov wrote:
On 10.05.2016 19:36, Tejun Heo wrote:
Hello,
On Tue, May 10, 2016 at 07:28:08PM +0300, Konstantin Khlebnikov wrote:
On 10.05.2016 11:21, Konstantin Khlebnikov wrote:
I've got plenty warnings,
On 2016-05-13 09:32, Sebastian Frias wrote:
Hi Austin,
On 05/13/2016 03:11 PM, Austin S. Hemmelgarn wrote:
On 2016-05-13 08:39, Sebastian Frias wrote:
Well, a more urgent problem would be that in that case overcommit=never is not
really well tested.
I know more people who use overcommit=neve
On 05/13/2016 06:30 AM, Arnd Bergmann wrote:
From: Steven Rostedt
The introduction of switch_mm_irqs_off() brought back an old bug
regarding the use of preempt_enable_no_resched:
As part of 62b94a08da1b ("sched/preempt: Take away
preempt_enable_no_resched() from modules"), the definition of
pr
Replace hex flags with human-readable symbols from arm-gic.h header
which makes it easier to recognize what is configured.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm64/boot/dts/exynos/exynos7.dtsi | 13 +
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/arch/arm64/b
A patch that went into Linux-4.4 to fix big-endian mode on a Lantiq
MIPS system unfortunately broke big-endian operation on PowerPC
APM82181 as reported by Christian Lamparter, and likely other
systems.
It actually introduced multiple issues:
- it broke big-endian ARM kernels: any machine that wa
On my system, simply enabling and disabling function graph tracer can
crash the kernel. I don't know how it worked until now.
The ftrace_disable_ftrace_graph_caller() modifies jmp instruction at
ftrace_graph_call assuming it's a 5 bytes near jmp (e9 ).
However it's a short jmp consisting of 2 byt
The newly added stm32_pconf_dbg_show function has an incorrect format
string that does not match the arguments, as reported by the gcc warning:
drivers/pinctrl/stm32/pinctrl-stm32.c: In function 'stm32_pconf_dbg_show':
drivers/pinctrl/stm32/pinctrl-stm32.c:797:17: error: too many arguments for
fo
This patch adds the platform driver for the Amlogic Meson GXBB Reset
Controller.
Signed-off-by: Neil Armstrong
---
drivers/reset/Kconfig| 6 ++
drivers/reset/Makefile | 1 +
drivers/reset/reset-meson-gxbb.c | 160 +++
3 files changed,
Add DT bindings for the Meson GXBB SoC Reset Controller documentation and the
associated include file.
Signed-off-by: Neil Armstrong
---
.../bindings/reset/amlogic,meson-gxbb-reset.txt| 16 +++
.../dt-bindings/reset/amlogic,meson-gxbb-reset.h | 160 +
2 files changed,
On Fri, May 13, 2016 at 03:01:01PM +0900, Namhyung Kim wrote:
> The commit 140aeadc1fb5 ("perf stat: Abstract stat metrics printing")
> changed way to print shadow metrics, but it missed to update the width
> of stalled backend cycles event to 7.2% like others. This resulted in
> misaligned output
Update DTSI file to add the reset controller node.
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
index 832815d..2b8
Matt,
This bug looks very similar to what you were hitting with the function
profiler. Can you apply this patch and see if it fixes the issue for
you.
Thanks!
-- Steve
On Fri, 13 May 2016 22:53:43 +0900
Namhyung Kim wrote:
> On my system, simply enabling and disabling function graph tracer c
On Fri, May 13, 2016 at 09:35:45AM +0100, Dr. David Alan Gilbert wrote:
> also between 4.4 and 4.5 it did seem worth mentioning as a long shot,
> but it was no more than a long shot.
It was however helpful. I'd have bisected kernel configuration instead
of using the runtime control first, and seei
Hi,
On Fri, May 13, 2016 at 09:15:38AM +0300, Ivaylo Dimitrov wrote:
> I prefer the shorter "nokia,n900-ir", will resend the series with
> it used, unless someone has concerns about it.
Sounds fine to me.
-- Sebastian
signature.asc
Description: PGP signature
On Fri 13-05-16 14:15:35, Mason wrote:
> On 13/05/2016 13:44, Michal Hocko wrote:
>
> > Anyway, this is my laptop where I do not run anything really special
> > (xfce, browser, few consoles, git, mutt):
> > $ grep Commit /proc/meminfo
> > CommitLimit: 3497288 kB
> > Committed_AS:3560804 kB
Patchset to add and enable the reset controller driver on GXBB platforms.
Neil Armstrong (3):
reset: Add support for the Amlogic Meson GXBB Reset Controller
dt-bindings: reset: Add bindings for the Meson GXBB Reset Controller
ARM64: dts: amlogic: Enable Reset Controller on GXBB-based platfor
On May 13, 2016 2:42 AM, "Dr. Greg Wettstein" wrote:
>
> On Sun, May 08, 2016 at 06:32:10PM -0700, Andy Lutomirski wrote:
>
> Good morning, running behind on e-mail this week but wanted to get
> some reflections out on Andy's well taken comments and concerns.
>
> > On May 8, 2016 2:59 AM, "Dr. Gre
Mark, please see below...
On Fri, May 13, 2016 at 12:55:40PM +0100, Mark Brown wrote:
> On Tue, Apr 26, 2016 at 01:01:05PM -0500, Andreas Dannenberg wrote:
> > On Tue, Apr 26, 2016 at 06:29:36PM +0100, Mark Brown wrote:
>
> > > Is the device actually going to mess up if someone sends it something
On 2016-05-13 09:34, Sebastian Frias wrote:
Hi Austin,
On 05/13/2016 03:11 PM, Austin S. Hemmelgarn wrote:
On 2016-05-13 08:39, Sebastian Frias wrote:
My point is that it seems to be possible to deal with such conditions in a more
controlled way, ie: a way that is less random and less abrupt
Hi Michal,
On 05/13/2016 04:01 PM, Michal Hocko wrote:
> On Fri 13-05-16 14:15:35, Mason wrote:
>> On 13/05/2016 13:44, Michal Hocko wrote:
>>
>>> Anyway, this is my laptop where I do not run anything really special
>>> (xfce, browser, few consoles, git, mutt):
>>> $ grep Commit /proc/meminfo
>>>
On Tue 10-05-16 09:36:02, Vlastimil Babka wrote:
> During reclaim/compaction loop, compaction priority can be increased by the
> should_compact_retry() function, but the current code is not optimal for
> several reasons:
>
> - priority is only increased when compaction_failed() is true, which mean
Commit-ID: ef0491ea17f8019821c7e9c8e801184ecf17f85a
Gitweb: http://git.kernel.org/tip/ef0491ea17f8019821c7e9c8e801184ecf17f85a
Author: Steven Rostedt
AuthorDate: Fri, 13 May 2016 15:30:13 +0200
Committer: Ingo Molnar
CommitDate: Fri, 13 May 2016 16:12:53 +0200
ARM: Hide finish_arch_pos
On 12/05/16 11:26, Jacek Anaszewski wrote:
On 05/11/2016 03:42 PM, Tony Makkiel wrote:
On 11/05/16 10:41, Jacek Anaszewski wrote:
On 05/10/2016 06:55 PM, Tony Makkiel wrote:
On 10/05/16 14:26, Jacek Anaszewski wrote:
On 05/10/2016 11:36 AM, Tony Makkiel wrote:
On 09/05/16 15:45, Jace
On Thu, 12 May 2016, Vikram Mulukutla wrote:
> preempt_disable();
> /* --cut, lots of code-- */
> preempt_enable_no_resched();
> put_user()
> preempt_disable();
>
> (If you wish to seriously question the usage of the preempt API in this
> manner, I unfortunately have no comment since I didn't writ
201 - 300 of 541 matches
Mail list logo
