From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] x86/HVM: avoid memory_type_changed() invocations when possible
Date: Mon, 16 Jul 2018 18:08:00 +0100 [thread overview]
Message-ID: <d98d9f04-e22e-6104-3c21-8f90d8a58db2@citrix.com> (raw)
In-Reply-To: <5B4CCBB502000078001D4904@prv1-mh.provo.novell.com>
On 16/07/18 17:45, Jan Beulich wrote:
> They're expensive, and nothing changes if MTRRs are disabled and any of
> the ranges gets changed, or if fixed range MTRRs are disabled and any of
> them gets changed.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
There is still far more room improve here, but this is a start.
Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-07-16 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 16:45 [PATCH] x86/HVM: avoid memory_type_changed() invocations when possible Jan Beulich
2018-07-16 17:08 ` Andrew Cooper [this message]
2018-07-17 11:07 ` Roger Pau Monné
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=d98d9f04-e22e-6104-3c21-8f90d8a58db2@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.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 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).