From: Avi Kivity <avi@redhat.com>
To: dlaor@redhat.com
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
kvm-devel <kvm@vger.kernel.org>
Subject: Re: Better qemu/kvm defaults (was Re: [RFC PATCH 0/4] Gang scheduling in CFS)
Date: Thu, 29 Dec 2011 18:13:20 +0200 [thread overview]
Message-ID: <4EFC91A0.6050100@redhat.com> (raw)
In-Reply-To: <4EFC903C.3030509@redhat.com>
On 12/29/2011 06:07 PM, Dor Laor wrote:
> On 12/26/2011 11:05 AM, Avi Kivity wrote:
>> On 12/26/2011 05:14 AM, Nikunj A Dadhania wrote:
>>>>
>>>> btw you can get an additional speedup by enabling x2apic, for
>>>> default_send_IPI_mask_logical().
>>>>
>>> In the host?
>>>
>>
>> In the host, for the guest:
>>
>> qemu -cpu ...,+x2apic
>>
>
> It seems to me that we should improve our default flags.
> So many times users fail to submit the proper huge command-line
> options that we require. Honestly, we can't blame them, there are so
> many flags and so many use cases its just too hard to get it right for
> humans.
>
> I propose a basic idea and folks are welcome to discuss it:
>
> 1. Improve qemu/kvm defaults
> Break the current backward compatibility (but add a --default-
> backward-compat-mode)
This exists, -M pc-1.0.
> and set better values for:
> - rtc slew time
> - cache=none
> - x2apic, maybe enhance qemu64 or move to -cpu host?
We tried this for 1.0, but it caused regressions. Need to try again for
1.1.
> - aio=native|threads (auto-sense?)
> - use virtio devices by default
Can't install non-Linux guests.
> - more?
>
> Different defaults may be picked automatically when TCG|KVM used.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: dlaor@redhat.com
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Better qemu/kvm defaults (was Re: [RFC PATCH 0/4] Gang scheduling in CFS)
Date: Thu, 29 Dec 2011 18:13:20 +0200 [thread overview]
Message-ID: <4EFC91A0.6050100@redhat.com> (raw)
In-Reply-To: <4EFC903C.3030509@redhat.com>
On 12/29/2011 06:07 PM, Dor Laor wrote:
> On 12/26/2011 11:05 AM, Avi Kivity wrote:
>> On 12/26/2011 05:14 AM, Nikunj A Dadhania wrote:
>>>>
>>>> btw you can get an additional speedup by enabling x2apic, for
>>>> default_send_IPI_mask_logical().
>>>>
>>> In the host?
>>>
>>
>> In the host, for the guest:
>>
>> qemu -cpu ...,+x2apic
>>
>
> It seems to me that we should improve our default flags.
> So many times users fail to submit the proper huge command-line
> options that we require. Honestly, we can't blame them, there are so
> many flags and so many use cases its just too hard to get it right for
> humans.
>
> I propose a basic idea and folks are welcome to discuss it:
>
> 1. Improve qemu/kvm defaults
> Break the current backward compatibility (but add a --default-
> backward-compat-mode)
This exists, -M pc-1.0.
> and set better values for:
> - rtc slew time
> - cache=none
> - x2apic, maybe enhance qemu64 or move to -cpu host?
We tried this for 1.0, but it caused regressions. Need to try again for
1.1.
> - aio=native|threads (auto-sense?)
> - use virtio devices by default
Can't install non-Linux guests.
> - more?
>
> Different defaults may be picked automatically when TCG|KVM used.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-12-29 16:13 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 8:33 [RFC PATCH 0/4] Gang scheduling in CFS Nikunj A. Dadhania
2011-12-19 8:34 ` [RFC PATCH 1/4] sched: Adding cpu.gang file to cpu cgroup Nikunj A. Dadhania
2011-12-19 8:34 ` [RFC PATCH 2/4] sched: Adding gang scheduling infrastrucure Nikunj A. Dadhania
2011-12-19 15:51 ` Peter Zijlstra
2011-12-19 16:51 ` Peter Zijlstra
2011-12-20 1:43 ` Nikunj A Dadhania
2011-12-20 1:39 ` Nikunj A Dadhania
2011-12-19 8:34 ` [RFC PATCH 3/4] sched: Gang using set_next_buddy Nikunj A. Dadhania
2011-12-19 8:35 ` [RFC PATCH 4/4] sched:Implement set_gang_buddy Nikunj A. Dadhania
2011-12-19 15:51 ` Peter Zijlstra
2011-12-20 1:43 ` Nikunj A Dadhania
2011-12-26 2:30 ` Nikunj A Dadhania
2011-12-19 11:23 ` [RFC PATCH 0/4] Gang scheduling in CFS Ingo Molnar
2011-12-19 11:44 ` Avi Kivity
2011-12-19 11:50 ` Nikunj A Dadhania
2011-12-19 11:59 ` Avi Kivity
2011-12-19 12:06 ` Nikunj A Dadhania
2011-12-19 12:50 ` Avi Kivity
2011-12-19 13:09 ` Nikunj A Dadhania
2011-12-19 11:45 ` Nikunj A Dadhania
2011-12-19 13:22 ` Nikunj A Dadhania
2011-12-19 16:28 ` Ingo Molnar
2011-12-21 10:39 ` Nikunj A Dadhania
2011-12-21 10:43 ` Avi Kivity
2011-12-23 3:20 ` Nikunj A Dadhania
2011-12-23 10:36 ` Ingo Molnar
2011-12-25 10:58 ` Avi Kivity
2011-12-25 15:45 ` Avi Kivity
2011-12-26 3:14 ` Nikunj A Dadhania
2011-12-26 9:05 ` Avi Kivity
2011-12-26 11:33 ` Nikunj A Dadhania
2011-12-26 11:41 ` Avi Kivity
2011-12-27 1:47 ` Nikunj A Dadhania
2011-12-27 9:15 ` Avi Kivity
2011-12-27 10:24 ` Nikunj A Dadhania
2011-12-29 16:07 ` Better qemu/kvm defaults (was Re: [RFC PATCH 0/4] Gang scheduling in CFS) Dor Laor
2011-12-29 16:07 ` [Qemu-devel] " Dor Laor
2011-12-29 16:13 ` Avi Kivity [this message]
2011-12-29 16:13 ` Avi Kivity
2011-12-29 16:16 ` Anthony Liguori
2011-12-29 16:16 ` Anthony Liguori
2012-01-01 10:16 ` Dor Laor
2012-01-01 10:16 ` [Qemu-devel] " Dor Laor
2012-01-01 14:01 ` Ronen Hod
2012-01-01 14:01 ` Ronen Hod
2012-01-02 9:37 ` Dor Laor
2012-01-02 9:37 ` [Qemu-devel] " Dor Laor
2012-01-03 15:48 ` Anthony Liguori
2012-01-03 15:48 ` Anthony Liguori
2012-01-03 22:31 ` Dor Laor
2012-01-03 22:31 ` Dor Laor
2012-01-03 22:45 ` Anthony Liguori
2012-01-03 22:45 ` [Qemu-devel] " Anthony Liguori
2012-01-03 22:59 ` Dor Laor
2012-01-03 22:59 ` Dor Laor
2011-12-27 3:15 ` [RFC PATCH 0/4] Gang scheduling in CFS Nikunj A Dadhania
2011-12-27 9:17 ` Avi Kivity
2011-12-27 9:44 ` Nikunj A Dadhania
2011-12-27 9:51 ` Avi Kivity
2011-12-27 10:10 ` Nikunj A Dadhania
2011-12-27 10:34 ` Avi Kivity
2011-12-27 10:43 ` Nikunj A Dadhania
2011-12-27 10:53 ` Avi Kivity
2011-12-30 9:51 ` Ingo Molnar
2011-12-30 10:10 ` Nikunj A Dadhania
2011-12-31 2:21 ` Nikunj A Dadhania
2012-01-02 4:20 ` Nikunj A Dadhania
2012-01-02 9:39 ` Avi Kivity
2012-01-02 10:22 ` Nikunj A Dadhania
2012-01-02 9:37 ` Avi Kivity
2012-01-02 10:30 ` Nikunj A Dadhania
2012-01-02 13:33 ` Avi Kivity
2012-01-04 10:52 ` Nikunj A Dadhania
2012-01-04 14:41 ` Avi Kivity
2012-01-04 14:56 ` Srivatsa Vaddagiri
2012-01-04 17:13 ` Avi Kivity
2012-01-05 6:57 ` Nikunj A Dadhania
2012-01-04 16:47 ` Rik van Riel
2012-01-04 17:16 ` Avi Kivity
2012-01-04 20:56 ` Rik van Riel
2012-01-04 21:31 ` Peter Zijlstra
2012-01-04 21:41 ` Avi Kivity
2012-01-05 9:10 ` Ingo Molnar
2012-02-20 8:08 ` Nikunj A Dadhania
2012-02-20 8:14 ` Ingo Molnar
2012-02-20 10:51 ` Peter Zijlstra
2012-02-20 11:53 ` Nikunj A Dadhania
2012-02-20 12:02 ` Srivatsa Vaddagiri
2012-02-20 12:14 ` Peter Zijlstra
2012-01-05 2:10 ` Nikunj A Dadhania
2011-12-19 15:51 ` Peter Zijlstra
2011-12-19 16:09 ` Alan Cox
2011-12-19 22:10 ` Benjamin Herrenschmidt
2011-12-20 1:56 ` Nikunj A Dadhania
2011-12-20 8:52 ` Jeremy Fitzhardinge
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=4EFC91A0.6050100@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=dlaor@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=nikunj@linux.vnet.ibm.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 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.