qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kashyap Chamarthy <kchamart@redhat.com>
To: qemu-devel@nongnu.org
Cc: aarcange@redhat.com, dgilbert@redhat.com, rjones@redhat.com,
	stefanha@redhat.com, pbonzini@redhat.com, vkuznets@redhat.com
Subject: Re: [PATCH qemu-web] Add a blog post on "Micro-Optimizing KVM VM-Exits"
Date: Tue, 12 Nov 2019 10:42:38 +0100	[thread overview]
Message-ID: <20191112094238.GK7754@paraplu> (raw)
In-Reply-To: <20191108092247.16207-1-kchamart@redhat.com>

[Cc: Rich Jones, addressing his feedback on IRC, below.]

On Fri, Nov 08, 2019 at 10:22:47AM +0100, Kashyap Chamarthy wrote:
> This blog post summarizes the talk "Micro-Optimizing KVM VM-Exits"[1],
> given by Andrea Arcangeli at the recently concluded KVM Forum 2019.
> 
> [1] https://kvmforum2019.sched.com/event/Tmwr/micro-optimizing-kvm-vm-exits-andrea-arcangeli-red-hat-inc
> 
> Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
> ---

[...]

> +The microbechmark: CPUID in a one million loop
> +----------------------------------------------
> +
> +The synthetic microbenchmark (meaning, focus on measuring the
> +performance of a specific area of code) Andrea used was to run the CPUID
> +instruction one million times, without any GCC optimizations or caching.
> +This was done to test the latency of VM-Exits.

I can send a v2 (but will wait for any other feedback), or when applying
someone please replace the above paragraph with the following:

    "Andrea constructed a synthetic microbenchmark program (without any
    GCC optimizations or caching) which runs the CPUID instructions one
    million times in a loop.  This microbenchmark is meant to focus on
    measuring the performance of a specific area of the code -- in this
    case, to test the latency of VM-Exits."

(Rich, hope that reads better.  Thanks for the review.)

> +While stressing that the results of these microbenchmarks do not
> +represent real-world workloads, he had two goals in mind with it: (a)
> +explain how the software mitigation works; and (b) to justify to the
> +broader community the value of the software optimizations he's working
> +on in KVM.
> +
> +Andrea then reasoned through several interesting graphs that show how
> +CPU computation time gets impacted when you disable or enable the
> +various kernel-space mitigations for Spectre v2, L1TF, MDS, et al.

[...]

-- 
/kashyap



  reply	other threads:[~2019-11-12  9:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08  9:22 [PATCH qemu-web] Add a blog post on "Micro-Optimizing KVM VM-Exits" Kashyap Chamarthy
2019-11-12  9:42 ` Kashyap Chamarthy [this message]
2019-11-12 10:37 ` Stefan Hajnoczi
2019-11-15 12:08 ` Thomas Huth
2019-11-15 12:18   ` Paolo Bonzini
2019-11-15 12:25   ` Alex Bennée
2019-11-15 12:33   ` Daniel P. Berrangé
2019-11-15 12:37   ` Kashyap Chamarthy
2019-11-15 12:41     ` Paolo Bonzini
2019-11-15 15:19       ` Kashyap Chamarthy
2019-11-15 12:45 ` Laszlo Ersek
2019-11-15 15:27   ` Kashyap Chamarthy

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=20191112094238.GK7754@paraplu \
    --to=kchamart@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=vkuznets@redhat.com \
    /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).