All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: qemu-kvm: Remaining relevant bits in kvm/
Date: Wed, 28 Sep 2011 17:05:57 +0200	[thread overview]
Message-ID: <4E8337D5.4050301@siemens.com> (raw)

Hi all,

in order to reduce the diff between qemu-kvm.git and upstream, getting 
rid of the kvm subdirectory would be nice. What bits there are actually 
still in use today?

 From the top of my head, I only remember running kvm_stat and 
scripts/vmxcap from time to time. Obviously, there is nothing actively 
built anymore during normal qemu production. So what is the role of, e.g.,

  - kvm/bios
  - kvm/extboot
  - kvm/vgabios
  - kvm/scripts

today? Anything there we want to push upstream? And then drop the rest?

Jan

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

             reply	other threads:[~2011-09-28 15:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-28 15:05 Jan Kiszka [this message]
2011-09-29 17:10 ` qemu-kvm: Remaining relevant bits in kvm/ Marcelo Tosatti
2011-09-29 17:42   ` Jan Kiszka
2011-10-02 12:33   ` Avi Kivity
2011-10-03 20:04     ` Marcelo Tosatti

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=4E8337D5.4050301@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /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.