Can VS-mode directly access vsiph's separate CSR address?
No. The H extension substitutes VS state for the corresponding supervisor CSR when V=1; direct access to the separate VS CSR address raises a virtual-instruction exception.
vsiph is the RV32 upper-32-bit CSR for vsip.
vsiph is the AIA-defined RV32 high-half CSR for vsip[63:32]. RV32 M/HS can use the separate address; an RV32 guest with V=1 uses the siph alias, and access can be restricted by AIA state-enable bits.
RV32 M/HS software may access vsiph through the separate CSR address 0x254.
An RV32 guest with V=1 reaches vsiph through the siph alias; when XLEN > 32, siph/sieh high-half accesses do not become ordinary VS high-half CSR accesses under the AIA state-enable rules.
Check hideleg/hvien, AIA, and state-enable conditions before interpreting or updating VS-level interrupt bits 32..63.
No. The H extension substitutes VS state for the corresponding supervisor CSR when V=1; direct access to the separate VS CSR address raises a virtual-instruction exception.
vsiph holds vsip[63:32]. Those bits have pending meaning only for VS-level interrupts made visible by AIA, hideleg/hvien, or another official definition.