From the TODO, this serie of patch is trying to consolidate the various
functions that read and write guest memory.
We remove kvm_read_guest() and kvm_write_guest(), and we use instead
emulator_read_std() and emulator_write_emulated().

PATCH 1/6: read_std-vcpu, emulator_read_std() uses struct kvm_vcpu instead of
x86_emulate_ctxt to be called in place of kvm_read_guest().

PATCH 2/6: read_emulated-vcpu, emulator_read_emulated() uses struct kvm_vcpu
instead of x86_emulate_ctxt to be consistency with emulator_read_std().

PATCH 3/6: remove-kvm_read_guest, remove kvm_read_guest() and use
emulator_read_std() instead.

PATCH 4/6: write_emulated-vcpu, emulator_write_emulated() uses struct kvm_vcpu
instead of x86_emulate_ctxt to be called in place of kvm_write_guest().

PATCH 5/6: remove-kvm_write, remove kvm_write_guest() and use
emulator_write_emulated() instead.

PATCH 6/6: cmpxchg_emulated-vcpu, emulator_cmpxchr_emulated() uses struct
kvm_vcpu instead of x86_emulate_ctxt to be consistency with other memops.

Signed-off-by: Laurent Vivier <[EMAIL PROTECTED]>
-- 
------------- [EMAIL PROTECTED]  --------------
          "Software is hard" - Donald Knuth

Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
kvm-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Reply via email to