From: Bastian Blank <waldi@debian.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Konrad Rzeszutek <konrad@darnok.org>, xen-devel@lists.xensource.com
Subject: Re: Re: pvops: i915 kms crashs with corrupt page table
Date: Thu, 25 Feb 2010 11:32:34 +0100 [thread overview]
Message-ID: <20100225103234.GA2324@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <20100225100620.GA31747@wavehammer.waldi.eu.org>
On Thu, Feb 25, 2010 at 11:06:20AM +0100, Bastian Blank wrote:
> On Wed, Feb 24, 2010 at 11:23:37AM -0800, Jeremy Fitzhardinge wrote:
> > On 02/24/2010 09:55 AM, Bastian Blank wrote:
> >> I run a 2.6.32 dom0 kernel (the Debian distribution config). If I enable
> >> KMS in the intel driver, Xorg crashs with corrupt page table.
> > Does this help?
>
> No.
But it is something like that:
intel_i810_configure:
pci_read_config_dword(intel_private.pcidev, I810_GMADDR, &temp);
agp_bridge->gart_bus_addr = (temp & PCI_BASE_ADDRESS_MEM_MASK);
agp_copy_info:
info->aper_base = bridge->gart_bus_addr;
drm_agp_init:
head->base = head->agp_info.aper_base;
dev->agp = head
i915_gem_init_ringbuffer:
ring->map.offset = dev->agp->base + obj_priv->gtt_offset;
This address is directly used to create a userspace mapping.
Bastian
--
Without freedom of choice there is no creativity.
-- Kirk, "The return of the Archons", stardate 3157.4
next prev parent reply other threads:[~2010-02-25 10:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 17:55 pvops: i915 kms crashs with corrupt page table Bastian Blank
2010-02-24 19:23 ` Jeremy Fitzhardinge
2010-02-25 10:06 ` Bastian Blank
2010-02-25 10:32 ` Bastian Blank [this message]
2010-02-26 0:37 ` Jeremy Fitzhardinge
2010-02-26 12:44 ` Bastian Blank
2010-02-26 17:29 ` Jeremy Fitzhardinge
[not found] ` <20100226180545.GC21871@wavehammer.waldi.eu.org>
[not found] ` <4B880EC0.8000803@goop.org>
2010-02-27 0:45 ` Bastian Blank
2010-02-27 1:17 ` Jeremy Fitzhardinge
2010-02-28 12:27 ` Bastian Blank
2010-03-01 8:43 ` Ian Campbell
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=20100225103234.GA2324@wavehammer.waldi.eu.org \
--to=waldi@debian.org \
--cc=jeremy@goop.org \
--cc=konrad@darnok.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;
as well as URLs for NNTP newsgroup(s).