From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: linuxppc-dev@lists.ozlabs.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Alistair Popple <alistair@popple.id.au>,
Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
Reza Arbab <arbab@linux.ibm.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH kernel 0/2] powerpc/powernv/npu: Move platform shared code to sysdev
Date: Mon, 14 Jan 2019 11:55:59 +1100 [thread overview]
Message-ID: <20190114005601.1220-1-aik@ozlabs.ru> (raw)
This is to avoid pseries calling into powernv code. The first patch
changes data structure a bit, the second is cut-n-paste without
changing logic or data structures.
This is not changing symbol names as the NVIDIA UVM driver calls some of
them (pnv_npu2_init_context, pnv_npu2_destroy_context, pnv_pci_get_npu_dev,
pnv_npu2_handle_fault).
This is based on sha1
574823bf Linus Torvalds "Change mincore() to count "mapped" pages rather than "cached" pages".
Please comment. Thanks.
Alexey Kardashevskiy (2):
powerpc/powernv/npu: Move compound PEs to powernv
powerpc/powernv/npu: Move platform shared code to sysdev
arch/powerpc/sysdev/Makefile | 1 +
arch/powerpc/include/asm/npu.h | 88 +++
arch/powerpc/include/asm/pci.h | 8 +-
arch/powerpc/include/asm/powernv.h | 24 -
arch/powerpc/platforms/powernv/pci.h | 4 +
arch/powerpc/platforms/powernv/npu-dma.c | 672 +---------------------
arch/powerpc/sysdev/npu.c | 677 +++++++++++++++++++++++
arch/powerpc/sysdev/Kconfig | 3 +
8 files changed, 781 insertions(+), 696 deletions(-)
create mode 100644 arch/powerpc/include/asm/npu.h
create mode 100644 arch/powerpc/sysdev/npu.c
--
2.17.1
next reply other threads:[~2019-01-14 0:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 0:55 Alexey Kardashevskiy [this message]
2019-01-14 0:56 ` [PATCH kernel 1/2] powerpc/powernv/npu: Move compound PEs to powernv Alexey Kardashevskiy
2019-01-14 0:56 ` [PATCH kernel 2/2] powerpc/powernv/npu: Move platform shared code to sysdev Alexey Kardashevskiy
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=20190114005601.1220-1-aik@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=alistair@popple.id.au \
--cc=andrew.donnellan@au1.ibm.com \
--cc=arbab@linux.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).