From: Avi Kivity <avi@qumranet.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [kvm-devel] [PATCH 0/3] KVM paravirtualization framework (v2)
Date: Sun, 09 Sep 2007 15:29:49 +0300 [thread overview]
Message-ID: <46E3E73D.1060404@qumranet.com> (raw)
In-Reply-To: <1188243723984-git-send-email-aliguori@us.ibm.com>
Anthony Liguori wrote:
> This patchset refactors KVM's paravirtualization support to better support
> guest SMP and cross platform migration. It also introduces a bare-bones KVM
> paravirt_ops implementation.
>
> I've tested this on VT and it works nicely. I'm having trouble getting a
> bzImage to boot on SVM so I haven't been able to test on SVM yet.
>
> I've incorporated all of the feedback into this series from posting the
> last series.
>
Can you send this patchset out again? There were some updated patches
posted and I'm not sure I can find the most recent ones.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2007-09-09 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 19:42 [PATCH 0/3] KVM paravirtualization framework (v2) Anthony Liguori
2007-08-27 19:42 ` [PATCH 1/3] Refactor hypercall infrastructure (v2) Anthony Liguori
2007-08-27 19:42 ` [PATCH 2/3] KVM paravirt-ops implementation (v2) Anthony Liguori
[not found] ` <11882437252643-git-send-email-aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-08-27 19:42 ` [PATCH 3/3] Add the paravirtualization CPUID entry to QEMU (v2) Anthony Liguori
[not found] ` <1188243725114-git-send-email-aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-08-27 19:54 ` Avi Kivity
[not found] ` <46D32BF5.2030904-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-27 20:04 ` Anthony Liguori
2007-09-09 12:29 ` Avi Kivity [this message]
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=46E3E73D.1060404@qumranet.com \
--to=avi@qumranet.com \
--cc=aliguori@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@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