All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Glauber Costa <glommer@redhat.com>,
	aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] create kvm-shared-all.c and kvm-shared.h
Date: Tue, 09 Jun 2009 19:26:58 +0300	[thread overview]
Message-ID: <4A2E8D52.4080600@redhat.com> (raw)
In-Reply-To: <4A2E8B15.3010401@siemens.com>

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.
>   

Yes, we could simply append libkvm-all.c and qemu-kvm.c to kvm-all.c, 
and gradually include more of kvm-all.c as we delete parts of libkvm.c 
and qemu-kvm.c.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2009-06-09 16:27 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 [this message]
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

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=4A2E8D52.4080600@redhat.com \
    --to=avi@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=glommer@redhat.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 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.