Re: [PATCH] pids: introduce find_get_task_by_vpid helper

On 10/26, Mike Rapoport wrote: > > There are several functions that do find_task_by_vpid() followed by > get_task_struct(). We can use a helper function instead. Yes, agreed, I was going to do this many times. > --- a/kernel/futex.c > +++ b/kernel/futex.c > @@ -870,12 +870,7 @@ static struct

Re: [PATCH] pids: introduce find_get_task_by_vpid helper

On 10/26, Mike Rapoport wrote: > > There are several functions that do find_task_by_vpid() followed by > get_task_struct(). We can use a helper function instead. Yes, agreed, I was going to do this many times. > --- a/kernel/futex.c > +++ b/kernel/futex.c > @@ -870,12 +870,7 @@ static struct

bpf.h drift due to bpf_sk_redirect_map()

Hi John, Recently the tools/perf/ build system noticed drift in tools/include/uapi/linux/bpf.h from its master copy include/uapi/linux/bpf.h, which comes from changes from you, can you please check this? [acme@jouet linux]$ diff -u tools/include/uapi/linux/bpf.h include/uapi/linux/bpf.h

Re: [Part2 PATCH v6 13/38] crypto: ccp: Add Secure Encrypted Virtualization (SEV) command support

On Mon, Oct 23, 2017 at 02:57:04PM -0500, Brijesh Singh wrote: > Calling PLATFORM_GET_STATUS is not required, we can manage the state through > a simple ref count variable. Issuing PSP commands will always be much more > expensive compare to accessing a protected global variable. What does

bpf.h drift due to bpf_sk_redirect_map()

Hi John, Recently the tools/perf/ build system noticed drift in tools/include/uapi/linux/bpf.h from its master copy include/uapi/linux/bpf.h, which comes from changes from you, can you please check this? [acme@jouet linux]$ diff -u tools/include/uapi/linux/bpf.h include/uapi/linux/bpf.h

Re: [Part2 PATCH v6 13/38] crypto: ccp: Add Secure Encrypted Virtualization (SEV) command support

On Mon, Oct 23, 2017 at 02:57:04PM -0500, Brijesh Singh wrote: > Calling PLATFORM_GET_STATUS is not required, we can manage the state through > a simple ref count variable. Issuing PSP commands will always be much more > expensive compare to accessing a protected global variable. What does

Re: [PATCH V12 0/5] mmc: Add Command Queue support

On 26/10/17 16:32, Linus Walleij wrote: > On Tue, Oct 24, 2017 at 10:40 AM, Adrian Hunter > wrote: > >> Here is V12 of the hardware command queue patches without the software >> command queue patches, now using blk-mq and now with blk-mq support for >> non-CQE I/O. > >

Re: [PATCH V12 0/5] mmc: Add Command Queue support

On 26/10/17 16:32, Linus Walleij wrote: > On Tue, Oct 24, 2017 at 10:40 AM, Adrian Hunter > wrote: > >> Here is V12 of the hardware command queue patches without the software >> command queue patches, now using blk-mq and now with blk-mq support for >> non-CQE I/O. > > Since I had my test

[PATCH v3] tpm: use struct tpm_chip for tpm_chip_find_get()

Device number (the character device index) is not a stable identifier for a TPM chip. That is the reason why every call site passes TPM_ANY_NUM to tpm_chip_find_get(). This commit changes the API in a way that instead a struct tpm_chip instance is given and NULL means the default chip. In

[PATCH v3] tpm: use struct tpm_chip for tpm_chip_find_get()

Device number (the character device index) is not a stable identifier for a TPM chip. That is the reason why every call site passes TPM_ANY_NUM to tpm_chip_find_get(). This commit changes the API in a way that instead a struct tpm_chip instance is given and NULL means the default chip. In

Re: [PATCH] drivers/crypto: Convert timers to use timer_setup()

On Wed, Oct 25, 2017 at 03:18:42AM -0700, Kees Cook wrote: > In preparation for unconditionally passing the struct timer_list pointer to > all timer callbacks, switch to using the new timer_setup() and from_timer() > to pass the timer pointer explicitly. > > Cc: Herbert Xu

Re: [PATCH] drivers/crypto: Convert timers to use timer_setup()

On Wed, Oct 25, 2017 at 03:18:42AM -0700, Kees Cook wrote: > In preparation for unconditionally passing the struct timer_list pointer to > all timer callbacks, switch to using the new timer_setup() and from_timer() > to pass the timer pointer explicitly. > > Cc: Herbert Xu > Cc: Jesper Nilsson

Re: [PATCH 03/18] x86/asm/64: Move SWAPGS into the common iret-to-usermode path

On Thu, Oct 26, 2017 at 4:26 AM, Andy Lutomirski wrote: > All of the code paths that ended up doing IRET to usermode did > SWAPGS immediately beforehand. Move the SWAPGS into the common > code. > > Signed-off-by: Andy Lutomirski >

