search for: trap_page_fault

Hi, I am trying to understand the exception handler of Xen. In xen/arch/x86/x86_64/entry.S, the entry of the page fault handler is : ENTRY(page_fault) movl $TRAP_page_fault,4(%rsp) jmp handle_exception Here I did not get why to put the exception vector ($TRAP_page_fault) to stack before calling handle_exception? Thanks, -- Xinxin _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-deve...

This series of patches fix the mistake for debug exception(#DB), overflow exception(#OF) and INT3(#BP), INTn instruction emulation. Introduce new function vmx_inject_sw_exception() which deliver the software excetion, software interrupt and privileged software exception. Split hardware exception as a seperate function(old function vmx_inject_hw_exception()). Also Passed down intruction length

Changes from v1: - Define new struct hvm_trap to represent information of trap, include instruction length. - Renames hvm_inject_exception to hvm_inject_trap. Then define a couple of wrappers around that function for existing callers, so that their parameter lists actually *shrink*. This series of patches fix the mistake for debug exception(#DB), overflow exception(#OF) and INT3(#BP),

...gned long vaddr) +{ + unsigned long gfn; + mfn_t mfn; + p2m_type_t p2mt; + uint32_t pfec = PFEC_page_present | PFEC_write_access; + + /* Translate the VA to a GFN */ + gfn = paging_gva_to_gfn(v, vaddr, &pfec); + if ( gfn == INVALID_GFN ) + { + hvm_inject_exception(TRAP_page_fault, pfec, vaddr); + return _mfn(BAD_GVA_TO_GFN); + } + + /* Translate the GFN to an MFN */ + mfn = gfn_to_mfn(v->domain, gfn, &p2mt); + + if ( p2mt == p2m_ram_ro ) + return _mfn(READONLY_GFN); + if ( !p2m_is_ram(p2mt) ) + return _mfn(BAD_GFN_TO_MFN);...

Hello, This series has been split into two patches, one for arm and one for x86. I figured that this was easier than doing it as a single combined patch, especially as the changes are functionally independent. x86 has been boot tested, but arm has not even been compile tested as I lack a suitable cross compiler. However, the changes are just text replacement, so I dont expect any issues. The