[PATCH] atm: firestream: Replace GFP_ATOMIC with GFP_KERNEL in fs_send

After checking all possible call chains to fs_send() here, my tool finds that fs_send() is never called in atomic context. And this function is assigned to a function pointer "dev->ops->send", which is only called by vcc_sendmsg() (net/atm/common.c) through vcc->dev->ops->send(), and vcc_sendmsg()

Re: [PATCH v4 4/8] PCI: brcmstb: Add dma-range mapping for inbound traffic

On Wed, Jan 24, 2018 at 12:04:58PM -0800, Florian Fainelli wrote: > This looks nicer than the current shape, but this still requires to > register a PCI fixup to override phys_to_dma() and dma_to_phys(), and it > would appear that you have dodged my question about how this is supposed > to fit with

Re: [RFC v2 3/4] drm/nouveau: Add support for BLCG on Kepler2

On Thu, Jan 25, 2018 at 10:35 PM, Lyude Paul wrote: > Same as the previous patch, but for Kepler2 now > > Signed-off-by: Lyude Paul > --- > drivers/gpu/drm/nouveau/include/nvkm/subdev/fb.h | 1 + > drivers/gpu/drm/nouveau/nvkm/engine/device/base.c | 8 +-- > drivers/gpu/drm/nouveau/nvkm/engin

Re: [PATCH] MAINTAINERS: add the iommu list for swiotlb and xen-swiotlb

On Thu, Jan 25, 2018 at 09:26:18AM -0500, Konrad Rzeszutek Wilk wrote: > On Tue, Jan 16, 2018 at 08:56:24AM +0100, Christoph Hellwig wrote: > > All other discussions related to the dma mapping interfaces are on the > > iommu list, so let's make it the official list for swiotlb and the > > second li

Re: [PATCH v2 2/2] perf stat: Add support to print counts after a period of time

On Fri, Jan 26, 2018 at 09:59:02AM +0800, 禹舟键 wrote: > 2018-01-25 20:27 GMT+08:00 Jiri Olsa : > > > On Thu, Jan 25, 2018 at 10:10:04AM +0100, ufo19890607 wrote: > > > > SNIP > > > > > --metric-only:: > > > Only print computed metrics. Print them in a single line. > > > diff --git a/tools/perf/bu

Re: Kdump kernel start failed with intel_iommu=on

