From: Alexander Graf <agraf@suse.de>
To: qemu-devel Developers <qemu-devel@nongnu.org>
Cc: riku.voipio@linaro.org
Subject: [Qemu-devel] [PATCH 0/4] linux-user: kpartx fixes
Date: Tue, 31 Jan 2012 22:49:47 +0100 [thread overview]
Message-ID: <1328046591-1641-1-git-send-email-agraf@suse.de> (raw)
As part of our OBS build process, we also want to be able to create kiwi images
for ARM on x86 hardware. One of the crucial bits there is the kpartx tool, since
that allows us to map images on the fly through device mapper.
So this patch set goes in and implements all the device mapper ioctls and fixes
a few hickups to actually make things work along the way. With this applied, I
can successfully run kpartx -av on an image file and have that available in the
system. As far as possible, I also verified all the other ioctls to actually
work.
Alex
Alexander Graf (4):
linux-user: implement device mapper ioctls
linux-user: add struct old_dev_t compat
linux-user: fix BLK ioctl arguments
linux-user: add BLKSSZGET ioctl wrapper
linux-user/ioctls.h | 34 +++++++
linux-user/syscall.c | 226 ++++++++++++++++++++++++++++++++++++++++++++
linux-user/syscall_defs.h | 26 +++++-
linux-user/syscall_types.h | 40 ++++++++-
thunk.c | 28 ++++++
thunk.h | 28 ++++++
6 files changed, 377 insertions(+), 5 deletions(-)
next reply other threads:[~2012-01-31 23:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 21:49 Alexander Graf [this message]
2012-01-31 21:49 ` [Qemu-devel] [PATCH 1/4] linux-user: implement device mapper ioctls Alexander Graf
2012-02-06 15:06 ` Alexander Graf
2012-01-31 21:49 ` [Qemu-devel] [PATCH 2/4] linux-user: add struct old_dev_t compat Alexander Graf
2012-01-31 22:23 ` Alexander Graf
2012-01-31 21:49 ` [Qemu-devel] [PATCH 3/4] linux-user: fix BLK ioctl arguments Alexander Graf
2012-01-31 21:49 ` [Qemu-devel] [PATCH 4/4] linux-user: add BLKSSZGET ioctl wrapper 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=1328046591-1641-1-git-send-email-agraf@suse.de \
--to=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@linaro.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).