From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jaya Kumar <jayakumar.lkml@gmail.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Xen-devel <xen-devel@lists.xensource.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Xen fbdev fixups
Date: Wed, 09 Dec 2009 17:03:02 -0800 [thread overview]
Message-ID: <4B2048C6.6030307@goop.org> (raw)
Hi Linus,
Here are some small updates to fbdev to make the Xen fbdev driver work
properly. The bulk of the change is to make sure we only set VM_IO on
vmas which actually map device memory, and not set it on plain old
vmalloc memory. This is necessary in Xen, because we end up using that
flag to determine whether the ptes are mapping real machine physical
memory or guest pseudo-physical memory.
We also do this on the other fbdev drivers which allocate vmalloc
framebuffers for consistency.
Thanks,
J
The following changes since commit 74fca6a42863ffacaf7ba6f1936a9f228950f657:
Linus Torvalds (1):
Linux 2.6.31
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git xen/fbdev
Konrad Rzeszutek Wilk (4):
Fix toogle whether xenbus driver should be built as module or part of kernel.
fb-defio: If FBINFO_VIRTFB is defined, do not set VM_IO flag.
fb-defio: Inhibit VM_IO flag to be set on vmalloc-ed framebuffers.
xen pvfb: Inhibit VM_IO flag to be set on vmalloc-ed framebuffers.
drivers/input/Kconfig | 1 +
drivers/video/Kconfig | 1 +
drivers/video/broadsheetfb.c | 2 +-
drivers/video/fb_defio.c | 4 +++-
drivers/video/hecubafb.c | 2 +-
drivers/video/metronomefb.c | 2 +-
drivers/video/xen-fbfront.c | 2 +-
include/linux/fb.h | 1 +
8 files changed, 10 insertions(+), 5 deletions(-)
reply other threads:[~2009-12-10 1:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B2048C6.6030307@goop.org \
--to=jeremy@goop.org \
--cc=jayakumar.lkml@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox