From: Anthony PERARD <anthony.perard@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: xen-devel@lists.xen.org
Subject: Re: OVMF very slow on AMD
Date: Wed, 27 Jul 2016 12:35:39 +0100 [thread overview]
Message-ID: <20160727113539.GO1835@perard.uk.xensource.com> (raw)
In-Reply-To: <20160727110804.GN1835@perard.uk.xensource.com>
On Wed, Jul 27, 2016 at 12:08:04PM +0100, Anthony PERARD wrote:
> I can try to describe how OVMF is setting up the memory.
From the start of the day:
setup gdt
cr0 = 0x40000023
jump to 32bit
cr4 = 0x640
setup page tables:
page directory attributes: (PAGE_ACCESSED + PAGE_READ_WRITE + PAGE_PRESENT)
page tables attributes: (PAGE_2M_MBO + PAGE_ACCESSED + PAGE_DIRTY + PAGE_READ_WRITE + PAGE_PRESENT)
I think they map the all 4GB with 2MB pages.
set cr3.
enable PAE
set LME
set PG
jump to 64bit
I think that's it, before running this painfully slow decompression
function.
Is there something wrong, or maybe missing? Is the hypervisor or maybe
the hardware does not do the right thing?
Thanks,
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-27 11:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 15:53 OVMF very slow on AMD Anthony PERARD
2016-07-15 13:48 ` Konrad Rzeszutek Wilk
2016-07-15 15:22 ` Boris Ostrovsky
2016-07-27 11:08 ` Anthony PERARD
2016-07-27 11:35 ` Anthony PERARD [this message]
2016-07-27 19:45 ` Boris Ostrovsky
2016-07-28 10:18 ` Anthony PERARD
2016-07-28 10:43 ` George Dunlap
2016-07-28 10:54 ` Andrew Cooper
2016-07-28 11:28 ` Anthony PERARD
2016-07-28 15:17 ` Boris Ostrovsky
2016-07-28 15:51 ` Andrew Cooper
2016-07-28 19:25 ` Boris Ostrovsky
2016-07-28 19:44 ` Andrew Cooper
2016-07-28 19:54 ` Boris Ostrovsky
2016-07-29 15:54 ` Anthony PERARD
2016-07-18 14:10 ` Anthony PERARD
2016-07-18 15:09 ` Anthony PERARD
2016-07-22 10:40 ` Dario Faggioli
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=20160727113539.GO1835@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=xen-devel@lists.xen.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 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).