From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] linux-user sysinfo support & do_sigreturn fix for i386-user
Date: Sat, 19 Jun 2004 19:40:32 +0200 [thread overview]
Message-ID: <40D47A90.2020100@bellard.org> (raw)
In-Reply-To: <BAY12-F92z7EjQxzmWe0006e81c@hotmail.com>
François Guimond wrote:
>
> Fabrice Bellard wrote:
>
>> The code was buggy, but your patch is still not correct. I tried to
>> make a correction. Try it !
>
>
> Just tried it with strace and it looks good, no sigprocmask incoherence
> present.
Good.
>[...]
> Minor, is there any work being done or planned to support the i386
> syscalls 149 and 252? (I think it corresponds to sysctl and
> exit_group) My application still complains about those, although they
> don't seem to affect operation of the program (well, the lack of
> exit_group does cause problems quitting it, but nothing a kill can't
> fix..).
exit_group() may not be implemented on < 2.6 kernels. A patch was
submitted some time ago for some functions of sysctl, but I never took
the time to merge it.
Fabrice.
prev parent reply other threads:[~2004-06-19 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 17:28 [Qemu-devel] Re: [PATCH] linux-user sysinfo support & do_sigreturn fix for i386-user François Guimond
2004-06-19 17:40 ` Fabrice Bellard [this message]
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=40D47A90.2020100@bellard.org \
--to=fabrice@bellard.org \
--cc=qemu-devel@nongnu.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).