All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: Q: status of kvm/ subdir in qemu-kvm tarball?
Date: Wed, 23 Feb 2011 12:31:20 +0100	[thread overview]
Message-ID: <4D64F008.7050308@siemens.com> (raw)
In-Reply-To: <4D64E9C6.8000505@msgid.tls.msk.ru>

On 2011-02-23 12:04, Michael Tokarev wrote:
> What's the current status of files in kvm/ subdirectory
> in the qemu-kvm distribution (0.14 or git) ?
> 
> As far as I can see, all that is old and unused stuff,
> which only confuses users.  It is not used during build
> the Makefiles are obsolete and refers to non-existed
> files/directories, some remaining bits (like vgabios)
> are too old to be useful for current qemu-kvm, etc.
> 
> Maybe it's better to just drop the whole thing to stop
> confusion?
> 
> If it may be needed in the future, it can be taken from
> older source tarballs.  Just letting that stuff to bitrot
> isn't a nice thing to do. ;)
> 
> I mentioned this yesterday to Avi (my question was
> especially about vgabios), and he told me to send a
> patch with justification.  But it's way too simpler
> to just do `git rm -r kvm' than apply a patch to
> remove the whole thing.

I think there are a few bits still in use:

- kvm/kvm_stat
- kvm/include (latest kernel headers) *)

Otherwise, removing this cruft would be good.

Jan

*) This should really be discussed upstream again: Carry private copy of
kvm headers or rely on distro / kvm-kmod to provide required defines,
types etc.? I'm more and more in favor of option 1.

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

  reply	other threads:[~2011-02-23 11:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 11:04 Q: status of kvm/ subdir in qemu-kvm tarball? Michael Tokarev
2011-02-23 11:31 ` Jan Kiszka [this message]
2011-02-23 11:42   ` Michael Tokarev
2011-02-23 12:58     ` Jan Kiszka
2011-02-23 13:15       ` Michael Tokarev
2011-02-23 13:45         ` Jan Kiszka
2011-02-23 14:30           ` Michael Tokarev
2011-02-23 14:57             ` Jan Kiszka
2011-02-27 16:28               ` Avi Kivity
2011-02-27 18:36                 ` Jan Kiszka

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=4D64F008.7050308@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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.