diff options
| author | Cédric Le Goater <clg@kaod.org> | 2017-08-30 21:46:16 +0200 |
|---|---|---|
| committer | Michael Ellerman <mpe@ellerman.id.au> | 2017-09-02 21:02:38 +1000 |
| commit | ac5e5a5402d64acd48af3287718e24ff8ba9fa21 (patch) | |
| tree | 2e8e36d8f5e94a3c80db0c89a653352e21bbd138 /arch/powerpc/mm/fsl_booke_mmu.c | |
| parent | bed81ee181dd6b21171cffbb80472cc5b774c24d (diff) | |
| download | blackbird-obmc-linux-ac5e5a5402d64acd48af3287718e24ff8ba9fa21.tar.gz blackbird-obmc-linux-ac5e5a5402d64acd48af3287718e24ff8ba9fa21.zip | |
powerpc/xive: add XIVE Exploitation Mode to CAS
On POWER9, the Client Architecture Support (CAS) negotiation process
determines whether the guest operates in XIVE Legacy compatibility or
in XIVE exploitation mode. Now that we have initial guest support for
the XIVE interrupt controller, let's inform the hypervisor what we can
do.
The platform advertises the XIVE Exploitation Mode support using the
property "ibm,arch-vec-5-platform-support-vec-5", byte 23 bits 0-1 :
- 0b00 XIVE legacy mode Only
- 0b01 XIVE exploitation mode Only
- 0b10 XIVE legacy or exploitation mode
The OS asks for XIVE Exploitation Mode support using the property
"ibm,architecture-vec-5", byte 23 bits 0-1:
- 0b00 XIVE legacy mode Only
- 0b01 XIVE exploitation mode Only
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'arch/powerpc/mm/fsl_booke_mmu.c')
0 files changed, 0 insertions, 0 deletions
