From: Matt Evans <matt@ozlabs.org>
To: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org
Cc: penberg@kernel.org, asias.hejun@gmail.com,
levinsasha928@gmail.com, gorcunov@gmail.com
Subject: [PATCH V3 0/2] kvm tools: Prepare kvmtool for another architecture
Date: Tue, 13 Dec 2011 17:21:45 +1100 [thread overview]
Message-ID: <1323757307-10411-1-git-send-email-matt@ozlabs.org> (raw)
The last remaining patches from the preparation series, with changes:
- Map from hugetlbfs does plain statfs (without odd error checking),
checks result of ftruncate()
- Remove typo whereby kvm_cpu__emulate_mmio() calls self.....
Cheers,
Matt
Matt Evans (2):
kvm tools: Add ability to map guest RAM from hugetlbfs
kvm tools: Create arch-specific kvm_cpu__emulate_{mm}io()
tools/kvm/builtin-run.c | 4 ++-
tools/kvm/include/kvm/kvm.h | 4 +-
tools/kvm/include/kvm/util.h | 4 +++
tools/kvm/kvm-cpu.c | 34 +++++++++++++-------------
tools/kvm/kvm.c | 4 +-
tools/kvm/util.c | 38 ++++++++++++++++++++++++++++++
tools/kvm/x86/include/kvm/kvm-cpu-arch.h | 17 ++++++++++++-
tools/kvm/x86/kvm.c | 20 +++++++++++++--
8 files changed, 99 insertions(+), 26 deletions(-)
next reply other threads:[~2011-12-13 6:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 6:21 Matt Evans [this message]
2011-12-13 6:21 ` [PATCH V3 1/2] kvm tools: Add ability to map guest RAM from hugetlbfs Matt Evans
2011-12-14 0:03 ` David Evensky
2011-12-14 1:45 ` Matt Evans
2011-12-13 6:21 ` [PATCH V3 2/2] kvm tools: Create arch-specific kvm_cpu__emulate_{mm}io() Matt Evans
2011-12-23 12:58 ` Alexander Graf
2011-12-23 13:26 ` Matt Evans
2011-12-23 13:39 ` Alexander Graf
2012-01-06 5:32 ` Matt Evans
2012-01-09 13:41 ` Alexander Graf
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=1323757307-10411-1-git-send-email-matt@ozlabs.org \
--to=matt@ozlabs.org \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=penberg@kernel.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).