qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.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 11:28:17 +0200	[thread overview]
Message-ID: <506D56B1.8090804@web.de> (raw)
In-Reply-To: <20121003182652.GA32381@amt.cnet>

[-- Attachment #1: Type: text/plain, Size: 2604 bytes --]

On 2012-10-03 20:26, Marcelo Tosatti wrote:
> On Wed, Oct 03, 2012 at 07:24:48PM +0200, Jan Kiszka wrote:
>> On 2012-10-03 19:16, Anthony Liguori wrote:
>>> Jan Kiszka <jan.kiszka@web.de> writes:
>>>
>>>> On 2012-10-03 17:03, Marcelo Tosatti wrote:
>>>>> On Wed, Oct 03, 2012 at 09:40:17AM -0500, Anthony Liguori wrote:
>>>>>> Marcelo Tosatti <mtosatti@redhat.com> writes:
>>>>>>
>>>>>>> Commit 3ad763fcba5bd0ec5a79d4a9b6baeef119dd4a3d from qemu-kvm.git.
>>>>>>>
>>>>>>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>>>>>>     
>>>>>>> Upstream is moving towards this mechanism, so start using it in qemu-kvm
>>>>>>> already to configure the specific defaults: kvm enabled on, just like
>>>>>>> in-kernel irqchips.
>>>>>>>
>>>>>>> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
>>>>>>
>>>>>>
>>>>>> Reviewed-by: Anthony Liguori <aliguori@us.ibm.com>
>>>>>>
>>>>>> Although it's a little odd to have From: Jan without a SoB...
>>>>>
>>>>> Agree, Jan can you ACK?
>>>>
>>>> I wasn't able to join the call yesterday: Is there a removal schedule
>>>> associated with those switches? Also, why pushing things upstream, even
>>>> when only for one release, that have been loudly deprecated for a while
>>>> in qemu-kvm? Some switches are lacking deprecated warnings on the
>>>> console, and -no-kvm is missing completely. I tend to focus on patch 1 &
>>>> 5, dropping the rest - based on relevance for production use.
>>>
>>> The distros need to keep these flags to do the switch.
>>
>> Why? Should be documented in commit log.
>>
>>>  I see no point
>>> in deprecating them since they're trivially easy to maintain.
>>
>> Given the level of cr** we already have in the command line, they are
>> kind of noise, yes. But even then, these patches are not consistent as
>> pointed out above.
>>
>> Also, they should not be documented to avoid being spread. That's what
>> we did with other deprecated switches in QEMU.
>>
>> Jan
> 
> Jan,
> 
> You're comments to the patch are:
> 
> - No documentation.

See e.g. how -M is handled in qemu-options.hx.

> - Expiration date.

Anthony said "forever", but I think we should remove all those that
issue deprecation warnings after 1-2 years.

> - Changelog explaining what?? (didnt get that). Perhaps better changelog
>   in general?

I'm still failing to understand who could depend on -no-kvm-irqchip or
-no-kvm-pit. And I don't understand why -no-kvm was not included. Soe
the reasons for include -X should be provided. Also check your patch
subjects again, at least one was wrong.

Jan



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  reply	other threads:[~2012-10-04  9:29 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 [this message]
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
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=506D56B1.8090804@web.de \
    --to=jan.kiszka@web.de \
    --cc=aliguori@us.ibm.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).