Re: Question about the repeated page fault

[Andrew Cooper <andrew.cooper3@citrix.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1701 bytes --]

On 21/09/2013 15:52, Kai Luo wrote:
>
> Hello everyone:
>
>     Recently,I am working on a feature of intercepting the giving
> function in windows SSDT table,I replace address of function in SSDT
> whith an invalid address.
>     The question is when I trapped the page fault caused by accessing
> the invalid address and I recovered it to the correct function
> address,I can recive the same page fault again.That is to say:
>           1.I trapped a page fault caused by an invalid address in
> sh_page_fault(struct vcpu *v,unsigned long va,struct cpu_user_regs *regs)
>           2.I rescover the guest eip to the correct address using the
> following code(Missing something?):
>                   regs->eip = <correct_addr>
>                   __vmwrite(GUEST_RIP, <correct_addr>);
>           3.Another page fault caused by the same address occured
>     I dumped the vmcs when the page faults occured,contents in vmcs
> are almost the same except the 'Virtual processor ID',still
> confused.Could you help me to analyse the strange phenomenon?Thank you
> very much!
>
> Jone
>
>

Ignoring for now whether this is sensible in the slightest, are you
certain that the SSDT function is only being executed once by Windows
and still resulting in two pagefaults?

(Not directly related, but) sh_page_fault() is only valid for shadow
mode, and not valid for EPT/NPT, which HVM domains default on
appropriate hardware.

The vmentry helper writes regs->rip back to GUEST_RIP so you should not
need to do that.  If you have followed the instructions at the top of
sh_page_fault(), the guest should retry the access with the correct RIP.

As for the VPID being different, that is to be expected.

~Andrew

[-- Attachment #1.2: Type: text/html, Size: 2954 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel