All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: Xen Devel <xen-devel@lists.xensource.com>,
	QEMU-devel <qemu-devel@nongnu.org>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH V2 0/3] Enable QEMU to handle more than 2GB with Xen.
Date: Wed, 27 Jul 2011 14:56:47 +0200	[thread overview]
Message-ID: <4E300B0F.5080200@suse.de> (raw)
In-Reply-To: <1311185864-32745-1-git-send-email-anthony.perard@citrix.com>

On 07/20/2011 08:17 PM, Anthony PERARD wrote:
> Hi all,
>
> Update on this series:
>    - Use a RAM address of 64bits only on 64bits targets when Xen is enable.
>    - Add some comment on the memory registration done for Xen.
>
>
> Xen is not limited by the QEMU's virtual address space for the allocation of
> the guest RAM. So even with a QEMU 32bits, a Xen guest can have more than 4 GB
> of RAM.
>
> With this serie, we will be able to run a guest with more than 4GB. The main
> point is to change ram_addr_t from ulong to uin64 when QEMU is configure with
> Xen. The second point is better register the memory in QEMU.
>
> Regards,
>
> Anthony PERARD (3):
>    cpu-common: Have a ram_addr_t of uint64 with Xen.
>    xen: Fix the memory registration to reflect of what is done by Xen.
>    vl.c: Check the asked ram_size later.
>
>   cpu-common.h |    8 ++++++++
>   exec.c       |    9 +++++----
>   vl.c         |   14 ++++++++------
>   xen-all.c    |   29 +++++++++++++++++++++--------
>   4 files changed, 42 insertions(+), 18 deletions(-)

Thanks, applied all to xen-next. I also squashed the following patch 
into 3/3:

diff --git a/vl.c b/vl.c
index 24df37f..d8c7c01 100644
--- a/vl.c
+++ b/vl.c
@@ -3096,7 +3096,9 @@ int main(int argc, char **argv, char **envp)
      /* init the memory */
      if (ram_size == 0) {
          ram_size = DEFAULT_RAM_SIZE * 1024 * 1024;
-    } else if (!xen_enabled()) {
+    }
+
+    if (!xen_enabled()) {
          /* On 32-bit hosts, QEMU is limited by virtual address space */
          if (ram_size > (2047 << 20) && HOST_LONG_BITS == 32) {
              fprintf(stderr, "qemu: at most 2047 MB RAM can be 
simulated\n");


Alex

WARNING: multiple messages have this Message-ID (diff)
From: Alexander Graf <agraf@suse.de>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: Xen Devel <xen-devel@lists.xensource.com>,
	QEMU-devel <qemu-devel@nongnu.org>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH V2 0/3] Enable QEMU to handle more than 2GB with Xen.
Date: Wed, 27 Jul 2011 14:56:47 +0200	[thread overview]
Message-ID: <4E300B0F.5080200@suse.de> (raw)
In-Reply-To: <1311185864-32745-1-git-send-email-anthony.perard@citrix.com>

On 07/20/2011 08:17 PM, Anthony PERARD wrote:
> Hi all,
>
> Update on this series:
>    - Use a RAM address of 64bits only on 64bits targets when Xen is enable.
>    - Add some comment on the memory registration done for Xen.
>
>
> Xen is not limited by the QEMU's virtual address space for the allocation of
> the guest RAM. So even with a QEMU 32bits, a Xen guest can have more than 4 GB
> of RAM.
>
> With this serie, we will be able to run a guest with more than 4GB. The main
> point is to change ram_addr_t from ulong to uin64 when QEMU is configure with
> Xen. The second point is better register the memory in QEMU.
>
> Regards,
>
> Anthony PERARD (3):
>    cpu-common: Have a ram_addr_t of uint64 with Xen.
>    xen: Fix the memory registration to reflect of what is done by Xen.
>    vl.c: Check the asked ram_size later.
>
>   cpu-common.h |    8 ++++++++
>   exec.c       |    9 +++++----
>   vl.c         |   14 ++++++++------
>   xen-all.c    |   29 +++++++++++++++++++++--------
>   4 files changed, 42 insertions(+), 18 deletions(-)

Thanks, applied all to xen-next. I also squashed the following patch 
into 3/3:

diff --git a/vl.c b/vl.c
index 24df37f..d8c7c01 100644
--- a/vl.c
+++ b/vl.c
@@ -3096,7 +3096,9 @@ int main(int argc, char **argv, char **envp)
      /* init the memory */
      if (ram_size == 0) {
          ram_size = DEFAULT_RAM_SIZE * 1024 * 1024;
-    } else if (!xen_enabled()) {
+    }
+
+    if (!xen_enabled()) {
          /* On 32-bit hosts, QEMU is limited by virtual address space */
          if (ram_size > (2047 << 20) && HOST_LONG_BITS == 32) {
              fprintf(stderr, "qemu: at most 2047 MB RAM can be 
simulated\n");


Alex

  parent reply	other threads:[~2011-07-27 12:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20 18:17 [Qemu-devel] [PATCH V2 0/3] Enable QEMU to handle more than 2GB with Xen Anthony PERARD
2011-07-20 18:17 ` Anthony PERARD
2011-07-20 18:17 ` [Qemu-devel] [PATCH V2 1/3] cpu-common: Have a ram_addr_t of uint64 " Anthony PERARD
2011-07-20 18:17   ` Anthony PERARD
2011-07-20 18:17 ` [Qemu-devel] [PATCH V2 2/3] xen: Fix the memory registration to reflect of what is done by Xen Anthony PERARD
2011-07-20 18:17   ` Anthony PERARD
2011-07-21 11:10   ` Stefano Stabellini
2011-07-20 18:17 ` [Qemu-devel] [PATCH V2 3/3] vl.c: Check the asked ram_size later Anthony PERARD
2011-07-20 18:17   ` Anthony PERARD
2011-07-27 12:53   ` [Qemu-devel] " Alexander Graf
2011-07-27 12:53     ` Alexander Graf
2011-07-27 12:56 ` Alexander Graf [this message]
2011-07-27 12:56   ` [PATCH V2 0/3] Enable QEMU to handle more than 2GB with Xen Alexander Graf

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=4E300B0F.5080200@suse.de \
    --to=agraf@suse.de \
    --cc=anthony.perard@citrix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.