All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: "Cui, Dexuan" <dexuan.cui@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [Patch] Qemu map cache
Date: Mon, 04 Dec 2006 12:26:30 -0600	[thread overview]
Message-ID: <45746856.5020502@linux.vnet.ibm.com> (raw)
In-Reply-To: <666CC8FCE3247C4DA876BA979059781A5C27DD@pdsmsx401.ccr.corp.intel.com>

Cui, Dexuan wrote:
> On IA32 host or IA32 PAE host, at present, generally, we can't create an
> HVM guest with more than 2G memory, because generally it's almost
> impossible for Qemu to find a large enough and consecutive virtual
> address space to map an HVM guest's whole physical address space.
> The attached patch fixes this issue using dynamic mapping based on
> little blocks of memory.

I have a feeling this patch is going to require quite a lot more work 
for V2E.  Have you guys considered implementing this functionality for 
upstream QEMU?  The Xen specific portions should be small and upstream 
QEMU has the same problem.

Regards,

Anthony Liguori

> -- Dexuan Cui
> 
> Signed-off-by: Jun Nakajima <jun.nakajima@intel.com>
> Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2006-12-04 18:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-04 17:33 [Patch] Qemu map cache Cui, Dexuan
2006-12-04 18:26 ` Anthony Liguori [this message]
2006-12-04 22:58 ` Anthony Liguori
2006-12-05 20:28   ` Ian Pratt
2006-12-05 20:48     ` Anthony Liguori
2006-12-06  0:33       ` Ian Pratt
  -- strict thread matches above, loose matches on Subject: below --
2006-12-07  2:08 Cui, Dexuan
2006-12-07 10:35 ` Keir Fraser

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=45746856.5020502@linux.vnet.ibm.com \
    --to=aliguori@linux.vnet.ibm.com \
    --cc=dexuan.cui@intel.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.