[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC] Host vs Guest memory allocation
From: |
Richard Henderson |
Subject: |
Re: [Qemu-devel] [RFC] Host vs Guest memory allocation |
Date: |
Mon, 12 Apr 2010 07:55:22 -0700 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.0.4-1.fc12 Thunderbird/3.0.4 |
On 04/12/2010 04:48 AM, Avi Kivity wrote:
(1) Enable softmmu for userland. This is of course the highest overhead,
but will work for all combinations.
...
You could reduce the overhead somewhat by using kvm for memory
translation on hosts that support it. Of course tcg translation and
syscall costs will grow by the exit overhead.
I've thought about this a bit, and what seemed to be the stickler is
what is the environment that runs in the guest? TCG generated code
is of course fine, but what about the helper functions? How can we
tell whether a given helper function can run in the restricted
environment of the guest or whether it needs to transition back to the
environment of the host to do its work?
I suppose the obvious solution is some sort of flag on the function that
well-maintained ports will set. But the whole marshalling thing is
still pretty tricky.
r~
- [Qemu-devel] [RFC] Host vs Guest memory allocation, Richard Henderson, 2010/04/05
- Re: [Qemu-devel] [RFC] Host vs Guest memory allocation, Aurelien Jarno, 2010/04/05
- Re: [Qemu-devel] [RFC] Host vs Guest memory allocation, Avi Kivity, 2010/04/12
- Re: [Qemu-devel] [RFC] Host vs Guest memory allocation,
Richard Henderson <=
- Re: [Qemu-devel] [RFC] Host vs Guest memory allocation, Avi Kivity, 2010/04/12
- Re: [Qemu-devel] [RFC] Host vs Guest memory allocation, Alexander Graf, 2010/04/12
- Re: [Qemu-devel] [RFC] Host vs Guest memory allocation, Avi Kivity, 2010/04/12
- Re: [Qemu-devel] [RFC] Host vs Guest memory allocation, Alexander Graf, 2010/04/12
- Re: [Qemu-devel] [RFC] Host vs Guest memory allocation, Avi Kivity, 2010/04/12
Re: [Qemu-devel] [RFC] Host vs Guest memory allocation, Paul Brook, 2010/04/12