From: Martin Mohring <martin.mohring@opensuse.org>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Riku Voipio <riku.voipio@iki.fi>
Subject: [Qemu-devel] [PATCH] linux-user: fix for loopmount ioctl
Date: Sun, 09 Jan 2011 00:25:47 +0100 [thread overview]
Message-ID: <4D28F27B.8020805@opensuse.org> (raw)
In-Reply-To: <cover.1294433287.git.riku.voipio@nokia.com>
[-- Attachment #1: Type: text/plain, Size: 110 bytes --]
Hi,
I had fixed the loopmount ioctl for linux-user, working correctly for arm, mips, ppc32 and sh4.
Martin
[-- Attachment #2: qemu-0.14-git-linux_user-ioctl_loopmount_fix.patch --]
[-- Type: text/x-patch, Size: 1235 bytes --]
From: Martin Mohring <martin.mohring@5edatasoft.com>
In case a chrooted build uses XEN or KVM, a looped mount needs to be done to setup the chroot.
The ioctl for loop mount works correctly for arm, mips, ppc32 and sh4, so its now activated.
Signed-off-by: Martin Mohring <martin.mohring@5edatasoft.com>
---
diff -u -r qemu-0.14git2011.01.06.2243.orig//linux-user/ioctls.h qemu-0.14git2011.01.06.2243//linux-user/ioctls.h
--- qemu-0.14git2011.01.06.2243.orig//linux-user/ioctls.h 2011-01-08 20:50:21.000000000 +0100
+++ qemu-0.14git2011.01.06.2243//linux-user/ioctls.h 2011-01-09 00:17:41.000000000 +0100
@@ -312,10 +312,8 @@
IOCTL(LOOP_CLR_FD, 0, TYPE_INT)
IOCTL(LOOP_SET_STATUS, IOC_W, MK_PTR(MK_STRUCT(STRUCT_loop_info)))
IOCTL(LOOP_GET_STATUS, IOC_W, MK_PTR(MK_STRUCT(STRUCT_loop_info)))
-#if 0 /* These have some problems - not fully tested */
IOCTL(LOOP_SET_STATUS64, IOC_W, MK_PTR(MK_STRUCT(STRUCT_loop_info64)))
IOCTL(LOOP_GET_STATUS64, IOC_W, MK_PTR(MK_STRUCT(STRUCT_loop_info64)))
-#endif
IOCTL(LOOP_CHANGE_FD, 0, TYPE_INT)
IOCTL(MTIOCTOP, IOC_W, MK_PTR(MK_STRUCT(STRUCT_mtop)))
Only in qemu-0.14git2011.01.06.2243//linux-user: ioctls.h.orig
Only in qemu-0.14git2011.01.06.2243//linux-user: ioctls.h~
next prev parent reply other threads:[~2011-01-08 23:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 20:52 [Qemu-devel] [PATCH 0/7] linux-user fixes for pull Riku Voipio
2011-01-07 20:52 ` [Qemu-devel] [PATCH 1/7] linux-user: Implement sync_file_range{, 2} syscalls Riku Voipio
2011-01-07 20:52 ` [Qemu-devel] [PATCH 2/7] linux-user: Support ioctls whose parameter size is not constant Riku Voipio
2011-01-07 20:52 ` [Qemu-devel] [PATCH 3/7] linux-user: Implement FS_IOC_FIEMAP ioctl Riku Voipio
2011-01-09 14:47 ` Blue Swirl
2011-01-09 17:47 ` riku voipio
2011-01-09 19:08 ` Blue Swirl
2011-01-10 4:01 ` Peter Maydell
2011-01-09 20:06 ` Martin Mohring
2011-01-07 20:52 ` [Qemu-devel] [PATCH 4/7] softfloat: Implement floatx80_is_any_nan() and float128_is_any_nan() Riku Voipio
2011-01-07 20:52 ` [Qemu-devel] [PATCH 5/7] linux-user: Fix incorrect NaN detection in ARM nwfpe emulation Riku Voipio
2011-01-07 20:52 ` [Qemu-devel] [PATCH 6/7] Fix commandline handling for ARM semihosted executables Riku Voipio
2011-01-07 20:52 ` [Qemu-devel] [PATCH 7/7] Remove dead code for ARM semihosting commandline handling Riku Voipio
2011-01-08 15:35 ` [Qemu-devel] [PATCH 0/7] linux-user fixes for pull Aurelien Jarno
2011-01-08 23:25 ` Martin Mohring [this message]
2011-01-10 16:18 ` [Qemu-devel] [PATCH] linux-user: fix for loopmount ioctl Martin Mohring
2011-01-10 21:13 ` Riku Voipio
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=4D28F27B.8020805@opensuse.org \
--to=martin.mohring@opensuse.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).