From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Eamon Walsh <ewalsh@tycho.nsa.gov>
Cc: George Coker <gscoker@tycho.nsa.gov>,
Xen-devel <xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Fbdev graphics broken in xen/next dom0
Date: Fri, 12 Mar 2010 16:51:30 -0800 [thread overview]
Message-ID: <4B9AE192.30104@goop.org> (raw)
In-Reply-To: <4B9ADFDB.1070300@tycho.nsa.gov>
On 03/12/2010 04:44 PM, Eamon Walsh wrote:
> I have narrowed the problem down: it has something to do with mmap of
> /dev/fb0 not syncing. The attached C code mmaps /dev/fb0 and writes
> some random bits. On a configuration that does work (2.6.31.4 on
> 4.0-rc6, or xen/next on bare metal) the random bits are visible on the
> screen. With xen/next on 4.0-rc6, nothing is visible. Calling msync()
> before the sleep has no effect. Also, using write() on /dev/fb0 always
> works so it appears to be mmap related.
>
Yes. I suspect there's a missing VM_IO in there, and so the mmap is
mapping the wrong pages (if you're lucky you might be able to crash the
machine to see something juicy).
J
next prev parent reply other threads:[~2010-03-13 0:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 20:24 Fbdev graphics broken in xen/next dom0 Eamon Walsh
2010-03-12 21:42 ` Jeremy Fitzhardinge
2010-03-13 0:44 ` Eamon Walsh
2010-03-13 0:51 ` Jeremy Fitzhardinge [this message]
2010-03-16 0:46 ` Konrad Rzeszutek Wilk
2010-03-16 21:52 ` Eamon Walsh
2010-03-16 22:19 ` Konrad Rzeszutek Wilk
2010-03-25 23:55 ` Eamon Walsh
2010-03-27 9:14 ` Arvind R
2010-03-27 21:52 ` Jeremy Fitzhardinge
2010-03-28 9:33 ` Arvind R
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=4B9AE192.30104@goop.org \
--to=jeremy@goop.org \
--cc=ewalsh@tycho.nsa.gov \
--cc=gscoker@tycho.nsa.gov \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.