On 04/12/2010 06:56 PM, Alexander Graf wrote:
For fully system emulation on the other hand I can imagine quite some nice
tricks one could pull.
On PPC hosts you get a huge number of VSIDs that are basically like tags on the
TLB. So if you'd give every x86 page table one VSID you'd potentially
On 12.04.2010, at 17:49, Avi Kivity wrote:
> 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. Yo
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 insid
On 12.04.2010, at 17:09, Avi Kivity wrote:
> On 04/12/2010 05:55 PM, Richard Henderson wrote:
>>
>>> 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'v
On 04/12/2010 05:55 PM, Richard Henderson wrote:
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 i
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
On 04/12/2010 04:25 AM, Paul Brook wrote:
(1) Enable softmmu for userland. This is of course the highest overhead,
but will work for all combinations.
This has a significant performance hit, and gets very tricky for things like
mmaped files.
It has the advantage of actually working for s
On 04/06/2010 02:18 AM, Aurelien Jarno wrote:
(1) Enable softmmu for userland. This is of course the highest overhead,
but will work for all combinations.
This option would solve a lot of problems and simplify a lot of code:
unaligned access on hosts requiring strict alignements, d
> The Problem:
>
> CONFIG_USER_ONLY kinda sorta tries to manage the distinction between
> qemu memory and guest memory. This can be seen in the PAGE_RESERVED
> frobbing and qemu_malloc etc. However, it doesn't handle random malloc
> calls eg from libc itself or other libraries in use.
>
> Possibl
On Mon, Apr 05, 2010 at 03:45:23PM -0700, Richard Henderson wrote:
> The Problem:
>
> CONFIG_USER_ONLY kinda sorta tries to manage the distinction between
> qemu memory and guest memory. This can be seen in the PAGE_RESERVED
> frobbing and qemu_malloc etc. However, it doesn't handle random malloc
The Problem:
CONFIG_USER_ONLY kinda sorta tries to manage the distinction between
qemu memory and guest memory. This can be seen in the PAGE_RESERVED
frobbing and qemu_malloc etc. However, it doesn't handle random malloc
calls eg from libc itself or other libraries in use.
Possible solutions:
Th
11 matches
Mail list logo
