From: Rob Gardner <rob.gardner@xxxxxxxxxx> Date: Thu, 14 Sep 2017 17:51:31 -0600 > David, thanks for the feedback. Here is what we're going to do: > 1) Verify commands going to the hypervisor by examining the opcode in > each ccb. Addresses are already being examined to make sure they are > virtual only, which ensures respect for all process specific memory > mappings, a process can only access its own memory via the > coprocessor, never that of another process. > 2) Expanded documentation on the ccb contents, and hopefully a link to > documentation on the hypervisor api. > 3) Example user space code that demonstrates the raw driver api to > submit a coprocessor ccb > 4) Example kernel code that demonstrates how to submit commands to the > coprocessor. If some crypto driver wants to do decompression using the > coprocessor, it will be able to do so by constructing a suitable > command and submitting it. There will be enough documentation to allow > this, but we are not providing such higher level services for use in > the kernel. > > Do you have any other comments or feedback on the code or anything > else? That sounds like a good start and I look forward to reviewing your next version. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
