Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] pango: use qemu to generate pango.modules during rootfs construction
Date: Sun, 11 Sep 2011 22:33:20 +0100	[thread overview]
Message-ID: <1315776800.8535.2.camel@lenovo.internal.reciva.com> (raw)
In-Reply-To: <1315646891.4368.13.camel@lenovo.internal.reciva.com>

On Sat, 2011-09-10 at 10:28 +0100, Phil Blundell wrote: 
> The other odd thing is that, from a quick look at the qemu source code,
> it does seem as though sys_futex (which is syscall 240 on i386 and
> syscall 202 on x86-64) ought to be supported if qemu was built with NPTL
> on.  However, in my x86-64 test I did see the "unsupported syscall 202"
> syscall although the binary still seemed to run fine.

This part turns out not (quite) to be so mysterious.  For some reason,
qemu's configure script doesn't set target_nptl=yes for i386 or x86-64,
though it does for the majority of other arches.  So it will indeed be
the case that sys_futex will show up as an "unsupported syscall" on
those two architectures.

I'm not quite sure why qemu would be deciding not to do futexes on those
two architectures specifically.  I guess there must be some
functionality missing from the x86 emulation backend though I am not
sure exactly what that would be or how hard it would be to add.

p.





      parent reply	other threads:[~2011-09-11 22:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31 15:35 [PATCH] pango: use qemu to generate pango.modules during rootfs construction Phil Blundell
2011-09-08  1:12 ` Saul Wold
2011-09-09 21:19 ` Saul Wold
2011-09-10  8:24   ` Richard Purdie
2011-09-10  9:28     ` Phil Blundell
2011-09-10  9:54       ` Richard Purdie
2011-09-10 11:53         ` Phil Blundell
2011-09-13 17:08           ` Richard Purdie
2011-09-13 17:14             ` Otavio Salvador
2011-09-13 17:25             ` Phil Blundell
2011-09-13 18:33               ` Otavio Salvador
2011-09-13 18:46                 ` Saul Wold
2011-09-14  9:10                 ` Phil Blundell
2011-09-11 21:33       ` Phil Blundell [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=1315776800.8535.2.camel@lenovo.internal.reciva.com \
    --to=philb@gnu.org \
    --cc=openembedded-core@lists.openembedded.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