From: Jan Kiszka <jan.kiszka@web.de>
To: Vadim Rozenfeld <vrozenfe@redhat.com>
Cc: kvm@vger.kernel.org, Avi Kivity <avi@redhat.com>
Subject: Re: [RFC PATCH 1/7] [hyper-v] Add hyper-v parameters block.
Date: Mon, 10 Oct 2011 08:54:04 +0200 [thread overview]
Message-ID: <4E92968C.2000306@web.de> (raw)
In-Reply-To: <1318186375-27672-2-git-send-email-vrozenfe@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
On 2011-10-09 20:52, Vadim Rozenfeld wrote:
> ---
> qemu-options.hx | 23 +++++++++++++++++++++++
> vl.c | 2 ++
> 2 files changed, 25 insertions(+), 0 deletions(-)
>
> diff --git a/qemu-options.hx b/qemu-options.hx
> index 3a13533..9f60059 100644
> --- a/qemu-options.hx
> +++ b/qemu-options.hx
> @@ -2483,6 +2483,29 @@ DEF("kvm-shadow-memory", HAS_ARG, QEMU_OPTION_kvm_shadow_memory,
> " allocate MEGABYTES for kvm mmu shadowing\n",
> QEMU_ARCH_I386)
>
> +DEF("hyperv", HAS_ARG, QEMU_OPTION_hyperv,
> + "-hyperv [vapic=on|off][,spinlock=retries][,wd=on|off]\n"
> + " enable Hyper-V Enlightenment\n",
> + QEMU_ARCH_ALL)
These are CPU feature, so -cpu +/-hv_vapic,+/-hv_spinlock etc. looks
more appropriate than a new command line parameter.
BTW, documentation and maybe also option processing should make clear
that this is limited to KVM mode for now.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-10-10 6:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 18:52 [RFC PATCH 0/7] Initial support for Microsoft Hyper-V Vadim Rozenfeld
2011-10-09 18:52 ` [RFC PATCH 1/7] [hyper-v] Add hyper-v parameters block Vadim Rozenfeld
2011-10-10 6:54 ` Jan Kiszka [this message]
2011-10-10 9:40 ` Vadim Rozenfeld
2011-10-10 10:25 ` Jan Kiszka
2011-10-11 7:35 ` Paolo Bonzini
2011-10-11 7:42 ` Paolo Bonzini
2011-10-09 18:52 ` [RFC PATCH 2/7] [hyper-v] add hyper-v placeholders Vadim Rozenfeld
2011-10-11 7:40 ` Paolo Bonzini
2011-10-09 18:52 ` [RFC PATCH 3/7] [hyper-v] make Hyper-V option configurable Vadim Rozenfeld
2011-10-10 6:54 ` Jan Kiszka
2011-10-09 18:52 ` [RFC PATCH 4/7] [hyper-v] hyper-v parameters Vadim Rozenfeld
2011-10-09 18:52 ` [RFC PATCH 5/7] [hyper-v] hyper-v helper functions Vadim Rozenfeld
2011-10-09 19:01 ` Alon Levy
2011-10-10 6:45 ` Vadim Rozenfeld
2011-10-09 18:52 ` [RFC PATCH 6/7] [hyper-v] parse hyper-v parameters Vadim Rozenfeld
2011-10-09 18:52 ` [RFC PATCH 7/7] [hyper-v] init hyper-v cpuid leafs Vadim Rozenfeld
2011-10-11 7:38 ` Paolo Bonzini
2011-10-11 13:46 ` Vadim Rozenfeld
2011-10-11 15:52 ` Paolo Bonzini
2011-10-11 16:09 ` Vadim Rozenfeld
2011-10-11 16:17 ` Paolo Bonzini
2011-10-10 6:53 ` [RFC PATCH 0/7] Initial support for Microsoft Hyper-V Jan Kiszka
2011-10-10 9:39 ` Vadim Rozenfeld
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=4E92968C.2000306@web.de \
--to=jan.kiszka@web.de \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=vrozenfe@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