From: Michael Ellerman <mpe@ellerman.id.au> To: Christophe Leroy <christophe.leroy@csgroup.eu>, Haren Myneni <haren@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org, linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au, npiggin@gmail.com Cc: hbabu@us.ibm.com, haren@us.ibm.com Subject: Re: [PATCH 02/16] powerpc/vas: Make VAS API powerpc platform independent Date: Tue, 13 Apr 2021 22:59:15 +1000 [thread overview] Message-ID: <87k0p6s5lo.fsf@mpe.ellerman.id.au> (raw) In-Reply-To: <1804692b-f9d4-964d-bbe4-cb809dad5ee8@csgroup.eu> Christophe Leroy <christophe.leroy@csgroup.eu> writes: > Le 11/04/2021 à 02:31, Haren Myneni a écrit : >> >> Using the same /dev/crypto/nx-gzip interface for both powerNV and >> pseries. So this patcb moves VAS API to powerpc platform indepedent >> directory. The actual functionality is not changed in this patch. > > This patch seems to do a lot more than moving VAS API to independent directory. A more detailed > description would help. > > And it is not something defined in the powerpc architecture I think, so it should > remain in some common platform related directory. > >> >> Signed-off-by: Haren Myneni <haren@linux.ibm.com> >> --- >> arch/powerpc/Kconfig | 15 +++++ >> arch/powerpc/include/asm/vas.h | 22 ++++++- >> arch/powerpc/kernel/Makefile | 1 + >> .../{platforms/powernv => kernel}/vas-api.c | 64 ++++++++++-------- >> arch/powerpc/platforms/powernv/Kconfig | 14 ---- >> arch/powerpc/platforms/powernv/Makefile | 2 +- >> arch/powerpc/platforms/powernv/vas-window.c | 66 +++++++++++++++++++ >> 7 files changed, 140 insertions(+), 44 deletions(-) >> rename arch/powerpc/{platforms/powernv => kernel}/vas-api.c (83%) >> >> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig >> index 386ae12d8523..7aa1fbf7c1dc 100644 >> --- a/arch/powerpc/Kconfig >> +++ b/arch/powerpc/Kconfig >> @@ -478,6 +478,21 @@ config PPC_UV >> >> If unsure, say "N". >> >> +config PPC_VAS >> + bool "IBM Virtual Accelerator Switchboard (VAS)" >> + depends on PPC_POWERNV && PPC_64K_PAGES >> + default y >> + help >> + This enables support for IBM Virtual Accelerator Switchboard (VAS). > > IIUC is a functionnality in a coprocessor of some IBM processors. Something similar in principle to > the communication coprocessors we find in Freescale processors. It's not a coprocessor, it's a way you talk to coprocessors. > It is not a generic functionnality part of the powerpc architecture, I don't think this belongs to > arch/powerpc/Kconfig But you're right it's not part of the ISA. > I think it should go in arch/powerpc/platform/Kconfig The problem with that is it's shared between two existing platforms, ie. powernv and pseries. We don't want to put it in one or the other. In the past we have put code like that in arch/powerpc/sysdev, but I am not a big fan of it, because it's just a bit of a dumping ground. A while back I created arch/powerpc/platforms/4xx for 40x and 44x related things, even though there's no actual 4xx platform. I don't think that's caused any problems. So I'm inclined to say we should make a arch/powerpc/platforms/book3s and put VAS in there. The naming is a bit fishy, because not all book3s CPUs do or will have VAS. But we would expect any future CPU with VAS to be book3s. In contrast if we named it platforms/ibm, we could potentially have a future non-IBM CPU that contains VAS, which would then make the ibm name confusing. cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au> To: Christophe Leroy <christophe.leroy@csgroup.eu>, Haren Myneni <haren@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org, linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au, npiggin@gmail.com Subject: Re: [PATCH 02/16] powerpc/vas: Make VAS API powerpc platform independent Date: Tue, 13 Apr 2021 22:59:15 +1000 [thread overview] Message-ID: <87k0p6s5lo.fsf@mpe.ellerman.id.au> (raw) In-Reply-To: <1804692b-f9d4-964d-bbe4-cb809dad5ee8@csgroup.eu> Christophe Leroy <christophe.leroy@csgroup.eu> writes: > Le 11/04/2021 à 02:31, Haren Myneni a écrit : >> >> Using the same /dev/crypto/nx-gzip interface for both powerNV and >> pseries. So this patcb moves VAS API to powerpc platform indepedent >> directory. The actual functionality is not changed in this patch. > > This patch seems to do a lot more than moving VAS API to independent directory. A more detailed > description would help. > > And it is not something defined in the powerpc architecture I think, so it should > remain in some common platform related directory. > >> >> Signed-off-by: Haren Myneni <haren@linux.ibm.com> >> --- >> arch/powerpc/Kconfig | 15 +++++ >> arch/powerpc/include/asm/vas.h | 22 ++++++- >> arch/powerpc/kernel/Makefile | 1 + >> .../{platforms/powernv => kernel}/vas-api.c | 64 ++++++++++-------- >> arch/powerpc/platforms/powernv/Kconfig | 14 ---- >> arch/powerpc/platforms/powernv/Makefile | 2 +- >> arch/powerpc/platforms/powernv/vas-window.c | 66 +++++++++++++++++++ >> 7 files changed, 140 insertions(+), 44 deletions(-) >> rename arch/powerpc/{platforms/powernv => kernel}/vas-api.c (83%) >> >> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig >> index 386ae12d8523..7aa1fbf7c1dc 100644 >> --- a/arch/powerpc/Kconfig >> +++ b/arch/powerpc/Kconfig >> @@ -478,6 +478,21 @@ config PPC_UV >> >> If unsure, say "N". >> >> +config PPC_VAS >> + bool "IBM Virtual Accelerator Switchboard (VAS)" >> + depends on PPC_POWERNV && PPC_64K_PAGES >> + default y >> + help >> + This enables support for IBM Virtual Accelerator Switchboard (VAS). > > IIUC is a functionnality in a coprocessor of some IBM processors. Something similar in principle to > the communication coprocessors we find in Freescale processors. It's not a coprocessor, it's a way you talk to coprocessors. > It is not a generic functionnality part of the powerpc architecture, I don't think this belongs to > arch/powerpc/Kconfig But you're right it's not part of the ISA. > I think it should go in arch/powerpc/platform/Kconfig The problem with that is it's shared between two existing platforms, ie. powernv and pseries. We don't want to put it in one or the other. In the past we have put code like that in arch/powerpc/sysdev, but I am not a big fan of it, because it's just a bit of a dumping ground. A while back I created arch/powerpc/platforms/4xx for 40x and 44x related things, even though there's no actual 4xx platform. I don't think that's caused any problems. So I'm inclined to say we should make a arch/powerpc/platforms/book3s and put VAS in there. The naming is a bit fishy, because not all book3s CPUs do or will have VAS. But we would expect any future CPU with VAS to be book3s. In contrast if we named it platforms/ibm, we could potentially have a future non-IBM CPU that contains VAS, which would then make the ibm name confusing. cheers
next prev parent reply other threads:[~2021-04-13 12:59 UTC|newest] Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-11 0:27 [PATCH 00/16] Enable VAS and NX-GZIP support on powerVM Haren Myneni 2021-04-11 0:27 ` Haren Myneni 2021-04-11 0:29 ` [PATCH 01/16] powerpc/powernv/vas: Rename register/unregister functions Haren Myneni 2021-04-11 0:29 ` Haren Myneni 2021-04-11 0:31 ` [PATCH 02/16] powerpc/vas: Make VAS API powerpc platform independent Haren Myneni 2021-04-11 0:31 ` Haren Myneni 2021-04-11 8:49 ` Christophe Leroy 2021-04-11 8:49 ` Christophe Leroy 2021-04-12 0:29 ` Haren Myneni 2021-04-12 0:29 ` Haren Myneni 2021-04-13 12:59 ` Michael Ellerman [this message] 2021-04-13 12:59 ` Michael Ellerman 2021-04-11 0:32 ` [PATCH 03/16] powerpc/vas: Create take/drop task reference functions Haren Myneni 2021-04-11 0:32 ` Haren Myneni 2021-04-11 0:33 ` [PATCH 04/16] powerpc/vas: Move update_csb/dump_crb to platform independent Haren Myneni 2021-04-11 0:33 ` Haren Myneni 2021-04-11 0:34 ` [PATCH 05/16] powerpc/vas: Define and use common vas_window struct Haren Myneni 2021-04-11 0:34 ` Haren Myneni 2021-04-11 0:35 ` [PATCH 06/16] powerpc/pseries/vas: Define VAS/NXGZIP HCALLs and structs Haren Myneni 2021-04-11 0:35 ` Haren Myneni 2021-04-11 0:35 ` [PATCH 07/16] powerpc/vas: Define QoS credit flag to allocate window Haren Myneni 2021-04-11 0:35 ` Haren Myneni 2021-04-11 0:36 ` [PATCH 08/16] powerpc/pseries/VAS: Implement allocate/modify/deallocate HCALLS Haren Myneni 2021-04-11 0:36 ` Haren Myneni 2021-04-11 0:38 ` [PATCH 09/16] powerpc/pseries/vas: Implement to get all capabilities Haren Myneni 2021-04-11 0:38 ` Haren Myneni 2021-04-11 0:39 ` [PATCH 10/16] powerpc/pseries/vas: Integrate API with open/close windows Haren Myneni 2021-04-11 0:39 ` Haren Myneni 2021-04-11 0:40 ` [PATCH 11/16] powerpc/pseries/vas: Setup IRQ and fault handling Haren Myneni 2021-04-11 0:40 ` Haren Myneni 2021-04-11 0:41 ` [PATCH 12/16] powerpc/pseries/vas: sysfs interface to export capabilities Haren Myneni 2021-04-11 0:41 ` Haren Myneni 2021-04-11 0:41 ` [PATCH 13/16] crypto/nx: Rename nx-842-pseries file name to nx-common-pseries Haren Myneni 2021-04-11 0:41 ` Haren Myneni 2021-04-11 0:43 ` [PATCH 14/16] crypto/nx: Register and unregister VAS interface Haren Myneni 2021-04-11 0:43 ` Haren Myneni 2021-04-11 7:48 ` kernel test robot 2021-04-11 7:48 ` kernel test robot 2021-04-11 7:48 ` kernel test robot 2021-04-11 0:44 ` [PATCH 15/16] crypto/nx: Get NX capabilities for GZIP coprocessor type Haren Myneni 2021-04-11 0:44 ` Haren Myneni 2021-04-11 7:48 ` kernel test robot 2021-04-11 7:48 ` kernel test robot 2021-04-11 7:48 ` kernel test robot 2021-04-11 0:45 ` [PATCH 16/16] crypto/nx: sysfs interface to export NX capabilities Haren Myneni 2021-04-11 0:45 ` Haren Myneni 2021-04-11 8:07 ` [PATCH 00/16] Enable VAS and NX-GZIP support on powerVM Christophe Leroy 2021-04-11 8:07 ` Christophe Leroy
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=87k0p6s5lo.fsf@mpe.ellerman.id.au \ --to=mpe@ellerman.id.au \ --cc=christophe.leroy@csgroup.eu \ --cc=haren@linux.ibm.com \ --cc=haren@us.ibm.com \ --cc=hbabu@us.ibm.com \ --cc=herbert@gondor.apana.org.au \ --cc=linux-crypto@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=npiggin@gmail.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.