kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Avi Kivity <avi@redhat.com>
Cc: Glauber Costa <glommer@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 7/8] use kvm_upstream sw_breakpoints structure
Date: Wed, 08 Jul 2009 17:23:19 +0200	[thread overview]
Message-ID: <4A54B9E7.9000801@web.de> (raw)
In-Reply-To: <4A54A2A7.7040309@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 743 bytes --]

Avi Kivity wrote:
> On 07/08/2009 04:39 PM, Glauber Costa wrote:
>> On Wed, Jul 08, 2009 at 04:27:27PM +0300, Avi Kivity wrote:
>>   
>>> On 07/08/2009 04:09 PM, Glauber Costa wrote:
>>>     
>>>> Signed-off-by: Glauber Costa<glommer@redhat.com>
>>>> ---
>>>>    kvm-all.c         |   27 ++++++++++++++++++---------
>>>>    qemu-kvm.h        |    6 +++---
>>>>    target-i386/kvm.c |    4 ++--
>>>>    3 files changed, 23 insertions(+), 14 deletions(-)
>>>>
>>>>
>>>>        
>>> Did you test the functionality to ensure we do not regress?
>>>      
>> just briefly. To be honest, I'd feel much more confortable
>> if Jan could give it a try.
>>    
> 
> A Jan try (+review) will definitely help.
> 

Queued.

Jan


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

  reply	other threads:[~2009-07-08 15:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 13:08 [PATCH 0/8] Move closer to upstream Glauber Costa
2009-07-08 13:08 ` [PATCH 1/8] Provide KVMState definition outside CONFIG_KVM Glauber Costa
2009-07-08 13:22   ` Avi Kivity
     [not found]   ` <1247058542-31211-3-git-send-email-glommer@redhat.com>
2009-07-08 13:08     ` [PATCH 3/8] put qemu-kvm-x86.c into kvm.c Glauber Costa
2009-07-08 13:08       ` [PATCH 4/8] replace malloc with qemu_malloc Glauber Costa
2009-07-08 13:08         ` [PATCH 5/8] move kvm_context inside KVMState Glauber Costa
2009-07-08 13:09           ` [PATCH 6/8] provide env->kvm_fd Glauber Costa
2009-07-08 13:09             ` [PATCH 7/8] use kvm_upstream sw_breakpoints structure Glauber Costa
2009-07-08 13:09               ` [PATCH 8/8] use upstream code for breakpoint handling Glauber Costa
2009-07-08 13:27               ` [PATCH 7/8] use kvm_upstream sw_breakpoints structure Avi Kivity
2009-07-08 13:39                 ` Glauber Costa
2009-07-08 13:44                   ` Avi Kivity
2009-07-08 15:23                     ` Jan Kiszka [this message]
2009-07-08 19:44                       ` Jan Kiszka
2009-07-08 19:55                         ` Avi Kivity
2009-07-08 13:32             ` [PATCH 6/8] provide env->kvm_fd Gleb Natapov
2009-07-08 13:44               ` Glauber Costa
2009-07-08 13:38                 ` Gleb Natapov
2009-07-08 13:23       ` [PATCH 3/8] put qemu-kvm-x86.c into kvm.c Avi Kivity
2009-07-08 13:28       ` Gleb Natapov
2009-07-08 13:41         ` Glauber Costa
2009-07-08 13:23     ` [PATCH 2/8] move qemu-kvm.c to kvm-all.c Avi Kivity
2009-07-08 13:52       ` Glauber Costa
2009-07-08 13:27 ` [PATCH 0/8] Move closer to upstream 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=4A54B9E7.9000801@web.de \
    --to=jan.kiszka@web.de \
    --cc=avi@redhat.com \
    --cc=glommer@redhat.com \
    --cc=kvm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).