qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel Developers <qemu-devel@nongnu.org>,
	Aurelien Jarno <aurelien@aurel32.net>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [RFC] Host vs Guest memory allocation
Date: Mon, 12 Apr 2010 18:49:30 +0300	[thread overview]
Message-ID: <4BC3410A.2040506@redhat.com> (raw)
In-Reply-To: <FE4E80DC-6127-4711-9F02-F233D568CC06@suse.de>

On 04/12/2010 06:39 PM, Alexander Graf wrote:
>
>> Pass everything through memory; will there be many transitions apart from trapping instructions and missing translations?
>>      
> I don't see how that would help with the 64-on-32 issue. You still don't get a 64 bit address space from running inside KVM.
>    

True.  Like the other options, it's just another tool in the toolbox and 
doesn't solve all problems.

You could cheat and have a 64-bit kernel under a 32-bit qemu.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

  reply	other threads:[~2010-04-12 15:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-05 22:45 [Qemu-devel] [RFC] Host vs Guest memory allocation Richard Henderson
2010-04-05 23:18 ` Aurelien Jarno
2010-04-12 11:48   ` Avi Kivity
2010-04-12 14:55     ` Richard Henderson
2010-04-12 15:09       ` Avi Kivity
2010-04-12 15:39         ` Alexander Graf
2010-04-12 15:49           ` Avi Kivity [this message]
2010-04-12 15:56             ` Alexander Graf
2010-04-12 16:08               ` Avi Kivity
2010-04-12 11:25 ` Paul Brook
2010-04-12 14:48   ` Richard Henderson

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=4BC3410A.2040506@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=aurelien@aurel32.net \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).