All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Cc: Tim Deegan <tim@xen.org>, Keir Fraser <keir@xen.org>
Subject: Re: [PATCH] x86/HVM: extend LAPIC shortcuts around P2M lookups
Date: Fri, 01 Aug 2014 15:27:31 +0100	[thread overview]
Message-ID: <53DBBFF302000078000287BE@mail.emea.novell.com> (raw)
In-Reply-To: <53DBB5860200007800028738@mail.emea.novell.com>

>>> On 01.08.14 at 15:43, <JBeulich@suse.com> wrote:
> ... to all internally handled MMIO regions. It is in particular the
> HPET page that, e.g. on Windows Server 2012 R2, can get heavily
> accessed, and hence avoiding the unnecessary lookups is rather
> beneficial (in the reported case a 40+-vCPU guest would previously not
> have booted at all while with hvm_hap_nested_page_fault() shortcut
> alone it was able to boot up in 18 minutes [i.e. still room for
> improvement]).

Btw., while I expect the second shortcut to also help a little (I was
only able to functionality test it, as I don't have a big enough system
around to meaningfully test that big a guest), while going through
all the pCPU-s' stack trace snapshots it occurred to me that for
hvm_hap_nested_page_fault()-induced MMIO emulation it is in many
cases quite pointless to "manually" do the VA->GPA translation, since
the handler already gets passed the offending GPA. Of course some
care would need to be taken to e.g. not use this on instructions
having more than one memory operand, or where the memory
operand crosses page boundaries, but all the information needed
for this would be available after decoding the instruction, i.e. well
in time before evaluating instruction operands. Am I overlooking
any other aspect making such an optimization unsafe?

Jan

  reply	other threads:[~2014-08-01 14:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-01 13:43 [PATCH] x86/HVM: extend LAPIC shortcuts around P2M lookups Jan Beulich
2014-08-01 14:27 ` Jan Beulich [this message]
2014-08-01 19:15   ` Tim Deegan
2014-08-04  7:12     ` Jan Beulich
2014-08-05 19:53       ` Tim Deegan
2014-08-06  8:34         ` Jan Beulich
2014-08-06  9:38           ` Tim Deegan
2014-08-11 12:26             ` Jan Beulich
2014-08-01 19:03 ` Tim Deegan

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=53DBBFF302000078000287BE@mail.emea.novell.com \
    --to=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --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.