linux-next: Tree for Mar 30

Hi all, Changes since 20170329: Undropped tree: xen-tip The vfs tree gained a conflict against Linus' tree. The drm tree gained conflicts against the drm-intel-fixes tree. The mailbox tree lost its build failure. The phy-next tree gained a build failure, so I used the version from next

linux-next: Tree for Mar 30

Hi all, Changes since 20170329: Undropped tree: xen-tip The vfs tree gained a conflict against Linus' tree. The drm tree gained conflicts against the drm-intel-fixes tree. The mailbox tree lost its build failure. The phy-next tree gained a build failure, so I used the version from next

Re: [PATCH v8 3/3] printk: fix double printing with earlycon

On (03/28/17 14:56), Petr Mladek wrote: [..] > > > Is it better? If not, I will send a version with console_cmdline_last. > > > > personally I'm fine with the nested loop. the latest version > > "for (last = MAX_CMDLINECONSOLES - 1; last >= 0;..." > > > > is even easier to read. > > The

Re: [PATCH v8 3/3] printk: fix double printing with earlycon

On (03/28/17 14:56), Petr Mladek wrote: [..] > > > Is it better? If not, I will send a version with console_cmdline_last. > > > > personally I'm fine with the nested loop. the latest version > > "for (last = MAX_CMDLINECONSOLES - 1; last >= 0;..." > > > > is even easier to read. > > The

Re: [PATCH v4 19/23] drivers/fsi: Add GPIO based FSI master

On Thu, Mar 30, 2017 at 4:13 AM, Christopher Bostic wrote: > From: Chris Bostic > > Implement a FSI master using GPIO. Will generate FSI protocol for > read and write commands to particular addresses. Sends master command > and waits for

Re: [PATCH v4 19/23] drivers/fsi: Add GPIO based FSI master

On Thu, Mar 30, 2017 at 4:13 AM, Christopher Bostic wrote: > From: Chris Bostic > > Implement a FSI master using GPIO. Will generate FSI protocol for > read and write commands to particular addresses. Sends master command > and waits for and decodes a slave response. > > Includes changes from

Re: [REGRESSION 4.11] Commit d8514d8edb5b ("ovl: copy up regular file using O_TMPFILE") breaks ubifs

Hi Richard, On Thu, 30 Mar 2017 00:15:31 +0200 Richard Weinberger wrote: > Ralph, > > Am 29.03.2017 um 23:26 schrieb Ralph Sennhauser: > >> # create and link a tmpfile - then remove it > >> sudo rm -rf foo; sudo xfs_io -T -c "flink foo" . ; ls -l foo; sudo > >> rm foo > > >

Re: [REGRESSION 4.11] Commit d8514d8edb5b ("ovl: copy up regular file using O_TMPFILE") breaks ubifs

Hi Richard, On Thu, 30 Mar 2017 00:15:31 +0200 Richard Weinberger wrote: > Ralph, > > Am 29.03.2017 um 23:26 schrieb Ralph Sennhauser: > >> # create and link a tmpfile - then remove it > >> sudo rm -rf foo; sudo xfs_io -T -c "flink foo" . ; ls -l foo; sudo > >> rm foo > > > > next-20170328,

[PATCH v2 3/4] zram: make deduplication feature optional

From: Joonsoo Kim Benefit of deduplication is dependent on the workload so it's not preferable to always enable. Therefore, make it optional in Kconfig and device param. Default is 'off'. This option will be beneficial for users who use the zram as blockdev and stores

[PATCH v2 4/4] zram: compare all the entries with same checksum for deduplication

From: Joonsoo Kim Until now, we compare just one entry with same checksum when checking duplication since it is the simplest way to implement. However, for the completeness, checking all the entries is better so this patch implement to compare all the entries with same

Re: [PATCH net-next] virtio_net: don't reset twice on XDP on/off

On 2017年03月30日 04:14, Michael S. Tsirkin wrote: We already do a reset once in remove_vq_common - there appears to be no point in doing another one when we add/remove XDP. Signed-off-by: Michael S. Tsirkin --- drivers/net/virtio_net.c | 1 - 1 file changed, 1 deletion(-)

[PATCH v2 3/4] zram: make deduplication feature optional

From: Joonsoo Kim Benefit of deduplication is dependent on the workload so it's not preferable to always enable. Therefore, make it optional in Kconfig and device param. Default is 'off'. This option will be beneficial for users who use the zram as blockdev and stores build output to it.

[PATCH v2 4/4] zram: compare all the entries with same checksum for deduplication

From: Joonsoo Kim Until now, we compare just one entry with same checksum when checking duplication since it is the simplest way to implement. However, for the completeness, checking all the entries is better so this patch implement to compare all the entries with same checksum. Since this event

Re: [PATCH net-next] virtio_net: don't reset twice on XDP on/off

