qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Glauber Costa <glommer@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] create kvm-shared-all.c and kvm-shared.h
Date: Tue, 9 Jun 2009 13:37:46 -0300	[thread overview]
Message-ID: <20090609163746.GN11966@poweredge.glommer> (raw)
In-Reply-To: <4A2E8B15.3010401@siemens.com>

On Tue, Jun 09, 2009 at 06:17:25PM +0200, Jan Kiszka wrote:
> Glauber Costa wrote:
> > Following a suggestion given by Jan, the idea here is to
> > move shared pieces between qemu and qemu-kvm.git into a common
> > file, so we can do sharing while avoid clashes.
> > 
> > In the future, this files should disappear.
> > 
> 
> OK for the header - but why do we have to push the ioctl services into a
> separate module? Will all functions qemu-kvm start to use from upstream
> have to be pushed around? Or what is special about the ioctls?
> 
> I rather think qemu-kvm should build kvm-all.c and #ifdef out those
> parts which collide with its own implementation. Moreover, when we morph
> qemu-kvm services for upstream, this could already happen where they
> shall once be located: in kvm-all.c or target-*/kvm.c.
I also think qemu-kvm should build kvm-all.c. But right now, it is so full
of conflicts, that it would be impossible. My go with the module, is, whenever
we move all the code in kvm-all.c away, it should mean it is safe to go back to
it: qemu-kvm will be granted not to conflict with it.

      parent reply	other threads:[~2009-06-09 16:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 16:04 [Qemu-devel] [PATCH] create kvm-shared-all.c and kvm-shared.h Glauber Costa
2009-06-09 16:17 ` [Qemu-devel] " Jan Kiszka
2009-06-09 16:26   ` Avi Kivity
2009-06-09 16:39     ` Glauber Costa
2009-06-09 16:42       ` Avi Kivity
2009-06-09 16:42       ` Jan Kiszka
2009-06-09 16:51         ` Glauber Costa
2009-06-09 16:51           ` Jan Kiszka
2009-06-09 16:37   ` Glauber Costa [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=20090609163746.GN11966@poweredge.glommer \
    --to=glommer@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=jan.kiszka@siemens.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 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).