| Message ID | 4D28F27B.8020805@opensuse.org |
|---|---|
| State | New |
| Headers | show |
On 01/09/2011 12:25 AM, Martin Mohring wrote: > Hi, > > I had fixed the loopmount ioctl for linux-user, working correctly for arm, mips, ppc32 and sh4. > > Martin > > ping Aurelien, Riku, is that patch ok? Its only 2 lines of change to activate an ioctl.
On Mon, Jan 10, 2011 at 05:18:43PM +0100, Martin Mohring wrote: > On 01/09/2011 12:25 AM, Martin Mohring wrote: > > Hi, > > > > I had fixed the loopmount ioctl for linux-user, working correctly for arm, mips, ppc32 and sh4. > ping > Aurelien, Riku, is that patch ok? Its only 2 lines of change to activate > an ioctl. Dont worry, I'm looking on it. The original comment suggested the ioctl had problems, so I'd like to close look on it first. Riku
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~