On Thu, 29 Mar 2018 18:24:31 +0100
Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in message text
>
> Signed-off-by: Colin Ian King
Oops, thanks!
Acked-by: Masami Hiramatsu
> ---
> tools/testing/selftests/ftrace/test.d/trigger/trigger-multihist.tc | 2 +-
>
On 2 April 2018 at 04:30, Jia He wrote:
> This is the preparation for further optimizing in early_pfn_valid
> on arm and arm64.
>
Same as before
- please share the code between ARM and arm64. if necessary, you can
invent a new HAVE_ARCH_xxx symbol that is only defined by ARM and
arm64
- please ex
On 2 April 2018 at 04:30, Jia He wrote:
> This api is the preparation for further optimizing early_pfn_valid
>
Please add more explanatation here of what it is you are doing and why.
> Signed-off-by: Jia He
> ---
> include/linux/memblock.h | 2 ++
> mm/memblock.c| 9 +
> 2
Linus,
Please pull the latest locking-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
locking-core-for-linus
# HEAD: 19193bcad8dced863f2f720b1a76110bda07c970 locking/Kconfig:
Restructure the lock debugging menu
The main changes in the locking subs
On 2 April 2018 at 04:30, Jia He wrote:
> Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
> where possible") optimized the loop in memmap_init_zone(). But there is
> still some room for improvement. E.g. if pfn and pfn+1 are in the same
> memblock region, we can simply pfn+
On 2 April 2018 at 04:30, Jia He wrote:
> Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
> where possible") optimized the loop in memmap_init_zone(). But it causes
> possible panic bug. So Daniel Vacek reverted it later.
>
> But as suggested by Daniel Vacek, it is fine to
Hi Johan,
On Mon, 2 Apr 2018 08:38:03 +0300 Johan Hedberg wrote:
>
> On Mon, Apr 02, 2018, Stephen Rothwell wrote:
> > 45a42bc9cc65 ("Bluetooth: hci_bcm: Remove DMI quirk for the MINIX Z83-4")
> > f9b95db0165a ("Bluetooth: btrsi: remove unused including
> > ")
> > 96e58d368fa6 ("Bluetooth:
Hi Ganesh,
On Mon, Apr 2, 2018 at 3:33 AM, Ganesh Mahendran
wrote:
> 2018-03-30 19:00 GMT+08:00 Geert Uytterhoeven :
>> On Fri, Mar 30, 2018 at 12:25 PM, Rafael J. Wysocki
>> wrote:
>>> On Monday, March 5, 2018 9:47:46 AM CEST Ganesh Mahendran wrote:
single_open() interface requires that t
On Mon, Apr 2, 2018 at 8:01 AM, Greentime Hu wrote:
>
> This tag contains the core nds32 Linux port(including interrupt controller
> driver and timer driver), which has been through 7 rounds of review on mailing
> list.
Reviewed-by:
2018-04-02 14:34 GMT+08:00 Minchan Kim :
> On Fri, Mar 30, 2018 at 12:04:07PM +0200, Greg Kroah-Hartman wrote:
>> On Fri, Mar 30, 2018 at 10:29:21AM +0900, Minchan Kim wrote:
>> > Hi Ganesh,
>> >
>> > On Fri, Mar 30, 2018 at 09:21:55AM +0800, Ganesh Mahendran wrote:
>> > > 2018-03-29 14:54 GMT+08:0
On Sun, 01 Apr 2018 17:20:30 +0100
Ben Hutchings wrote:
> On Mon, 2018-03-19 at 19:05 +0100, Greg Kroah-Hartman wrote:
> > 4.4-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Masami Hiramatsu
> >
> >
> > [ Upstream commit d0381
On Sun, Apr 01, 2018 at 02:48:54PM -0700, Eric Biggers wrote:
> [+Cc linux-nfs]
> >
> > [ 42.965515] net/sunrpc/rpc_pipe.c: __rpc_create_common failed to
> > allocate inode for dentry blocklayout
> > [ 42.967234] net/sunrpc/rpc_pipe.c: rpc_mkpipe_dentry() failed to create
> > pipe nfs/blockl
Hi Neil,
On 2018/4/1 13:44, Neil Leeder wrote:
> Hi Yisheng Xie,
>
> On 3/29/2018 03:03 AM, Yisheng Xie wrote:
>>
>> Hi Neil,
>>
>> On 2017/8/5 3:59, Neil Leeder wrote:
>>> +mem_resource_0 = platform_get_resource(pdev, IORESOURCE_MEM, 0);
>>> +mem_map_0 = devm_ioremap_resource(&pdev->dev,
Hi Bjorn,
On 3/27/2018 11:19 PM, Bjorn Andersson wrote:
> On Fri 23 Mar 03:18 PDT 2018, Sricharan R wrote:
>
>> Reviewed-by: Abhishek Sahu
>> Signed-off-by: Sricharan R
>> ---
>> arch/arm64/boot/dts/qcom/ipq8074-hk01.dts | 103
>> ++
>> 1 file changed, 103 inserti
On 3/27/2018 11:16 PM, Bjorn Andersson wrote:
> On Fri 23 Mar 03:18 PDT 2018, Sricharan R wrote:
>
>> The driver/phy support for ipq8074 is available now.
>> So enabling the nodes in DT.
>>
>
> Acked-by: Bjorn Andersson
>
Thanks.
Regards,
Sricharan
> Regards,
> Bjorn
>
>> Reviewed-by:
On 3/27/2018 11:15 PM, Bjorn Andersson wrote:
> On Fri 23 Mar 03:18 PDT 2018, Sricharan R wrote:
>> +serial_blsp0: serial@78af000 {
>
> Please try to have a single scheme for how you name your labels; this is
> serial0 or blsp1_uart1.
>
> [..]
>> +i2c_0: i2c@78b6000 {
>
On Fri, Mar 30, 2018 at 12:04:07PM +0200, Greg Kroah-Hartman wrote:
> On Fri, Mar 30, 2018 at 10:29:21AM +0900, Minchan Kim wrote:
> > Hi Ganesh,
> >
> > On Fri, Mar 30, 2018 at 09:21:55AM +0800, Ganesh Mahendran wrote:
> > > 2018-03-29 14:54 GMT+08:00 Minchan Kim :
> > > > binder_update_page_rang
On 26-03-18, 16:52, Suman Anna wrote:
> Commit 05829d9431df ("cpufreq: ti-cpufreq: kfree opp_data when
> failure") has fixed a memory leak in the failure path, however
> kmemleak still keeps reporting a leak even on successful probes.
> This is a false-positive and is mostly a result of the opp_dat
On Fri, Mar 23, 2018 at 03:48:49PM +0530, Sricharan R wrote:
> Reviewed-by: Abhishek Sahu
> Signed-off-by: Sricharan R
> ---
> arch/arm/boot/dts/Makefile | 1 +
> arch/arm/boot/dts/qcom-ipq4019-ap.dk04.1-c1.dts | 20
> 2 files changed, 21 insertions(+)
Linus,
Please pull the latest core-rcu-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-rcu-for-linus
# HEAD: c4fb5f37001514c0004d17b79cf74a499b9bc320 Merge branch 'for-mingo' of
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu into co
Linus,
Please pull the latest core-headers-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
core-headers-for-linus
# HEAD: 562c45d635ecd5c0648ceb4d4aff9bdc1ad91252 headers: Drop two #included
headers from
A single change that drops two #includes from a
Linus,
Please pull the latest core-debugobjects-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
core-debugobjects-for-linus
# HEAD: 163cf842f5837334bc69aaf09ad38e11f4573914 debugobjects: Avoid another
unused variable warning
Misc improvements:
- add
Linus,
Please pull the latest core-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-core-for-linus
# HEAD: 5ad751053704df3f00d2bb2dc9345c697c212150 panic: Add closing panic
marker parenthesis
Two changes:
- add membarriers to Documentation/fe
Hi David,
I love your patch! Yet something to improve:
[auto build test ERROR on v4.16-rc7]
[cannot apply to linus/master tip/x86/core tip/locking/core v4.16 next-20180329]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github
Hi Bjorn,
On 3/27/2018 10:59 PM, Bjorn Andersson wrote:
> On Fri 23 Mar 03:18 PDT 2018, Sricharan R wrote:
>
>> Reviewed-by: Abhishek Sahu
>> Signed-off-by: Sricharan R
>> ---
>> arch/arm/boot/dts/Makefile | 1 +
>> arch/arm/boot/dts/qcom-ipq4019-ap.dk07.1-c2.dts | 26
>>
Hi David,
I love your patch! Yet something to improve:
[auto build test ERROR on v4.16-rc7]
[cannot apply to linus/master tip/x86/core tip/locking/core v4.16 next-20180329]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github
Hi David,
I love your patch! Yet something to improve:
[auto build test ERROR on v4.16-rc7]
[cannot apply to linus/master tip/x86/core tip/locking/core v4.16 next-20180329]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github
Hi David,
I love your patch! Yet something to improve:
[auto build test ERROR on v4.16-rc7]
[cannot apply to linus/master tip/x86/core tip/locking/core v4.16 next-20180329]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github
On 3/27/2018 10:52 PM, Bjorn Andersson wrote:
> On Fri 23 Mar 03:18 PDT 2018, Sricharan R wrote:
>> +#include "qcom-ipq4019-ap.dk07.1.dtsi"
>> +
>> +/ {
>> +model = "Qualcomm Technologies, Inc. IPQ4019/AP-DK07.1-C1";
>
> Add compatible for the board.
>
ok.
Regards,
Sricharan
--
"QUALC
On 3/27/2018 10:50 PM, Bjorn Andersson wrote:
> On Fri 23 Mar 03:18 PDT 2018, Sricharan R wrote:
>> +#include "qcom-ipq4019.dtsi"
>> +#include
>> +#include
>> +
>> +/ {
>> +model = "Qualcomm Technologies, Inc. IPQ4019/AP-DK07.1";
>> +compatible = "qcom,ipq4019";
>
> The board should se
Hello,
>> (Added cover letter to avoid much text in patch description)
>>
>> LZ4 specification defines 2 byte offset length for 64 KB data.
>> But in case of ZRAM we compress data per page and in most of
>> architecture PAGE_SIZE is 4KB. So we can decide offset length based
>> on actual offset
On 2018/4/2 13:29, Sergey Senozhatsky wrote:
On (04/02/18 13:14), wen.yan...@zte.com.cn wrote:
> It's true that this print for the same device is useless. But it's
> useful for different devices. Is it possible to limit the print only
> for the same device?
In our scene, it's
On 3/27/2018 10:44 PM, Bjorn Andersson wrote:
> On Fri 23 Mar 03:18 PDT 2018, Sricharan R wrote:
>> +#include "qcom-ipq4019-ap.dk04.1.dtsi"
>> +
>> +/ {
>> +model = "Qualcomm Technologies, Inc. IPQ4019/AP-DK04.1-C3";
>
> Add a compatible to the board file.
>
ok.
> Also, things like alias
Hi,
>> diff --git a/drivers/block/zram/zcomp.c b/drivers/block/zram/zcomp.c
>> index 4ed0a78..5bc5aab 100644
>> --- a/drivers/block/zram/zcomp.c
>> +++ b/drivers/block/zram/zcomp.c
>> @@ -17,11 +17,15 @@
>> #include
>>
>> #include "zcomp.h"
>> +#define KB(1 << 10)
>>
>> static cons
On 2018/4/2 13:14, wen.yan...@zte.com.cn wrote:
Hello,
> It's true that this print for the same device is useless. But it's
> useful for different devices. Is it possible to limit the print only
> for the same device?
In our scene, it's just for the same device (q->queuedata), Thanks.
The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
are available in the Git repository at:
ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/greentime/linux.git
tags/nds32-for-linus-4.17
for you to fetch changes up
Hello,
syzbot hit the following crash on upstream commit
10b84daddbec72c6b440216a69de9a9605127f7a (Sat Mar 31 17:59:00 2018 +)
Merge branch 'perf-urgent-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=4859f
Hello,
syzbot hit the following crash on upstream commit
10b84daddbec72c6b440216a69de9a9605127f7a (Sat Mar 31 17:59:00 2018 +)
Merge branch 'perf-urgent-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=d9046
Hello,
syzbot hit the following crash on upstream commit
10b84daddbec72c6b440216a69de9a9605127f7a (Sat Mar 31 17:59:00 2018 +)
Merge branch 'perf-urgent-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=230d9
Hello,
syzbot hit the following crash on upstream commit
10b84daddbec72c6b440216a69de9a9605127f7a (Sat Mar 31 17:59:00 2018 +)
Merge branch 'perf-urgent-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=f3ce7
lots of application will read /proc/stat, like ps and vmstat, but we
find the reading time are spreading on Purley platform which has lots
of possible CPUs and interrupt.
To reduce the reading time, only scan the present CPUs, not all possible
CPUs, which speeds the reading of /proc/stat 20 times
Hi,
On Mon, Apr 02, 2018, Stephen Rothwell wrote:
> 45a42bc9cc65 ("Bluetooth: hci_bcm: Remove DMI quirk for the MINIX Z83-4")
> f9b95db0165a ("Bluetooth: btrsi: remove unused including ")
> 96e58d368fa6 ("Bluetooth: Set HCI_QUIRK_SIMULTANEOUS_DISCOVERY for
> BTUSB_QCA_ROME")
> 9ea471320e1
Hi,
On Wednesday 28 March 2018 05:08 PM, Gustavo Pimentel wrote:
> Adds the designware EP device ID entry to pci_endpoint_test driver table
> to allow this device to be recognize and handle by the pci_endpoint_test
> driver.
>
> Signed-off-by: Gustavo Pimentel
> ---
> drivers/misc/pci_endpoint_
On Wednesday 28 March 2018 05:08 PM, Gustavo Pimentel wrote:
> Signed-off-by: Gustavo Pimentel
Please add a commit message.
> ---
> Documentation/devicetree/bindings/pci/designware-pcie.txt | 13 +
> 1 file changed, 13 insertions(+)
>
> diff --git a/Documentation/devicetree/bindin
Hi Bjorn,
On 3/27/2018 10:42 PM, Bjorn Andersson wrote:
> On Fri 23 Mar 03:18 PDT 2018, Sricharan R wrote:
>> +#include "qcom-ipq4019-ap.dk04.1.dtsi"
>> +
>> +/ {
>> +model = "Qualcomm Technologies, Inc. IPQ4019/AP-DK04.1-C1";
>> +
>
> If this is the board and qcom-ipq4019-ap.dk04.1.dtsi is t
Hi,
On Wednesday 28 March 2018 05:08 PM, Gustavo Pimentel wrote:
> The PCIe controller dual mode is capable of operating in host mode as well
> as endpoint mode by configuration, therefore this patch aims to add
> endpoint mode support to the designware driver.
>
> Signed-off-by: Gustavo Pimentel
From: Rao Shoaib
kfree_call_rcu does not belong in linux/rcupdate.h and should be moved to
slab_common.c
Signed-off-by: Rao Shoaib
---
include/linux/rcupdate.h | 43 +++
include/linux/rcutree.h | 2 --
include/linux/slab.h | 42
From: Rao Shoaib
kfree_rcu() should use the new kfree_bulk() interface for freeing
rcu structures as it is more efficient.
Signed-off-by: Rao Shoaib
---
include/linux/mm.h | 5 ++
include/linux/rcutiny.h | 8 ++-
kernel/sysctl.c | 40
mm/slab.h | 2
From: Rao Shoaib
This patch moves kfree_call_rcu() out of rcu related code to
mm/slab_common and updates kfree_rcu() to use new bulk memory free
functions as they are more efficient.
This is a resubmission of the previous patch.
Changes:
1) checkpatch.pl has been fixed, so kfree_rcu macro is m
On (04/02/18 13:14), wen.yan...@zte.com.cn wrote:
>
>> It's true that this print for the same device is useless. But it's
>> useful for different devices. Is it possible to limit the print only
>> for the same device?
>
>In our scene, it's just for the same device (q->queuedata),
On 3/27/2018 10:34 PM, Bjorn Andersson wrote:
> On Fri 23 Mar 03:18 PDT 2018, Sricharan R wrote:
>> +soc {
>> +pinctrl@100 {
>> +serial_0_pins: serial0_pinmux {
>
> Please, no underscores in the node name.
ok.
>
>> +mux {
>
Hi Bjorn,
Thanks a lot for all the reviews.
On 3/27/2018 10:20 PM, Bjorn Andersson wrote:
> On Fri 23 Mar 03:18 PDT 2018, Sricharan R wrote:
>> @@ -172,6 +180,22 @@
>> clock-names = "core", "iface";
>> #address-cells = <1>;
>> #size-
Hi,
On Wednesday 28 March 2018 05:08 PM, Gustavo Pimentel wrote:
> Changes the IP registers size to accommodate the ATU unroll space.
>
> Replaces "ctrlreg" reg-name by "dbi" to be coherent with similar drivers.
>
> Replaces the pcie base address example by a real pcie base address in use.
>
>
On Thursday 29 March 2018 12:36 AM, Sean Paul wrote:
Ensure that any queued events are issued when disabling the crtc. This
avoids timeouts when we come back and wait for dependencies (like the
previous frame's flip_done).
Reviewed-by: Archit Taneja
Changes in v2:
- None
Signed-off-by: S
On Thursday 29 March 2018 12:36 AM, Sean Paul wrote:
Don't leave the event != NULL once it's consumed, this is used a signal
s/used a/used as a ?
to the atomic helpers that the event will be handled by the driver.
Reviewed-by: Archit Taneja
Changes in v2:
- None
Cc: Jeykumar Sankaran
On Thursday 29 March 2018 12:36 AM, Sean Paul wrote:
Factor out the commit_tail() portions of complete_commit() into a
separate function to facilitate moving to the atomic helpers in future
patches.
Reviewed-by: Archit Taneja
Changes in v2:
- None
Cc: Jeykumar Sankaran
Signed-off-by: Se
On Thursday 29 March 2018 12:36 AM, Sean Paul wrote:
Now that we have private state handled by the core, we can use those
instead of rolling our own swap_state for private data.
Originally posted here: https://patchwork.freedesktop.org/patch/211361/
Changes in v2:
- Use state->state in disp
On 04/01/2018 11:31 AM, Anton Gary Ceph wrote:
> As the Linux networking stack is growing, more and more protocols are
> added, increasing the complexity of stack itself.
> Modern processors, contrary to common belief, are very bad in branch
> prediction, so it's our task to give hints to the com
Hi David,
I love your patch! Yet something to improve:
[auto build test ERROR on v4.16-rc7]
[cannot apply to linus/master tip/x86/core tip/locking/core v4.16 next-20180329]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github
On Thu, Mar 29, 2018 at 04:57:22PM -0500, Alan Tull wrote:
> On Mon, Mar 26, 2018 at 9:35 PM, Wu Hao wrote:
>
> Hi Hao,
>
> Currently there is one set of functions that handles port enable,
> disable, and reset and it's in dfl.c and dfl.h, so that's not in any
> driver module that can be switche
On 3/29/2018 4:22 AM, Doug Anderson wrote:
Hi,
On Wed, Mar 28, 2018 at 6:08 AM, Vijay Viswanath
wrote:
During probe check whether the vdd-io regulator of sdhc platform device
can support 1.8V and 3V and store this information as a capability of
platform device.
Signed-off-by: Vijay Viswanat
2018-03-30 18:44 GMT+09:00 Kunihiko Hayashi :
> Pro4 SoC has clock lines for Giga-bit feature and ethernet phy,
> and these are mandatory to activate the ethernet controller. This adds
> support for the clock lines.
>
> Signed-off-by: Kunihiko Hayashi
> ---
Acked-by: Masahiro Yamada
--
Be
2018-03-30 18:44 GMT+09:00 Kunihiko Hayashi :
> Add clock control for SATA controller on UniPhier SoCs. This adds
> support for PXs2, LD20 and PXs3.
>
> Signed-off-by: Kunihiko Hayashi
> ---
Acked-by: Masahiro Yamada
--
Best Regards
Masahiro Yamada
On Mon, Apr 02 2018, Sean Wang wrote:
> On Mon, 2018-04-02 at 09:34 +1000, NeilBrown wrote:
>> On Thu, Mar 29 2018, Chris Coffey wrote:
>>
>> > This fixes the following sparse warning:
>> >
>> > drivers/staging/mt7621-eth/ethtool.c:213:6: warning: symbol
>> > 'mtk_set_ethtool_ops' was not declare
2018-03-30 18:44 GMT+09:00 Kunihiko Hayashi :
> Add reset lines for SATA controller on UniPhier SoCs.
> This adds support for Pro4 and PXs3 in addition to PXs2.
>
> And this changes the ID of the reset line for SATA-PHY on PXs2.
> Since some SoCs have two controller instances with a common PHY, thi
2018-03-30 18:44 GMT+09:00 Kunihiko Hayashi :
> Add clock control for PCIe controller on UniPhier SoCs. This adds
> support for Pro5, LD20 and PXs3.
>
> Signed-off-by: Kunihiko Hayashi
> ---
Acked-by: Masahiro Yamada
--
Best Regards
Masahiro Yamada
2018-03-30 18:44 GMT+09:00 Kunihiko Hayashi :
> Add reset lines for PCIe controller on UniPhier SoCs. This adds support for
> Pro5, LD20 and PXs3.
>
> Signed-off-by: Kunihiko Hayashi
> ---
Acked-by: Masahiro Yamada
--
Best Regards
Masahiro Yamada
This patch is used to tell the kernel that newer Centaur CPU support CMCI.
Signed-off-by: David Wang
---
arch/x86/kernel/cpu/mcheck/mce.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/kernel/cpu/mcheck/mce.c b/arch/x86/kernel/cpu/mcheck/mce.c
index c3db7ce..361d95e 100644
--- a/ar
This patch set is to provide MCA support on new Centaur CPU.
The first patch is used to tell the kernel that newer Centaur CPU
support MCE broadcasting.
The second patch is used to tell the kernel that newer Centaur
CPU support CMCI.
Changes from v1 to v2:
* Capatilize 'Centaur' in the comments
This patch is used to tell the kernel that newer Centaur CPU support
MCE broadcasting.
Signed-off-by: David Wang
---
arch/x86/kernel/cpu/mcheck/mce.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/x86/kernel/cpu/mcheck/mce.c b/arch/x86/kernel/cpu/mcheck/mce.c
index 7065846
Current suspend/resume implementation reuses the mvneta_open() and
mvneta_close(), but it could be optimized to take only necessary
actions during suspend/resume.
One obvious problem of current implementation is: after hundreds of
system suspend/resume cycles, the resume of mvneta could fail due t
This is to prepare the suspend/resume improvement in next patch. The
SW parts can be optimized out during resume.
As for rxq handling during suspend, we'd like to drop packets by
calling mvneta_rxq_drop_pkts() which is both SW and HW operation,
so we don't split rxq deinit.
Signed-off-by: Jisheng
This series tries to optimize the mvneta's suspend/resume
implementation by only taking necessary actions.
Since v2:
- keep rtnl lock when calling mvneta_start_dev() and mvneta_stop_dev()
Thank Russell for pointing this out
Since v1:
- unify ret check
- try best to keep the suspend/resume b
FYI, we noticed the following commit (built with gcc-7):
commit: 42658d54ce4d9c25c8a286651c60cbc869f2f91e ("list_lru: Add memcg argument
to list_lru_from_kmem()")
url:
https://github.com/0day-ci/linux/commits/Kirill-Tkhai/Improve-shrink_slab-scalability-old-complexity-was-O-n-2-new-is-O-n/20180
On Mon, 2018-04-02 at 09:34 +1000, NeilBrown wrote:
> On Thu, Mar 29 2018, Chris Coffey wrote:
>
> > This fixes the following sparse warning:
> >
> > drivers/staging/mt7621-eth/ethtool.c:213:6: warning: symbol
> > 'mtk_set_ethtool_ops' was not declared. Should it be static?
> >
> > Signed-off-by:
On 30/03/2018 10:53, jiangyiwen wrote:
> Currently, I found virtio-9p in VirtFS don't support "O_DIRECT + aio"
> mode, both v9fs and qemu. So when user use "O_DIRECT + aio" mode and
> increase iodepths, they can't get higher IOPS.
>
> I want to know why v9fs don't implement this mode? And I will t
Hi, Yang,
On 2018/4/2 9:58, Wen Yang wrote:
There would be so many same lines printed by frequent printk if one
disk went wrong, like,
[ 546.185242] sd 0:1:0:0: rejecting I/O to offline device
[ 546.185258] sd 0:1:0:0: rejecting I/O to offline device
[ 546.185280] sd 0:1:0:0: rejecting I/O to
From: Ralph Campbell
Use of pte_write(pte) is only valid for present pte, the common code
which set the migration entry can be reach for both valid present
pte and special swap entry (for device memory). Fix the code to use
the mpfn value which properly handle both cases.
On x86 this did not hav
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") optimized the loop in memmap_init_zone(). But there is
still some room for improvement. E.g. in early_pfn_valid(), if pfn and
pfn+1 are in the same memblock region, we can record the last returned
memblock regi
This is the preparation for further optimizing in early_pfn_valid
on arm and arm64.
Signed-off-by: Jia He
---
arch/arm/include/asm/page.h | 3 ++-
arch/arm/mm/init.c| 24
arch/arm64/include/asm/page.h | 3 ++-
arch/arm64/mm/init.c | 24 ++
This api is the preparation for further optimizing early_pfn_valid
Signed-off-by: Jia He
---
include/linux/memblock.h | 2 ++
mm/memblock.c| 9 +
2 files changed, 11 insertions(+)
diff --git a/include/linux/memblock.h b/include/linux/memblock.h
index 0257aee..a0127b3 100644
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") tried to optimize the loop in memmap_init_zone(). But
there is still some room for improvement.
Patch 1 remain the memblock_next_valid_pfn on arm and arm64
Patch 2 optimizes the memblock_next_valid_pfn()
Patch
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") optimized the loop in memmap_init_zone(). But there is
still some room for improvement. E.g. if pfn and pfn+1 are in the same
memblock region, we can simply pfn++ instead of doing the binary search
in memblock_
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") optimized the loop in memmap_init_zone(). But it causes
possible panic bug. So Daniel Vacek reverted it later.
But as suggested by Daniel Vacek, it is fine to using memblock to skip
gaps and finding next valid
Hi all,
Commits
45a42bc9cc65 ("Bluetooth: hci_bcm: Remove DMI quirk for the MINIX Z83-4")
f9b95db0165a ("Bluetooth: btrsi: remove unused including ")
96e58d368fa6 ("Bluetooth: Set HCI_QUIRK_SIMULTANEOUS_DISCOVERY for
BTUSB_QCA_ROME")
9ea471320e13 ("Bluetooth: Mark expected switch fall-th
On Fri, 30 Mar 2018 15:59:32 +0200 Andrew Lunn wrote:
> On Fri, Mar 30, 2018 at 11:02:11AM +0800, Jisheng Zhang wrote:
> > Synaptics has acquired the Multimedia Solutions Business of Marvell[1].
> > So change the berlin entry name and move it to its alphabetical
> > location. We move to ARM/Synapt
Hey,
I am sorry to encroach into your privacy in this manner, I want to solicit your
attention to assist me receive two (2) trunk boxes on my behalf.
I am an Army officer with the USA Military and currently in Baghdad with the
Combat Support Squad, US Base Camp, Speicher - Baghdad, Iraq. I am
From: Florian Fainelli
Date: Sun, 1 Apr 2018 10:26:28 -0700
> This patch series fixes a couple of warnings reported by sparse, should not
> cause any functional problems since bgmac is typically used on LE platforms
> anyway.
Series applied, thanks Florian.
Hello,
On (04/02/18 09:58), Wen Yang wrote:
> There would be so many same lines printed by frequent printk if one
> disk went wrong, like,
> [ 546.185242] sd 0:1:0:0: rejecting I/O to offline device
> [ 546.185258] sd 0:1:0:0: rejecting I/O to offline device
> [ 546.185280] sd 0:1:0:0: rejecti
On (04/02/18 10:54), Sergey Senozhatsky wrote:
> > > If you forward the report, please keep this part and the footer.
> > >
> > > llcp: nfc_llcp_send_ui_frame: Could not allocate PDU
> > > llcp: nfc_llcp_send_ui_frame: Could not allocate PDU
> > > llcp: nfc_llcp_send_ui_frame: Could not allocate PD
There would be so many same lines printed by frequent printk if one
disk went wrong, like,
[ 546.185242] sd 0:1:0:0: rejecting I/O to offline device
[ 546.185258] sd 0:1:0:0: rejecting I/O to offline device
[ 546.185280] sd 0:1:0:0: rejecting I/O to offline device
[ 546.185307] sd 0:1:0:0: rej
On 3/26/18 11:29 PM, Michal Hocko wrote:
On Tue 27-03-18 02:20:39, Yang Shi wrote:
[...]
The patch looks reasonable to me. Maybe it would be better to be more
explicit about the purpose of the patch. As others noticed, this alone
wouldn't solve the mmap_sem contention issues. I _think_ that if
On (04/01/18 12:52), Dmitry Vyukov wrote:
>
> Seems to be the same as:
>
> #syz dup: INFO: rcu detected stall in vprintk_func
>
> +nfc maintainers
Yes, seems to be the same issue.
-ss
On (04/01/18 10:56), Richard Weinberger wrote:
> As the printk subsystem gains more and more popularity it is time to add
> the final missing feature to make it perfect, namely cowsay output.
> Currently only one type of cow is supported and the only user is kmsg,
> but I can see more use cases for
On (04/01/18 12:51), Dmitry Vyukov wrote:
[..]
> > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > Reported-by: syzbot+3f28bd18291266ec8...@syzkaller.appspotmail.com
> > It will help syzbot understand when the bug is fixed. See footer for
> > details.
> > If you forwa
2018-03-30 19:00 GMT+08:00 Geert Uytterhoeven :
> On Fri, Mar 30, 2018 at 12:25 PM, Rafael J. Wysocki
> wrote:
>> On Monday, March 5, 2018 9:47:46 AM CEST Ganesh Mahendran wrote:
>>> single_open() interface requires that the whole output must
>>> fit into a single buffer. This will lead to timeou
2018-03-30 18:25 GMT+08:00 Rafael J. Wysocki :
> On Monday, March 5, 2018 9:47:46 AM CEST Ganesh Mahendran wrote:
>> single_open() interface requires that the whole output must
>> fit into a single buffer. This will lead to timeout when
>> system memory is not in a good situation.
>>
>> This patch
From: Kai-Heng Feng
Date: Sat, 31 Mar 2018 23:42:03 +0800
> The sky2 ethernet stops working after system resume from suspend:
> [ 582.852065] sky2 :04:00.0: Refused to change power state, currently in
> D3
>
> The current 150ms delay is not enough, change it to 200ms can solve the
> issue.
On Sat, Mar 31, 2018 at 5:42 AM, Steven Rostedt wrote:
> On Fri, 30 Mar 2018 17:30:31 -0400
> Steven Rostedt wrote:
>
>> I'll take a look at si_mem_available() that Joel suggested and see if
>> we can make that work.
>
> Wow, this appears to work great! Joel and Zhaoyang, can you test this?
>
> -
Yes, I'm also seeing good performance improvement after adding
likely() and prefetch().
On Sun, Apr 1, 2018 at 2:50 PM, Stephen Hemminger
wrote:
> On Sun, 1 Apr 2018 20:31:21 +0200
> Anton Gary Ceph wrote:
>
>> As the Linux networking stack is growing, more and more protocols are
>> added, incr
1 - 100 of 275 matches
Mail list logo
