[PATCH 0/3] Drivers: hv: vmbus: Miscellaneous enhancements and fixes

From: "K. Y. Srinivasan" Miscellaneous enhancements and fixes. K. Y. Srinivasan (1): Drivers: hv: vmbus: Make pannic reporting to be more useful Stephen Hemminger (2): Drivers: hv: vmbus: Expose per-channel interrupts and events counters vmbus: initialize reserved

[PATCH 0/3] Drivers: hv: vmbus: Miscellaneous enhancements and fixes

From: "K. Y. Srinivasan" Miscellaneous enhancements and fixes. K. Y. Srinivasan (1): Drivers: hv: vmbus: Make pannic reporting to be more useful Stephen Hemminger (2): Drivers: hv: vmbus: Expose per-channel interrupts and events counters vmbus: initialize reserved fields in messages

Re: [linux-next][DLPAR CPU][Oops] Kernel crash with CPU hotunplug

Abdul Haleem writes: > Hi, > > linux-next kernel panic while DLPAR CPU add/remove operation in a loop. > > Test: CPU hot-unplug > Machine Type: Power8 PowerVM LPAR > kernel: 4.14.0-rc2-next-20170928 > gcc : 5.2.1 > > trace logs > -- > cpu 10 (hwid 10) Ready

Re: [linux-next][DLPAR CPU][Oops] Kernel crash with CPU hotunplug

Abdul Haleem writes: > Hi, > > linux-next kernel panic while DLPAR CPU add/remove operation in a loop. > > Test: CPU hot-unplug > Machine Type: Power8 PowerVM LPAR > kernel: 4.14.0-rc2-next-20170928 > gcc : 5.2.1 > > trace logs > -- > cpu 10 (hwid 10) Ready to die... > cpu 11 (hwid 11)

Re: [RFC PATCH -tip 0/5] kprobes: Abolish jprobe APIs

On Thu, 5 Oct 2017 16:35:22 -0700 Kees Cook wrote: > On Thu, Oct 5, 2017 at 4:13 PM, Masami Hiramatsu wrote: > > Hi, > > > > This series abolishes jprobe APIs and remove or disable related > > code. This is a preparation of removing all jprobe code

Re: [RFC PATCH -tip 0/5] kprobes: Abolish jprobe APIs

