From: Marcelo Tosatti <mtosatti@redhat.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Wanpeng Li <kernellwp@gmail.com>, kvm-devel <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Bandan Das <bsd@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] sched: introduce configurable delay before entering idle
Date: Tue, 14 May 2019 14:42:37 -0300 [thread overview]
Message-ID: <20190514174235.GA12269@amt.cnet> (raw)
In-Reply-To: <20190514152015.GM20906@char.us.oracle.com>
On Tue, May 14, 2019 at 11:20:15AM -0400, Konrad Rzeszutek Wilk wrote:
> On Tue, May 14, 2019 at 10:50:23AM -0300, Marcelo Tosatti wrote:
> > On Mon, May 13, 2019 at 05:20:37PM +0800, Wanpeng Li wrote:
> > > On Wed, 8 May 2019 at 02:57, Marcelo Tosatti <mtosatti@redhat.com> wrote:
> > > >
> > > >
> > > > Certain workloads perform poorly on KVM compared to baremetal
> > > > due to baremetal's ability to perform mwait on NEED_RESCHED
> > > > bit of task flags (therefore skipping the IPI).
> > >
> > > KVM supports expose mwait to the guest, if it can solve this?
> > >
> > > Regards,
> > > Wanpeng Li
> >
> > Unfortunately mwait in guest is not feasible (uncompatible with multiple
> > guests). Checking whether a paravirt solution is possible.
>
> There is the obvious problem with that the guest can be malicious and
> provide via the paravirt solution bogus data. That is it expose 0% CPU
> usage but in reality be mining and using 100%.
The idea is to have a hypercall for the guest to perform the
need_resched=1 bit set. It can only hurt itself.
next prev parent reply other threads:[~2019-05-14 18:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 18:56 [PATCH] sched: introduce configurable delay before entering idle Marcelo Tosatti
2019-05-07 22:15 ` Peter Zijlstra
2019-05-07 23:44 ` Marcelo Tosatti
2019-05-13 9:20 ` Wanpeng Li
2019-05-13 11:31 ` Konrad Rzeszutek Wilk
2019-05-13 11:51 ` Raslan, KarimAllah
2019-05-13 12:30 ` Boris Ostrovsky
2019-05-15 1:45 ` Wanpeng Li
2019-05-14 13:50 ` Marcelo Tosatti
2019-05-14 15:20 ` Konrad Rzeszutek Wilk
2019-05-14 17:42 ` Marcelo Tosatti [this message]
2019-05-15 1:42 ` Wanpeng Li
2019-05-15 20:26 ` Marcelo Tosatti
2019-05-15 18:42 ` Ankur Arora
2019-05-15 20:43 ` Marcelo Tosatti
2019-05-17 4:32 ` Ankur Arora
2019-05-17 17:49 ` Marcelo Tosatti
2019-05-16 1:07 ` Wanpeng Li
2019-05-17 2:06 ` Ankur Arora
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=20190514174235.GA12269@amt.cnet \
--to=mtosatti@redhat.com \
--cc=aarcange@redhat.com \
--cc=bsd@redhat.com \
--cc=kernellwp@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
/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