From: Paolo Bonzini <pbonzini@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] provide a stub version of kvm-all.c if !CONFIG_KVM
Date: Fri, 02 Apr 2010 19:33:40 +0200 [thread overview]
Message-ID: <4BB62A74.6090109@redhat.com> (raw)
In-Reply-To: <z2gf43fc5581004021029j56b6b220w5a11f0b218ae7e2e@mail.gmail.com>
On 04/02/2010 07:29 PM, Blue Swirl wrote:
> Could you stub also kvm_init?
It is stubbed, but it returns ENOSYS:
+int kvm_init(int smp_cpus)
+{
+ return -ENOSYS;
+}
+
and in fact I'm relying this to remove this:
if (!(kvm_available())) {
printf("Option %s not supported for this target\n", popt->name);
exit(1);
}
and instead looking for an error when I call kvm_init. I don't see why
kvm_init should be called if not passing -enable-kvm (which is kvm_allowed).
> Then this part would be simpler because
> you can call unconditionally kvm_init. I guess there would be no need
> to export kvm_allowed for !CONFIG_KVM case.
I don't understand what you mean. If this doesn't clarify enough, feel
free to pick up the patch and tweak it; I'm not going to spend much time
on QEMU for a while.
Paolo
next prev parent reply other threads:[~2010-04-02 17:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 15:46 [Qemu-devel] [PATCH 1/2] Move KVM init to arch_init.c, compile vl.c once Blue Swirl
2010-04-02 17:05 ` [Qemu-devel] [PATCH] provide a stub version of kvm-all.c if !CONFIG_KVM Paolo Bonzini
2010-04-02 17:29 ` [Qemu-devel] " Blue Swirl
2010-04-02 17:33 ` Paolo Bonzini [this message]
2010-04-02 18:17 ` Blue Swirl
2010-04-02 18:33 ` Paolo Bonzini
2010-04-02 19:04 ` Blue Swirl
2010-04-03 9:04 ` Paolo Bonzini
2010-04-03 9:07 ` Blue Swirl
2010-04-04 7:12 ` Paolo Bonzini
2010-04-04 7:25 ` Blue Swirl
2010-04-04 18:13 ` Paolo Bonzini
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=4BB62A74.6090109@redhat.com \
--to=pbonzini@redhat.com \
--cc=blauwirbel@gmail.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).