From: Mark Kanda <mark.kanda@oracle.com>
To: Qemu Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Nested SVM only enabled (by default) in pc-i440fx-2.1?
Date: Wed, 27 Feb 2019 16:05:23 -0600 [thread overview]
Message-ID: <b83ee802-1f9a-f379-f1bf-4e13bfd8a94f@oracle.com> (raw)
Hi all,
I noticed nested SVM is enabled only in pc-i440fx-2.1 (default is
disabled); this was added when 2.1 was the latest:
75d373ef97 ("target-i386: Disable SVM by default in KVM mode")
However, this change was not carried forward to newer machine types. Is
this an oversight? Is there a reason we (still) need SVM disabled by
default?
Default setting - target/i386/cpu.c:
static PropValue kvm_default_props[] = {
{ "kvmclock", "on" },
...
{ "monitor", "off" },
{ "svm", "off" },
{ NULL, NULL },
};
2.1 override - hw/i386/pc_piix.c:
static void pc_compat_2_1_fn(MachineState *machine)
{
pc_compat_2_2_fn(machine);
x86_cpu_change_kvm_default("svm", NULL);
}
Thanks and best regards,
-Mark
next reply other threads:[~2019-02-27 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 22:05 Mark Kanda [this message]
2019-02-28 3:58 ` [Qemu-devel] Nested SVM only enabled (by default) in pc-i440fx-2.1? Mark Kanda
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=b83ee802-1f9a-f379-f1bf-4e13bfd8a94f@oracle.com \
--to=mark.kanda@oracle.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).