On Thu, 5 Oct 2017 16:35:22 -0700 Kees Cook wrote: > On Thu, Oct 5, 2017 at 4:13 PM, Masami Hiramatsu wrote: > > Hi, > > > > This series abolishes jprobe APIs and remove or disable related > > code. This is a preparation of removing all jprobe code (including > > kprobe's break_handler.) > >

Re: r8169 Wake-on-LAN causes immediate ACPI GPE wakeup

Daniel Drake : [...] > Also, is there a standard behaviour defined for ethernet drivers > regarding wake-on-LAN? r8169 appears to enable wake-on-LAN by default > if it believes the hardware is capable of it, If so it isn't its designed behavior. The r8169 driver does not

Re: r8169 Wake-on-LAN causes immediate ACPI GPE wakeup

Daniel Drake : [...] > Also, is there a standard behaviour defined for ethernet drivers > regarding wake-on-LAN? r8169 appears to enable wake-on-LAN by default > if it believes the hardware is capable of it, If so it isn't its designed behavior. The r8169 driver does not enable specific WoL

Re: [PATCH] md: raid10: remove VLAIS

Hi Neil, El Fri, Oct 06, 2017 at 10:58:59AM +1100 NeilBrown ha dit: > On Thu, Oct 05 2017, Matthias Kaehlcke wrote: > > > The raid10 driver can't be built with clang since it uses a variable > > length array in a structure (VLAIS): > > > > drivers/md/raid10.c:4583:17: error: fields must have a

Re: [PATCH] md: raid10: remove VLAIS

Hi Neil, El Fri, Oct 06, 2017 at 10:58:59AM +1100 NeilBrown ha dit: > On Thu, Oct 05 2017, Matthias Kaehlcke wrote: > > > The raid10 driver can't be built with clang since it uses a variable > > length array in a structure (VLAIS): > > > > drivers/md/raid10.c:4583:17: error: fields must have a

Re: [RFC PATCH -tip 0/5] kprobes: Abolish jprobe APIs

On Thu, Oct 5, 2017 at 4:58 PM, Steven Rostedt wrote: > On Thu, 5 Oct 2017 16:35:22 -0700 > Kees Cook wrote: > >> > As far as I can see, tcp probe, dccp probe, sctp probe and lkdtm >> > are using jprobe to probe function. Please consider to migrate. >>

Re: [RFC PATCH -tip 0/5] kprobes: Abolish jprobe APIs

On Thu, Oct 5, 2017 at 4:58 PM, Steven Rostedt wrote: > On Thu, 5 Oct 2017 16:35:22 -0700 > Kees Cook wrote: > >> > As far as I can see, tcp probe, dccp probe, sctp probe and lkdtm >> > are using jprobe to probe function. Please consider to migrate. >> >> I'm happy to do so, but I'm quite

Re: [PATCH] md: raid10: remove VLAIS

On Thu, Oct 05 2017, Matthias Kaehlcke wrote: > The raid10 driver can't be built with clang since it uses a variable > length array in a structure (VLAIS): > > drivers/md/raid10.c:4583:17: error: fields must have a constant size: > 'variable length array in structure' extension will never be

[PATCH v3] irqchip/gicv3: Add support for Range Selector (RS) feature

A new feature Range Selector (RS) has been added to GIC specification in order to support more than 16 CPUs at affinity level 0. New fields are introduced in SGI system registers (ICC_SGI0R_EL1, ICC_SGI1R_EL1 and ICC_ASGI1R_EL1) to relax an artificial limit of 16 at level 0. - A new RSS field in

Re: [PATCH] md: raid10: remove VLAIS

On Thu, Oct 05 2017, Matthias Kaehlcke wrote: > The raid10 driver can't be built with clang since it uses a variable > length array in a structure (VLAIS): > > drivers/md/raid10.c:4583:17: error: fields must have a constant size: > 'variable length array in structure' extension will never be

[PATCH v3] irqchip/gicv3: Add support for Range Selector (RS) feature

A new feature Range Selector (RS) has been added to GIC specification in order to support more than 16 CPUs at affinity level 0. New fields are introduced in SGI system registers (ICC_SGI0R_EL1, ICC_SGI1R_EL1 and ICC_ASGI1R_EL1) to relax an artificial limit of 16 at level 0. - A new RSS field in

Re: [RFC PATCH -tip 0/5] kprobes: Abolish jprobe APIs

On Thu, 5 Oct 2017 16:35:22 -0700 Kees Cook wrote: > > As far as I can see, tcp probe, dccp probe, sctp probe and lkdtm > > are using jprobe to probe function. Please consider to migrate. > > I'm happy to do so, but I'm quite unfamiliar with how to do this (I > didn't

Re: [RFC PATCH -tip 0/5] kprobes: Abolish jprobe APIs

On Thu, 5 Oct 2017 16:35:22 -0700 Kees Cook wrote: > > As far as I can see, tcp probe, dccp probe, sctp probe and lkdtm > > are using jprobe to probe function. Please consider to migrate. > > I'm happy to do so, but I'm quite unfamiliar with how to do this (I > didn't write lkdtm's jprobe

RE: [PATCH v4 4/5] cramfs: add mmap support

On Thursday, October 05, 2017, Nicolas Pitre wrote: > Do you have the same amount of free memory once booted in both cases? Yes, almost exactly the same, so obvious it must be working the same for both cases. That's enough evidence for me. Thanks. Chris

RE: [PATCH v4 4/5] cramfs: add mmap support

On Thursday, October 05, 2017, Nicolas Pitre wrote: > Do you have the same amount of free memory once booted in both cases? Yes, almost exactly the same, so obvious it must be working the same for both cases. That's enough evidence for me. Thanks. Chris

[PATCH] staging: rtlwifi: remove duplicated macros in comments

Removing a comment that duplicates definitions for pci_power_t enumeration, and pointing to the relevant header file (current comment is also missing PCI_POWER_ERROR). Signed-off-by: Matthew Giassa --- drivers/staging/rtlwifi/pci.c | 7 +-- 1 file changed, 1

[PATCH] staging: rtlwifi: remove duplicated macros in comments

Removing a comment that duplicates definitions for pci_power_t enumeration, and pointing to the relevant header file (current comment is also missing PCI_POWER_ERROR). Signed-off-by: Matthew Giassa --- drivers/staging/rtlwifi/pci.c | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(-)

Re: [PATCH 8/8] ktest: Use config-bisect.pl in ktest.pl

On Thu, 05 Oct 2017 18:18:54 -0500 Scott Wood wrote: > On Thu, 2017-10-05 at 08:50 -0400, Steven Rostedt wrote: > > On Wed, 04 Oct 2017 15:24:23 -0500 > > Scott Wood wrote: > > > > > It should also be noted that ktest.pl only depends on config- > > >

Re: [PATCH 8/8] ktest: Use config-bisect.pl in ktest.pl

On Thu, 05 Oct 2017 18:18:54 -0500 Scott Wood wrote: > On Thu, 2017-10-05 at 08:50 -0400, Steven Rostedt wrote: > > On Wed, 04 Oct 2017 15:24:23 -0500 > > Scott Wood wrote: > > > > > It should also be noted that ktest.pl only depends on config- > > > bisect.pl > > > if a config bisect is

[PATCH] staging: irda: resolve sparse errors due to implicit pci_power_t casts

Explicitly casting pci_power_t types to resolve sparse warnings (shown below). Also fixing a related logging bug where pci_power_t is cast to unsigned (can be negative, i.e. PCI_POWER_ERROR). Original sparse report: drivers/staging/irda/drivers//vlsi_ir.c:170:51: warning: cast from restricted

[PATCH] staging: irda: resolve sparse errors due to implicit pci_power_t casts

Explicitly casting pci_power_t types to resolve sparse warnings (shown below). Also fixing a related logging bug where pci_power_t is cast to unsigned (can be negative, i.e. PCI_POWER_ERROR). Original sparse report: drivers/staging/irda/drivers//vlsi_ir.c:170:51: warning: cast from restricted

Re: [PATCH] ahci: Convert timers to use timer_setup()

On Thu, Oct 5, 2017 at 7:21 AM, Tejun Heo wrote: > On Wed, Oct 04, 2017 at 05:54:17PM -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

Re: [PATCH] ahci: Convert timers to use timer_setup()

On Thu, Oct 5, 2017 at 7:21 AM, Tejun Heo wrote: > On Wed, Oct 04, 2017 at 05:54:17PM -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

[PATCH v8 2/5] x86/cpuid: Add generic table for cpuid dependencies

Some CPUID features depend on other features. Currently it's possible to to clear dependent features, but not clear the base features, which can cause various interesting problems. This patch implements a generic table to describe dependencies between CPUID features, to be used by all code that

[PATCH v8 2/5] x86/cpuid: Add generic table for cpuid dependencies

Some CPUID features depend on other features. Currently it's possible to to clear dependent features, but not clear the base features, which can cause various interesting problems. This patch implements a generic table to describe dependencies between CPUID features, to be used by all code that

Re: [RFC PATCH -tip 0/5] kprobes: Abolish jprobe APIs

On Thu, Oct 5, 2017 at 4:13 PM, Masami Hiramatsu wrote: > Hi, > > This series abolishes jprobe APIs and remove or disable related > code. This is a preparation of removing all jprobe code (including > kprobe's break_handler.) > I'm not so sure how many jprobe users still

Re: [RFC PATCH -tip 0/5] kprobes: Abolish jprobe APIs

On Thu, Oct 5, 2017 at 4:13 PM, Masami Hiramatsu wrote: > Hi, > > This series abolishes jprobe APIs and remove or disable related > code. This is a preparation of removing all jprobe code (including > kprobe's break_handler.) > I'm not so sure how many jprobe users still exists, but > please

Re: [PATCH 1/3] Arm: dts: stm32: remove extra compatible string for uart

On Thu, Sep 28, 2017 at 03:51:24PM -0700, Vikas Manocha wrote: > This patch removes the extra compatibility string "st,stm32-usart" to > avoid confusion, save some time & space. I'm confused why you don't need it anymore. I thought the h/w blocks were configured differently. > > Signed-off-by:

Re: [PATCH 1/3] Arm: dts: stm32: remove extra compatible string for uart

On Thu, Sep 28, 2017 at 03:51:24PM -0700, Vikas Manocha wrote: > This patch removes the extra compatibility string "st,stm32-usart" to > avoid confusion, save some time & space. I'm confused why you don't need it anymore. I thought the h/w blocks were configured differently. > > Signed-off-by:

Re: [PATCH v3 00/20] Speculative page faults

On Wed, Oct 04, 2017 at 08:50:49AM +0200, Laurent Dufour wrote: > On 25/09/2017 18:27, Alexei Starovoitov wrote: > > On Mon, Sep 18, 2017 at 12:15 AM, Laurent Dufour > > wrote: > >> Despite the unprovable lockdep warning raised by Sergey, I didn't get any > >> feedback

Re: [PATCH v3 00/20] Speculative page faults

On Wed, Oct 04, 2017 at 08:50:49AM +0200, Laurent Dufour wrote: > On 25/09/2017 18:27, Alexei Starovoitov wrote: > > On Mon, Sep 18, 2017 at 12:15 AM, Laurent Dufour > > wrote: > >> Despite the unprovable lockdep warning raised by Sergey, I didn't get any > >> feedback on this series. > >> > >>

[PATCH] iommu/vt-d: only attempt to cleanup svm page request irq if one assigned

Only try to clean up the svm page request irq if one has been assigned. Also clear pr_irq in the error path if irq request fails. Signed-off-by: Jerry Snitselaar --- drivers/iommu/intel-svm.c | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git

[PATCH] iommu/vt-d: only attempt to cleanup svm page request irq if one assigned

Only try to clean up the svm page request irq if one has been assigned. Also clear pr_irq in the error path if irq request fails. Signed-off-by: Jerry Snitselaar --- drivers/iommu/intel-svm.c | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/drivers/iommu/intel-svm.c

Re: [PATCH v2 2/2] dt-bindings: i2c: Update documentation for "mv78230-a0-i2c"

On Thu, Oct 05, 2017 at 01:08:20PM +0200, Wolfram Sang wrote: > On Mon, Oct 02, 2017 at 04:23:43PM +0200, Gregory CLEMENT wrote: > > Hi Wolfram, > > > > On ven., sept. 29 2017, Kalyan Kinthada > > wrote: > > > > > This commit modifies the documentation

Re: [PATCH v2 2/2] dt-bindings: i2c: Update documentation for "mv78230-a0-i2c"

On Thu, Oct 05, 2017 at 01:08:20PM +0200, Wolfram Sang wrote: > On Mon, Oct 02, 2017 at 04:23:43PM +0200, Gregory CLEMENT wrote: > > Hi Wolfram, > > > > On ven., sept. 29 2017, Kalyan Kinthada > > wrote: > > > > > This commit modifies the documentation for > > > "marvell,mv78230-a0-i2c"

Re: [PATCH v7 2/2] tracing: Add support for preempt and irq enable/disable events

On Thu, Oct 5, 2017 at 4:28 PM, Joel Fernandes wrote: > Hi Peter, > > On Wed, Oct 4, 2017 at 9:01 AM, Peter Zijlstra wrote: >> On Fri, Sep 29, 2017 at 02:22:45PM -0700, Joel Fernandes wrote: [...] >>> EXPORT_SYMBOL(trace_hardirqs_off); >>> >>> __visible

Re: [PATCH v7 2/2] tracing: Add support for preempt and irq enable/disable events

On Thu, Oct 5, 2017 at 4:28 PM, Joel Fernandes wrote: > Hi Peter, > > On Wed, Oct 4, 2017 at 9:01 AM, Peter Zijlstra wrote: >> On Fri, Sep 29, 2017 at 02:22:45PM -0700, Joel Fernandes wrote: [...] >>> EXPORT_SYMBOL(trace_hardirqs_off); >>> >>> __visible void trace_hardirqs_on_caller(unsigned

Re: [PATCH v7 2/2] tracing: Add support for preempt and irq enable/disable events

Hi Peter, On Wed, Oct 4, 2017 at 9:01 AM, Peter Zijlstra wrote: > On Fri, Sep 29, 2017 at 02:22:45PM -0700, Joel Fernandes wrote: [...] >> + */ >> +static DEFINE_PER_CPU(int, tracing_irq_cpu); >> + >> #if defined(CONFIG_TRACE_IRQFLAGS) && !defined(CONFIG_PROVE_LOCKING) >>

Re: [PATCH v7 2/2] tracing: Add support for preempt and irq enable/disable events

Hi Peter, On Wed, Oct 4, 2017 at 9:01 AM, Peter Zijlstra wrote: > On Fri, Sep 29, 2017 at 02:22:45PM -0700, Joel Fernandes wrote: [...] >> + */ >> +static DEFINE_PER_CPU(int, tracing_irq_cpu); >> + >> #if defined(CONFIG_TRACE_IRQFLAGS) && !defined(CONFIG_PROVE_LOCKING) >> void

[PATCH v3] ACPI / LPIT: Add Low Power Idle Table (LPIT) support

Added functionality to read LPIT table, which provides: - Sysfs interface to read residency counters via /sys/devices/system/cpu/cpuidle/low_power_idle_cpu_residency_us /sys/devices/system/cpu/cpuidle/low_power_idle_system_residency_us Here the count "low_power_idle_cpu_residency_us" shows the

[PATCH v3] ACPI / LPIT: Add Low Power Idle Table (LPIT) support

Added functionality to read LPIT table, which provides: - Sysfs interface to read residency counters via /sys/devices/system/cpu/cpuidle/low_power_idle_cpu_residency_us /sys/devices/system/cpu/cpuidle/low_power_idle_system_residency_us Here the count "low_power_idle_cpu_residency_us" shows the

Re: [PATCH v3 03/22] dt-bindings: arm: scmi: add ARM MHU specific mailbox client bindings

On Thu, Sep 28, 2017 at 02:11:27PM +0100, Sudeep Holla wrote: > This patch adds ARM MHU specific mailbox client bindings to support > SCMI. Since SCMI specification just requires doorbell mechanism from > mailbox controllers, we add mailbox data to specify the doorbell bit(s). > > Cc: Rob Herring

Re: [PATCH v3 03/22] dt-bindings: arm: scmi: add ARM MHU specific mailbox client bindings

On Thu, Sep 28, 2017 at 02:11:27PM +0100, Sudeep Holla wrote: > This patch adds ARM MHU specific mailbox client bindings to support > SCMI. Since SCMI specification just requires doorbell mechanism from > mailbox controllers, we add mailbox data to specify the doorbell bit(s). > > Cc: Rob Herring

[rcu:dev.2017.10.05a 32/34] include/linux/compiler.h:343:2: error: implicit declaration of function 'smp_read_barrier_depends'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2017.10.05a head: 39ae2675aa536e6ef9d334fe9097d1e2c6b25fbc commit: 7e3675cc18bbf4d84f60bfc02ff563ae3764ad35 [32/34] locking/barriers: Kill lockless_dereference config: h8300-h8300h-sim_defconfig (attached as

[rcu:dev.2017.10.05a 32/34] include/linux/compiler.h:343:2: error: implicit declaration of function 'smp_read_barrier_depends'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2017.10.05a head: 39ae2675aa536e6ef9d334fe9097d1e2c6b25fbc commit: 7e3675cc18bbf4d84f60bfc02ff563ae3764ad35 [32/34] locking/barriers: Kill lockless_dereference config: h8300-h8300h-sim_defconfig (attached as

Re: [PATCH 8/8] ktest: Use config-bisect.pl in ktest.pl

On Thu, 2017-10-05 at 08:50 -0400, Steven Rostedt wrote: > On Wed, 04 Oct 2017 15:24:23 -0500 > Scott Wood wrote: > > > It should also be noted that ktest.pl only depends on config- > > bisect.pl > > if a config bisect is being performed, so other ktest.pl functions > > still >

Re: [PATCH 8/8] ktest: Use config-bisect.pl in ktest.pl

On Thu, 2017-10-05 at 08:50 -0400, Steven Rostedt wrote: > On Wed, 04 Oct 2017 15:24:23 -0500 > Scott Wood wrote: > > > It should also be noted that ktest.pl only depends on config- > > bisect.pl > > if a config bisect is being performed, so other ktest.pl functions > > still > > work

[RFC PATCH -tip 5/5] kprobes: docs: Remove jprobe related document

Remove jprobe related documentations from kprobes.txt. It also add some migration advice for the people who still using jprobe. Signed-off-by: Masami Hiramatsu --- Documentation/kprobes.txt | 153 +++-- 1 file changed, 51

[RFC PATCH -tip 5/5] kprobes: docs: Remove jprobe related document

Remove jprobe related documentations from kprobes.txt. It also add some migration advice for the people who still using jprobe. Signed-off-by: Masami Hiramatsu --- Documentation/kprobes.txt | 153 +++-- 1 file changed, 51 insertions(+), 102 deletions(-)

[PATCH v2] block/laptop_mode: Convert timers to use timer_setup()

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: Jens Axboe Cc: Michal Hocko Cc: Andrew Morton

[PATCH v2] block/laptop_mode: Convert timers to use timer_setup()

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: Jens Axboe Cc: Michal Hocko Cc: Andrew Morton Cc: Jan Kara Cc: Johannes Weiner Cc: Nicholas Piggin

[RFC PATCH -tip 4/5] kprobes: Remove jprobe sample code

Remove jprobe sample module because jprobe is deprecated. Signed-off-by: Masami Hiramatsu --- samples/kprobes/Makefile |2 + samples/kprobes/jprobe_example.c | 67 -- 2 files changed, 1 insertion(+), 68 deletions(-) delete

[RFC PATCH -tip 4/5] kprobes: Remove jprobe sample code

Remove jprobe sample module because jprobe is deprecated. Signed-off-by: Masami Hiramatsu --- samples/kprobes/Makefile |2 + samples/kprobes/jprobe_example.c | 67 -- 2 files changed, 1 insertion(+), 68 deletions(-) delete mode 100644

[RFC PATCH -tip 3/5] kprobes: Disable jprobe test code

Disable jprobe test code because jprobe is deprecated. This code will be completely removed when jprobe code is removed. Signed-off-by: Masami Hiramatsu --- kernel/test_kprobes.c |9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git

[RFC PATCH -tip 3/5] kprobes: Disable jprobe test code

Disable jprobe test code because jprobe is deprecated. This code will be completely removed when jprobe code is removed. Signed-off-by: Masami Hiramatsu --- kernel/test_kprobes.c |9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/kernel/test_kprobes.c

[RFC PATCH -tip 2/5] kprobes: Abolish jprobe APIs

Abolish jprobe APIs and comment out the jprobe API function code. This is a preparation of removing all jprobe related code (including kprobe's break_handler) Nowadays ftrace and other tracing features are enough matured to replace jprobe use-cases. Users can safely use ftrace and perf probe etc.

[RFC PATCH -tip 2/5] kprobes: Abolish jprobe APIs

Abolish jprobe APIs and comment out the jprobe API function code. This is a preparation of removing all jprobe related code (including kprobe's break_handler) Nowadays ftrace and other tracing features are enough matured to replace jprobe use-cases. Users can safely use ftrace and perf probe etc.

[RFC PATCH -tip 1/5] kprobes: Use ENOTSUPP instead of ENOSYS

Use ENOTSUPP instead of ENOSYS because ENOSYS is reserved only for invalid syscall number. Signed-off-by: Masami Hiramatsu --- include/linux/kprobes.h | 16 kernel/kprobes.c|4 ++-- 2 files changed, 10 insertions(+), 10 deletions(-) diff

[RFC PATCH -tip 1/5] kprobes: Use ENOTSUPP instead of ENOSYS

Use ENOTSUPP instead of ENOSYS because ENOSYS is reserved only for invalid syscall number. Signed-off-by: Masami Hiramatsu --- include/linux/kprobes.h | 16 kernel/kprobes.c|4 ++-- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git

[PATCH v2] block/aoe: Convert timers to use timer_setup()

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: Jens Axboe Cc: "Ed L. Cashin" Cc: linux-bl...@vger.kernel.org Cc:

Re: [PATCH v5 3/3] KVM: LAPIC: Apply change to TDCR right away to the timer

2017-10-06 2:14 GMT+08:00 Radim Krčmář : > 2017-10-05 07:35-0700, Wanpeng Li: >> From: Wanpeng Li >> >> The description in the Intel SDM of how the divide configuration >> register is used: "The APIC timer frequency will be the processor's bus >> clock

[RFC PATCH -tip 0/5] kprobes: Abolish jprobe APIs

Hi, This series abolishes jprobe APIs and remove or disable related code. This is a preparation of removing all jprobe code (including kprobe's break_handler.) I'm not so sure how many jprobe users still exists, but please migrate your tool to trace-event or perf-probe. As we discussed this

[PATCH v2] block/aoe: Convert timers to use timer_setup()

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: Jens Axboe Cc: "Ed L. Cashin" Cc: linux-bl...@vger.kernel.org Cc: Thomas Gleixner Signed-off-by:

Re: [PATCH v5 3/3] KVM: LAPIC: Apply change to TDCR right away to the timer

2017-10-06 2:14 GMT+08:00 Radim Krčmář : > 2017-10-05 07:35-0700, Wanpeng Li: >> From: Wanpeng Li >> >> The description in the Intel SDM of how the divide configuration >> register is used: "The APIC timer frequency will be the processor's bus >> clock or core crystal clock frequency divided by

[RFC PATCH -tip 0/5] kprobes: Abolish jprobe APIs

Hi, This series abolishes jprobe APIs and remove or disable related code. This is a preparation of removing all jprobe code (including kprobe's break_handler.) I'm not so sure how many jprobe users still exists, but please migrate your tool to trace-event or perf-probe. As we discussed this

Re: [RFC PATCH 1/4] dt-bindings: add bindings for USB physical connector

On Thu, Sep 28, 2017 at 03:07:27PM +0200, Andrzej Hajda wrote: > These bindings allows to describe most known standard USB connectors > and it should be possible to extend it if necessary. > USB connectors, beside USB can be used to route other protocols, > for example UART, Audio, MHL. In such

Re: [RFC PATCH 1/4] dt-bindings: add bindings for USB physical connector

On Thu, Sep 28, 2017 at 03:07:27PM +0200, Andrzej Hajda wrote: > These bindings allows to describe most known standard USB connectors > and it should be possible to extend it if necessary. > USB connectors, beside USB can be used to route other protocols, > for example UART, Audio, MHL. In such

Re: [PATCH v8 2/5] x86/cpuid: Add generic table for cpuid dependencies

On Fri, Oct 06, 2017 at 12:41:56AM +0200, Thomas Gleixner wrote: > On Thu, 5 Oct 2017, Andi Kleen wrote: > > +/* > > + * Table of CPUID features that depend on others. > > + * > > + * This only includes dependencies that can be usefully disabled, not > > + * features part of the base set (like

Re: [PATCH v8 2/5] x86/cpuid: Add generic table for cpuid dependencies

On Fri, Oct 06, 2017 at 12:41:56AM +0200, Thomas Gleixner wrote: > On Thu, 5 Oct 2017, Andi Kleen wrote: > > +/* > > + * Table of CPUID features that depend on others. > > + * > > + * This only includes dependencies that can be usefully disabled, not > > + * features part of the base set (like

Re: [PATCH] vfs: fix statfs64() returning impossible EOVERFLOW for 64-bit f_files

On Thu, Oct 05, 2017 at 03:31:05PM -0700, Linus Torvalds wrote: > On Thu, Oct 5, 2017 at 1:57 PM, Al Viro wrote: > > > > AFAICS, the real bug here is in hugetlbfs; that's where obscene values in > > ->f_bsize come from. IMO all that code in put_compat_statfs64() should

Re: [PATCH] vfs: fix statfs64() returning impossible EOVERFLOW for 64-bit f_files

On Thu, Oct 05, 2017 at 03:31:05PM -0700, Linus Torvalds wrote: > On Thu, Oct 5, 2017 at 1:57 PM, Al Viro wrote: > > > > AFAICS, the real bug here is in hugetlbfs; that's where obscene values in > > ->f_bsize come from. IMO all that code in put_compat_statfs64() should be > > replaced with > >

[PATCH v2 02/16] iommu/vt-d: add bind_pasid_table function

Add Intel VT-d ops to the generic iommu_bind_pasid_table API functions. The primary use case is for direct assignment of SVM capable device. Originated from emulated IOMMU in the guest, the request goes through many layers (e.g. VFIO). Upon calling host IOMMU driver, caller passes guest PASID

[PATCH v2 02/16] iommu/vt-d: add bind_pasid_table function

Add Intel VT-d ops to the generic iommu_bind_pasid_table API functions. The primary use case is for direct assignment of SVM capable device. Originated from emulated IOMMU in the guest, the request goes through many layers (e.g. VFIO). Upon calling host IOMMU driver, caller passes guest PASID

[PATCH v2 01/16] iommu: introduce bind_pasid_table API function

Virtual IOMMU was proposed to support Shared Virtual Memory (SVM) use in the guest: https://lists.gnu.org/archive/html/qemu-devel/2016-11/msg05311.html As part of the proposed architecture, when an SVM capable PCI device is assigned to a guest, nested mode is turned on. Guest owns the first level

[PATCH v2 01/16] iommu: introduce bind_pasid_table API function

Virtual IOMMU was proposed to support Shared Virtual Memory (SVM) use in the guest: https://lists.gnu.org/archive/html/qemu-devel/2016-11/msg05311.html As part of the proposed architecture, when an SVM capable PCI device is assigned to a guest, nested mode is turned on. Guest owns the first level

[PATCH v2 09/16] driver core: add iommu device fault reporting data

DMA faults can be detected by IOMMU at device level. Adding a pointer to struct device allows IOMMU subsystem to report relevant faults back to the device driver for further handling. For direct assigned device (or user space drivers), guest OS holds responsibility to handle and respond per device

[PATCH v2 09/16] driver core: add iommu device fault reporting data

DMA faults can be detected by IOMMU at device level. Adding a pointer to struct device allows IOMMU subsystem to report relevant faults back to the device driver for further handling. For direct assigned device (or user space drivers), guest OS holds responsibility to handle and respond per device

[PATCH v2 07/16] iommu/vt-d: assign PFSID in device TLB invalidation

When SRIOV VF device IOTLB is invalidated, we need to provide the PF source SID such that IOMMU hardware can gauge the depth of invalidation queue which is shared among VFs. This is needed when device invalidation throttle (DIT) capability is supported. Signed-off-by: Jacob Pan

[PATCH v2 00/16] IOMMU driver support for SVM virtualization

Hi All, Shared virtual memory (SVM) space between devices and applications can reduce programming complexity and enhance security. To enable SVM in the guest, i.e. shared guest application address space and physical device DMA address, IOMMU driver must provide some new functionalities. This

[PATCH v2 08/16] iommu: introduce device fault data

Device faults detected by IOMMU can be reported outside IOMMU subsystem. This patch intends to provide a generic device fault data such that device drivers can communicate IOMMU faults without model specific knowledge. The assumption is that model specific IOMMU driver can filter and handle most

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

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

[PATCH v2 07/16] iommu/vt-d: assign PFSID in device TLB invalidation

When SRIOV VF device IOTLB is invalidated, we need to provide the PF source SID such that IOMMU hardware can gauge the depth of invalidation queue which is shared among VFs. This is needed when device invalidation throttle (DIT) capability is supported. Signed-off-by: Jacob Pan ---

[PATCH v2 00/16] IOMMU driver support for SVM virtualization

Hi All, Shared virtual memory (SVM) space between devices and applications can reduce programming complexity and enhance security. To enable SVM in the guest, i.e. shared guest application address space and physical device DMA address, IOMMU driver must provide some new functionalities. This

[PATCH v2 08/16] iommu: introduce device fault data

Device faults detected by IOMMU can be reported outside IOMMU subsystem. This patch intends to provide a generic device fault data such that device drivers can communicate IOMMU faults without model specific knowledge. The assumption is that model specific IOMMU driver can filter and handle most

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

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 a/drivers/iommu/dmar.c

[PATCH v2 05/16] iommu/vt-d: add iommu invalidate function

This patch adds Intel VT-d specific function to implement iommu passdown invalidate API. The use case is for supporting caching structure invalidation of assigned SVM capable devices. Emulated IOMMU exposes queue invalidation capability and passes down all descriptors from the guest to the

[PATCH v2 11/16] iommu/vt-d: use threaded irq for dmar_fault

Currently, dmar fault IRQ handler does nothing more than rate limited printk, no critical hardware handling need to be done in IRQ context. Convert it to threaded IRQ would allow fault processing that requires process context. e.g. find out offending device based on source ID in the fault rasons.

[PATCH v2 11/16] iommu/vt-d: use threaded irq for dmar_fault

Currently, dmar fault IRQ handler does nothing more than rate limited printk, no critical hardware handling need to be done in IRQ context. Convert it to threaded IRQ would allow fault processing that requires process context. e.g. find out offending device based on source ID in the fault rasons.

[PATCH v2 05/16] iommu/vt-d: add iommu invalidate function

This patch adds Intel VT-d specific function to implement iommu passdown invalidate API. The use case is for supporting caching structure invalidation of assigned SVM capable devices. Emulated IOMMU exposes queue invalidation capability and passes down all descriptors from the guest to the

[PATCH v2 06/16] iommu/vt-d: move device_domain_info to header

Allow both intel-iommu.c and dmar.c to access device_domain_info. Prepare for additional per device arch data used in TLB flush function Signed-off-by: Jacob Pan --- drivers/iommu/intel-iommu.c | 18 -- include/linux/intel-iommu.h | 19

[PATCH v2 06/16] iommu/vt-d: move device_domain_info to header

Allow both intel-iommu.c and dmar.c to access device_domain_info. Prepare for additional per device arch data used in TLB flush function Signed-off-by: Jacob Pan --- drivers/iommu/intel-iommu.c | 18 -- include/linux/intel-iommu.h | 19 +++ 2 files changed, 19

[PATCH v2 10/16] iommu: introduce device fault report API

Traditionally, device specific faults are detected and handled within their own device drivers. When IOMMU is enabled, faults such as DMA related transactions are detected by IOMMU. There is no generic reporting mechanism to report faults back to the in-kernel device driver or the guest OS in case

[PATCH v2 10/16] iommu: introduce device fault report API

Traditionally, device specific faults are detected and handled within their own device drivers. When IOMMU is enabled, faults such as DMA related transactions are detected by IOMMU. There is no generic reporting mechanism to report faults back to the in-kernel device driver or the guest OS in case

[PATCH v2 12/16] iommu/vt-d: report unrecoverable device faults

Currently, when device DMA faults are detected by IOMMU the fault reasons are printed but the driver of the offending device is involved in fault handling. This patch uses per device fault reporting API to send fault event data for further processing. Offending device is identified by the source

[PATCH v2 12/16] iommu/vt-d: report unrecoverable device faults

Currently, when device DMA faults are detected by IOMMU the fault reasons are printed but the driver of the offending device is involved in fault handling. This patch uses per device fault reporting API to send fault event data for further processing. Offending device is identified by the source

<    1   2   3   4   5   6   7   8   9   10   >