On 2017年03月30日 04:14, Michael S. Tsirkin wrote: We already do a reset once in remove_vq_common - there appears to be no point in doing another one when we add/remove XDP. Signed-off-by: Michael S. Tsirkin --- drivers/net/virtio_net.c | 1 - 1 file changed, 1 deletion(-) diff --git

[PATCH v2 1/4] zram: introduce zram_entry to prepare dedup functionality

From: Joonsoo Kim Following patch will implement deduplication functionality in the zram and it requires an indirection layer to manage the life cycle of zsmalloc handle. To prepare that, this patch introduces zram_entry which can be used to manage the life-cycle of

[PATCH v2 2/4] zram: implement deduplication in zram

From: Joonsoo Kim This patch implements deduplication feature in zram. The purpose of this work is naturally to save amount of memory usage by zram. Android is one of the biggest users to use zram as swap and it's really important to save amount of memory usage. There is

[PATCH v2 1/4] zram: introduce zram_entry to prepare dedup functionality

From: Joonsoo Kim Following patch will implement deduplication functionality in the zram and it requires an indirection layer to manage the life cycle of zsmalloc handle. To prepare that, this patch introduces zram_entry which can be used to manage the life-cycle of zsmalloc handle. Many lines

[PATCH v2 2/4] zram: implement deduplication in zram

From: Joonsoo Kim This patch implements deduplication feature in zram. The purpose of this work is naturally to save amount of memory usage by zram. Android is one of the biggest users to use zram as swap and it's really important to save amount of memory usage. There is a paper that reports

[PATCH v2 0/4] zram: implement deduplication in zram

