From c7696ef2a9d028f10adb3ceef36ba0ff3e5a467c Mon Sep 17 00:00:00 2001 From: "rogier.brussee@b90d8f15ea9cc02d3617789f77a64c35bcd838d8" Date: Wed, 2 May 2018 21:18:10 +0100 Subject: [PATCH] --- isa_conflict_resolution.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn index b9d94972f..dd253a40d 100644 --- a/isa_conflict_resolution.mdwn +++ b/isa_conflict_resolution.mdwn @@ -322,7 +322,7 @@ NOTE: under discussion. ==RB 2018-5-1 dropped IOCTL proposal for the much simpler overloadable opcodes proposal== -The xext proposal defines 8 standardised R-type instructions xcmd0, xcmd1, ...xcmd7 (preferably in the brownfield opcode space). +The overloadable opcodes proposal defines 8 standardised R-type instructions xcmd0, xcmd1, ...xcmd7 preferably in the brownfield opcode space. Each xcmd takes in rs1 a 12 bit "logical unit" (lun) identifying a device on the cpu that implements some "extension interface" (xintf) together with some additional data. An xintf is a set of up to 8 commands with 2 input and 1 output port (i.e. like an R-type instruction), together with a description of the semantics of the commands. Calling e.g. xcmd3 routes its two inputs and one output ports to command 3 on the device determined by the lun bits in rs1. Thus, the 8 standard xcmd instructions are standard-designated overloadable opcodes, with the non standard semantics of the opcode determined by the lun. Portable software, does not use luns directly. Instead, it goes through a level of indirection using a further instruction xext that translates a 20 bit globally unique identifier UUID of an xintf, to the lun of a device on the cpu that implements that xintf. The cpu can do this, because it knows (at manufacturing or boot time) which devices it has, and which xintfs they provide. This includes devices that would be described as non standard extension of the cpu if the designers had used custom opcodes instead of xintf as an interface. If the UUID of the xintf is not recognised at the current privilege level, the xext instruction returns the special lun = 0, causing any xcmd to trap. Minor variations of this scheme (requiring two more instructions) cause xcmd instructions to fallback to always return 0 or -1 instead of trapping. -- 2.30.2