qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Glauber Costa <glommer@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org,
	stefano.stabellini@eu.citrix.com
Subject: [Qemu-devel] Re: [PATCH] hook cpu running at a higher level.
Date: Tue, 30 Dec 2008 12:44:45 +0200	[thread overview]
Message-ID: <4959FB9D.8030706@redhat.com> (raw)
In-Reply-To: <18777.63215.125693.799799@mariner.uk.xensource.com>

Ian Jackson wrote:
> The way we have approached these problems in the Xen tree is to supply
> an alternative implementation of (say) main_loop and arrange for the
> standard one not to be compiled.  Is it the intent to make kvm a
> run-time selectable option ?  It seems to me that that given that we
> already have different qemu builds for all of the various target
> (guest) cpu architectures, it might be simpler to continue that
> approach.  With a bit of judicious movement of code into appropriate
> files, this will avoid the need for ifs and ifdefs.
>   

kvm is run-time selectable, both in upstream and in kvm-userspace.  If 
kvm is not detected (or the caller lacks sufficient privileges), we fall 
back to tcg (of course we'd also like the option of not compiling tcg 
where emulation is unacceptable like server deployments).

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

  reply	other threads:[~2008-12-30 10:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-29 18:29 [Qemu-devel] [PATCH] hook cpu running at a higher level Glauber Costa
2008-12-30 10:24 ` [Qemu-devel] " Ian Jackson
2008-12-30 10:44   ` Avi Kivity [this message]
2008-12-30 13:45     ` Ian Jackson
2008-12-30 11:35   ` Glauber Costa
2008-12-30 17:25     ` Ian Jackson
2008-12-30 13:54   ` Avi Kivity
2008-12-30 14:44     ` Ian Jackson

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=4959FB9D.8030706@redhat.com \
    --to=avi@redhat.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=glommer@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    /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).