________________________________ >> spapr_hcall.c: >> function h_enter call ppc_hash64_hpte_page_shift_noslb, >> ppc_hash64_map_hptes and ppc_hash64_unmap_hptes >> function remove_hpte call ppc_hash64_map_hptes, ppc_hash64_unmap_hptes >> and ppc_hash64_tlb_flush_hpte >> function h_protect call ppc_hash64_map_hptes, ppc_hash64_unmap_hptes and >> ppc_hash64_tlb_flush_hpte >> function h_read call ppc_hash64_map_hptes and ppc_hash64_unmap_hptes >> function rehash_hpte call ppc_hash64_hpte_page_shift_noslb >> function rehash_hpt call ppc_hash64_map_hptes and ppc_hash64_unmap_hptes > >h_enter, remove_hpte, h_protect, h_read and rehash_hpte should never >be called for a KVM guest (KVM will intercept the relevant hcalls >before they reach qemu). I think it would make sense to split of a >TCG only portion of spapr_hcall.c into a new file. You'll then >probably need !TCG stubs for those hypercalls, which should trip a >fatal error (if KVM hasn't handled the calls, there's nothing we can >do that will salvage the situation). Besides the aforementioned functions, will all spapr hypercalls beginning with H_* be intercepted (and therefore, should trip a fatal error in the KVM-only file) or only a subset of these functions will be intercepted? If the latter is there an interval of opcodes that'll be intercepted?
Re: target/ppc: sPAPR invalid function calls when compiling without TCG
Lucas Mateus Martins Araujo e Castro Tue, 20 Apr 2021 11:28:15 -0700
- target/ppc: sPAPR invalid function ca... Lucas Mateus Martins Araujo e Castro
- Re: target/ppc: sPAPR invalid fu... David Gibson
- Re: target/ppc: sPAPR invalid fu... Lucas Mateus Martins Araujo e Castro
- Re: target/ppc: sPAPR invali... David Gibson
- Re: target/ppc: sPAPR invalid fu... Lucas Mateus Martins Araujo e Castro
- Re: target/ppc: sPAPR invali... David Gibson