public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Anthony Liguori <aliguori-NZpS4cJIG2HvQtjrzfazuQ@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [RFC] QEMU KVM Patch Queue
Date: Fri, 03 Nov 2006 08:14:41 +0200	[thread overview]
Message-ID: <454ADE51.6080104@qumranet.com> (raw)
In-Reply-To: <454ABB9C.2070500-NZpS4cJIG2HvQtjrzfazuQ@public.gmane.org>

Anthony Liguori wrote:
> Howdy,
>
> In an attempt to help prepare KVM's QEMU changes for upstream 
> submission, I spent some time this evening splitting apart the
> qemu-kvm-1.patch available on sf.net.  

Thanks, this is very useful!

> I've split them up into:
>
> apic-save-restore.diff - apic save/restore fix
>
> timer-save-restore.diff - timer save/restore fix

I think these two are actually from qemu cvs.

>
> gdbstubs-x86_64.diff - gdbstub for x86_64

I've tried to submit this to qemu already, not much luck.


>
> kvm.diff - kvm changes
>
> kvm-same-binary.diff - changes to kvm to allow it to be used in the same
> binary as kqemu or normal qemu.  You can select to use kvm with the
> -enable-kvm option.

This is massively useful.


>
> I did this using a mercurial patch queue which is available here:
>
> http://hg.codemonkey.ws/qemu-kvm/
>
> If you're unfamiliar with mercurial, you can grab a tarball of the
> patches here:
>
> http://hg.codemonkey.ws/qemu-kvm/?ca=tip;type=bz2
>
> I've tested a FC4 and Win2k guest.  Neither are working perfect under
> KVM but my patches do not make it any worse at least :-)
>
> This cleanup reduces the main KVM patch (not including the random 
> cleanups) from about ~1300 lines to ~800 lines.
>
> If preferred, I can send the patches to this list via a patch bomb...

Please do.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

      parent reply	other threads:[~2006-11-03  6:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03  3:46 [RFC] QEMU KVM Patch Queue Anthony Liguori
     [not found] ` <454ABB9C.2070500-NZpS4cJIG2HvQtjrzfazuQ@public.gmane.org>
2006-11-03  6:14   ` 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=454ADE51.6080104@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=aliguori-NZpS4cJIG2HvQtjrzfazuQ@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