Re: [PATCH 03/18] x86/asm/64: Move SWAPGS into the common iret-to-usermode path

On Thu, Oct 26, 2017 at 4:26 AM, Andy Lutomirski wrote: > All of the code paths that ended up doing IRET to usermode did > SWAPGS immediately beforehand. Move the SWAPGS into the common > code. > > Signed-off-by: Andy Lutomirski > +GLOBAL(swapgs_restore_regs_and_return_to_usermode) Is adding

Re: [PATCH] VFS: use synchronize_rcu_expedited() in namespace_unlock()

On Thu, Oct 26, 2017 at 05:27:43AM -0700, Paul E. McKenney wrote: > On Thu, Oct 26, 2017 at 01:26:37PM +1100, NeilBrown wrote: > > > > The synchronize_rcu() in namespace_unlock() is called every time > > a filesystem is unmounted. If a great many filesystems are mounted, > > this can cause a

Re: [PATCH] VFS: use synchronize_rcu_expedited() in namespace_unlock()

On Thu, Oct 26, 2017 at 05:27:43AM -0700, Paul E. McKenney wrote: > On Thu, Oct 26, 2017 at 01:26:37PM +1100, NeilBrown wrote: > > > > The synchronize_rcu() in namespace_unlock() is called every time > > a filesystem is unmounted. If a great many filesystems are mounted, > > this can cause a

Re: [PATCH] ARM64: dts: meson-gxl: Add alternate ARM Trusted Firmware reserved memory zone

On Wed, Oct 11, 2017 at 05:23:12PM +0200, Neil Armstrong wrote: > This year, Amlogic updated the ARM Trusted Firmware reserved memory mapping > for Meson GXL SoCs and products sold since May 2017 uses this alternate > reserved memory mapping. > But products had been sold using the previous

Re: [PATCH] ARM64: dts: meson-gxl: Add alternate ARM Trusted Firmware reserved memory zone

On Wed, Oct 11, 2017 at 05:23:12PM +0200, Neil Armstrong wrote: > This year, Amlogic updated the ARM Trusted Firmware reserved memory mapping > for Meson GXL SoCs and products sold since May 2017 uses this alternate > reserved memory mapping. > But products had been sold using the previous

Re: [PATCH 2/2] kvm: x86: fix KVM_XEN_HVM_CONFIG ioctl

On Thu, Oct 26, 2017 at 3:45 PM, Paolo Bonzini wrote: > This ioctl is obsolete (it was used by Xenner as far as I know) but > still let's not break it gratuitously... Its handler is copying > directly into struct kvm. Go through a bounce buffer instead, with > the added

Re: [PATCH 2/2] kvm: x86: fix KVM_XEN_HVM_CONFIG ioctl

On Thu, Oct 26, 2017 at 3:45 PM, Paolo Bonzini wrote: > This ioctl is obsolete (it was used by Xenner as far as I know) but > still let's not break it gratuitously... Its handler is copying > directly into struct kvm. Go through a bounce buffer instead, with > the added benefit that we can

[PATCH v2 1/3] usb: host: remove ehci-msm.c

No Qualcomm SoC requires the "ehci-msm.c" code any more. So remove it. Suggested-by: Stephen Boyd Signed-off-by: Alex Elder Acked-by: Bjorn Andersson Acked-by: Andy Gross --- v2: Update the Kconfig

[PATCH v2 1/3] usb: host: remove ehci-msm.c

No Qualcomm SoC requires the "ehci-msm.c" code any more. So remove it. Suggested-by: Stephen Boyd Signed-off-by: Alex Elder Acked-by: Bjorn Andersson Acked-by: Andy Gross --- v2: Update the Kconfig file so it no longer offers to build this code, as suggested by Manu Gautam.

Re: [PATCH] iio/light/opt3001: Use common error handling code in opt3001_get_lux()

On 26/10/2017 at 14:17:30 +0200, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 26 Oct 2017 14:06:49 +0200 > > * Add jump targets so that two error messages are stored only once > at the end of this function implementation. > > * Adjust condition

[PATCH v2 0/3] usb: remove some unused code

