qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Michael Walle <michael@walle.cc>
Cc: blauwirbel@gmail.com,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	Benjamin Poirier <benjamin.poirier@gmail.com>,
	qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: [Qemu-devel] Re: [PATCH] configure: disable opengl per default
Date: Sun, 10 Apr 2011 09:34:55 +0200	[thread overview]
Message-ID: <4DA15D9F.3070401@web.de> (raw)
In-Reply-To: <1302383601-9955-1-git-send-email-michael@walle.cc>

[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]

On 2011-04-09 23:13, Michael Walle wrote:
> There is a bug in nvidia's binary GPU driver, which causes a segmentation
> fault if linked to libGL.
> 
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
>  configure |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/configure b/configure
> index 2bb3faa..be40a31 100755
> --- a/configure
> +++ b/configure
> @@ -177,6 +177,7 @@ spice=""
>  rbd=""
>  smartcard=""
>  smartcard_nss=""
> +opengl="no"
>  
>  # parse CC options first
>  for opt do

I stumbled over this issue as well, but was unhappy about simply
disabling OpenGL without understanding what goes wrong. Still, I can't
provide a better solution yet, just some maybe helpful insights:

...
00908000-0134f000 rw-p 00000000 00:00 0 [heap]
41944000-43944000 rwxp 00000000 00:00 0
...

That's an extract of /proc/$QEMU_PID/maps with -lGL, and below without it:

00908000-010bd000 rw-p 00000000 00:00 0
010bd000-010be000 rwxp 00000000 00:00 0
010be000-01335000 rw-p 00000000 00:00 0 [heap]
40514000-42514000 rwxp 00000000 00:00 0

IOW, we are lacking the executable code_gen_prologue page. This problem
behaves like a heisenbug, ie. it disappears here when I run qemu in gdb
or under strace. But ftrace confirms that the qemu process issues
mprotect to make the whole heap non-executable after setting up that TCG
buffer - it just doesn't tell me which part of qemu is responsible for this.

Note that I'm still forced to use this wonderful binary nvidia stuff.

Anyone any ideas?
Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  reply	other threads:[~2011-04-10  7:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 12:04 [Qemu-devel] [regression] configure: add opengl detection Benjamin Poirier
2011-04-04 18:13 ` [Qemu-devel] " Michael Walle
2011-04-06 14:13   ` Benjamin Poirier
2011-04-07 21:35     ` Michael Walle
2011-04-07 22:38       ` Alexander Graf
2011-04-07 22:38       ` Benjamin Poirier
2011-04-08 10:00       ` Edgar E. Iglesias
2011-04-08 21:13         ` Michael Walle
2011-04-09  0:04           ` Alexander Graf
2011-04-09  4:20             ` Edgar E. Iglesias
2011-04-09 21:13         ` [Qemu-devel] [PATCH] configure: disable opengl per default Michael Walle
2011-04-10  7:34           ` Jan Kiszka [this message]
2011-04-12 21:34           ` Aurelien Jarno

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=4DA15D9F.3070401@web.de \
    --to=jan.kiszka@web.de \
    --cc=agraf@suse.de \
    --cc=benjamin.poirier@gmail.com \
    --cc=blauwirbel@gmail.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=michael@walle.cc \
    --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).