From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [IPv6:2401:3900:2:1::2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3rrTtx304DzDqyc for ; Fri, 15 Jul 2016 20:53:13 +1000 (AEST) In-Reply-To: <1468444634-1866-6-git-send-email-imunsie@au.ibm.com> To: Ian Munsie , Michael Neuling , Frederic Barrat , Andrew Donnellan , linuxppc-dev@lists.ozlabs.org, Huy Nguyen From: Michael Ellerman Cc: Ian Munsie Subject: Re: [05/15] cxl: Allow a default context to be associated with an external pci_dev Message-Id: <3rrTtx0PP1z9srY@ozlabs.org> Date: Fri, 15 Jul 2016 20:53:12 +1000 (AEST) List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 2016-13-07 at 21:17:04 UTC, Ian Munsie wrote: > From: Ian Munsie > > The cxl kernel API has a concept of a default context associated with > each PCI device under the virtual PHB. The Mellanox CX4 will also use > the cxl kernel API, but it does not use a virtual PHB - rather, the AFU > appears as a physical function as a peer to the networking functions. > > In order to allow the kernel API to work with those networking > functions, we will need to associate a default context with them as > well. To this end, refactor the corresponding code to do this in vphb.c > and export it so that it can be called from the PHB code. > > Signed-off-by: Ian Munsie > Reviewed-by: Frederic Barrat > Reviewed-by: Andrew Donnellan Applied to powerpc next, thanks. https://git.kernel.org/powerpc/c/a19bd79e31769626d288cc016e cheers