From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
Joerg Roedel <joerg.roedel@amd.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/3] qemu-kvm: Invert svm-flag setting logic
Date: Tue, 07 Sep 2010 15:43:39 +0300 [thread overview]
Message-ID: <4C86337B.3010302@redhat.com> (raw)
In-Reply-To: <F63843AD-1177-44EB-96F8-F8193D852014@suse.de>
On 09/07/2010 03:37 PM, Alexander Graf wrote:
>
>> Why do you lost migration?
> Is that part fixed already? Joerg worked so hard on so many things that I lost track of what works and what doesn't :).
Was it broken? How?
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 1/3] qemu-kvm: Invert svm-flag setting logic
Date: Tue, 07 Sep 2010 15:43:39 +0300 [thread overview]
Message-ID: <4C86337B.3010302@redhat.com> (raw)
In-Reply-To: <F63843AD-1177-44EB-96F8-F8193D852014@suse.de>
On 09/07/2010 03:37 PM, Alexander Graf wrote:
>
>> Why do you lost migration?
> Is that part fixed already? Joerg worked so hard on so many things that I lost track of what works and what doesn't :).
Was it broken? How?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-09-07 12:43 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 11:27 [PATCH 0/3] Add svm cpuid features to qemu-kvm Joerg Roedel
2010-09-07 11:27 ` [Qemu-devel] " Joerg Roedel
2010-09-07 11:27 ` [PATCH 1/3] qemu-kvm: Invert svm-flag setting logic Joerg Roedel
2010-09-07 11:27 ` [Qemu-devel] " Joerg Roedel
2010-09-07 12:23 ` Alexander Graf
2010-09-07 12:23 ` Alexander Graf
2010-09-07 12:30 ` Daniel P. Berrange
2010-09-07 12:33 ` Alexander Graf
2010-09-07 12:35 ` Avi Kivity
2010-09-07 12:35 ` Avi Kivity
2010-09-07 12:37 ` Alexander Graf
2010-09-07 12:37 ` Alexander Graf
2010-09-07 12:43 ` Avi Kivity [this message]
2010-09-07 12:43 ` Avi Kivity
2010-09-07 12:55 ` Alexander Graf
2010-09-07 12:55 ` Alexander Graf
2010-09-07 12:59 ` Avi Kivity
2010-09-07 12:59 ` Avi Kivity
2010-09-07 14:14 ` Roedel, Joerg
2010-09-07 14:14 ` Roedel, Joerg
2010-09-07 13:51 ` Avi Kivity
2010-09-07 14:12 ` Roedel, Joerg
2010-09-07 14:12 ` Roedel, Joerg
2010-09-07 14:14 ` Alexander Graf
2010-09-07 14:14 ` Alexander Graf
2010-09-07 14:18 ` Roedel, Joerg
2010-09-07 14:18 ` Roedel, Joerg
2010-09-07 14:16 ` Alexander Graf
2010-09-07 14:16 ` Alexander Graf
2010-09-07 14:20 ` Roedel, Joerg
2010-09-07 14:20 ` Roedel, Joerg
2010-09-07 14:22 ` Alexander Graf
2010-09-07 14:22 ` Alexander Graf
2010-09-07 14:33 ` Roedel, Joerg
2010-09-07 14:33 ` Roedel, Joerg
2010-09-07 14:36 ` Alexander Graf
2010-09-07 14:36 ` Alexander Graf
2010-09-07 14:56 ` Avi Kivity
2010-09-07 11:27 ` [PATCH 2/3] qemu-kvm: Set cpuid definition to 0 before initializing it Joerg Roedel
2010-09-07 11:27 ` [Qemu-devel] " Joerg Roedel
2010-09-07 11:27 ` [PATCH 3/3] qemu-kvm: Add svm cpuid features Joerg Roedel
2010-09-07 11:27 ` [Qemu-devel] " Joerg Roedel
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=4C86337B.3010302@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=berrange@redhat.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.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.