From: Igor Mammedov <imammedo@redhat.com>
To: Anthony Xu <anthony.xu@intel.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Memory: use memory address space for cpu-memory
Date: Wed, 17 May 2017 11:27:56 +0200 [thread overview]
Message-ID: <20170517112756.74cf6e47@nial.brq.redhat.com> (raw)
In-Reply-To: <1494972923-31756-1-git-send-email-anthony.xu@intel.com>
On Tue, 16 May 2017 15:15:23 -0700
Anthony Xu <anthony.xu@intel.com> wrote:
> If cpu-memory address space is same as memory address space,
> use memory address space for cpu-memory address space.
>
> any memory region change causeaddress space to rebuild PhysPageMap,
> rebuilding PhysPageMap is very expensive.
>
> removing cpu-memory address space reduces the guest boot time and
> memory usage.
>
> Signed-off-by: Anthony Xu <anthony.xu@intel.com>
> ---
> cpus.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/cpus.c b/cpus.c
> index 740b8dc..15c7a6a 100644
> --- a/cpus.c
> +++ b/cpus.c
> @@ -1748,8 +1748,13 @@ void qemu_init_vcpu(CPUState *cpu)
> /* If the target cpu hasn't set up any address spaces itself,
> * give it the default one.
> */
> - AddressSpace *as = address_space_init_shareable(cpu->memory,
> - "cpu-memory");
> + AddressSpace *as;
> + if (cpu->memory == address_space_memory.root) {
> + address_space_memory.ref_count++;
probably this would cause reference leak when vcpu is destroyed
> + as = &address_space_memory;
> + } else {
> + as = address_space_init_shareable(cpu->memory, "cpu-memory");
> + }
> cpu->num_ases = 1;
> cpu_address_space_init(cpu, as, 0);
> }
next prev parent reply other threads:[~2017-05-17 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 22:15 [Qemu-devel] [PATCH] Memory: use memory address space for cpu-memory Anthony Xu
2017-05-17 9:27 ` Igor Mammedov [this message]
2017-05-17 17:01 ` Xu, Anthony
2017-05-18 21:38 ` Paolo Bonzini
2017-05-18 21:48 ` Xu, Anthony
2017-05-18 21:49 ` Paolo Bonzini
2017-05-18 23:28 ` Xu, Anthony
2017-05-19 9:30 ` Paolo Bonzini
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=20170517112756.74cf6e47@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=anthony.xu@intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).