From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Paul Durrant <paul@xen.org>, Paul Durrant <pdurrant@amazon.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Laurent Vivier <laurent@vivier.eu>,
"open list:X86" <xen-devel@lists.xenproject.org>,
Anthony Perard <anthony.perard@citrix.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] configure: define CONFIG_XEN when Xen is enabled
Date: Tue, 28 Jul 2020 11:56:03 +0200 [thread overview]
Message-ID: <a09853d3-5c27-893f-54ed-63dc461bfacb@redhat.com> (raw)
In-Reply-To: <CAFEAcA84fH3aGpbrJoA6S3qJ-FjD3NZMoj0G7jqvRneH_pS6=A@mail.gmail.com>
On 7/28/20 11:53 AM, Peter Maydell wrote:
> On Tue, 28 Jul 2020 at 10:51, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>> I'd rather uninline xen_enabled() but I'm not sure this has perf
>> penalties. Paolo is that OK to uninline it?
I suppose no because it is in various hot paths:
exec.c:588: if (xen_enabled() && memory_access_is_direct(mr, is_write)) {
exec.c:2243: if (xen_enabled()) {
exec.c:2326: if (xen_enabled()) {
exec.c:2478: } else if (xen_enabled()) {
exec.c:2525: } else if (xen_enabled()) {
exec.c:2576: if (xen_enabled() && block->host == NULL) {
exec.c:2609: if (xen_enabled() && block->host == NULL) {
exec.c:2657: if (xen_enabled()) {
exec.c:3625: if (xen_enabled()) {
exec.c:3717: if (xen_enabled()) {
include/exec/ram_addr.h:295: if (!mask && !xen_enabled()) {
>
> Can we just follow the same working pattern we already have
> for kvm_enabled() etc ?
This was the idea... I'll look at what I missed.
Phil.
next prev parent reply other threads:[~2020-07-28 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 9:18 [PATCH] configure: define CONFIG_XEN when Xen is enabled Paul Durrant
2020-07-28 9:27 ` Peter Maydell
2020-07-28 9:51 ` Philippe Mathieu-Daudé
2020-07-28 9:53 ` Peter Maydell
2020-07-28 9:56 ` Philippe Mathieu-Daudé [this message]
2020-07-28 10:00 ` Philippe Mathieu-Daudé
2020-07-28 10:13 ` Peter Maydell
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=a09853d3-5c27-893f-54ed-63dc461bfacb@redhat.com \
--to=philmd@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=laurent@vivier.eu \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=pdurrant@amazon.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.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 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).