All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Jan Beulich <JBeulich@suse.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: anthony.perard@citrix.com, xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: gross qemu behavior
Date: Fri, 04 Apr 2014 11:34:20 +0200	[thread overview]
Message-ID: <533E7C9C.7000709@redhat.com> (raw)
In-Reply-To: <533E712D02000078000057CE@nat28.tlf.novell.com>

Il 04/04/2014 08:45, Jan Beulich ha scritto:
> Implying that any execution of code in the ROM would be fully
> emulated.

ROM is never executed in place.  It is always copied to low RAM and 
executed from there.  It might slow down the copy.

In fact, on AMD it is not always possible to execute from ROM; if the 
ROM includes page tables, as was the case for example for 64-bit OVMF, 
it crashes because NPT expects page tables to be in writable guest memory.

> Very odd, but fitting the picture of trying to be as slow
> as possible (in the context of the breakage introduced by
> ef437690 "x86/HVM: correct CPUID leaf 80000008 handling" I
> had to run qemu-traditional and qemu-upstream, and the
> performance of the guest visibly _much_ better with the former,
> which I consider rather worrying).

That's quite unexpected.  What was your configuration and workload?  And 
what was slower exactly?  Disk, network or video (as an initial 
simplification).

Paolo

  reply	other threads:[~2014-04-04  9:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28  7:48 gross qemu behavior Jan Beulich
2014-03-28  9:21 ` Jan Beulich
2014-03-28  9:30 ` Fabio Fantoni
2014-03-28 10:37   ` Jan Beulich
2014-03-28 17:46 ` Stefano Stabellini
2014-03-28 17:52   ` Stefano Stabellini
2014-03-28 18:01     ` Paolo Bonzini
2014-03-28 18:30       ` Stefano Stabellini
2014-03-29  7:31         ` Paolo Bonzini
2014-03-30  7:57           ` Fabio Fantoni
2014-03-31  9:07   ` Jan Beulich
2014-04-03 16:12     ` Stefano Stabellini
2014-04-04  6:45       ` Jan Beulich
2014-04-04  9:34         ` Paolo Bonzini [this message]
2014-04-04  9:45           ` Jan Beulich
2014-04-04 13:53         ` Stefano Stabellini
2014-04-04 14:58           ` Jan Beulich
2014-04-04 15:32             ` Stefano Stabellini
2014-04-04 16:00               ` Jan Beulich
2014-04-04 16:54                 ` Stefano Stabellini
2014-05-05 10:04                   ` Fabio Fantoni
2014-05-05 10:35                     ` Jan Beulich
2014-05-05 11:10                       ` Fabio Fantoni

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=533E7C9C.7000709@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=JBeulich@suse.com \
    --cc=anthony.perard@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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.