From: Stefan Hajnoczi <stefanha@gmail.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-trivial@nongnu.org, Jan Kiszka <jan.kiszka@siemens.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
Bruce Rogers <brogers@suse.com>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] Legacy qemu-kvm options have no argument
Date: Fri, 23 Nov 2012 07:50:49 +0100 [thread overview]
Message-ID: <20121123065049.GB22787@stefanha-thinkpad.hitronhub.home> (raw)
In-Reply-To: <20121122103411.0eefef6a@doriath.home>
On Thu, Nov 22, 2012 at 10:34:11AM -0200, Luiz Capitulino wrote:
> On Wed, 21 Nov 2012 13:12:53 +0100
> Jan Kiszka <jan.kiszka@siemens.com> wrote:
>
> > On 2012-11-20 16:14, Markus Armbruster wrote:
> > > Cc'ing Marcelo & Jan to speed up patch application.
> > >
> > > Bruce Rogers <brogers@suse.com> writes:
> > >
> > >> The options no-kvm, no-kvm-pit, no-kvm-pit-reinjection, and no-kvm-irqchip
> > >> should be marked as having no argument.
> > >>
> > >> Signed-off-by: Bruce Rogers <brogers@suse.com>
> > >> ---
> > >> qemu-options.hx | 8 ++++----
> > >> 1 files changed, 4 insertions(+), 4 deletions(-)
> > >>
> > >> diff --git a/qemu-options.hx b/qemu-options.hx
> > >> index 9bb29d3..fbcf079 100644
> > >> --- a/qemu-options.hx
> > >> +++ b/qemu-options.hx
> > >> @@ -2918,17 +2918,17 @@ Enable FIPS 140-2 compliance mode.
> > >> ETEXI
> > >>
> > >> HXCOMM Deprecated by -machine accel=tcg property
> > >> -DEF("no-kvm", HAS_ARG, QEMU_OPTION_no_kvm, "", QEMU_ARCH_I386)
> > >> +DEF("no-kvm", 0, QEMU_OPTION_no_kvm, "", QEMU_ARCH_I386)
> > >>
> > >> HXCOMM Deprecated by kvm-pit driver properties
> > >> -DEF("no-kvm-pit-reinjection", HAS_ARG, QEMU_OPTION_no_kvm_pit_reinjection,
> > >> +DEF("no-kvm-pit-reinjection", 0, QEMU_OPTION_no_kvm_pit_reinjection,
> > >> "", QEMU_ARCH_I386)
> > >>
> > >> HXCOMM Deprecated (ignored)
> > >> -DEF("no-kvm-pit", HAS_ARG, QEMU_OPTION_no_kvm_pit, "", QEMU_ARCH_I386)
> > >> +DEF("no-kvm-pit", 0, QEMU_OPTION_no_kvm_pit, "", QEMU_ARCH_I386)
> > >>
> > >> HXCOMM Deprecated by -machine kernel_irqchip=on|off property
> > >> -DEF("no-kvm-irqchip", HAS_ARG, QEMU_OPTION_no_kvm_irqchip, "", QEMU_ARCH_I386)
> > >> +DEF("no-kvm-irqchip", 0, QEMU_OPTION_no_kvm_irqchip, "", QEMU_ARCH_I386)
> > >>
> > >> HXCOMM Deprecated (ignored)
> > >> DEF("tdf", 0, QEMU_OPTION_tdf,"", QEMU_ARCH_ALL)
> >
> > Reviewed-by: Jan Kiszka <jan.kiszka@siemens.com>
>
> Candidate for -trivial.
This is more urgent than trivial. It is necessary for qemu-kvm
compatibility and I think should go into QEMU 1.3. Otherwise we have to
wait until QEMU 1.4 to complete the qemu-kvm -> qemu transition.
Stefan
next prev parent reply other threads:[~2012-11-23 6:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 14:11 [Qemu-devel] [PATCH] Legacy qemu-kvm options have no argument Bruce Rogers
2012-11-20 15:14 ` Markus Armbruster
2012-11-21 12:12 ` Jan Kiszka
2012-11-22 12:34 ` Luiz Capitulino
2012-11-23 6:50 ` Stefan Hajnoczi [this message]
2012-11-23 11:48 ` [Qemu-devel] [Qemu-trivial] " Luiz Capitulino
2012-11-23 6:49 ` [Qemu-devel] [PATCH 1.3] " Stefan Hajnoczi
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=20121123065049.GB22787@stefanha-thinkpad.hitronhub.home \
--to=stefanha@gmail.com \
--cc=armbru@redhat.com \
--cc=brogers@suse.com \
--cc=jan.kiszka@siemens.com \
--cc=lcapitulino@redhat.com \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).