xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: greg@enjellic.com
Cc: xen-devel@lists.xen.org
Subject: Re: i915 KMS framebuffer issues in 4.2.1/3.7.1.
Date: Fri, 4 Jan 2013 16:36:39 -0500	[thread overview]
Message-ID: <20130104213639.GA8308@phenom.dumpdata.com> (raw)
In-Reply-To: <201212261439.qBQEdOFl017226@wind.enjellic.com>

On Wed, Dec 26, 2012 at 08:39:24AM -0600, Dr. Greg Wettstein wrote:
> Good morning, hope the week is going well for everyone.
> 
> We have been putting 4.2.1 through its paces and noted an issue which
> is specific to the kernel running on top of the hypervisor.  It isn't
> specific to 4.2.1 but we validated the issue on this platform and on
> the 3.7.1 kernel for completeness.
> 
> An attempt to mmap the framebuffer provided by the i915 KMS driver
> causes a fork() to fail with ENOMEM.  Same hardware and kernel on

Is the kernel compiled with CONFIG_INTEL_DMAR .. something?

> bare-metal works fine.  The 'fbterm' utility demonstrates the problem
> but we can demonstrate on a minimal implemenation of 'mmap + forkpty'.

It could be that the _PAGE_IOMAP flag needs to be set. There was a patch
floating around for that. Hmm, could be this:

http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git;a=commit;h=0cfd8ac8e702db147a9a664212f597f627b3f7e9

or these two patches:
http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git;a=shortlog;h=refs/heads/devel/ioperm

but not sure.
> 
> Would be happy to test any patches or ideas if people have a though on
> the issue.
> 
> Have a good day.
> 
> As always,
> Dr. G.W. Wettstein, Ph.D.   Enjellic Systems Development, LLC.
> 4206 N. 19th Ave.           Specializing in information infra-structure
> Fargo, ND  58102            development.
> PH: 701-281-1686
> FAX: 701-281-3949           EMAIL: greg@enjellic.com
> ------------------------------------------------------------------------------
> "Experience is something you don't get until just after you need it."
>                                 -- Olivier
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
> 

  reply	other threads:[~2013-01-04 21:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-26 14:39 i915 KMS framebuffer issues in 4.2.1/3.7.1 Dr. Greg Wettstein
2013-01-04 21:36 ` Konrad Rzeszutek Wilk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-01-12 16:49 Dr. Greg Wettstein
2013-01-13 12:39 ` Ben Guthro
2013-01-14 15:27 ` Konrad Rzeszutek Wilk

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=20130104213639.GA8308@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=greg@enjellic.com \
    --cc=xen-devel@lists.xen.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).