public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Vivier <Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
To: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: [PATCH 0/6] Consolidate the various functions that read and write guest memory
Date: Mon, 30 Jul 2007 11:37:24 +0200	[thread overview]
Message-ID: <46ADB154.9030709@bull.net> (raw)


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

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 <Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
-- 
------------- Laurent.Vivier-6ktuUTfB/bM@public.gmane.org  --------------
          "Software is hard" - Donald Knuth


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

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

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

             reply	other threads:[~2007-07-30  9:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30  9:37 Laurent Vivier [this message]
     [not found] ` <46ADB154.9030709-6ktuUTfB/bM@public.gmane.org>
2007-07-30  9:58   ` [PATCH 0/6] Consolidate the various functions that read and write guest memory Avi Kivity
     [not found]     ` <46ADB62E.5050802-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-30 10:23       ` Laurent Vivier
     [not found]         ` <46ADBC17.7070702-6ktuUTfB/bM@public.gmane.org>
2007-07-30 10:26           ` Avi Kivity
2007-07-30 10:43   ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46ADB154.9030709@bull.net \
    --to=laurent.vivier-6ktuutfb/bm@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox