On Wed, 20 Jun 2018 at 10:41, Michael S. Tsirkin wrote:
>
> On Wed, Jun 20, 2018 at 08:46:10AM +0800, Wanpeng Li wrote:
> > On Wed, 20 Jun 2018 at 08:07, Michael S. Tsirkin wrote:
> > >
> > > On Tue, Jun 19, 2018 at 05:07:46PM -0500, Eric Blake wrote:
> > > > On 06/19/2018 10:17 AM, Paolo Bonzini
On 20/06/2018 16:29, Michael S. Tsirkin wrote:
> On Wed, Jun 20, 2018 at 04:20:40PM +0200, Paolo Bonzini wrote:
>> On 19/06/2018 22:43, Michael S. Tsirkin wrote:
>>>
2) Maybe -hostresource?
>>>
>>> Is ability to cause high latency for other threads really a resource?
>>
>> The "resource" here
On Wed, Jun 20, 2018 at 04:20:40PM +0200, Paolo Bonzini wrote:
> On 19/06/2018 22:43, Michael S. Tsirkin wrote:
> >
> >> 2) Maybe -hostresource?
> >
> > Is ability to cause high latency for other threads really a resource?
>
> The "resource" here is host CPU time.
Right but then everything we do
On 19/06/2018 22:43, Michael S. Tsirkin wrote:
>
>> 2) Maybe -hostresource?
>
> Is ability to cause high latency for other threads really a resource?
The "resource" here is host CPU time. In general, a vCPU with
KVM_CPU_X86_DISABLE_EXITS will use more host CPU time and block
overcommitting, just
On Wed, Jun 20, 2018 at 08:46:10AM +0800, Wanpeng Li wrote:
> On Wed, 20 Jun 2018 at 08:07, Michael S. Tsirkin wrote:
> >
> > On Tue, Jun 19, 2018 at 05:07:46PM -0500, Eric Blake wrote:
> > > On 06/19/2018 10:17 AM, Paolo Bonzini wrote:
> > > > On 16/06/2018 00:29, Michael S. Tsirkin wrote:
> > >
On Wed, 20 Jun 2018 at 08:07, Michael S. Tsirkin wrote:
>
> On Tue, Jun 19, 2018 at 05:07:46PM -0500, Eric Blake wrote:
> > On 06/19/2018 10:17 AM, Paolo Bonzini wrote:
> > > On 16/06/2018 00:29, Michael S. Tsirkin wrote:
> > > > +static QemuOptsList qemu_dedicated_opts = {
> > > > +.name = "d
On Tue, Jun 19, 2018 at 05:07:46PM -0500, Eric Blake wrote:
> On 06/19/2018 10:17 AM, Paolo Bonzini wrote:
> > On 16/06/2018 00:29, Michael S. Tsirkin wrote:
> > > +static QemuOptsList qemu_dedicated_opts = {
> > > +.name = "dedicated",
> > > +.head = QTAILQ_HEAD_INITIALIZER(qemu_dedicated_
On 06/19/2018 10:17 AM, Paolo Bonzini wrote:
On 16/06/2018 00:29, Michael S. Tsirkin wrote:
+static QemuOptsList qemu_dedicated_opts = {
+.name = "dedicated",
+.head = QTAILQ_HEAD_INITIALIZER(qemu_dedicated_opts.head),
+.desc = {
+{
+.name = "mem-lock",
+
On Tue, Jun 19, 2018 at 05:17:45PM +0200, Paolo Bonzini wrote:
> On 16/06/2018 00:29, Michael S. Tsirkin wrote:
> >
> > +static QemuOptsList qemu_dedicated_opts = {
> > +.name = "dedicated",
> > +.head = QTAILQ_HEAD_INITIALIZER(qemu_dedicated_opts.head),
> > +.desc = {
> > +{
On 16/06/2018 00:29, Michael S. Tsirkin wrote:
>
> +static QemuOptsList qemu_dedicated_opts = {
> +.name = "dedicated",
> +.head = QTAILQ_HEAD_INITIALIZER(qemu_dedicated_opts.head),
> +.desc = {
> +{
> +.name = "mem-lock",
> +.type = QEMU_OPT_BOOL,
> +
With this flag, kvm allows guest to control host CPU power state. This
increases latency for other processes using same host CPU in an
unpredictable way, but if decreases idle entry/exit times for the
running VCPU, so it works best if you use a dedicated host cpu,
hence the name.
Follow-up patche
11 matches
Mail list logo
