From: "Andreas Färber" <afaerber@suse.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [patch 2/6] Use machine options to emulate -no-kvm-irqchip
Date: Thu, 04 Oct 2012 18:13:48 +0200 [thread overview]
Message-ID: <506DB5BC.3070901@suse.de> (raw)
In-Reply-To: <506DB38F.4010704@siemens.com>
Am 04.10.2012 18:04, schrieb Jan Kiszka:
> On 2012-10-04 17:36, Andreas Färber wrote:
>> Am 04.10.2012 16:30, schrieb Jan Kiszka:
>>> On 2012-10-04 16:21, Anthony Liguori wrote:
>>> - avoid adding them to the help or other user documentation
>>
>> That's dangerous - at some point someone will notice and propose a patch
>> documenting them and the reviewers may have forgotten by then why it was
>> not documented in the first place. Better clearly document them in help
>> output as "DEPRECATED, to be removed in future versions" or so.
>
> -M is marked as deprecated in the file that you would have to mess up.
If it's not within +/- 3 lines and goes through qemu-trivial then that
point is moot. Don't see how deprecation of -no-kvm-irqchip et al. is
related to -M being deprecated either way.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-10-04 16:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 10:52 [Qemu-devel] [patch 0/6] qemu-kvm compat Marcelo Tosatti
2012-10-03 10:52 ` [Qemu-devel] [patch 1/6] cirrus_vga: allow configurable vram size Marcelo Tosatti
2012-10-03 14:39 ` Anthony Liguori
2012-10-03 10:52 ` [Qemu-devel] [patch 2/6] Use machine options to emulate -no-kvm-irqchip Marcelo Tosatti
2012-10-03 14:40 ` Anthony Liguori
2012-10-03 15:03 ` Marcelo Tosatti
2012-10-03 15:46 ` Jan Kiszka
2012-10-03 15:49 ` Jan Kiszka
2012-10-03 17:16 ` Anthony Liguori
2012-10-03 17:24 ` Jan Kiszka
2012-10-03 18:14 ` Anthony Liguori
2012-10-03 18:26 ` Marcelo Tosatti
2012-10-04 9:28 ` Jan Kiszka
2012-10-04 14:21 ` Anthony Liguori
2012-10-04 14:30 ` Jan Kiszka
2012-10-04 15:36 ` Andreas Färber
2012-10-04 16:04 ` Jan Kiszka
2012-10-04 16:13 ` Andreas Färber [this message]
2012-10-04 16:40 ` Jan Kiszka
2012-10-04 17:16 ` Marcelo Tosatti
2012-10-04 17:14 ` Marcelo Tosatti
2012-10-04 17:46 ` Anthony Liguori
2012-10-03 18:54 ` Aurelien Jarno
2012-10-03 10:52 ` [Qemu-devel] [patch 3/6] Use machine options to emulate -no-kvm-pit Marcelo Tosatti
2012-10-03 14:40 ` Anthony Liguori
2012-10-03 10:52 ` [Qemu-devel] [patch 4/6] Use global properties to emulate -no-kvm-pit-reinjection Marcelo Tosatti
2012-10-03 14:41 ` Anthony Liguori
2012-10-03 10:53 ` [Qemu-devel] [patch 5/6] Emulate qemu-kvms drive parameter boot=on|off Marcelo Tosatti
2012-10-03 14:43 ` Anthony Liguori
2012-10-03 10:53 ` [Qemu-devel] [patch 6/6] Emulate qemu-kvms -tdf option Marcelo Tosatti
2012-10-03 14:44 ` Anthony Liguori
2012-10-03 14:45 ` [Qemu-devel] [patch 0/6] qemu-kvm compat Anthony Liguori
2012-10-03 15:05 ` Marcelo Tosatti
2012-10-03 15:34 ` Anthony Liguori
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=506DB5BC.3070901@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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).