Re: [PATCH v1 1/1] misc: IBM Virtual Management Channel Driver

On 04/23/18 12:53, Greg KH wrote: > On Mon, Apr 23, 2018 at 11:38:18AM -0700, Randy Dunlap wrote: >> On 04/23/18 07:46, Bryant G. Ly wrote: >>> This driver is a logical device which provides an >>> interface between the hypervisor and a management >>> partition. >>> >>> This driver is to be used

Re: [PATCH v1 1/1] misc: IBM Virtual Management Channel Driver

On 4/23/18 2:53 PM, Greg KH wrote: > On Mon, Apr 23, 2018 at 11:38:18AM -0700, Randy Dunlap wrote: >> On 04/23/18 07:46, Bryant G. Ly wrote: >>> This driver is a logical device which provides an >>> interface between the hypervisor and a management >>> partition. >>> >>> This driver is to be used

Re: [PATCH v1 1/1] misc: IBM Virtual Management Channel Driver

On Mon, Apr 23, 2018 at 11:38:18AM -0700, Randy Dunlap wrote: > On 04/23/18 07:46, Bryant G. Ly wrote: > > This driver is a logical device which provides an > > interface between the hypervisor and a management > > partition. > > > > This driver is to be used for the POWER Virtual > > Management

Re: [PATCH v1 1/1] misc: IBM Virtual Management Channel Driver

On 04/23/18 07:46, Bryant G. Ly wrote: > This driver is a logical device which provides an > interface between the hypervisor and a management > partition. > > This driver is to be used for the POWER Virtual > Management Channel Virtual Adapter on the PowerVM > platform. It provides both

Re: [PATCH v4 00/10] Add the I3C subsystem

On Mon, Apr 23, 2018 at 07:38:14PM +0200, Boris Brezillon wrote: > Hi, > > On Fri, 30 Mar 2018 09:47:41 +0200 > Boris Brezillon wrote: > > > This patch series is a proposal for a new I3C subsystem. > > This v4 has been sent almost a month ago and I didn't get any

[PATCH] thermal: core: fix emulation of subzero temps

The current implementation casted away its sign. It was also using '0' to disable emulation, but 0C is a valid thermal reading. A large negative value (below absolute zero) now disables the emulation. Test: Build kernel with CONFIG_THERMAL_EMULATION=y, then write negative values to the emul_temp

Re: [PATCH v3 03/10] drivers/peci: Add support for PECI bus driver core

On 4/23/2018 3:52 AM, Greg KH wrote: On Tue, Apr 10, 2018 at 11:32:05AM -0700, Jae Hyun Yoo wrote: +static void peci_adapter_dev_release(struct device *dev) +{ + /* do nothing */ +} As per the in-kernel documentation, I am now allowed to make fun of you. You are trying to "out smart"

Re: [PATCH v4 00/10] Add the I3C subsystem

Hi, On Fri, 30 Mar 2018 09:47:41 +0200 Boris Brezillon wrote: > This patch series is a proposal for a new I3C subsystem. This v4 has been sent almost a month ago and I didn't get any feedback so far apart from Rob's R-b. Greg, is there any chance we can get these

Re: [PATCH v7 0/5] cpuset: Enable cpuset controller in default hierarchy

On 04/20/2018 04:23 AM, Mike Galbraith wrote: > On Thu, 2018-04-19 at 09:46 -0400, Waiman Long wrote: >> v7: >> - Add a root-only cpuset.cpus.isolated control file for CPU isolation. >> - Enforce that load_balancing can only be turned off on cpusets with >>CPUs from the isolated list. >> -

Re: [PATCH v7 3/5] cpuset: Add a root-only cpus.isolated v2 control file

On 19/04/18 09:47, Waiman Long wrote: [...] > + cpuset.cpus.isolated > + A read-write multiple values file which exists on root cgroup > + only. > + > + It lists the CPUs that have been withdrawn from the root cgroup > + for load balancing. These CPUs can still be allocated to

[PATCH v1 1/1] misc: IBM Virtual Management Channel Driver

This driver is a logical device which provides an interface between the hypervisor and a management partition. This driver is to be used for the POWER Virtual Management Channel Virtual Adapter on the PowerVM platform. It provides both request/response and async message support through the

[PATCH v1 0/1] misc: IBM Virtual Management Channel Driver

Steven Royer had previously attempted to upstream this driver two years ago, but never got the chance to address the concerns from Greg Kroah-Hartman. The thread with the initial upstream is: https://lkml.org/lkml/2016/2/16/918 I have addressed the following: - Documentation - Use of dev_dbg

Re: [PATCH v7 0/5] cpuset: Enable cpuset controller in default hierarchy

On 04/23/2018 09:57 AM, Juri Lelli wrote: > On 23/04/18 15:07, Juri Lelli wrote: >> Hi Waiman, >> >> On 19/04/18 09:46, Waiman Long wrote: >>> v7: >>> - Add a root-only cpuset.cpus.isolated control file for CPU isolation. >>> - Enforce that load_balancing can only be turned off on cpusets with

Re: [PATCH v7 0/5] cpuset: Enable cpuset controller in default hierarchy

On 23/04/18 15:07, Juri Lelli wrote: > Hi Waiman, > > On 19/04/18 09:46, Waiman Long wrote: > > v7: > > - Add a root-only cpuset.cpus.isolated control file for CPU isolation. > > - Enforce that load_balancing can only be turned off on cpusets with > >CPUs from the isolated list. > > -

Re: [PATCH v7 0/5] cpuset: Enable cpuset controller in default hierarchy

Hi Waiman, On 19/04/18 09:46, Waiman Long wrote: > v7: > - Add a root-only cpuset.cpus.isolated control file for CPU isolation. > - Enforce that load_balancing can only be turned off on cpusets with >CPUs from the isolated list. > - Update sched domain generation to allow cpusets with CPUs

Re: [RFC 01/10] PCI: dwc: Add MSI-X callbacks handler

Hi Kishon, On 16/04/2018 10:29, Kishon Vijay Abraham I wrote: > Hi Gustavo, > > On Tuesday 10 April 2018 10:44 PM, Gustavo Pimentel wrote: >> Changes the pcie_raise_irq function signature, namely the interrupt_num >> variable type from u8 to u16 to accommodate the MSI-X maximum interrupts >> of

Re: [PATCH bpf-next v3 4/8] bpf: add documentation for eBPF helpers (23-32)

On 04/20/2018 08:54 PM, Quentin Monnet wrote: > 2018-04-19 13:16 UTC+0200 ~ Daniel Borkmann >> On 04/17/2018 04:34 PM, Quentin Monnet wrote: >>> Add documentation for eBPF helper functions to bpf.h user header file. >>> This documentation can be parsed with the Python script

Re: [PATCH v2 5/7] ocxl: Expose the thread_id needed for wait on p9

On 18/04/18 11:08, Alastair D'Silva wrote: From: Alastair D'Silva In order to successfully issue as_notify, an AFU needs to know the TID to notify, which in turn means that this information should be available in userspace so it can be communicated to the AFU.