All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <levinsasha928@gmail.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Pekka Enberg <penberg@kernel.org>,
	torvalds@linux-foundation.org, mingo@elte.hu, avi@redhat.com,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org, gorcunov@gmail.com, asias.hejun@gmail.com,
	prasadjoshi124@gmail.com
Subject: Re: [GIT PULL] Native Linux KVM tool for 3.1
Date: Mon, 25 Jul 2011 10:50:01 +0300	[thread overview]
Message-ID: <1311580201.3446.30.camel@lappy> (raw)
In-Reply-To: <4E2CA6DE.4040900@web.de>

On Mon, 2011-07-25 at 01:12 +0200, Jan Kiszka wrote:
> On 2011-07-24 22:37, Pekka Enberg wrote:
> > Hi Linus,
> > 
> > Please consider pulling from
> > 
> >   ssh://master.kernel.org/pub/scm/linux/kernel/git/penberg/linux.git
> > kvm-tool-for-linus
> > 
> > to merge the Native Linux KVM tool to Linux 3.1.
> > 
> > [ The changes to 9p headers were already merged but show up in the pull
> > request. ]
> > 
> > The goal of this tool is to provide a clean, from-scratch, lightweight
> > KVM host
> > tool implementation that can boot Linux guest images with no BIOS
> > dependencies
> > and with only the minimal amount of legacy device emulation. The primary
> > focus
> > of the tool is to Linux but there are already people on working on
> > supporting
> > GRUB and other operating systems.
> > 
> > We want the tool to be part of Linux kernel source tree because we
> > believe that
> > ‘perf’ clearly showed the benefits of a single repository for both
> > kernel and
> > userspace components. See Ingo Molnar’s email that started the project for
> > details:
> > 
> >   http://thread.gmane.org/gmane.linux.kernel/962051/focus=962620
> 
> I've read several times now that developing in a single tree leads to
> better results. Can you provide some example from the QEMU/KVM projects
> where the split is preventing innovation, optimizations, or some other
> kind of progress?
> 

Anthony had a talk on last years KVM forum regarding the QEMU threading
model (slide:
http://www.linux-kvm.org/wiki/images/7/70/2010-forum-threading-qemu.pdf) .

It was suggested that the KVM part of QEMU is having a hard time
achieving the ideal threading model due to its need to support TCG -
something which has nothing to do with KVM itself.


-- 

Sasha.


  parent reply	other threads:[~2011-07-25  7:50 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-24 20:37 [GIT PULL] Native Linux KVM tool for 3.1 Pekka Enberg
2011-07-24 23:12 ` Jan Kiszka
2011-07-25  7:37   ` Pekka Enberg
2011-07-25  7:53     ` Ingo Molnar
2011-07-25  8:14       ` Alexander Graf
2011-07-25  8:23         ` Pekka Enberg
2011-07-25  8:31           ` Alexander Graf
2011-07-25  8:35             ` Avi Kivity
2011-07-25 13:10               ` Joerg Roedel
2011-07-25 15:05                 ` Avi Kivity
2011-07-25  8:37             ` Pekka Enberg
2011-07-25  8:44               ` Alexander Graf
2011-07-25  8:51                 ` Pekka Enberg
2011-07-25  8:55                   ` Alexander Graf
2011-07-25  9:16               ` Ingo Molnar
2011-07-25  9:14           ` Ingo Molnar
2011-07-25  8:30         ` Pekka Enberg
2011-07-25  8:37           ` Alexander Graf
2011-07-25  8:47             ` Pekka Enberg
2011-07-25  9:06               ` Alexander Graf
2011-07-25 12:45                 ` Pekka Enberg
2011-07-25 12:47                   ` Avi Kivity
2011-07-25 12:51                     ` Sasha Levin
2011-07-25 12:54                       ` Alexander Graf
2011-07-25 13:14                         ` Sasha Levin
2011-07-25 12:51                     ` Alexander Graf
2011-07-25 13:09                       ` Pekka Enberg
2011-07-25 13:29                         ` Alexander Graf
2011-07-25  9:26               ` Ingo Molnar
2011-07-25  9:42                 ` Alexander Graf
2011-07-25 10:16                   ` Ingo Molnar
2011-07-25 10:21                     ` Alexander Graf
2011-07-25 10:35                       ` Ingo Molnar
2011-07-25 10:47             ` Ingo Molnar
2011-07-25 12:24           ` Kevin Wolf
2011-07-25 12:41             ` Pekka Enberg
2011-07-25 12:46               ` Avi Kivity
2011-07-25  8:54         ` Ingo Molnar
2011-07-25  8:59           ` Ingo Molnar
2011-07-25  9:03           ` Alexander Graf
2011-07-25  9:41             ` Ingo Molnar
2011-07-25  9:46               ` Alexander Graf
2011-07-25 10:28                 ` Ingo Molnar
2011-07-25  9:48               ` Avi Kivity
2011-07-25 10:03                 ` Ingo Molnar
2011-07-25 10:17                   ` Avi Kivity
2011-07-25 10:29                     ` Ingo Molnar
2011-07-25 11:26             ` Olivier Galibert
2011-07-25 10:38         ` Christoph Hellwig
2011-07-25 11:08           ` Ingo Molnar
2011-07-25 11:24             ` Christoph Hellwig
2011-07-25 11:32               ` Ingo Molnar
2011-07-25 11:34               ` Olivier Galibert
2011-07-25 11:41                 ` Christoph Hellwig
2011-07-25 12:09           ` Ingo Molnar
2011-07-25 12:36           ` Pekka Enberg
2011-07-25 19:21             ` david
2011-07-25 18:24     ` Jan Kiszka
2011-07-25 19:43       ` Pekka Enberg
2011-07-25  7:50   ` Sasha Levin [this message]
2011-07-25  8:34     ` Alexander Graf
2011-07-25 12:59     ` Paolo Bonzini
2011-07-25 13:16       ` Anthony Liguori
2011-07-25  1:19 ` Anthony Liguori
2011-07-25  7:27   ` Pekka Enberg
2011-07-25  7:36     ` Avi Kivity
2011-07-25  7:39       ` Pekka Enberg
2011-07-25  7:55       ` Sasha Levin
     [not found]       ` <CAFO3S428qqUAu19QjPxDDAVv+eJSX0MEfYp5y03znNi6XbEtTg@mail.gmail.com>
2011-07-25  8:11         ` Ingo Molnar
2011-07-25  8:17           ` Pekka Enberg

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=1311580201.3446.30.camel@lappy \
    --to=levinsasha928@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=asias.hejun@gmail.com \
    --cc=avi@redhat.com \
    --cc=gorcunov@gmail.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@kernel.org \
    --cc=prasadjoshi124@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.