This series deletes some Qualcomm USB code is no longer needed by any Qualcomm hardware. This version properly deletes the sections of Kconfig files that control whether the deleted code gets built. (This time I'm also sending to linux-arm-msm and linux-arm-kernel.)

[PATCH v2 3/3] usb: phy: remove phy-qcom-8x16-usb.c

No Qualcomm SoC requires the "phy-qcom-8x16-usb.c" USB phy driver support any more, so remove the code. Suggested-by: Stephen Boyd Signed-off-by: Alex Elder Acked-by: Bjorn Andersson Acked-by: Andy Gross

Re: [PATCH] iio/light/opt3001: Use common error handling code in opt3001_get_lux()

On 26/10/2017 at 14:17:30 +0200, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 26 Oct 2017 14:06:49 +0200 > > * Add jump targets so that two error messages are stored only once > at the end of this function implementation. > > * Adjust condition checks. > > * Replace string

[PATCH v2 0/3] usb: remove some unused code

This series deletes some Qualcomm USB code is no longer needed by any Qualcomm hardware. This version properly deletes the sections of Kconfig files that control whether the deleted code gets built. (This time I'm also sending to linux-arm-msm and linux-arm-kernel.)

[PATCH v2 3/3] usb: phy: remove phy-qcom-8x16-usb.c

No Qualcomm SoC requires the "phy-qcom-8x16-usb.c" USB phy driver support any more, so remove the code. Suggested-by: Stephen Boyd Signed-off-by: Alex Elder Acked-by: Bjorn Andersson Acked-by: Andy Gross --- v2: Update the Kconfig file so it no longer offers to build this code, as

[PATCH v2 2/3] usb: phy: remove phy-msm-usb.c

No Qualcomm SoC requires the "phy-msm-usb.c" USB phy driver support any more, so remove the code. Suggested-by: Stephen Boyd Signed-off-by: Alex Elder Acked-by: Bjorn Andersson Acked-by: Andy Gross ---

[PATCH v2 2/3] usb: phy: remove phy-msm-usb.c

No Qualcomm SoC requires the "phy-msm-usb.c" USB phy driver support any more, so remove the code. Suggested-by: Stephen Boyd Signed-off-by: Alex Elder Acked-by: Bjorn Andersson Acked-by: Andy Gross --- v2: Update the Kconfig file so it no longer offers to build this code, as suggested by

[PATCH 1/2] kvm: whitelist struct kvm_vcpu_arch

On x86, ARM and s390, struct kvm_vcpu_arch has a usercopy region taht is read and written by the KVM_GET/SET_CPUID2 ioctls (x86) or KVM_GET/SET_ONE_REG (ARM/s390). Without whitelisting the area, KVM is completely broken on those architectures with usercopy hardening enabled. For now, allow

[PATCH 1/2] kvm: whitelist struct kvm_vcpu_arch

On x86, ARM and s390, struct kvm_vcpu_arch has a usercopy region taht is read and written by the KVM_GET/SET_CPUID2 ioctls (x86) or KVM_GET/SET_ONE_REG (ARM/s390). Without whitelisting the area, KVM is completely broken on those architectures with usercopy hardening enabled. For now, allow

Re: [PATCH v5 1/2] Add new elements for per-event-dump option

Em Thu, Oct 26, 2017 at 10:01:43AM -0300, Arnaldo Carvalho de Melo escreveu: > Em Wed, Oct 25, 2017 at 04:53:18PM +0800, yuzhoujian escreveu: > > + boolper_event_dump; > > + const char *last_evsel_name; > > enum show_feature_header show_feat_hdr; > Ditto, this should be

Re: [PATCH v5 1/2] Add new elements for per-event-dump option

Em Thu, Oct 26, 2017 at 10:01:43AM -0300, Arnaldo Carvalho de Melo escreveu: > Em Wed, Oct 25, 2017 at 04:53:18PM +0800, yuzhoujian escreveu: > > + boolper_event_dump; > > + const char *last_evsel_name; > > enum show_feature_header show_feat_hdr; > Ditto, this should be

[PATCH] iio/pressure/hp206c: Use common error handling code in hp206c_conv_and_read()

From: Markus Elfring Date: Thu, 26 Oct 2017 15:34:46 +0200 Add a jump target so that a specific error message is stored only once at the end of this function implementation. Replace two calls of the function "dev_err" by goto statements. This issue was detected by

[PATCH] iio/pressure/hp206c: Use common error handling code in hp206c_conv_and_read()

From: Markus Elfring Date: Thu, 26 Oct 2017 15:34:46 +0200 Add a jump target so that a specific error message is stored only once at the end of this function implementation. Replace two calls of the function "dev_err" by goto statements. This issue was detected by using the Coccinelle software.

[PATCH 2/2] kvm: x86: fix KVM_XEN_HVM_CONFIG ioctl

This ioctl is obsolete (it was used by Xenner as far as I know) but still let's not break it gratuitously... Its handler is copying directly into struct kvm. Go through a bounce buffer instead, with the added benefit that we can actually do something useful with the flags argument---the previous

[PATCH 2/2] kvm: x86: fix KVM_XEN_HVM_CONFIG ioctl

This ioctl is obsolete (it was used by Xenner as far as I know) but still let's not break it gratuitously... Its handler is copying directly into struct kvm. Go through a bounce buffer instead, with the added benefit that we can actually do something useful with the flags argument---the previous

[PATCH v2 0/2] KVM: fixes for the kernel-hardening tree

Four KVM ioctls (KVM_GET/SET_CPUID2 on x86, KVM_GET/SET_ONE_REG on ARM and s390) directly access the kvm_vcpu_arch struct. Therefore, the new usercopy hardening work in linux-next, which forbids copies from and to slab objects unless they are from kmalloc or explicitly whitelisted, breaks KVM on

[PATCH v2 0/2] KVM: fixes for the kernel-hardening tree

Four KVM ioctls (KVM_GET/SET_CPUID2 on x86, KVM_GET/SET_ONE_REG on ARM and s390) directly access the kvm_vcpu_arch struct. Therefore, the new usercopy hardening work in linux-next, which forbids copies from and to slab objects unless they are from kmalloc or explicitly whitelisted, breaks KVM on

Re: [PATCH 1/2] hwmon: (jc42) optionally try to disable the SMBUS timeout

On 10/25/2017 11:44 PM, Peter Rosin wrote: On 2017-10-18 04:38, Guenter Roeck wrote: On 10/17/2017 03:16 PM, Rob Herring wrote: On Fri, Oct 13, 2017 at 01:35:27PM -0700, Guenter Roeck wrote: On Fri, Oct 13, 2017 at 04:26:57PM +0200, Peter Rosin wrote: On 2017-10-13 15:50, Guenter Roeck

Re: [PATCH 1/2] hwmon: (jc42) optionally try to disable the SMBUS timeout

On 10/25/2017 11:44 PM, Peter Rosin wrote: On 2017-10-18 04:38, Guenter Roeck wrote: On 10/17/2017 03:16 PM, Rob Herring wrote: On Fri, Oct 13, 2017 at 01:35:27PM -0700, Guenter Roeck wrote: On Fri, Oct 13, 2017 at 04:26:57PM +0200, Peter Rosin wrote: On 2017-10-13 15:50, Guenter Roeck

Re: 4.14-rc2 on thinkpad x220: out of memory when inserting mmc card

On Mon, Oct 23, 2017 at 11:27 PM, Pavel Machek wrote: > On Mon 2017-10-23 14:16:40, Linus Walleij wrote: >> On Mon, Oct 23, 2017 at 11:31 AM, Pavel Machek wrote: >> >> >> > Thinkpad X220... how do I tell if I was using them? I believe so, >> >> > because I uncovered

Re: 4.14-rc2 on thinkpad x220: out of memory when inserting mmc card

On Mon, Oct 23, 2017 at 11:27 PM, Pavel Machek wrote: > On Mon 2017-10-23 14:16:40, Linus Walleij wrote: >> On Mon, Oct 23, 2017 at 11:31 AM, Pavel Machek wrote: >> >> >> > Thinkpad X220... how do I tell if I was using them? I believe so, >> >> > because I uncovered bug in them before. >> >> >>

Re: [PATCH] PREEMPT_RT: sched/rr, sched/fair: defer CFS scheduler put_prev_task()

On Wed, Oct 25, 2017 at 03:26:43PM -0700, Allen Martin wrote: This is a _really_ ugly patch.

Re: [PATCH] PREEMPT_RT: sched/rr, sched/fair: defer CFS scheduler put_prev_task()

On Wed, Oct 25, 2017 at 03:26:43PM -0700, Allen Martin wrote: This is a _really_ ugly patch.

[PATCH] hw_random: Include device.h instead of declaring struct device

Include linux/device.h instead of declaring struct device. Signed-off-by: PrasannaKumar Muralidharan --- include/linux/hw_random.h | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/include/linux/hw_random.h b/include/linux/hw_random.h index

[PATCH] hw_random: Include device.h instead of declaring struct device

Include linux/device.h instead of declaring struct device. Signed-off-by: PrasannaKumar Muralidharan --- include/linux/hw_random.h | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/include/linux/hw_random.h b/include/linux/hw_random.h index bee0827..2ec9af7 100644 ---

Re: [tip:sched/core] sched/idle: Micro-optimize the idle loop

On Thu, Oct 26, 2017 at 02:31:34AM -0700, tip-bot for Cheng Jian wrote: > After patch (execution in loop): > 872: 0f ae e8lfence > ARM64: > After patch (execution in loop): > c84: d5033d9fdsb ld > @@ -225,7 +226,7 @@ static void do_idle(void)

Re: [tip:sched/core] sched/idle: Micro-optimize the idle loop

On Thu, Oct 26, 2017 at 02:31:34AM -0700, tip-bot for Cheng Jian wrote: > After patch (execution in loop): > 872: 0f ae e8lfence > ARM64: > After patch (execution in loop): > c84: d5033d9fdsb ld > @@ -225,7 +226,7 @@ static void do_idle(void)

Re: [PATCH V12 0/5] mmc: Add Command Queue support

On Tue, Oct 24, 2017 at 10:40 AM, Adrian Hunter wrote: > Here is V12 of the hardware command queue patches without the software > command queue patches, now using blk-mq and now with blk-mq support for > non-CQE I/O. Since I had my test setup going I gave this a spin

Re: [PATCH V12 0/5] mmc: Add Command Queue support

On Tue, Oct 24, 2017 at 10:40 AM, Adrian Hunter wrote: > Here is V12 of the hardware command queue patches without the software > command queue patches, now using blk-mq and now with blk-mq support for > non-CQE I/O. Since I had my test setup going I gave this a spin with the same set of tests

[RFC PATCH v8 3/7] arm64: dts: rockchip: Handle PCIe WAKE# signal in pcie driver for Gru

Currently we are handling PCIe WAKE# signal in mrvl wifi driver. Move it to rockchip pcie driver for Gru boards. Also avoid this irq been considered as the PCI interrupt pin in the of_irq_parse_pci(). Signed-off-by: Jeffy Chen --- Changes in v8: Rewrite the commit

[RFC PATCH v8 3/7] arm64: dts: rockchip: Handle PCIe WAKE# signal in pcie driver for Gru

Currently we are handling PCIe WAKE# signal in mrvl wifi driver. Move it to rockchip pcie driver for Gru boards. Also avoid this irq been considered as the PCI interrupt pin in the of_irq_parse_pci(). Signed-off-by: Jeffy Chen --- Changes in v8: Rewrite the commit message. Changes in v7: None

[RFC PATCH v8 5/7] PCI: Make pci_platform_pm_ops's callbacks optional

Allow platforms not to provide some of the pci_platform_pm_ops's callbacks. Also change the return value -ENOSYS to -ENODEV for: warning: drivers/pci/pci.c,594: ENOSYS means 'invalid syscall nr' and nothing else Signed-off-by: Jeffy Chen --- Changes in v8: None

[RFC PATCH v8 5/7] PCI: Make pci_platform_pm_ops's callbacks optional

Allow platforms not to provide some of the pci_platform_pm_ops's callbacks. Also change the return value -ENOSYS to -ENODEV for: warning: drivers/pci/pci.c,594: ENOSYS means 'invalid syscall nr' and nothing else Signed-off-by: Jeffy Chen --- Changes in v8: None Changes in v7: None Changes in

[RFC PATCH v8 6/7] PCI / PM: Move acpi wakeup code to pci core

Move acpi wakeup code to pci core as pci_set_wakeup(), so that other platform could reuse it. Also add .setup_dev() / .setup_host_bridge() / .cleanup() platform pm ops's callbacks to setup and cleanup pci devices and host bridge for wakeup. Signed-off-by: Jeffy Chen

[RFC PATCH v8 6/7] PCI / PM: Move acpi wakeup code to pci core

Move acpi wakeup code to pci core as pci_set_wakeup(), so that other platform could reuse it. Also add .setup_dev() / .setup_host_bridge() / .cleanup() platform pm ops's callbacks to setup and cleanup pci devices and host bridge for wakeup. Signed-off-by: Jeffy Chen --- Changes in v8: None

[RFC PATCH v8 4/7] of/irq: Adjust of pci irq parsing for multiple interrupts

Currently we are considering the first irq as the PCI interrupt pin, but a pci device may have multiple interrupts(e.g. PCIe WAKE# pin). Only parse the PCI interrupt pin when the irq is unnamed or named as "pci". Signed-off-by: Jeffy Chen --- Changes in v8: None

[RFC PATCH v8 7/7] PCI / PM: Add support for the PCIe WAKE# signal for OF

Add pci-of.c to handle the PCIe WAKE# interrupt. Also use the dedicated wakeirq infrastructure to simplify it. Signed-off-by: Jeffy Chen --- Changes in v8: Add pci-of.c and use platform_pm_ops to handle the PCIe WAKE# signal. Changes in v7: Move PCIE_WAKE handling

[RFC PATCH v8 4/7] of/irq: Adjust of pci irq parsing for multiple interrupts

Currently we are considering the first irq as the PCI interrupt pin, but a pci device may have multiple interrupts(e.g. PCIe WAKE# pin). Only parse the PCI interrupt pin when the irq is unnamed or named as "pci". Signed-off-by: Jeffy Chen --- Changes in v8: None Changes in v7: None Changes in

[RFC PATCH v8 7/7] PCI / PM: Add support for the PCIe WAKE# signal for OF

Add pci-of.c to handle the PCIe WAKE# interrupt. Also use the dedicated wakeirq infrastructure to simplify it. Signed-off-by: Jeffy Chen --- Changes in v8: Add pci-of.c and use platform_pm_ops to handle the PCIe WAKE# signal. Changes in v7: Move PCIE_WAKE handling into pci core. Changes in

[RFC PATCH v8 0/7] PCI: rockchip: Move PCIe WAKE# handling into pci core

Currently we are handling wake irq in mrvl wifi driver. Move it into pci core. Tested on my chromebook bob(with cros 4.4 kernel and mrvl wifi). Changes in v8: Add optional "pci", and rewrite commit message. Rewrite the commit message. Add pci-of.c and use platform_pm_ops to handle the PCIe

[RFC PATCH v8 0/7] PCI: rockchip: Move PCIe WAKE# handling into pci core

Currently we are handling wake irq in mrvl wifi driver. Move it into pci core. Tested on my chromebook bob(with cros 4.4 kernel and mrvl wifi). Changes in v8: Add optional "pci", and rewrite commit message. Rewrite the commit message. Add pci-of.c and use platform_pm_ops to handle the PCIe

[RFC PATCH v8 2/7] mwifiex: Disable wakeup irq handling for pcie

We are going to handle the wakeup irq in the pci core. Signed-off-by: Jeffy Chen --- Changes in v8: None Changes in v7: None Changes in v6: None Changes in v5: None Changes in v3: None Changes in v2: None drivers/net/wireless/marvell/mwifiex/main.c | 4 1 file

[RFC PATCH v8 2/7] mwifiex: Disable wakeup irq handling for pcie

We are going to handle the wakeup irq in the pci core. Signed-off-by: Jeffy Chen --- Changes in v8: None Changes in v7: None Changes in v6: None Changes in v5: None Changes in v3: None Changes in v2: None drivers/net/wireless/marvell/mwifiex/main.c | 4 1 file changed, 4 insertions(+)

[RFC PATCH v8 1/7] dt-bindings: PCI: Add definition of PCIe WAKE# irq and PCI irq

Add optional interrupts for PCIe WAKE# pin and PCI interrupt pin. Signed-off-by: Jeffy Chen --- Changes in v8: Add optional "pci", and rewrite commit message. Changes in v7: None Changes in v6: None Changes in v5: Move to pci.txt Changes in v3: None Changes in v2:

[RFC PATCH v8 1/7] dt-bindings: PCI: Add definition of PCIe WAKE# irq and PCI irq

Add optional interrupts for PCIe WAKE# pin and PCI interrupt pin. Signed-off-by: Jeffy Chen --- Changes in v8: Add optional "pci", and rewrite commit message. Changes in v7: None Changes in v6: None Changes in v5: Move to pci.txt Changes in v3: None Changes in v2: None

Re: Enabling peer to peer device transactions for PCIe devices

- Original Message - > From: "David Laight" > To: "Petrosyan, Ludwig" , "Logan Gunthorpe" > > Cc: "Alexander Deucher" , "linux-kernel" > , "linux-rdma" >

Re: [PATCH 1/3] usb: host: remove ehci-msm.c

On 10/26/2017 12:10 AM, Manu Gautam wrote: > Hi, I'll re-send with the kconfig updates pointed out by you and Felipe Balbi. Sorry about that. -Alex > > On 10/26/2017 3:31 AM, Alex Elder wrote: >> No Qualcomm SoC requires the "ehci-msm.c" code any more.

Re: Enabling peer to peer device transactions for PCIe devices

- Original Message - > From: "David Laight" > To: "Petrosyan, Ludwig" , "Logan Gunthorpe" > > Cc: "Alexander Deucher" , "linux-kernel" > , "linux-rdma" > , "linux-nvdimm" , > "Linux-media" , > "dri-devel" , "linux-pci" > , "John Bridgman" > , "Felix Kuehling" , "Serguei >

Re: [PATCH 1/3] usb: host: remove ehci-msm.c

On 10/26/2017 12:10 AM, Manu Gautam wrote: > Hi, I'll re-send with the kconfig updates pointed out by you and Felipe Balbi. Sorry about that. -Alex > > On 10/26/2017 3:31 AM, Alex Elder wrote: >> No Qualcomm SoC requires the "ehci-msm.c" code any more.

LTP cases covered by 0day kernel test robot

Hi Ben, Here you can find the LTP cases that we run or ignore. The ignored ones are mostly problematic or too time consuming for us. https://github.com/intel/lkp-tests/blob/master/jobs/ltp.yaml https://github.com/intel/lkp-tests/blob/master/jobs/ltp-1hdd.yaml

LTP cases covered by 0day kernel test robot

Hi Ben, Here you can find the LTP cases that we run or ignore. The ignored ones are mostly problematic or too time consuming for us. https://github.com/intel/lkp-tests/blob/master/jobs/ltp.yaml https://github.com/intel/lkp-tests/blob/master/jobs/ltp-1hdd.yaml

[PATCH] pids: introduce find_get_task_by_vpid helper

There are several functions that do find_task_by_vpid() followed by get_task_struct(). We can use a helper function instead. Signed-off-by: Mike Rapoport --- include/linux/sched.h | 5 + kernel/futex.c | 7 +-- kernel/pid.c | 13

[PATCH] pids: introduce find_get_task_by_vpid helper

There are several functions that do find_task_by_vpid() followed by get_task_struct(). We can use a helper function instead. Signed-off-by: Mike Rapoport --- include/linux/sched.h | 5 + kernel/futex.c | 7 +-- kernel/pid.c | 13 + kernel/ptrace.c

Re: [tip:x86/mm] x86/mm: Add support for early encryption/decryption of memory

On 10/25/2017 12:34 PM, Dave Hansen wrote: On 07/18/2017 03:51 AM, tip-bot for Tom Lendacky wrote: +/* + * This routine does not change the underlying encryption setting of the + * page(s) that map this memory. It assumes that eventually the memory is + * meant to be accessed as either

Re: [tip:x86/mm] x86/mm: Add support for early encryption/decryption of memory

On 10/25/2017 12:34 PM, Dave Hansen wrote: On 07/18/2017 03:51 AM, tip-bot for Tom Lendacky wrote: +/* + * This routine does not change the underlying encryption setting of the + * page(s) that map this memory. It assumes that eventually the memory is + * meant to be accessed as either

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

On 10/19/2017 02:21 PM, Michal Hocko wrote: > On Thu 19-10-17 10:20:41, Michal Hocko wrote: >> On Thu 19-10-17 16:33:56, Joonsoo Kim wrote: >>> On Thu, Oct 19, 2017 at 09:15:03AM +0200, Michal Hocko wrote: On Thu 19-10-17 11:51:11, Joonsoo Kim wrote: >> [...] > Hello, > > This

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

On 10/19/2017 02:21 PM, Michal Hocko wrote: > On Thu 19-10-17 10:20:41, Michal Hocko wrote: >> On Thu 19-10-17 16:33:56, Joonsoo Kim wrote: >>> On Thu, Oct 19, 2017 at 09:15:03AM +0200, Michal Hocko wrote: On Thu 19-10-17 11:51:11, Joonsoo Kim wrote: >> [...] > Hello, > > This

Re: [v2,04/16] iommu/vt-d: support flushing more TLB types

On 10/6/2017 00:03, Jacob Pan wrote: Signed-off-by: Jacob Pan --- drivers/iommu/dmar.c| 53 ++--- drivers/iommu/intel-iommu.c | 3 ++- include/linux/intel-iommu.h | 10 +++-- 3 files changed, 60

Re: [v2,04/16] iommu/vt-d: support flushing more TLB types

On 10/6/2017 00:03, Jacob Pan wrote: Signed-off-by: Jacob Pan --- drivers/iommu/dmar.c| 53 ++--- drivers/iommu/intel-iommu.c | 3 ++- include/linux/intel-iommu.h | 10 +++-- 3 files changed, 60 insertions(+), 6 deletions(-) diff --git

Re: [PATCH v5 1/2] Add new elements for per-event-dump option

Em Wed, Oct 25, 2017 at 04:53:18PM +0800, yuzhoujian escreveu: > This patch will add two elements for perf_tool struct: per_event_dump > is used to mark the per-event-dump option, last_evsel_name is used > to save last evsel's name. Add a new struct perf_script_evsel to > save evsel's specific

Re: [PATCH v5 1/2] Add new elements for per-event-dump option

Em Wed, Oct 25, 2017 at 04:53:18PM +0800, yuzhoujian escreveu: > This patch will add two elements for perf_tool struct: per_event_dump > is used to mark the per-event-dump option, last_evsel_name is used > to save last evsel's name. Add a new struct perf_script_evsel to > save evsel's specific

Re: [PATCH 0/2] livepatch: Additional fixes for callbacks feature

On Fri, 20 Oct 2017, Petr Mladek wrote: > I have found few small problems when reviewing the patch adding > (un)patch callback, see > https://lkml.kernel.org/r/1507921723-1996-2-git-send-email-joe.lawre...@redhat.com > Feel free to merge them with the original patch if still possible. > > Petr

Re: [PATCH 0/2] livepatch: Additional fixes for callbacks feature

On Fri, 20 Oct 2017, Petr Mladek wrote: > I have found few small problems when reviewing the patch adding > (un)patch callback, see > https://lkml.kernel.org/r/1507921723-1996-2-git-send-email-joe.lawre...@redhat.com > Feel free to merge them with the original patch if still possible. > > Petr

Re: Fixing CVE-2017-15361

On Thu, 26 Oct 2017 13:16:32 +0200 Jarkko Sakkinen wrote: > On Thu, Oct 26, 2017 at 12:26:10AM +0200, Peter Huewe wrote: > > > > > > Am 25. Oktober 2017 20:53:49 MESZ schrieb Jarkko Sakkinen > > : > > >On Wed, Oct 25, 2017 at

Re: Fixing CVE-2017-15361

On Thu, 26 Oct 2017 13:16:32 +0200 Jarkko Sakkinen wrote: > On Thu, Oct 26, 2017 at 12:26:10AM +0200, Peter Huewe wrote: > > > > > > Am 25. Oktober 2017 20:53:49 MESZ schrieb Jarkko Sakkinen > > : > > >On Wed, Oct 25, 2017 at 07:17:17AM -0700, Matthew Garrett wrote: > > >> On Wed, Oct 25,

Re: Query regarding __hrtimer_get_next_event()

On Thu, 26 Oct 2017, Neeraj Upadhyay wrote: > We have one query regarding the __hrtimer_get_next_event(). > The expires_next.tv64 is set to 0 if it is < 0. We observed > an hrtimer interrupt storm for one of the hrtimers with > below properties: > > * Expires for the hrtimer was set to KTIME_MAX.

Re: [PATCH v3] lib: optimize cpumask_next_and()

> - Refactored _find_next_common_bit into _find_next_bit., as suggested >by Yury Norov. This has no adverse effects on the performance side, >as the compiler successfully inlines the code. 1) Gentoo ships 5.4.0 which doesn't inline this code on x86_64 defconfig (which has

Re: [PATCH v3] lib: optimize cpumask_next_and()

> - Refactored _find_next_common_bit into _find_next_bit., as suggested >by Yury Norov. This has no adverse effects on the performance side, >as the compiler successfully inlines the code. 1) Gentoo ships 5.4.0 which doesn't inline this code on x86_64 defconfig (which has

Re: Query regarding __hrtimer_get_next_event()

On Thu, 26 Oct 2017, Neeraj Upadhyay wrote: > We have one query regarding the __hrtimer_get_next_event(). > The expires_next.tv64 is set to 0 if it is < 0. We observed > an hrtimer interrupt storm for one of the hrtimers with > below properties: > > * Expires for the hrtimer was set to KTIME_MAX.

Re: [PATCH v9 02/29] x86/boot: Relocate definition of the initial state of CR0

On Thu, Oct 26, 2017 at 02:02:02AM -0700, Andy Lutomirski wrote: > I'm assuming that UMIP_REPORTED_CR0 will never change. If CR0 gets a > new field that we set some day, then I assume that CR0_STATE would add > that bit but UMIP_REPORTED_CR0 would not. Yeah, let's do that when it is actually

Re: [PATCH v9 02/29] x86/boot: Relocate definition of the initial state of CR0

On Thu, Oct 26, 2017 at 02:02:02AM -0700, Andy Lutomirski wrote: > I'm assuming that UMIP_REPORTED_CR0 will never change. If CR0 gets a > new field that we set some day, then I assume that CR0_STATE would add > that bit but UMIP_REPORTED_CR0 would not. Yeah, let's do that when it is actually

[PATCH v2] ipv6: esp6: use BUG_ON instead of if condition followed by BUG

Use BUG_ON instead of if condition followed by BUG in esp_remove_trailer. This issue was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- Changes in v2: Update the code as suggested by Herbert Xu: ret = foo(); BUG_ON(ret);

[PATCH v2] ipv6: esp6: use BUG_ON instead of if condition followed by BUG

Use BUG_ON instead of if condition followed by BUG in esp_remove_trailer. This issue was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- Changes in v2: Update the code as suggested by Herbert Xu: ret = foo(); BUG_ON(ret); net/ipv6/esp6.c | 4 ++-- 1 file

[PATCH 1/3] phy: phy-mtk-tphy: use auto instead of force to bypass utmi signals

When system is running, if usb2 phy is forced to bypass utmi signals, all PLL will be turned off, and it can't detect device connection anymore, so replace force mode with auto mode which can bypass utmi signals automatically if no device attached for normal flow. But keep the force mode to fix RX

[PATCH 1/3] phy: phy-mtk-tphy: use auto instead of force to bypass utmi signals

When system is running, if usb2 phy is forced to bypass utmi signals, all PLL will be turned off, and it can't detect device connection anymore, so replace force mode with auto mode which can bypass utmi signals automatically if no device attached for normal flow. But keep the force mode to fix RX

[PATCH 3/3] phy: phy-mtk-tphy: fix alignment warning

Fix alignment warning by checkpatch.pl with --strict Signed-off-by: Chunfeng Yun --- drivers/phy/mediatek/Kconfig|8 drivers/phy/mediatek/phy-mtk-tphy.c | 24 2 files changed, 16 insertions(+), 16 deletions(-) diff

[PATCH 3/3] phy: phy-mtk-tphy: fix alignment warning

Fix alignment warning by checkpatch.pl with --strict Signed-off-by: Chunfeng Yun --- drivers/phy/mediatek/Kconfig|8 drivers/phy/mediatek/phy-mtk-tphy.c | 24 2 files changed, 16 insertions(+), 16 deletions(-) diff --git

<    5   6   7   8   9   10   11   12   13   14   >