From: Jeff Moyer <jmoyer@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: linux-aio@kvack.org, Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: aio: compat_ioctl issue?
Date: Mon, 08 Mar 2010 17:25:24 -0500 [thread overview]
Message-ID: <x49mxyi78ob.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <4B957122.4060007@msgid.tls.msk.ru> (Michael Tokarev's message of "Tue, 09 Mar 2010 00:50:26 +0300")
Michael Tokarev <mjt@tls.msk.ru> writes:
> Jeff Moyer wrote:
>> Michael Tokarev <mjt@tls.msk.ru> writes:
>>
>>> Hello.
>>>
>>> I just come across a situation (next in a long row :)
>>> when on x86, 32bit userspace does not work with 64bit
>>> kernel. This time this is about aio requests.
>>>
>>> An application submits some aio job, and it is returned
>>> immediately (from io_getevents()) with EINVAL error.
> []
>> Can you post the program, please?
>
> The program which I'm trying is quite big - it's qemu-kvm
> v. 0.12.3 compiled with --enable-linux-aio. I bugged
> kvm folks about non-working aio support but immediately
> realized it's 32/64bit issue in the kernel, since 64bit
> kvm works just fine on the same kernel (which is 64bits).
> So I added 2 printfs into its linux-aio.c and re-run it.
[snip]
Well, I'm not experiencing such problems. I can run a 32bit aio
application on a 64bit kernel just fine with 2.6.31, 2.6.32 and
2.6.34-rc1.
Could you maybe print out the values that are passed to io_getevents?
Thanks,
Jeff
next prev parent reply other threads:[~2010-03-08 22:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 21:38 Michael Tokarev
2010-03-08 21:43 ` Jeff Moyer
2010-03-08 21:50 ` Michael Tokarev
2010-03-08 22:25 ` Jeff Moyer [this message]
2010-03-08 22:32 ` Michael Tokarev
2010-03-08 22:41 ` Michael Tokarev
2010-03-11 16:06 ` Jeff Moyer
2010-03-11 19:10 ` Michael Tokarev
2010-03-11 19:13 ` Jeff Moyer
2010-03-11 19:46 ` Michael Tokarev
2010-03-11 19:57 ` Jeff Moyer
2010-03-11 20:13 ` Michael Tokarev
2010-03-16 18:52 ` Jeff Moyer
2010-03-16 20:36 ` Michael Tokarev
2010-03-16 20:44 ` Jeff Moyer
2010-04-28 18:00 ` Avi Kivity
2010-04-28 18:11 ` Jeff Moyer
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=x49mxyi78ob.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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
all inboxes | Powered by JetHome®