From: Joonsoo Kim Changes from v1 o reogranize dedup specific functions o support Kconfig on/off o update zram documents o compare all the entries with same checksum (patch #4) This patchset implements deduplication feature in zram. Motivation is to save memory usage by

[PATCH v2 0/4] zram: implement deduplication in zram

From: Joonsoo Kim Changes from v1 o reogranize dedup specific functions o support Kconfig on/off o update zram documents o compare all the entries with same checksum (patch #4) This patchset implements deduplication feature in zram. Motivation is to save memory usage by zram. There are detailed

Re: linux-next: build failure after merge of the phy-next tree

> ffa0c278e89c ("phy: rockchip-inno-usb2: add support of u2phy for rk3328") > > I have used the phy-next tree from next-20170329 for today. Thanks for reporting this. Will fix it in my tree. -Kishon

Re: linux-next: build failure after merge of the phy-next tree

> ffa0c278e89c ("phy: rockchip-inno-usb2: add support of u2phy for rk3328") > > I have used the phy-next tree from next-20170329 for today. Thanks for reporting this. Will fix it in my tree. -Kishon

Re: [PATCH] phy: rockchip-inno-usb2: fix spelling mistake: "connecetd" -> "connected"

On Thursday 23 February 2017 05:00 AM, Colin King wrote: > From: Colin Ian King > > trivial fix to spelling mistake in dev_dbg message, also rejoin > lines to clean up checkpatch warning > > Signed-off-by: Colin Ian King merged, thanks.

Re: [PATCH] phy: rockchip-inno-usb2: fix spelling mistake: "connecetd" -> "connected"

On Thursday 23 February 2017 05:00 AM, Colin King wrote: > From: Colin Ian King > > trivial fix to spelling mistake in dev_dbg message, also rejoin > lines to clean up checkpatch warning > > Signed-off-by: Colin Ian King merged, thanks. -Kishon > --- > drivers/phy/phy-rockchip-inno-usb2.c

Re: [PATCH v2 2/2] mfd: axp20c-i2c: Select designware i2c-bus driver on x86

Hi Hans, [auto build test WARNING on ljones-mfd/for-mfd-next] [also build test WARNING on v4.11-rc4 next-20170329] [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/Hans-de-Goede/mfd

Re: [PATCH v2 2/2] mfd: axp20c-i2c: Select designware i2c-bus driver on x86

Hi Hans, [auto build test WARNING on ljones-mfd/for-mfd-next] [also build test WARNING on v4.11-rc4 next-20170329] [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/Hans-de-Goede/mfd

Re: [PATCH v2 2/2] mfd: axp20c-i2c: Select designware i2c-bus driver on x86

Hi Hans, [auto build test ERROR on ljones-mfd/for-mfd-next] [also build test ERROR on v4.11-rc4 next-20170329] [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/Hans-de-Goede/mfd-intel_soc_pmic

Re: [PATCH v2 2/2] mfd: axp20c-i2c: Select designware i2c-bus driver on x86

Hi Hans, [auto build test ERROR on ljones-mfd/for-mfd-next] [also build test ERROR on v4.11-rc4 next-20170329] [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/Hans-de-Goede/mfd-intel_soc_pmic

[PATCH] block: do not put mq context in blk_mq_alloc_request_hctx

In blk_mq_alloc_request_hctx, blk_mq_sched_get_request doesn't get sw context so we don't need to put the context with blk_mq_put_ctx. Unless, we will see preempt counter underflow. Cc: Sagi Grimberg Cc: Omar Sandoval Cc: Jens Axboe

Re: [PATCH v2] virtio_net: fix support for small rings

On 2017年03月30日 01:42, Michael S. Tsirkin wrote: When ring size is small (<32 entries) making buffers smaller means a full ring might not be able to hold enough buffers to fit a single large packet. Make sure a ring full of buffers is large enough to allow at least one packet of max size.

[PATCH] block: do not put mq context in blk_mq_alloc_request_hctx

In blk_mq_alloc_request_hctx, blk_mq_sched_get_request doesn't get sw context so we don't need to put the context with blk_mq_put_ctx. Unless, we will see preempt counter underflow. Cc: Sagi Grimberg Cc: Omar Sandoval Cc: Jens Axboe Signed-off-by: Minchan Kim --- Maybe, it would be fixed by

Re: [PATCH v2] virtio_net: fix support for small rings

On 2017年03月30日 01:42, Michael S. Tsirkin wrote: When ring size is small (<32 entries) making buffers smaller means a full ring might not be able to hold enough buffers to fit a single large packet. Make sure a ring full of buffers is large enough to allow at least one packet of max size.

Re: [v6 PATCH 00/21] x86: Enable User-Mode Instruction Prevention

On Wed, 2017-03-29 at 23:55 +0300, Stas Sergeev wrote: > 29.03.2017 07:38, Ricardo Neri пишет: > >> Probably you could also remove > >> the sldt and str emulation for protected mode, because, > >> as I understand from this thread, wine does not > >> need those. > > I see. I would lean on keeping

Re: [v6 PATCH 00/21] x86: Enable User-Mode Instruction Prevention

On Wed, 2017-03-29 at 23:55 +0300, Stas Sergeev wrote: > 29.03.2017 07:38, Ricardo Neri пишет: > >> Probably you could also remove > >> the sldt and str emulation for protected mode, because, > >> as I understand from this thread, wine does not > >> need those. > > I see. I would lean on keeping

Re: [PATCH 0/8] fujitsu-laptop: use sparse keymaps for input event handling

On Thu, Mar 30, 2017 at 02:26:26PM +1030, Jonathan Woithe wrote: > On Wed, Mar 29, 2017 at 08:36:50PM -0700, Darren Hart wrote: > > On Wed, Mar 29, 2017 at 07:35:50PM +0300, Andy Shevchenko wrote: > > > On Wed, Mar 29, 2017 at 10:19 AM, Micha?? K??pie?? > > > wrote: > > > > >

Re: [PATCH 0/8] fujitsu-laptop: use sparse keymaps for input event handling

On Thu, Mar 30, 2017 at 02:26:26PM +1030, Jonathan Woithe wrote: > On Wed, Mar 29, 2017 at 08:36:50PM -0700, Darren Hart wrote: > > On Wed, Mar 29, 2017 at 07:35:50PM +0300, Andy Shevchenko wrote: > > > On Wed, Mar 29, 2017 at 10:19 AM, Micha?? K??pie?? > > > wrote: > > > > > > > Darren, Andy,

Re: [PATCH v6 0/4] Broadcom SBA RAID support

On Wed, Mar 29, 2017 at 11:35:43AM +0530, Anup Patel wrote: > On Tue, Mar 21, 2017 at 2:48 PM, Vinod Koul wrote: > > On Tue, Mar 21, 2017 at 02:17:21PM +0530, Anup Patel wrote: > >> On Tue, Mar 21, 2017 at 2:00 PM, Vinod Koul wrote: > >> > On Mon, Mar

Re: [PATCH v6 0/4] Broadcom SBA RAID support

On Wed, Mar 29, 2017 at 11:35:43AM +0530, Anup Patel wrote: > On Tue, Mar 21, 2017 at 2:48 PM, Vinod Koul wrote: > > On Tue, Mar 21, 2017 at 02:17:21PM +0530, Anup Patel wrote: > >> On Tue, Mar 21, 2017 at 2:00 PM, Vinod Koul wrote: > >> > On Mon, Mar 06, 2017 at 03:13:24PM +0530, Anup Patel

Re: [PATCH v2 0/8] thermal: ti-soc-thermal: Migrate slope/offset data to device tree

On Thu, Mar 30, 2017 at 08:59:31AM +0530, Keerthy wrote: > > > On Wednesday 29 March 2017 10:07 AM, Eduardo Valentin wrote: > > Keerthy, > > > > On Fri, Mar 24, 2017 at 07:26:10AM -0700, Tony Lindgren wrote: > >> * Keerthy [170323 20:29]: > >>> > >>> > >>> On Friday 24 March

Re: [PATCH v2 0/8] thermal: ti-soc-thermal: Migrate slope/offset data to device tree

On Thu, Mar 30, 2017 at 08:59:31AM +0530, Keerthy wrote: > > > On Wednesday 29 March 2017 10:07 AM, Eduardo Valentin wrote: > > Keerthy, > > > > On Fri, Mar 24, 2017 at 07:26:10AM -0700, Tony Lindgren wrote: > >> * Keerthy [170323 20:29]: > >>> > >>> > >>> On Friday 24 March 2017 02:22 AM,

Re: [PATCH -mm -v7 4/9] mm, THP, swap: Add get_huge_swap_page()

Johannes Weiner writes: > On Tue, Mar 28, 2017 at 01:32:04PM +0800, Huang, Ying wrote: >> @@ -527,6 +527,23 @@ static inline swp_entry_t get_swap_page(void) >> >> #endif /* CONFIG_SWAP */ >> >> +#ifdef CONFIG_THP_SWAP_CLUSTER >> +static inline swp_entry_t

Re: [PATCH -mm -v7 4/9] mm, THP, swap: Add get_huge_swap_page()

Johannes Weiner writes: > On Tue, Mar 28, 2017 at 01:32:04PM +0800, Huang, Ying wrote: >> @@ -527,6 +527,23 @@ static inline swp_entry_t get_swap_page(void) >> >> #endif /* CONFIG_SWAP */ >> >> +#ifdef CONFIG_THP_SWAP_CLUSTER >> +static inline swp_entry_t get_huge_swap_page(void) >> +{ >> +

Re: [BUG nohz]: wrong user and system time accounting

On Wed, 2017-03-29 at 16:08 -0400, Rik van Riel wrote: > In other words, the tick on cpu0 is aligned > with the tick on the nohz_full cpus, and > jiffies is advanced while the nohz_full cpus > with an active tick happen to be in kernel > mode? You really want skew_tick=1, especially on big

Re: [BUG nohz]: wrong user and system time accounting

On Wed, 2017-03-29 at 16:08 -0400, Rik van Riel wrote: > In other words, the tick on cpu0 is aligned > with the tick on the nohz_full cpus, and > jiffies is advanced while the nohz_full cpus > with an active tick happen to be in kernel > mode? You really want skew_tick=1, especially on big

linux-next: build failure after merge of the vhost tree

) ctx ? ctx[i] : false); ^ Caused by commit a965e977a103 ("virtio: add context flag to find vqs") I have used the vhost tree from next-20170329 for today. -- Cheers, Stephen Rothwell

linux-next: build failure after merge of the vhost tree

) ctx ? ctx[i] : false); ^ Caused by commit a965e977a103 ("virtio: add context flag to find vqs") I have used the vhost tree from next-20170329 for today. -- Cheers, Stephen Rothwell

Re: [PATCH -mm -v7 9/9] mm, THP, swap: Delay splitting THP during swap out

Johannes Weiner writes: > On Tue, Mar 28, 2017 at 01:32:09PM +0800, Huang, Ying wrote: >> @@ -183,12 +184,53 @@ void __delete_from_swap_cache(struct page *page) >> ADD_CACHE_INFO(del_total, nr); >> } >> >> +#ifdef CONFIG_THP_SWAP_CLUSTER >> +int

Re: [PATCH -mm -v7 9/9] mm, THP, swap: Delay splitting THP during swap out

Johannes Weiner writes: > On Tue, Mar 28, 2017 at 01:32:09PM +0800, Huang, Ying wrote: >> @@ -183,12 +184,53 @@ void __delete_from_swap_cache(struct page *page) >> ADD_CACHE_INFO(del_total, nr); >> } >> >> +#ifdef CONFIG_THP_SWAP_CLUSTER >> +int add_to_swap_trans_huge(struct page *page,

