From: Glauber Costa <glommer@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>,
Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] Re: [PATCH 3/3] Add KVM support to QEMU
Date: Wed, 29 Oct 2008 15:41:22 -0200 [thread overview]
Message-ID: <20081029174122.GE11532@poweredge.glommer> (raw)
In-Reply-To: <1225224814-9875-3-git-send-email-aliguori@us.ibm.com>
resending, now with less quoted text:
> diff --git a/kvm-all.c b/kvm-all.c
> new file mode 100644
> index 0000000..4379071
> --- /dev/null
> +++ b/kvm-all.c
> @@ -0,0 +1,377 @@
> +/*
> + * QEMU KVM support
> + *
> + * Copyright IBM, Corp. 2008
> + *
> + * Authors:
> + * Anthony Liguori <aliguori@us.ibm.com>
> + *
> + * This work is licensed under the terms of the GNU GPL, version 2. See
> + * the COPYING file in the top-level directory.
> + *
> + */
> +
> +#include <sys/types.h>
> +#include <sys/ioctl.h>
> +#include <sys/mman.h>
> +
> +#include <linux/kvm.h>
> +
> +#include "qemu-common.h"
> +#include "sysemu.h"
> +#include "kvm.h"
> +
> +//#define DEBUG_KVM
> +
> +#ifdef DEBUG_KVM
> +#define dprintf(fmt, ...) \
> + do { fprintf(stderr, fmt, ## __VA_ARGS__); } while (0)
> +#else
> +#define dprintf(fmt, ...) \
> + do { } while (0)
> +#endif
> +
> +typedef struct kvm_userspace_memory_region KVMSlot;
Actually, I don't think it is a good idea.
We may want to keep internal-only data tied to the slot, such the slot's
dirty bitmap if we do per-slot dirty tracking.
Of course there may be other ways to do it, but this is the cleaner
and more adequate since we're going through a fresh start.
next prev parent reply other threads:[~2008-10-29 17:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 20:13 [Qemu-devel] [PATCH 1/3] Add additional CPU flag definitions Anthony Liguori
2008-10-28 20:13 ` [Qemu-devel] [PATCH 2/3] Split CPUID from op_helper Anthony Liguori
2008-10-28 20:13 ` [Qemu-devel] [PATCH 3/3] Add KVM support to QEMU Anthony Liguori
2008-10-28 20:49 ` Hollis Blanchard
2008-10-28 21:10 ` Anthony Liguori
2008-10-28 20:57 ` Andreas Färber
2008-10-28 21:04 ` Glauber Costa
2008-10-28 21:16 ` Anthony Liguori
2008-10-28 21:05 ` Anthony Liguori
2008-11-04 13:25 ` Avi Kivity
2008-10-28 21:41 ` [Qemu-devel] " Gerd Hoffmann
2008-10-28 21:51 ` Anthony Liguori
2008-10-28 23:04 ` Glauber Costa
2008-10-28 23:36 ` Anthony Liguori
2008-10-29 9:54 ` Avi Kivity
2008-10-29 12:35 ` Glauber Costa
2008-10-29 12:39 ` Avi Kivity
2008-10-29 12:56 ` Glauber Costa
2008-10-29 13:07 ` Anthony Liguori
2008-10-29 13:23 ` Avi Kivity
2008-10-29 13:32 ` Anthony Liguori
2008-10-29 13:51 ` Hollis Blanchard
2008-10-29 14:09 ` Avi Kivity
2008-10-29 14:16 ` Fabrice Bellard
2008-10-29 14:23 ` Anthony Liguori
2008-10-29 19:13 ` Blue Swirl
2008-11-01 16:25 ` Blue Swirl
2008-10-29 14:58 ` Glauber Costa
2008-10-29 17:41 ` Glauber Costa [this message]
2008-10-29 19:01 ` Anthony Liguori
2008-11-04 13:24 ` Avi Kivity
2008-11-04 14:02 ` Anthony Liguori
2008-11-04 14:46 ` Avi Kivity
2008-11-04 14:50 ` Anthony Liguori
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=20081029174122.GE11532@poweredge.glommer \
--to=glommer@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--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 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).