ub: ubcore add jfc, jfr, jfs and event definition.

driver inclusion
category: feature
bugzilla: NA
CVE: NA

--------------------------------

Ubcore add jfc, jfs, jfr (jetty for completion/send/recv)
and event definition.

Introduce of Jetty:

Jetty is a logical concept, an I/O unit that provides
end-to-end communication services. Jetty is classified into three types:
Jetty for Send, Jetty for Receive, and Jetty for Completion.
Each Jetty has a queue that maintains its sending and receiving requests.
1. JFS (Jetty for send): used to submit a DMA task
or send a message on the user side.
2. JFR (jetty for receive): used to prepare a resource for
receiving a message on the home side.
3. JFC (jetty for complete): stores JFS/JFR completion events.
It can be bound to JFS or JFR, or specified separately in specific
URMA commands.
A Jetty for Send (JFS) can implement the remote memory DMA service
on one side. JFS (source end) + JFR (destination end) can implement
bilateral message services.

Event in ubcore:

There are 2 types of event in ubcore:
- JFCE (jetty for completion event): JFS/JFR completion events.
The jfc_comp_callback interrupt processing function is used to set
the JFC completion type during kernel-mode driver loading.
This callback function searches for the kernel-mode JFC pointer based on
the jfc_id reported by the hardware, and invokes the comp_handler stored
in the JFC data structure.
- JFAE (jetty for async event): Kernel-Mode Exception Events. Once a Jetty
exception occurs, the chip reports a hardware interrupt to the UBN driver.
The UBN driver parses the interrupt information, finds the abnormal Jetty,
and invokes ubcore_event_callback to report the exception to the UB Core
protocol stack.

Signed-off-by: Guoxin Qian <qianguoxin@huawei.com>
Signed-off-by: Yizhen Fan <fanyizhen@huawei.com>