From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Laurent Vivier <Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH 0/6] Consolidate the various functions that read and write guest memory
Date: Mon, 30 Jul 2007 13:26:55 +0300 [thread overview]
Message-ID: <46ADBCEF.8050707@qumranet.com> (raw)
In-Reply-To: <46ADBC17.7070702-6ktuUTfB/bM@public.gmane.org>
Laurent Vivier wrote:
> Avi Kivity wrote:
>
>> Laurent Vivier wrote:
>>
>>> 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 2/6 did not seem to make it to the list. Can you resend?
>>
>>
>>
>
> Be patient, SMTP seems a little bit slow... do you have it now ?
> (BTW, the title is broken "PATCH 2/6]" instead of "[PATH 2/6]")
>
>
Yes, it's gotten there at last.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
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/
next prev parent reply other threads:[~2007-07-30 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 9:37 [PATCH 0/6] Consolidate the various functions that read and write guest memory Laurent Vivier
[not found] ` <46ADB154.9030709-6ktuUTfB/bM@public.gmane.org>
2007-07-30 9:58 ` 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 [this message]
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=46ADBCEF.8050707@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.