Editing HV Syscall Reference
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 785: | Line 785: | ||
=== lv1_detect_pending_interrupts === | === lv1_detect_pending_interrupts === | ||
Not used in current kernel | Not used in current kernel. | ||
===== Abstract Call ===== | ===== Abstract Call ===== | ||
Line 800: | Line 800: | ||
|- | |- | ||
|R3 | |R3 | ||
|p1 - unknown | |p1 - unknown | ||
|- | |- | ||
! colspan="2" | Outputs | ! colspan="2" | Outputs | ||
Line 808: | Line 808: | ||
|- | |- | ||
|R3 | |R3 | ||
|Status | |Status? | ||
|- | |- | ||
|R4 | |R4 | ||
|v1 - | |v1 - Unknown | ||
|- | |- | ||
|R5 | |R5 | ||
|v2 - | |v2 - Unknown | ||
|- | |- | ||
|R6 | |R6 | ||
|v3 - | |v3 - Unknown | ||
|- | |- | ||
|R7 | |R7 | ||
|v4 - | |v4 - Unknown | ||
|- | |- | ||
|} | |} | ||
Notes: | Notes: | ||
Info taken from kboot-10\dl\linux-2.6.16\include\asm-powerpc\lv1calltab.h (kboot-20061208) | Info taken from kboot-10\dl\linux-2.6.16\include\asm-powerpc\lv1calltab.h (kboot-20061208) | ||
---- | ---- | ||
=== lv1_end_of_interrupt === | === lv1_end_of_interrupt === | ||
Line 2,174: | Line 2,173: | ||
=== lv1_set_dabr === | === lv1_set_dabr === | ||
Sets dabr ( | Sets dabr (data address breakpoint register) - an exception should be thrown upon access to data at this address (range?) | ||
===== Kernel Call ===== | ===== Kernel Call ===== | ||
result = lv1_set_dabr( /*IN*/ dabr, | result = lv1_set_dabr( /*IN*/ dabr, DABR_KERNEL | DABR_USER); | ||
===== Parameters ===== | ===== Parameters ===== | ||
Line 2,189: | Line 2,188: | ||
|- | |- | ||
|R3 | |R3 | ||
|dabr - | |dabr - data address | ||
|- | |- | ||
|R4 | |R4 | ||
| | |(DABR_KERNEL | DABR_USER) - see notes | ||
|- | |- | ||
! colspan="2" | Outputs | ! colspan="2" | Outputs | ||
Line 2,205: | Line 2,204: | ||
Notes: | Notes: | ||
DABR_KERNEL and DABR_USER are defined in “setup.c” as follows | |||
enum {DABR_USER = 1, DABR_KERNEL = 2,}; | enum {DABR_USER = 1, DABR_KERNEL = 2,}; | ||
---- | ---- | ||
=== lv1_set_vmx_graphics_mode === | === lv1_set_vmx_graphics_mode === | ||
Line 2,263: | Line 2,246: | ||
The Cell Broadband Engine Programming Handbook has this to say on the subject: The first implementation of the Cell Broadband Engine Architecture (CBEA) (the CBE processor) supports instructions with a graphics rounding mode. This mode allows programs written with vector/SIMD multimedia extension instructions to produce floating-point results that are equivalent in precision to those written in the SPU instruction set. In this mode, as in the SPU environment, the default rounding mode is round to zero, denormals are treated as zero, and there are no infinities or NaNs. | The Cell Broadband Engine Programming Handbook has this to say on the subject: The first implementation of the Cell Broadband Engine Architecture (CBEA) (the CBE processor) supports instructions with a graphics rounding mode. This mode allows programs written with vector/SIMD multimedia extension instructions to produce floating-point results that are equivalent in precision to those written in the SPU instruction set. In this mode, as in the SPU environment, the default rounding mode is round to zero, denormals are treated as zero, and there are no infinities or NaNs. | ||
To change this mode, bit 12 in the HID1 register (known as grap_md or grap_mode in various documents). HID1 is a HV privileged resource, hence to change the mode from Supervisor mode requires a HV call. | |||
Reference Documents: Cell Broadband Engine Programming Handbook V1.1 Cell Broadband Engine Registers V1.5 | Reference Documents: Cell Broadband Engine Programming Handbook V1.1 Cell Broadband Engine Registers V1.5 | ||
Line 2,273: | Line 2,256: | ||
When recompiled into Kernel module init function, accepts values of 0 and 1 for p1. All other values return -17 (LV1_ILLEGAL_PARAMETER_VALUE) | When recompiled into Kernel module init function, accepts values of 0 and 1 for p1. All other values return -17 (LV1_ILLEGAL_PARAMETER_VALUE) | ||
---- | ---- | ||
=== lv1_set_thread_switch_control_register === | === lv1_set_thread_switch_control_register === | ||
Line 2,413: | Line 2,395: | ||
|- | |- | ||
|R3 | |R3 | ||
|status | |status | ||
|- | |- | ||
|R4 | |R4 | ||
Line 2,420: | Line 2,402: | ||
|} | |} | ||
---- | ---- | ||
=== lv1_write_remote_file === | === lv1_write_remote_file === | ||
Line 4,157: | Line 4,138: | ||
===== Kernel Call ===== | ===== Kernel Call ===== | ||
result = lv1_allocate_device_dma_region( /*IN*/ bus_id, dev_id, io_size, io_pagesize, flag, | result = lv1_allocate_device_dma_region( /*IN*/ bus_id, dev_id, io_size, io_pagesize, flag, &dma_region ); | ||
===== Parameters ===== | ===== Parameters ===== | ||
Line 4,197: | Line 4,178: | ||
Notes: When the device is little endian, the mode must be set to 8 bit for 8 bit DMA to work as expected, otherwise the bytes will be read/written in the wrong order. OTOH, this mode requires that 16 and 32-bit values are byte-swapped by the CPU since they will appear as little endian in memory. | Notes: When the device is little endian, the mode must be set to 8 bit for 8 bit DMA to work as expected, otherwise the bytes will be read/written in the wrong order. OTOH, this mode requires that 16 and 32-bit values are byte-swapped by the CPU since they will appear as little endian in memory. | ||
---- | ---- | ||
=== lv1_free_device_dma_region === | === lv1_free_device_dma_region === | ||