qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] qemu-kvm upstreaming: Do we want -kvm-shadow-memory sem


From: Jan Kiszka
Subject: Re: [Qemu-devel] qemu-kvm upstreaming: Do we want -kvm-shadow-memory semantics?
Date: Wed, 25 Jan 2012 13:10:38 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666

On 2012-01-25 13:04, Avi Kivity wrote:
> On 01/25/2012 01:57 PM, Jan Kiszka wrote:
>>>
>>> -kvm-shadow-memory is becoming less meaningful for ordinary workloads
>>> since everything uses TDP these days.  It's still meaningful for testing
>>> (forcing aggressive cache replacement), or perhaps nested virtualization.
>>
>> So, is it used for testing in fact? 
> 
> It is not, but it should be.  There's an extra_params option in
> autotest, I'll start using it to stress the mmu some more, even though
> it's going to slow things down for me.

OK.

> 
>> Would a machine option
>> "kvm_shadow_memory=n" be desirable?
> 
> Not sure, this is a host option, not a guest option.  Machine options
> should be guest-visible.

machine options are not guest visible. Basically, this options falls
into the same category as kernel_irqchip.

Do we have alternatives? A top-level command line options is surely none.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux



reply via email to

[Prev in Thread] Current Thread [Next in Thread]