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 13:58:33 +0100	[thread overview]
Message-ID: <4D650479.30609@siemens.com> (raw)
In-Reply-To: <4D64F2C0.4000609@msgid.tls.msk.ru>

On 2011-02-23 12:42, Michael Tokarev wrote:
> 23.02.2011 14:31, Jan Kiszka wrote:
>> 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) ?
> []
>> I think there are a few bits still in use:
>>
>> - kvm/kvm_stat
> 
> this is a tiny useful tool, yes, and we package
> it.
> 
>> - kvm/include (latest kernel headers) *)
> 
> This directory is always used (in configure)
> unless -kerneldir is specified - who uses that
> nowadays?  I dunno.

It may not be relevant to distros, provided they manage to keep their
/usr/include/linux stuff in sync with the kernel they ship. But if you
build qemu-kvm for a kernel (or kvm-kmod) that is more recent than your
user space headers, this matters.

> 
>> 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.
> 
> Yes indeed, having current defines of all the features
> we actually support is a good idea.

Would you like to propose this upstream in form of a patch series (that
demonstrates its usefulness by dropping tones of #ifdefs)?

Jan

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

  reply	other threads:[~2011-02-23 12:58 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
2011-02-23 11:42   ` Michael Tokarev
2011-02-23 12:58     ` Jan Kiszka [this message]
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=4D650479.30609@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.