public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Avi Kivity <avi@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [RFC/GIT PULL] Linux KVM tool for v3.2
Date: Fri, 04 Nov 2011 15:47:50 +0100	[thread overview]
Message-ID: <4EB3FB16.2000003@siemens.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1111041037290.16959@tux.localdomain>

On 2011-11-04 09:38, Pekka Enberg wrote:
> Finally, I discovered one interesting (and esoteric) use case at LinuxCon
> Europe for the KVM tool:
> 
>   https://events.linuxfoundation.org/events/linuxcon-europe/sweeney
> 
> It turns out they use KVM tool in some parts of their simulation clusters
> because its startup memory footprint is much smaller than Qemu's.

That's mostly due to QEMU's internal guest memory represenation which
will be reworked in the near future (the large amount of device models
for all the QEMU target architectures had to be converted first).

Jan

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

  parent reply	other threads:[~2011-11-04 14:48 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-04  8:38 [RFC/GIT PULL] Linux KVM tool for v3.2 Pekka Enberg
2011-11-04 12:16 ` Christoph Hellwig
2011-11-04 12:35   ` Pekka Enberg
2011-11-04 13:02     ` Christoph Hellwig
2011-11-04 13:32       ` Pekka Enberg
2011-11-04 14:42         ` Jan Kiszka
2011-11-04 15:16           ` Sasha Levin
2011-11-04 16:26             ` Jan Kiszka
2011-11-04 16:48               ` Sasha Levin
2011-11-04 17:33                 ` Jan Kiszka
2011-11-04 16:13           ` Joerg Roedel
2011-11-04 16:42             ` Jan Kiszka
2011-11-04 17:41               ` Pekka Enberg
2011-11-04 13:14     ` Joerg Roedel
2011-11-04 14:47 ` Jan Kiszka [this message]
2011-11-08 14:44 ` richard -rw- weinberger
2011-11-08 15:36   ` Pekka Enberg
2011-11-08 16:00     ` richard -rw- weinberger
2011-11-10  3:50 ` Anthony Liguori
2011-11-10  6:46   ` Pekka Enberg
2011-11-10  7:57     ` Markus Armbruster
2011-11-10  8:21       ` Pekka Enberg
2011-11-10  8:23       ` Sasha Levin
2011-11-10  8:28         ` Pekka Enberg
2011-11-10  8:57         ` Markus Armbruster
2011-11-10  9:04           ` Sasha Levin
2011-11-10  9:09             ` Avi Kivity
2011-11-10  9:14               ` Sasha Levin
2011-11-10  9:23                 ` Avi Kivity
2011-11-10  9:34                   ` Sasha Levin
2011-11-10  9:43                     ` Avi Kivity
2011-11-10  9:49                       ` Sasha Levin
2011-11-10  9:50                         ` Avi Kivity
2011-11-10  9:48             ` Markus Armbruster
2011-11-10 13:43     ` Anthony Liguori
2011-11-10 13:56       ` Pekka Enberg
2011-11-10 14:47         ` Markus Armbruster
2011-11-10 15:33           ` Stefan Hajnoczi

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=4EB3FB16.2000003@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=akpm@linux-foundation.org \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    --cc=torvalds@linux-foundation.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