From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] qemu-kvm upstreaming: Do we want -kvm-shadow-memory semantics?
Date: Wed, 25 Jan 2012 13:38:54 +0200 [thread overview]
Message-ID: <4F1FE9CE.5050401@redhat.com> (raw)
In-Reply-To: <4F185535.1060908@siemens.com>
On 01/19/2012 07:39 PM, Jan Kiszka wrote:
> On 2012-01-19 18:28, Marcelo Tosatti wrote:
> > On Thu, Jan 19, 2012 at 01:46:39PM +0100, Jan Kiszka wrote:
> >> Hi again,
> >>
> >> do we need some KVM knob comparable to qemu-kvm's -kvm-shadow-memory in
> >> upstream?
> >>
> >> If yes: The underlying IOCTL is x86-only. Are other archs interested in
> >> this long-term as well, ie. should the control become arch-independent?
> >>
> >> Jan
> >
> > Last time i asked about removal, Avi wished for it to remain.
> >
>
> Then I guess he should comment on this after returning to work. :)
-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.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-01-25 11:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 12:46 [Qemu-devel] qemu-kvm upstreaming: Do we want -kvm-shadow-memory semantics? Jan Kiszka
2012-01-19 13:24 ` Alexander Graf
2012-01-19 13:30 ` Jan Kiszka
2012-01-19 13:42 ` Alexander Graf
2012-01-19 17:28 ` Marcelo Tosatti
2012-01-19 17:39 ` Jan Kiszka
2012-01-25 11:38 ` Avi Kivity [this message]
2012-01-25 11:57 ` Jan Kiszka
2012-01-25 12:04 ` Avi Kivity
2012-01-25 12:10 ` Jan Kiszka
2012-01-25 12:15 ` Avi Kivity
2012-01-25 12:26 ` Jan Kiszka
2012-01-25 12:33 ` Avi Kivity
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=4F1FE9CE.5050401@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).