From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH] i386: Document when features can be added to kvm_default_props
Date: Fri, 25 Sep 2020 23:46:28 +0200 [thread overview]
Message-ID: <70cf3a0b-ddb8-129a-201f-ec583c3883d1@redhat.com> (raw)
In-Reply-To: <20200925211021.4158567-1-ehabkost@redhat.com>
On 25/09/20 23:10, Eduardo Habkost wrote:
> It's very easy to mistakenly extend kvm_default_props to include
> features that require a kernel version that's too recent. Add a
> comment warning about that, pointing to the documentation file
> where the minimum kernel version for KVM is documented.
>
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> ---
> target/i386/cpu.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> index 3ffd877dd51..c8558bb49ac 100644
> --- a/target/i386/cpu.c
> +++ b/target/i386/cpu.c
> @@ -4098,8 +4098,14 @@ static X86CPUDefinition builtin_x86_defs[] = {
> },
> };
>
> -/* KVM-specific features that are automatically added/removed
> +/*
> + * KVM-specific features that are automatically added/removed
> * from all CPU models when KVM is enabled.
> + *
> + * NOTE: features can be enabled by default only if they were
> + * already available in the oldest kernel version supported
> + * by the KVM accelerator (see "OS requirements" section at
> + * docs/system/target-i386.rst)
> */
> static PropValue kvm_default_props[] = {
> { "kvmclock", "on" },
>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
next prev parent reply other threads:[~2020-09-25 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 21:10 [PATCH] i386: Document when features can be added to kvm_default_props Eduardo Habkost
2020-09-25 21:46 ` Paolo Bonzini [this message]
2020-09-26 0:25 ` no-reply
2021-04-28 18:52 ` Eduardo Habkost
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=70cf3a0b-ddb8-129a-201f-ec583c3883d1@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=vkuznets@redhat.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).