linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: andre.przywara@arm.com (Andre Przywara)
To: linux-arm-kernel@lists.infradead.org
Subject: stand-alone kvmtool
Date: Fri, 13 Feb 2015 10:39:33 +0000	[thread overview]
Message-ID: <54DDD465.3050300@arm.com> (raw)

Hi,

as I found it increasingly inconvenient to use kvmtool[1] as part of a
Linux repository, I decided to give it a go and make it a stand-alone
project. So I filtered all the respective commits, adjusted the paths in
there (while keeping authorship and commit date, of course) and then
added the missing bits to let it compile without a kernel tree nearby.
The result is now available on:

git://linux-arm.org/kvmtool.git
http://linux-arm.org/kvmtool.git

You can simply check it out, type make and use "./lkvm run" for a quick
test. So far I briefly tested x86-64, arm and arm64, the later two were
also cross-compiled. For sure there are rough edges in there (for
instance copying a few non-uapi header files into), but I deem it worthy
enough to get some public comments.
For me that also fixed some nasty warnings about libfdt, which now are
gone due it using your system library version of it.
I also managed to get rid of the libc-i386-dev dependency when compiling
for x86-64, but that still needs to be cleaned up and thus is not in the
current HEAD.
I haven't got around to compile-test the other supported architectures,
but supporting them should be as easy as copying over the uapi kvm.h
header file (see the respective ARM commit). Contributions (and tests!)
are welcome.

Please give it a go and tell me what you think. I don't want to fork the
project, so I am happy if someone "official" picks it up.

Cheers,
Andre.

[1] https://github.com/penberg/linux-kvm/tree/master/tools/kvm

             reply	other threads:[~2015-02-13 10:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 10:39 Andre Przywara [this message]
2015-02-13 14:30 ` stand-alone kvmtool Claudio Fontana
2015-02-13 14:40   ` Andre Przywara
2015-02-13 16:36     ` Claudio Fontana
2015-02-18 15:50 ` Will Deacon
2015-02-23 10:11   ` Andre Przywara
2015-02-26 11:02     ` Alex Bennée
2015-03-01 10:21       ` Pekka Enberg
2015-02-23 17:23   ` Pekka Enberg
2015-02-25 12:16     ` Will Deacon
2015-06-03 17:04     ` Will Deacon
2015-02-19 10:56 ` Sasha Levin
2015-02-23 11:12   ` Andre Przywara
2015-02-23 12:14   ` Russell King - ARM Linux
2015-02-23 14:27   ` Christoffer Dall

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=54DDD465.3050300@arm.com \
    --to=andre.przywara@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).