All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kashyap Chamarthy <kchamart@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
	kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
	huth@tuxfamily.org, Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH v2 0/2] kvm: x86 CPU power management
Date: Fri, 22 Jun 2018 15:06:59 +0200	[thread overview]
Message-ID: <20180622130659.GA11827@paraplu> (raw)
In-Reply-To: <20180614081800.GH6355@redhat.com>

(Cc: Thomas Huth)

On Thu, Jun 14, 2018 at 09:18:00AM +0100, Daniel P. Berrangé wrote:

[...]

> IMHO this really shouldn't be under the -realtime flag. I don't think
> the -realtime flag should ever have been introduced, and we certainly
> shouldn't add more stuff under it.
> 
> "-realtime" is referring to a very specific use case, while the
> properties listed under it are all general purpose features. Real
> time guests just happen to be one possible use case, but it is
> valid to use them for non-real time guests.

Given what you say above, then it sounds like the "-realtime" QEMU
option should be deprecated, and removed in a future release.

[...]


-- 
/kashyap

WARNING: multiple messages have this Message-ID (diff)
From: Kashyap Chamarthy <kchamart@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	kvm@vger.kernel.org, Richard Henderson <rth@twiddle.net>,
	huth@tuxfamily.org
Subject: Re: [Qemu-devel] [PATCH v2 0/2] kvm: x86 CPU power management
Date: Fri, 22 Jun 2018 15:06:59 +0200	[thread overview]
Message-ID: <20180622130659.GA11827@paraplu> (raw)
In-Reply-To: <20180614081800.GH6355@redhat.com>

(Cc: Thomas Huth)

On Thu, Jun 14, 2018 at 09:18:00AM +0100, Daniel P. Berrangé wrote:

[...]

> IMHO this really shouldn't be under the -realtime flag. I don't think
> the -realtime flag should ever have been introduced, and we certainly
> shouldn't add more stuff under it.
> 
> "-realtime" is referring to a very specific use case, while the
> properties listed under it are all general purpose features. Real
> time guests just happen to be one possible use case, but it is
> valid to use them for non-real time guests.

Given what you say above, then it sounds like the "-realtime" QEMU
option should be deprecated, and removed in a future release.

[...]


-- 
/kashyap

  parent reply	other threads:[~2018-06-22 13:06 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12 18:47 [PATCH v2 0/2] kvm: x86 CPU power management Michael S. Tsirkin
2018-06-12 18:47 ` [Qemu-devel] " Michael S. Tsirkin
2018-06-12 18:47 ` [PATCH v2 1/2] kvm: support -realtime cpu-pm=on|off Michael S. Tsirkin
2018-06-12 18:47   ` [Qemu-devel] " Michael S. Tsirkin
2018-06-13 20:35   ` Eduardo Habkost
2018-06-13 20:35     ` [Qemu-devel] " Eduardo Habkost
2018-06-13 21:00   ` Eduardo Habkost
2018-06-13 21:00     ` [Qemu-devel] " Eduardo Habkost
2018-06-13 21:53     ` Michael S. Tsirkin
2018-06-13 21:53       ` [Qemu-devel] " Michael S. Tsirkin
2018-06-12 18:47 ` [PATCH v2 2/2] i386/cpu: make -cpu host support monitor/mwait Michael S. Tsirkin
2018-06-12 18:47   ` [Qemu-devel] " Michael S. Tsirkin
2018-06-13 21:24   ` Eduardo Habkost
2018-06-13 21:24     ` [Qemu-devel] " Eduardo Habkost
2018-06-12 19:18 ` [PATCH v2 0/2] kvm: x86 CPU power management no-reply
2018-06-12 19:18   ` [Qemu-devel] " no-reply
2018-06-12 20:29   ` Michael S. Tsirkin
2018-06-12 20:29     ` [Qemu-devel] " Michael S. Tsirkin
2018-06-13 22:34 ` Marcelo Tosatti
2018-06-13 22:34   ` [Qemu-devel] " Marcelo Tosatti
2018-06-13 23:37   ` Michael S. Tsirkin
2018-06-13 23:37     ` [Qemu-devel] " Michael S. Tsirkin
2018-06-15 18:32     ` Marcelo Tosatti
2018-06-15 18:32       ` [Qemu-devel] " Marcelo Tosatti
2018-06-15 21:53       ` Michael S. Tsirkin
2018-06-15 21:53         ` [Qemu-devel] " Michael S. Tsirkin
2018-06-14  8:18 ` Daniel P. Berrangé
2018-06-14  8:18   ` [Qemu-devel] " Daniel P. Berrangé
2018-06-14 15:40   ` Paolo Bonzini
2018-06-14 15:40     ` [Qemu-devel] " Paolo Bonzini
2018-06-14 15:44     ` Daniel P. Berrangé
2018-06-14 15:44       ` [Qemu-devel] " Daniel P. Berrangé
2018-06-14 20:32       ` Paolo Bonzini
2018-06-14 20:32         ` [Qemu-devel] " Paolo Bonzini
2018-06-15 14:15         ` Michael S. Tsirkin
2018-06-15 14:15           ` [Qemu-devel] " Michael S. Tsirkin
2018-06-14 16:53     ` Eduardo Habkost
2018-06-14 16:53       ` [Qemu-devel] " Eduardo Habkost
2018-06-14 21:21       ` Paolo Bonzini
2018-06-14 21:21         ` [Qemu-devel] " Paolo Bonzini
2018-06-15 13:52     ` Michael S. Tsirkin
2018-06-15 13:52       ` [Qemu-devel] " Michael S. Tsirkin
2018-06-22 13:06   ` Kashyap Chamarthy [this message]
2018-06-22 13:06     ` Kashyap Chamarthy
2018-06-22 19:18     ` Michael S. Tsirkin
2018-06-22 19:18       ` [Qemu-devel] " Michael S. Tsirkin

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=20180622130659.GA11827@paraplu \
    --to=kchamart@redhat.com \
    --cc=berrange@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=huth@tuxfamily.org \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.