Re: [PATCH v2] sd: Consider max_xfer_blocks if opt_xfer_blocks is unusable

On Wed, 03/29 22:37, Martin K. Petersen wrote: > Fam Zheng writes: > > Fam, > > > diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c > > index fcfeddc..a5c7e67 100644 > > --- a/drivers/scsi/sd.c > > +++ b/drivers/scsi/sd.c > > @@ -2957,6 +2957,7 @@ static int

Re: [PATCH v2] sd: Consider max_xfer_blocks if opt_xfer_blocks is unusable

On Wed, 03/29 22:37, Martin K. Petersen wrote: > Fam Zheng writes: > > Fam, > > > diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c > > index fcfeddc..a5c7e67 100644 > > --- a/drivers/scsi/sd.c > > +++ b/drivers/scsi/sd.c > > @@ -2957,6 +2957,7 @@ static int sd_revalidate_disk(struct gendisk

Re: [PATCH] zram: factor out partial IO routine

On (03/29/17 16:48), Minchan Kim wrote: > For architecture(PAGE_SIZE > 4K), zram have supported partial IO. > However, the mixed code for handling normal/partial IO is too mess, > error-prone to modify IO handler functions with upcoming feature > so this patch aims for cleaning up via factoring

Re: [PATCH] zram: factor out partial IO routine

On (03/29/17 16:48), Minchan Kim wrote: > For architecture(PAGE_SIZE > 4K), zram have supported partial IO. > However, the mixed code for handling normal/partial IO is too mess, > error-prone to modify IO handler functions with upcoming feature > so this patch aims for cleaning up via factoring

Re: spin_lock behavior with ARM64 big.Little/HMP

Hi Sudeep, Interesting. Just curious if this is r0p0/p1 A53 ? If so, is the errata 819472 enabled ? Sorry for bringing this up after the loo-ong delay, but I've been assured that the A53 involved is > r0p1. I've also confirmed this problem on multiple internal platforms, and I'm pretty

Re: spin_lock behavior with ARM64 big.Little/HMP

Hi Sudeep, Interesting. Just curious if this is r0p0/p1 A53 ? If so, is the errata 819472 enabled ? Sorry for bringing this up after the loo-ong delay, but I've been assured that the A53 involved is > r0p1. I've also confirmed this problem on multiple internal platforms, and I'm pretty

Re: [RFC PATCH 0/6] Unify the Interrupt Mode and setup it as soon as possible

On 03/30/17 at 11:09am, Dou Liyang wrote: > > > At 03/30/2017 11:03 AM, Dou Liyang wrote: > > Hi Baoquan, > > > > At 03/30/2017 10:08 AM, Baoquan He wrote: > > > Hi Liyang, > > > > > > This is awesome. I planned to do this after kaslr back porting, glad to > > > see your posting. I like below

Re: [RFC PATCH 0/6] Unify the Interrupt Mode and setup it as soon as possible

On 03/30/17 at 11:09am, Dou Liyang wrote: > > > At 03/30/2017 11:03 AM, Dou Liyang wrote: > > Hi Baoquan, > > > > At 03/30/2017 10:08 AM, Baoquan He wrote: > > > Hi Liyang, > > > > > > This is awesome. I planned to do this after kaslr back porting, glad to > > > see your posting. I like below

Re: [PATCH v9 10/15] ACPI: platform-msi: retrieve dev id from IORT

Hi all: 在 2017/3/30 11:07, Hanjun Guo 写道: > On 03/30/2017 01:32 AM, Lorenzo Pieralisi wrote: >> On Wed, Mar 29, 2017 at 05:13:54PM +0100, Lorenzo Pieralisi wrote: >>> On Wed, Mar 29, 2017 at 03:52:47PM +0100, Marc Zyngier wrote: On 29/03/17 14:00, Hanjun Guo wrote: > On 03/29/2017 08:38

Re: [PATCH v9 10/15] ACPI: platform-msi: retrieve dev id from IORT

Hi all: 在 2017/3/30 11:07, Hanjun Guo 写道: > On 03/30/2017 01:32 AM, Lorenzo Pieralisi wrote: >> On Wed, Mar 29, 2017 at 05:13:54PM +0100, Lorenzo Pieralisi wrote: >>> On Wed, Mar 29, 2017 at 03:52:47PM +0100, Marc Zyngier wrote: On 29/03/17 14:00, Hanjun Guo wrote: > On 03/29/2017 08:38

Re: [PATCH 4.8 50/96] firmware: fix usermode helper fallback loading

On Fri, Mar 24, 2017 at 04:01:58PM -0400, Ben Gamari wrote: > Greg Kroah-Hartman writes: > > > On Fri, Jan 06, 2017 at 10:54:38PM +0100, Yves-Alexis Perez wrote: > >> On Fri, 2017-01-06 at 22:43 +0100, Greg Kroah-Hartman wrote: > >> > 4.8-stable review patch.  If

Re: [PATCH 4.8 50/96] firmware: fix usermode helper fallback loading

On Fri, Mar 24, 2017 at 04:01:58PM -0400, Ben Gamari wrote: > Greg Kroah-Hartman writes: > > > On Fri, Jan 06, 2017 at 10:54:38PM +0100, Yves-Alexis Perez wrote: > >> On Fri, 2017-01-06 at 22:43 +0100, Greg Kroah-Hartman wrote: > >> > 4.8-stable review patch.  If anyone has any objections,

Re: [PATCH 1/8] platform/x86: fujitsu-laptop: move backlight input device setup to a separate function

On Wed, Mar 29, 2017 at 12:54:15PM -0700, Darren Hart wrote: > On Mon, Mar 20, 2017 at 10:32:17AM +0100, Micha?? K??pie?? wrote: > > + > > + return error; > > This return path could be cleaned up a bit: > > error = input_register_device(input); > if (error) >

Re: [PATCH 1/8] platform/x86: fujitsu-laptop: move backlight input device setup to a separate function

On Wed, Mar 29, 2017 at 12:54:15PM -0700, Darren Hart wrote: > On Mon, Mar 20, 2017 at 10:32:17AM +0100, Micha?? K??pie?? wrote: > > + > > + return error; > > This return path could be cleaned up a bit: > > error = input_register_device(input); > if (error) >

[PATCH] powerpc/prom: Increase RMA size to 512MB

>From 3ae8d1ed31b01b92b172fe20e4560cfbfab135ec Mon Sep 17 00:00:00 2001 From: root Date: Mon, 27 Mar 2017 19:43:14 -0400 Subject: [PATCH] powerpc/prom: Increase RMA size to 512MB When booting very large systems with a large initrd, we run out of space for

[PATCH] powerpc/prom: Increase RMA size to 512MB

>From 3ae8d1ed31b01b92b172fe20e4560cfbfab135ec Mon Sep 17 00:00:00 2001 From: root Date: Mon, 27 Mar 2017 19:43:14 -0400 Subject: [PATCH] powerpc/prom: Increase RMA size to 512MB When booting very large systems with a large initrd, we run out of space for either the RTAS or the flattened device

Re: [PATCH] virtio_net: enable big packets for large MTU values

On 2017年03月29日 20:38, Michael S. Tsirkin wrote: If one enables e.g. jumbo frames without mergeable buffers, packets won't fit in 1500 byte buffers we use. Switch to big packet mode instead. TODO: make sizing more exact, possibly extend small packet mode to use larger pages. Signed-off-by:

Re: [PATCH] virtio_net: enable big packets for large MTU values

On 2017年03月29日 20:38, Michael S. Tsirkin wrote: If one enables e.g. jumbo frames without mergeable buffers, packets won't fit in 1500 byte buffers we use. Switch to big packet mode instead. TODO: make sizing more exact, possibly extend small packet mode to use larger pages. Signed-off-by:

Re: lockdep warning: console vs. mem hotplug

On (03/28/17 16:22), Michal Hocko wrote: [..] > > Sebastian, does this change make lockdep happy? > > > > it removes console drivers from the __offline_isolated_pages(). not the > > best solution I can think of, but the simplest one. > > > > --- > > > > mm/page_alloc.c | 2 +- > > 1 file

Re: lockdep warning: console vs. mem hotplug

On (03/28/17 16:22), Michal Hocko wrote: [..] > > Sebastian, does this change make lockdep happy? > > > > it removes console drivers from the __offline_isolated_pages(). not the > > best solution I can think of, but the simplest one. > > > > --- > > > > mm/page_alloc.c | 2 +- > > 1 file

Re: [PATCH] virtio_net: fix mergeable bufs error handling

On 2017年03月29日 20:37, Michael S. Tsirkin wrote: On xdp error we try to free head_skb without having initialized it, that's clearly bogus. Fixes: f600b6905015 ("virtio_net: Add XDP support") Cc: John Fastabend Signed-off-by: Michael S. Tsirkin ---

Re: [PATCH] virtio_net: fix mergeable bufs error handling

On 2017年03月29日 20:37, Michael S. Tsirkin wrote: On xdp error we try to free head_skb without having initialized it, that's clearly bogus. Fixes: f600b6905015 ("virtio_net: Add XDP support") Cc: John Fastabend Signed-off-by: Michael S. Tsirkin --- drivers/net/virtio_net.c | 2 +- 1 file

Re: [PATCH 0/8] fujitsu-laptop: use sparse keymaps for input event handling

On Wed, Mar 29, 2017 at 08:36:50PM -0700, Darren Hart wrote: > On Wed, Mar 29, 2017 at 07:35:50PM +0300, Andy Shevchenko wrote: > > On Wed, Mar 29, 2017 at 10:19 AM, Micha?? K??pie?? > > wrote: > > > > > Darren, Andy, in light of the above I will be awaiting your review of >

Re: [PATCH 0/8] fujitsu-laptop: use sparse keymaps for input event handling

On Wed, Mar 29, 2017 at 08:36:50PM -0700, Darren Hart wrote: > On Wed, Mar 29, 2017 at 07:35:50PM +0300, Andy Shevchenko wrote: > > On Wed, Mar 29, 2017 at 10:19 AM, Micha?? K??pie?? > > wrote: > > > > > Darren, Andy, in light of the above I will be awaiting your review of > > > this series. I

Re: Random guest crashes since 5c34d002dcc7 ("virtio_pci: use shared interrupts for virtqueues")

On Wed, 2017-03-29 at 23:19 +0300, Michael S. Tsirkin wrote: > > > > > > > > > > > >max_nr_ports) == 0) { > > @@ -2179,7 +2179,9 @@ static struct virtio_device_id id_table[ > > > > static unsigned int features[] = { > > > >> > VIRTIO_CONSOLE_F_SIZE, > > +#ifndef

Re: Random guest crashes since 5c34d002dcc7 ("virtio_pci: use shared interrupts for virtqueues")

On Wed, 2017-03-29 at 23:19 +0300, Michael S. Tsirkin wrote: > > > > > > > > > > > >max_nr_ports) == 0) { > > @@ -2179,7 +2179,9 @@ static struct virtio_device_id id_table[ > > > > static unsigned int features[] = { > > > >> > VIRTIO_CONSOLE_F_SIZE, > > +#ifndef

Re: [PATCH net-next 8/8] vhost_net: use lockless peeking for skb array during busy polling

On 2017年03月30日 10:33, Michael S. Tsirkin wrote: On Thu, Mar 30, 2017 at 10:16:15AM +0800, Jason Wang wrote: On 2017年03月29日 20:07, Michael S. Tsirkin wrote: On Tue, Mar 21, 2017 at 12:04:47PM +0800, Jason Wang wrote: For the socket that exports its skb array, we can use lockless polling to

Re: [PATCH net-next 8/8] vhost_net: use lockless peeking for skb array during busy polling

On 2017年03月30日 10:33, Michael S. Tsirkin wrote: On Thu, Mar 30, 2017 at 10:16:15AM +0800, Jason Wang wrote: On 2017年03月29日 20:07, Michael S. Tsirkin wrote: On Tue, Mar 21, 2017 at 12:04:47PM +0800, Jason Wang wrote: For the socket that exports its skb array, we can use lockless polling to

linux-next: build failure after merge of the phy-next tree

:1148:17: error: 'rk3328_usb2phy_tuning' undeclared here (not in a function) .phy_tuning = rk3328_usb2phy_tuning, ^ Caused by commit ffa0c278e89c ("phy: rockchip-inno-usb2: add support of u2phy for rk3328") I have used the phy-next tree from next-20170329

linux-next: build failure after merge of the phy-next tree

:1148:17: error: 'rk3328_usb2phy_tuning' undeclared here (not in a function) .phy_tuning = rk3328_usb2phy_tuning, ^ Caused by commit ffa0c278e89c ("phy: rockchip-inno-usb2: add support of u2phy for rk3328") I have used the phy-next tree from next-20170329

Re: linux-next: manual merge of the tty tree with the tty.current tree

On Mon, 2017-03-20 at 10:26 +0100, Dmitry Vyukov wrote: > On Mon, Mar 20, 2017 at 10:21 AM, Dmitry Vyukov wrote: > > On Mon, Mar 20, 2017 at 3:28 AM, Stephen Rothwell > > wrote: > > > Hi Greg, > > > > > > Today's linux-next merge of the tty tree got a

Re: linux-next: manual merge of the tty tree with the tty.current tree

On Mon, 2017-03-20 at 10:26 +0100, Dmitry Vyukov wrote: > On Mon, Mar 20, 2017 at 10:21 AM, Dmitry Vyukov wrote: > > On Mon, Mar 20, 2017 at 3:28 AM, Stephen Rothwell > > wrote: > > > Hi Greg, > > > > > > Today's linux-next merge of the tty tree got a conflict in: > > > > > >  

Re: [PATCH] kernel.h: add IS_PTR_ALIGNED() macro

On 03/29/17 18:57, Masahiro Yamada wrote: > > Could you care to send a patch? > > Perhaps, ALIGN and PTR_ALIGN can be merged as well? > Can't promise when I'd get around to it... -hpa

Re: [PATCH] kernel.h: add IS_PTR_ALIGNED() macro

On 03/29/17 18:57, Masahiro Yamada wrote: > > Could you care to send a patch? > > Perhaps, ALIGN and PTR_ALIGN can be merged as well? > Can't promise when I'd get around to it... -hpa

Re: [PATCH 0/8] fujitsu-laptop: use sparse keymaps for input event handling

On Wed, Mar 29, 2017 at 07:35:50PM +0300, Andy Shevchenko wrote: > On Wed, Mar 29, 2017 at 10:19 AM, Michał Kępień wrote: > > > Darren, Andy, in light of the above I will be awaiting your review of > > this series. I will submit v2 afterwards, with all remarks from both > >

Re: [PATCH 0/8] fujitsu-laptop: use sparse keymaps for input event handling

On Wed, Mar 29, 2017 at 07:35:50PM +0300, Andy Shevchenko wrote: > On Wed, Mar 29, 2017 at 10:19 AM, Michał Kępień wrote: > > > Darren, Andy, in light of the above I will be awaiting your review of > > this series. I will submit v2 afterwards, with all remarks from both > > you and Jonathan

Re: [PATCH v4 1/2] module: verify address is read-only

+++ Eddie Kovsky [26/03/17 15:08 -0600]: Implement a mechanism to check if a module's address is in the rodata or ro_after_init sections. It mimics the existing functions that test if an address is inside a module's text section. Functions that take a module as an argument will be able to

Re: [PATCH v4 1/2] module: verify address is read-only

+++ Eddie Kovsky [26/03/17 15:08 -0600]: Implement a mechanism to check if a module's address is in the rodata or ro_after_init sections. It mimics the existing functions that test if an address is inside a module's text section. Functions that take a module as an argument will be able to

Re: [PATCH] virtio_console: fix uninitialized variable use

On Wed, 2017-03-29 at 23:27 +0300, Michael S. Tsirkin wrote: > Hi Mike > if you like, pls send me your Signed-off-by and I'll > change the patch to make you an author. Nah, it's perfect as it is. While I was pretty darn sure it was generic, I intentionally posted it as diagnostic

Re: [PATCH] virtio_console: fix uninitialized variable use

On Wed, 2017-03-29 at 23:27 +0300, Michael S. Tsirkin wrote: > Hi Mike > if you like, pls send me your Signed-off-by and I'll > change the patch to make you an author. Nah, it's perfect as it is. While I was pretty darn sure it was generic, I intentionally posted it as diagnostic

Re: [PATCH v2 0/8] thermal: ti-soc-thermal: Migrate slope/offset data to device tree

On Wednesday 29 March 2017 10:07 AM, Eduardo Valentin wrote: > Keerthy, > > On Fri, Mar 24, 2017 at 07:26:10AM -0700, Tony Lindgren wrote: >> * Keerthy [170323 20:29]: >>> >>> >>> On Friday 24 March 2017 02:22 AM, Tony Lindgren wrote: * Keerthy [170321

Re: [PATCH v2 0/8] thermal: ti-soc-thermal: Migrate slope/offset data to device tree

On Wednesday 29 March 2017 10:07 AM, Eduardo Valentin wrote: > Keerthy, > > On Fri, Mar 24, 2017 at 07:26:10AM -0700, Tony Lindgren wrote: >> * Keerthy [170323 20:29]: >>> >>> >>> On Friday 24 March 2017 02:22 AM, Tony Lindgren wrote: * Keerthy [170321 20:45]: > > > On

[PATCH 0/5] firmware: move UMH locks onto fallback code

Greg, One of the eyesores on the old API was the use of the UMH lock even when we don't use any of the usermode helpers. It took quite a bit of git archeology to draw up a solution which makes me feel comfortable in moving this code out of the way given it may have added new protections we never

[PATCH 0/5] firmware: move UMH locks onto fallback code

Greg, One of the eyesores on the old API was the use of the UMH lock even when we don't use any of the usermode helpers. It took quite a bit of git archeology to draw up a solution which makes me feel comfortable in moving this code out of the way given it may have added new protections we never

Re: [PATCH v2 3/8] ARM: OMAP5: Thermal: Add slope and offset values

On Wednesday 29 March 2017 10:03 AM, Eduardo Valentin wrote: > On Thu, Mar 09, 2017 at 01:35:57PM +0530, Keerthy wrote: >> Currently the slope and offset values for calculating the >> hot spot temperature of a particular thermal zone is part >> of driver data. Pass them here instead and obtain

Re: [PATCH v2 3/8] ARM: OMAP5: Thermal: Add slope and offset values

On Wednesday 29 March 2017 10:03 AM, Eduardo Valentin wrote: > On Thu, Mar 09, 2017 at 01:35:57PM +0530, Keerthy wrote: >> Currently the slope and offset values for calculating the >> hot spot temperature of a particular thermal zone is part >> of driver data. Pass them here instead and obtain

[PATCH 3/5] firmware: add sanity check on shutdown/suspend

The firmware API should not be used after we go to suspend and after we reboot/halt. The suspend/resume case is a bit complex, so this documents that so things are clearer. We want to know about users of the API in incorrect places so that their callers are corrected, so this also adds a warn for

[PATCH 3/5] firmware: add sanity check on shutdown/suspend

The firmware API should not be used after we go to suspend and after we reboot/halt. The suspend/resume case is a bit complex, so this documents that so things are clearer. We want to know about users of the API in incorrect places so that their callers are corrected, so this also adds a warn for

Re: [PATCH v4 2/2] extable: verify address is read-only

+++ Eddie Kovsky [28/03/17 21:28 -0600]: On 03/27/17, Kees Cook wrote: On Mon, Mar 27, 2017 at 1:43 AM, kbuild test robot wrote: > Hi Eddie, > > [auto build test ERROR on next-20170323] > [cannot apply to linus/master linux/master jeyu/modules-next v4.9-rc8 v4.9-rc7 v4.9-rc6

Re: [PATCH v4 2/2] extable: verify address is read-only

+++ Eddie Kovsky [28/03/17 21:28 -0600]: On 03/27/17, Kees Cook wrote: On Mon, Mar 27, 2017 at 1:43 AM, kbuild test robot wrote: > Hi Eddie, > > [auto build test ERROR on next-20170323] > [cannot apply to linus/master linux/master jeyu/modules-next v4.9-rc8 v4.9-rc7 v4.9-rc6 v4.11-rc4] > [if

[PATCH] usb: host: plat: Enable xHCI plat runtime PM

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

Re: [RFC PATCH 1/3] of/pci: dma-ranges to account highest possible host bridge dma_mask

On Wed, Mar 29, 2017 at 10:13 AM, Oza Oza wrote: > On Tue, Mar 28, 2017 at 7:59 PM, Robin Murphy wrote: >> On 28/03/17 06:27, Oza Oza wrote: >>> On Mon, Mar 27, 2017 at 8:16 PM, Rob Herring wrote: On Sat, Mar 25, 2017 at 12:31

  1   2   3   4   5   6   7   8   9   10   >