On 01/23/18 at 06:20pm, Weilong Chen wrote: > Hi, > > We came across this problem: > Second kernel hang with intel_iommu=on > > We can reproduce the problem by the following steps: > 1. start the kernel with intel_iommu=on > 2. ifconfig eth6 up;ifconfig eth8 up.(eth6 is Intel Corporation 82599ES

[RFC PATCH] vsprintf: add flag ZEROPAD handling before crng is ready

Before crng is ready, output of "%p" composes of "(ptrval)" and left padding spaces for alignment as no random address can be generated. This seems a little strange sometimes. For example, when irq domain names are built with "%p", the nodes under /sys/kernel/debug/irq/domains like this, [root@y i

Re: general protection fault in tun_do_read

On Fri, Jan 26, 2018 at 4:24 AM, Jason Wang wrote: > > > On 2018年01月25日 15:59, syzbot wrote: >> >> Hello, >> >> syzbot hit the following crash on net-next commit >> 43df215d99e6049d4680309c54232689e16ddd6b (Wed Jan 24 01:24:32 2018 +) >> Merge branch 'bpf-and-netdevsim-test-updates' >> >> So f

[PATCH v2 0/5] GICv3 Save and Restore

A lot of changes in v2. The distributor and redistributor saving and restoring is left to the PSCI/firmware implementation after discussions with ARM. This reduces the line changes by a lot and removes now unneeded patches. Patches are verified on an RK3399 platform with pending patches in the ARM

[PATCH v2 1/5] cpu_pm: add syscore_suspend error handling

If cpu_cluster_pm_enter() fails, cpu_pm_exit() should be called. This will put the CPU in the correct state to resume from the failure. Signed-off-by: Derek Basehore --- kernel/cpu_pm.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/kernel/cpu_pm.c b/kernel/cpu_pm.c index 67b02e138a47..0

[PATCH v2 2/5] irqchip/gic-v3-its: add ability to save/restore ITS state

Some platforms power off GIC logic in suspend, so we need to save/restore state. The distributor and redistributor registers need to be handled in platform code due to access permissions on those registers, but the ITS registers can be restored in the kernel. Signed-off-by: Derek Basehore --- dr

[PATCH v2 3/5] DT/arm,gic-v3-its: add reset-on-suspend property

This adds documentation for the new reset-on-suspend property. This property enables saving and restoring the ITS for when it loses state in system suspend. Signed-off-by: Derek Basehore --- Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt | 3 +++ 1 file changed, 3 insertio

RE: [PATCH 2/2] thermal: imx: add i.MX7 thermal sensor support

-Original Message- From: Dong Aisheng [mailto:donga...@gmail.com] Sent: 2018年1月26日 15:00 To: Anson Huang Cc: rui.zh...@intel.com; edubez...@gmail.com; robh...@kernel.org; mark.rutl...@arm.com; shawn...@kernel.org; ker...@pengutronix.de; Fabio Estevam ; li...@armlinux.org.uk; Jacky Bai

[PATCH v2 4/5] irqchip/gic-v3-its: add ability to resend MAPC on resume

This adds functionality to resend the MAPC command to an ITS node on resume. If the ITS is powered down during suspend and the collections are not backed by memory, the ITS will lose that state. This just sets up the known state for the collections after the ITS is restored. This feature is enable

[PATCH v2 5/5] DT/arm,gic-v3: add collections-reset-on-suspend property

This boolean property for the GIC-V3-ITS enables resending the MAP COLLECTIONS commands when resuming for when the state is reset on suspend. Signed-off-by: Derek Basehore --- Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt | 4 1 file changed, 4 insertions(+) diff --

Re: [PATCH] print kdump kernel loaded status in stack dump

On 01/19/18 at 12:47pm, Dave Young wrote: > On 01/18/18 at 01:57pm, Steven Rostedt wrote: > > On Thu, 18 Jan 2018 10:02:17 -0800 > > Andi Kleen wrote: > > > > > Dave Young writes: > > > > printk("%sHardware name: %s\n", > > > >log_lvl, dump_stack_arch_desc

Re: [RFC PATCH 2/2] gpio: provide a consumer when requesting a gpio

On Wed, Jan 24, 2018 at 05:42:15PM +0200, Andy Shevchenko wrote: > On Wed, Jan 24, 2018 at 3:07 PM, Ludovic Desroches > wrote: > > On Thu, Jan 18, 2018 at 04:22:28PM +0100, Ludovic Desroches wrote: > >> On Thu, Jan 18, 2018 at 11:30:00AM +0100, Linus Walleij wrote: > >> > On Mon, Jan 15, 2018 at 5

Re: [PATCH 2/2] usb: chipidea: imx: Fix ULPI on imx53

On Wed, Jan 24, 2018 at 06:14:39PM +0100, Sebastian Reichel wrote: > Traditionally, PORTSC should be set before initializing ULPI phys. But > setting PORTSC before powering on the phy results in a kernel freeze > on imx53 based GE PPD. As a workaround this initializes the phy early > in the imx pla

Re: [PATCH 2/4] usb: dwc3: add dwc3 glue layer for UniPhier SoCs

Hi, On Thu, 25 Jan 2018 11:09:30 +0900 wrote: > Hello Felipe, > > On Wed, 24 Jan 2018 14:58:12 +0200 wrote: > > > > > Hi, > > > > Kunihiko Hayashi writes: > > > Hello Felipe, > > > > > > Thank you for your comments. > > > > > > On Tue, 23 Jan 2018 15:12:36 +0200 wrote: > > > > > >> > > >

Re: [PATCH] of: use hash based search in of_find_node_by_phandle

On 1/25/2018 8:20 PM, Rob Herring wrote: On Thu, Jan 25, 2018 at 4:14 AM, Chintan Pandya wrote: of_find_node_by_phandle() takes a lot of time finding Got some numbers for what is "a lot of time"? On my SDM device, I see total saving of 400ms during boot time. For some clients whose node is q

Darlehen Geld für Einzelpersonen und Fachleute in weniger als 72 Stunden

Hallo, Sind Sie in einer schwierigen Situation, für die Sie sich für ein Darlehen suchen? Benötigen Sie eine Finanzierung, um eine Schuld zu begleichen oder eine Aktivität zu finanzieren? Haben Sie einen Verbraucherkredit, eine Hypothek, einen persönlichen Kredit, eine Hypothek, Investition Darleh

Re: [PATCH v2] ASoC: use seq_file to dump the contents of dai_list,platform_list and codec_list

On Wed, Jan 24, 2018 at 1:37 AM, Mark Brown wrote: > On Tue, Jan 23, 2018 at 07:08:15PM +0200, Andy Shevchenko wrote: > >> If it's not critical, I would suggest to wait till v4.16-rc1, where I >> would like to push [1], and switch to DEFINE_SHOW_ATTRIBUTE() macro. > > Too late, I already applied t

Re: [PATCH RESENT] nvme-pci: introduce RECONNECTING state to mark initializing procedure

Thanks, applied to nvme-4.16.

[PATCH v4] iommu/mediatek: Move attach_device after iommu-group is ready for M4Uv1

In the commit 05f80300dc8b ("iommu: Finish making iommu_group support mandatory"), the iommu framework has supposed all the iommu drivers have their owner iommu-group, it get rid of the FIXME workarounds while the group is NULL. But the flow of Mediatek M4U gen1 looks a bit trick that it will hang

Re: [PATCH] Update the RISC-V MAINTAINERS file

On Thu, Jan 25, 2018 at 08:23:15AM -0800, Palmer Dabbelt wrote: > Now that we're upstream in Linux we've been able to make some > infrastructure changes so our port works a bit more like other ports. > Specifically: > > * We now have a mailing list specific to the RISC-V Linux port, hosted > at

Re: [PATCH 2/2] thermal: imx: add i.MX7 thermal sensor support

On Mon, Jan 22, 2018 at 03:25:49PM +0800, Anson Huang wrote: > This patch adds i.MX7 thermal sensor support, most > of the i.MX7 thermal sensor functions are same with > i.MX6 except the registers offset/layout, so we move > those registers offset/layout definitions to soc data > structure. > > i.

Re: [PATCH 2/2] perf tools: Skip read of kernel maps once it failed

On Fri, Jan 19, 2018 at 05:11:03PM +0100, Jiri Olsa wrote: > Current perf report is real slow on newer kernels, > with following commit: > c0f3ea158939 ("stop using '%pK' for /proc/kallsyms pointer values") > > which prevent pointers in /proc/kallsyms, in case > kernel.perf_event_paranoid=2. >

Re: [PATCH 1/2] tools lib symbol: Use strtoul instead of hex2u64 in kallsyms__parse

On Fri, Jan 19, 2018 at 05:11:02PM +0100, Jiri Olsa wrote: > Current kallsyms__parse uses hex2u64, which gives > no indication of error. Using strtoul to checkup > on failed attempt to parse the number and stop the > rest of the kallsyms__parse processing early. > > Link: http://lkml.kernel.org/n/

Re: Back porting preemption timer patches from 4.13 to 4.9 RT kernel

On Fri, 26 Jan 2018, Wanpeng Li wrote: Folks, can you please stop this corporate email style nonsense? > On 1/26/18 12:55 AM, Arisetty, Chakravarthy wrote: > >> IIRC，the race which KVM: LAPIC: Fix reentrancy issues with preempt > >> notifiers

RE: [PATCH] ARM: dts: imx6sx: add pu power domain support

-Original Message- From: Dong Aisheng [mailto:donga...@gmail.com] Sent: 2018年1月25日 23:30 To: Anson Huang Cc: shawn...@kernel.org; ker...@pengutronix.de; Fabio Estevam ; robh...@kernel.org; A.s. Dong ; mark.rutl...@arm.com; li...@armlinux.org.uk; dl-linux-imx ; linux-arm-ker...@lists.

Re: [PATCH] cpufreq: intel_pstate: enable HWP before manipulating on corresponding registers

On Thu, Jan 25, 2018 at 02:44:59PM -0800, Srinivas Pandruvada wrote: > On Thu, 2018-01-25 at 19:08 +0800, Yu Chen wrote: > > Thanks for debugging. > > > The following warning was triggered after resumed from S3 - > > if all the nonboot CPUs were put offline before suspend: > > > > [ 1840.329515]

Re: [PATCH arm/aspeed/ast2500 v2] ipmi: add an Aspeed KCS IPMI BMC driver

On 2018-01-25 01:48, Corey Minyard wrote: On 01/24/2018 10:06 AM, Haiyue Wang wrote: The KCS (Keyboard Controller Style) interface is used to perform in-band IPMI communication between a server host and its BMC (BaseBoard Management Controllers). This driver exposes the KCS interface on ASp

Re: [PATCH arm/aspeed/ast2500 v2] ipmi: add an Aspeed KCS IPMI BMC driver

On 2018-01-25 01:48, Corey Minyard wrote: On 01/24/2018 10:06 AM, Haiyue Wang wrote: The KCS (Keyboard Controller Style) interface is used to perform in-band IPMI communication between a server host and its BMC (BaseBoard Management Controllers). This driver exposes the KCS interface on ASp

[PATCH] ARM: dts: exynos: Update x and y properties for mms114 touchscreen

The mms114 binding [1] specifies that the 'x' and 'y' should be called respectively 'touchscreen-size-x' and 'touchscreen-size-y' in coherence with the touchscreen [2] binding. Update the mms114 node for trats2 and trats dts according to the binding. [1] Documentation/devicetree/bindings/input/to

Re: [RFC 0/4] tools lib traceevent: Install fixes

Hi Jiri and Steve, On Fri, Jan 19, 2018 at 04:15:02PM +0100, Jiri Olsa wrote: > On Fri, Jan 19, 2018 at 10:07:28AM -0500, Steven Rostedt wrote: > > On Fri, 19 Jan 2018 11:37:13 +0100 > > Jiri Olsa wrote: > > > > > hi, > > > I checked on this one and was surprised last email is from 2016 ;-) > >

[RFC PATCH 1/8] media: add request API core and UAPI

The request API provides a way to group buffers and device parameters into units of work to be queued and executed. This patch introduces the UAPI and core framework. This patch is based on the previous work by Laurent Pinchart. The core has changed considerably, but the UAPI is mostly untouched.

[RFC PATCH 2/8] videodev2.h: Add request field to v4l2_buffer

From: Hans Verkuil When queuing buffers allow for passing the request ID that should be associated with this buffer. Signed-off-by: Hans Verkuil [acour...@chromium.org: make request ID 32-bit] Signed-off-by: Alexandre Courbot --- drivers/media/usb/cpia2/cpia2_v4l.c | 2 +- drivers/m

[RFC PATCH 3/8] media: videobuf2: add support for requests

Make vb2 aware of requests. Drivers can specify whether a given queue can accept requests or not. Queues that accept requests will block on a buffer that is part of a request until that request is submitted. Signed-off-by: Alexandre Courbot --- drivers/media/v4l2-core/videobuf2-core.c | 125

[RFC PATCH 5/8] media: Document the media request API

From: Laurent Pinchart The media request API is made of a new ioctl to implement request management. Document it. Signed-off-by: Laurent Pinchart [acour...@chromium.org: adapt for newest API] Signed-off-by: Alexandre Courbot --- Documentation/media/uapi/mediactl/media-funcs.rst | 1 + .../

[RFC PATCH 7/8] media: vim2m: add media device

Request API requires a media node. Add one to the vim2m driver so we can use requests with it. Signed-off-by: Alexandre Courbot --- drivers/media/platform/vim2m.c | 24 1 file changed, 24 insertions(+) diff --git a/drivers/media/platform/vim2m.c b/drivers/media/platform

[RFC PATCH 6/8] v4l2: document the request API interface

Document how the request API can be used along with the existing V4L2 interface. Signed-off-by: Alexandre Courbot --- Documentation/media/uapi/v4l/buffer.rst | 10 +- Documentation/media/uapi/v4l/common.rst | 1 + Documentation/media/uapi/v4l/request-api.rst | 194 ++

[RFC PATCH 8/8] media: vim2m: add request support

Set the necessary ops for supporting requests in vim2m. Signed-off-by: Alexandre Courbot --- drivers/media/platform/vim2m.c | 31 +++ 1 file changed, 31 insertions(+) diff --git a/drivers/media/platform/vim2m.c b/drivers/media/platform/vim2m.c index a32e8a7950eb..1dd

[RFC PATCH 4/8] media: vb2: add support for requests in QBUF ioctl

Support the request argument of the QBUF ioctl. Signed-off-by: Alexandre Courbot --- drivers/media/v4l2-core/v4l2-ioctl.c | 79 +++- 1 file changed, 78 insertions(+), 1 deletion(-) diff --git a/drivers/media/v4l2-core/v4l2-ioctl.c b/drivers/media/v4l2-core/v4l2-

[RFC PATCH 0/8] [media] Request API, take three

Howdy. Here is your bi-weekly request API redesign! ;) Again, this is a simple version that only implements the flow of requests, without applying controls. The intent is to get an agreement on a base to work on, since the previous versions went straight back to the redesign board. Highlights of

[PATCH 1/2] selftests/powerpc: Add ptrace tests for Protection Key registers

This test exercises read and write access to the AMR, IAMR and UAMOR. Signed-off-by: Thiago Jung Bauermann --- tools/testing/selftests/powerpc/include/reg.h | 1 + tools/testing/selftests/powerpc/ptrace/Makefile| 5 +- tools/testing/selftests/powerpc/ptrace/child.h | 130 +++

[PATCH 0/2] Testcases for protection keys feature in powerpc/next

Ram Pai submitted a separate series containing the rework of the x86 test and also the powerpc-specific tests: https://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=24741 There's a bug in the powerpc tests where they expect the AMR, IAMR and UAMOR registers to be zeroed when a process st

[PATCH 2/2] selftests/powerpc: Add core file test for Protection Key registers

This test verifies that the AMR, IAMR and UAMOR are being written to a process' core file. Signed-off-by: Thiago Jung Bauermann --- tools/testing/selftests/powerpc/ptrace/Makefile| 5 +- tools/testing/selftests/powerpc/ptrace/core-pkey.c | 460 + 2 files changed, 464 in

Re: [PATCH 6/8] kprobes/arm64: Fix %p uses in error messages

On Thu, 25 Jan 2018 16:42:31 + Will Deacon wrote: > On Thu, Jan 25, 2018 at 02:29:32PM +0900, Masami Hiramatsu wrote: > > Fix %p uses in error messages by removing it because > > those are redundant or meaningless. > > > > Signed-off-by: Masami Hiramatsu > > --- > > arch/arm64/kernel/probe

Re: [kernel-hardening] [PATCH 4/6] Protectable Memory

On Wed, Jan 24, 2018 at 08:10:53PM +0100, Jann Horn wrote: > I'm not entirely convinced by the approach of marking small parts of > kernel memory as readonly for hardening. It depends how significant the data stored in there are. For example, storing function pointers in read-only memory provides

Re: [PATCH arm/aspeed/ast2500 v2] ipmi: add an Aspeed KCS IPMI BMC driver

On 2018-01-25 01:05, Andy Shevchenko wrote: On Thu, 2018-01-25 at 00:06 +0800, Haiyue Wang wrote: The KCS (Keyboard Controller Style) interface is used to perform in- band IPMI communication between a server host and its BMC (BaseBoard Management Controllers). +config ASPEED_KCS_IPMI_BMC +

Re: [PATCH 4/4 v2] Input: mms114 - add support for mms152

Hi Simon and Dmitry, On Wed, Jan 24, 2018 at 01:32:01PM -0800, Dmitry Torokhov wrote: > From: Simon Shields > > MMS152 has no configuration registers, but the packet format used in > interrupts is identical to mms114. > > Signed-off-by: Simon Shields > Patchwork-Id: 10125841 > Signed-off-by: D

[RESEND PATCH] rtc: Fix overflow when converting time64_t to rtc_time

If we convert one large time values to rtc_time, in the original formula 'days * 86400' can be overflowed in 'unsigned int' type to make the formula get one incorrect remain seconds value. Thus we can use div_s64_rem() function to avoid this situation. Signed-off-by: Baolin Wang --- drivers/rtc/

Re: [PATCH 3/4] Input: mms114 - drop platform data and use generic APIs

Hi Simon and Dmitry, On Wed, Jan 24, 2018 at 11:38:03AM -0800, Dmitry Torokhov wrote: > From: Simon Shields > > The MMS114 platform data has no in-tree users, so drop it. > > Switch to using the standard touchscreen properties via > touchscreen_parse_properties(), and move the old DT parsing co

Re: [PATCH 2/4] Input: mms114 - mark as direct input device

Hi Dmitry, On Wed, Jan 24, 2018 at 11:38:02AM -0800, Dmitry Torokhov wrote: > mms14 is a touchscreen and thus a direct input device; let's mark it > as such. This also allows us to drop some initialization code as > input_init_mt_slots() will do that for us. > > Also add error handling for input_

Re: [PATCH 1/4] Input: mms114 - do not clobber interrupt trigger

Hi Dmitry, On Wed, Jan 24, 2018 at 11:38:01AM -0800, Dmitry Torokhov wrote: > Rely on the platform (device tree, ACPI, etc) to properly configure > interrupt trigger/polarity instead of hardcoding the falling edge. > > Signed-off-by: Dmitry Torokhov Reviewed-by: Andi Shyti Tested-by: Andi Shyt

Re: [PATCH v4] staging: lustre: separate a connection destroy from free struct kib_conn

On Jan 25, 2018, at 06:51, Eremin, Dmitry wrote: > > The logic of the original commit 4d99b2581eff ("staging: lustre: avoid > intensive reconnecting for ko2iblnd") was assumed conditional free of > struct kib_conn if the second argument free_conn in function > kiblnd_destroy_conn(struct kib_conn

Re: PATCH v6 6/6] livepatch: Add atomic replace

On 01/25/2018 11:02 AM, Petr Mladek wrote: > From: Jason Baron > > Sometimes we would like to revert a particular fix. Currently, this > is not easy because we want to keep all other fixes active and we > could revert only the last applied patch. > > One solution would be to apply new patch th

Re: [PATCH v6 11/12] arm64: topology: enable ACPI/PPTT based CPU topology

Hi Jeremy, On 2018/1/25 23:56, Jeremy Linton wrote: > Hi, > > On 01/25/2018 06:15 AM, Xiongfeng Wang wrote: >> Hi Jeremy, >> >> I have tested the patch with the newest UEFI. It prints the below error: >> >> [4.017371] BUG: arch topology borken >> [4.021069] BUG: arch topology borken >> [

Re: [PATCH net-next 12/12] tools/virtio: fix smp_mb on x86

On 2018年01月26日 07:36, Michael S. Tsirkin wrote: Offset 128 overlaps the last word of the redzone. Use 132 which is always beyond that. Signed-off-by: Michael S. Tsirkin --- tools/virtio/ringtest/main.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/virtio/ringtes

[PATCH] atm: atmtcp: Replace GFP_ATOMIC with GFP_KERNEL in atmtcp_v_send

After checking all possible call chains to atmtcp_v_send() here, my tool finds that atmtcp_v_send() is never called in atomic context. And this function is assigned to a function pointer "dev->ops->send", which is only called by vcc_sendmsg() (net/atm/common.c) through vcc->dev->ops->send(), and vc

[PATCH] atm: solos-pci: Replace GFP_ATOMIC with GFP_KERNEL in psend

After checking all possible call chains to psend() here, my tool finds that psend() is never called in atomic context. And this function is assigned to a function pointer "dev->ops->send", which is only called by vcc_sendmsg (net/atm/common.c) through vcc->dev->ops->send(), and vcc_sendmsg calls sc

Re: [PATCH net-next] ptr_ring: fix integer overflow

On 2018年01月26日 01:31, Michael S. Tsirkin wrote: On Thu, Jan 25, 2018 at 10:17:38PM +0800, Jason Wang wrote: On 2018年01月25日 21:45, Michael S. Tsirkin wrote: On Thu, Jan 25, 2018 at 03:31:42PM +0800, Jason Wang wrote: We try to allocate one more entry for lockless peeking. The adding operatio

[RFC v2 2/4] drm/nouveau: Add support for BLCG on Kepler1

This enables BLCG optimization for kepler1. When using clockgating, nvidia's firmware has a set of registers which are initially programmed by the vbios with various engine delays and other mysterious settings that are safe enough to bring up the GPU. However, the values used by the vbios are more

[RFC v2 3/4] drm/nouveau: Add support for BLCG on Kepler2

Same as the previous patch, but for Kepler2 now Signed-off-by: Lyude Paul --- drivers/gpu/drm/nouveau/include/nvkm/subdev/fb.h | 1 + drivers/gpu/drm/nouveau/nvkm/engine/device/base.c | 8 +-- drivers/gpu/drm/nouveau/nvkm/engine/gr/gk110.c| 62 drivers/gpu/drm/nouveau

[PATCH] atm: idt77252: Replace mdelay with usleep_range in idt77252_preset

After checking all possible call chains to idt77252_preset() here, my tool finds that idt77252_preset() is never called in atomic context, namely never in an interrupt handler or holding a spinlock. And idt77252_preset() calls deinit_card, which calls free_irq (can sleep), so it indicates that idt7

[RFC v2 4/4] drm/nouveau: Add support for SLCG for Kepler2

That's right, there's still more power saving to go! Starting with kepler 2, nvidia hardware has an additional level of clockgating known as second level clockgating. The details of this are not exact, but it seems to work by waiting for a collection of dependent hardware blocks to be gated before

[RFC v2 1/4] drm/nouveau: Add support for basic clockgating on Kepler1

This adds support for enabling automatic clockgating on nvidia GPUs for Kepler1. While this is not technically a clockgating level, it does enable clockgating using the clockgating values initially set by the vbios (which should be safe to use). This introduces two therm helpers for controlling ba

[RFC v2 0/4] Implement full clockgating for Kepler1 and 2

Next version of my patchseries for adding clockgating support for kepler1 and 2 on nouveau. The first version of this series can be found here: https://patchwork.freedesktop.org/series/36504/ Some minor changes: - Clarified that SLCG stands for 'secondary level clockgating', thanks for the sm

Re: [PATCH] kdb: use ktime_get_seconds() instead of ktime_get_ts()

On 01/25/2018 09:03 PM, Baolin Wang wrote: The kdb code will print the monotonic time by ktime_get_ts(), but the ktime_get_ts() will be protected by a sequence lock, that will introduce one deadlock risk if the lock was already held in the context from which we entered the debugger. Since kdb is

Re: [virtio-dev] Re: [PATCH v25 2/2] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT

On 01/26/2018 10:42 AM, Michael S. Tsirkin wrote: On Fri, Jan 26, 2018 at 09:40:44AM +0800, Wei Wang wrote: On 01/25/2018 09:49 PM, Michael S. Tsirkin wrote: On Thu, Jan 25, 2018 at 05:14:06PM +0800, Wei Wang wrote: The controversy is that the free list is not static once the lock is droppe

Re: [PATCH v24 1/2] mm: support reporting free page blocks

On 01/25/2018 09:41 PM, Michael S. Tsirkin wrote: On Wed, Jan 24, 2018 at 06:42:41PM +0800, Wei Wang wrote: This patch adds support to walk through the free page blocks in the system and report them via a callback function. Some page blocks may leave the free list after zone->lock is released, s

Re: general protection fault in tun_do_read

On 2018年01月25日 15:59, syzbot wrote: Hello, syzbot hit the following crash on net-next commit 43df215d99e6049d4680309c54232689e16ddd6b (Wed Jan 24 01:24:32 2018 +) Merge branch 'bpf-and-netdevsim-test-updates' So far this crash happened 2 times on net-next. Unfortunately, I don't have any

Re: [PATCH] x86/kvm: disable fast MMIO when running nested

On 2018年01月26日 10:49, Michael S. Tsirkin wrote: On Fri, Jan 26, 2018 at 10:41:58AM +0800, Jason Wang wrote: On 2018年01月26日 01:11, Michael S. Tsirkin wrote: On Thu, Jan 25, 2018 at 09:49:22AM -0500, Paolo Bonzini wrote: Michael and Jason, any progress on implementing a fast virtio mechanism

[PATCH] Fix compile warning with ATA_DEBUG enabled

From: Dong Bo This fixs the following comile warnings with ATA_DEBUG enabled, which detected by Linaro GCC 5.2-2015.11: In file included from ./include/linux/printk.h:7:0, from ./include/linux/kernel.h:14, from ./include/asm-generic/bug.h:16, fr

Re: [PATCH net-next 00/12] ptr_ring fixes

On 2018年01月26日 07:36, Michael S. Tsirkin wrote: This fixes a bunch of issues around ptr_ring use in net core. One of these: "tap: fix use-after-free" is also needed on net, but can't be backported cleanly. I will post a net patch separately. Lightly tested - Jason, could you pls confirm this

Re: [PATCH net-next 03/12] ptr_ring: READ/WRITE_ONCE for __ptr_ring_empty

On 2018年01月26日 10:44, Michael S. Tsirkin wrote: On Fri, Jan 26, 2018 at 10:37:58AM +0800, Jason Wang wrote: On 2018年01月26日 07:36, Michael S. Tsirkin wrote: Lockless __ptr_ring_empty requires that consumer head is read and written at once, atomically. Annotate accordingly to make sure compile

Re: [PATCH] ashmem: Fix lockdep issue during llseek

On Thu, Jan 25, 2018 at 06:46:49PM -0800, Joel Fernandes wrote: > ashmem_mutex create a chain of dependencies like so: > > (1) > mmap syscall -> > mmap_sem -> (acquired) > ashmem_mmap > ashmem_mutex (try to acquire) > (block) > > (2) > llseek syscall -> > ashmem_llseek -> > ashmem_mu

Re: [PATCH 1/2] mm,vmscan: Kill global shrinker lock.

Eric Wheeler wrote: > Hi Tetsuo, > > Thank you for looking into this! > > I tried running this C program in 4.14.15 but did not get a deadlock, just > OOM kills. Is the patch required to induce the deadlock? This reproducer must not trigger actual deadlock. Running this reproducer with this pat

[PATCH] kdb: use ktime_get_seconds() instead of ktime_get_ts()

The kdb code will print the monotonic time by ktime_get_ts(), but the ktime_get_ts() will be protected by a sequence lock, that will introduce one deadlock risk if the lock was already held in the context from which we entered the debugger. Since kdb is only interested in the second field, we can

Re: [PATCH v6 2/2] media: V3s: Add support for Allwinner CSI.

Hi Maxime, On Fri, 26 Jan 2018 09:46:58 +0800 Yong wrote: > Hi Maxime, > > Do you have any experience in solving this problem? > It seems the PHYS_OFFSET maybe undeclared when the ARCH is not arm. Got it. Should I add 'depends on ARM' in Kconfig? > > On Fri, 26 Jan 2018 08:04:18 +0800 > kbui

linux-next: Tree for Jan 26

Hi all, Changes since 20180119: The powerpc tree lost its build failures. The f2fs tree still had its build failure due to an interaction with the btrfs tree for which I reverted a commit. The vfs tree gained a conflict against the overlayfs tree. The iversion tree gained a conflict against th

RE: [RFC 09/10] x86/enter: Create macros to restrict/unrestrict Indirect Branch Speculation

> -Original Message- > From: Liran Alon [mailto:liran.a...@oracle.com] > Sent: Thursday, January 25, 2018 6:50 PM > To: Hansen, Dave > Cc: labb...@redhat.com; l...@kernel.org; janakarajan.natara...@amd.com; > torva...@linux-foundation.org; b...@suse.de; Mallick, Asit K > ; rkrc...@redh

Re: [RFC 09/10] x86/enter: Create macros to restrict/unrestrict Indirect Branch Speculation

- dave.han...@intel.com wrote: > On 01/25/2018 06:11 PM, Liran Alon wrote: > > It is true that attacker cannot speculate to a kernel-address, but > it > > doesn't mean it cannot use the leaked kernel-address together with > > another unrelated vulnerability to build a reliable exploit. > > T

Re: [PATCH] x86/kvm: disable fast MMIO when running nested

On Fri, Jan 26, 2018 at 10:41:58AM +0800, Jason Wang wrote: > > > On 2018年01月26日 01:11, Michael S. Tsirkin wrote: > > On Thu, Jan 25, 2018 at 09:49:22AM -0500, Paolo Bonzini wrote: > > > > > Michael and Jason, any progress on implementing a fast virtio > > > > > mechanism > > > > > that doesn't

Re: [PATCH net-next 08/12] ptr_ring: prevent queue load/store tearing

On Fri, Jan 26, 2018 at 10:38:12AM +0800, Jason Wang wrote: > > > On 2018年01月26日 07:36, Michael S. Tsirkin wrote: > > In theory compiler could tear queue loads or stores in two. It does not > > seem to be happening in practice but it seems easier to convert the > > cases where this would be a pro

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 01/25/18 at 06:50pm, Kirill A. Shutemov wrote: > On Wed, Jan 17, 2018 at 01:24:54PM +0800, Baoquan He wrote: > > Hi Kirill, > > > > I setup qemu 2.9.0 to test 5-level on kexec/kdump support. While both > > kexec and kdump reset to BIOS immediately after triggering. I saw your > > patch adding 5

[PATCH] ashmem: Fix lockdep issue during llseek

ashmem_mutex create a chain of dependencies like so: (1) mmap syscall -> mmap_sem -> (acquired) ashmem_mmap ashmem_mutex (try to acquire) (block) (2) llseek syscall -> ashmem_llseek -> ashmem_mutex -> (acquired) inode_lock -> inode->i_rwsem (try to acquire) (block) (3) getden

Re: [PATCH net-next 05/12] ptr_ring: disallow lockless __ptr_ring_full

On Fri, Jan 26, 2018 at 10:38:05AM +0800, Jason Wang wrote: > > > On 2018年01月26日 07:36, Michael S. Tsirkin wrote: > > Similar to bcecb4bbf88a ("net: ptr_ring: otherwise safe empty checks can > > overrun array bounds") a lockless use of __ptr_ring_full might > > cause an out of bounds access. > >

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

Stephen Rothwell writes: > Hi Eric, > > After merging the userns tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > arch/powerpc/kernel/mce.c: In function 'machine_process_ue_event': > arch/powerpc/kernel/mce.c:276:5: error: too many arguments to function > 'memory_fai

Re: [PATCH net-next 03/12] ptr_ring: READ/WRITE_ONCE for __ptr_ring_empty

On Fri, Jan 26, 2018 at 10:37:58AM +0800, Jason Wang wrote: > > > On 2018年01月26日 07:36, Michael S. Tsirkin wrote: > > Lockless __ptr_ring_empty requires that consumer head is read and > > written at once, atomically. Annotate accordingly to make sure compiler > > does it correctly. Switch locked

Re: [virtio-dev] Re: [PATCH v25 2/2] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT

On Fri, Jan 26, 2018 at 09:40:44AM +0800, Wei Wang wrote: > On 01/25/2018 09:49 PM, Michael S. Tsirkin wrote: > > On Thu, Jan 25, 2018 at 05:14:06PM +0800, Wei Wang wrote: > > > + > > > +static void report_free_page_func(struct work_struct *work) > > > +{ > > > + struct virtio_balloon *vb; > > > +

Re: [PATCH] x86/kvm: disable fast MMIO when running nested

On 2018年01月26日 01:11, Michael S. Tsirkin wrote: On Thu, Jan 25, 2018 at 09:49:22AM -0500, Paolo Bonzini wrote: Michael and Jason, any progress on implementing a fast virtio mechanism that doesn't rely on undefined behavior? (Encode writing instruction length into last 4 bits of MMIO address,

Re: [PATCH v2 11/15] gen_init_cpio: add newcx format

On 01/24/2018 09:27 PM, Taras Kondratiuk wrote: > diff --git a/usr/gen_init_cpio.c b/usr/gen_init_cpio.c > index 7a2a6d85345d..78a47a5bdcb1 100644 > --- a/usr/gen_init_cpio.c > +++ b/usr/gen_init_cpio.c > @@ -10,6 +10,7 @@ > #include > #include > #include > +#include You're adding an assert

Re: [PATCH v2 01/15] Documentation: add newcx initramfs format description

On 01/24/2018 09:27 PM, Taras Kondratiuk wrote: > diff --git a/Documentation/early-userspace/buffer-format.txt > b/Documentation/early-userspace/buffer-format.txt > index e1fd7f9dad16..d818df4f72dc 100644 > --- a/Documentation/early-userspace/buffer-format.txt > +++ b/Documentation/early-userspace

Re: [PATCH v2 01/15] Documentation: add newcx initramfs format description

On 01/25/2018 03:29 AM, Arnd Bergmann wrote: > On Thu, Jan 25, 2018 at 4:27 AM, Taras Kondratiuk wrote: >> Many of the Linux security/integrity features are dependent on file >> metadata, stored as extended attributes (xattrs), for making decisions. >> These features need to be initialized during

Re: [PATCH net-next 03/12] ptr_ring: READ/WRITE_ONCE for __ptr_ring_empty

On 2018年01月26日 07:36, Michael S. Tsirkin wrote: Lockless __ptr_ring_empty requires that consumer head is read and written at once, atomically. Annotate accordingly to make sure compiler does it correctly. Switch locked callers to __ptr_ring_peek which does not support the lockless operation.

Re: [PATCH net-next 08/12] ptr_ring: prevent queue load/store tearing

On 2018年01月26日 07:36, Michael S. Tsirkin wrote: In theory compiler could tear queue loads or stores in two. It does not seem to be happening in practice but it seems easier to convert the cases where this would be a problem to READ/WRITE_ONCE than worry about it. Signed-off-by: Michael S. Tsir

Re: [PATCH net-next 05/12] ptr_ring: disallow lockless __ptr_ring_full

On 2018年01月26日 07:36, Michael S. Tsirkin wrote: Similar to bcecb4bbf88a ("net: ptr_ring: otherwise safe empty checks can overrun array bounds") a lockless use of __ptr_ring_full might cause an out of bounds access. We can fix this, but it's easier to just disallow lockless __ptr_ring_full for

Re: [PATCH v3] drm/nouveau: Move irq setup/teardown to pci ctor/dtor

On Fri, 2018-01-26 at 02:20 +0100, Adam Borowski wrote: > On Thu, Jan 25, 2018 at 06:29:53PM -0500, Lyude Paul wrote: > > This was made apparent by what appeared to be a regression in the > > mainline kernel that started introducing suspend/resume issues for > > nouveau: > > > > a0c9259dc4

Re: [RFC 09/10] x86/enter: Create macros to restrict/unrestrict Indirect Branch Speculation

On 01/25/2018 06:11 PM, Liran Alon wrote: > It is true that attacker cannot speculate to a kernel-address, but it > doesn't mean it cannot use the leaked kernel-address together with > another unrelated vulnerability to build a reliable exploit. The address doesn't leak if you can't execute there.

  1   2   3   4   5   6   7   8   >