From: Dietmar Hahn <dietmar.hahn@ts.fujitsu.com>
To: xen-devel@lists.xen.org, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Issues with Intel HD graphics 4000
Date: Wed, 19 Jun 2013 13:36:56 +0200 [thread overview]
Message-ID: <6238960.KT93hsGIxD@amur> (raw)
In-Reply-To: <17149542.8Y7bGvdKBY@amur>
Am Dienstag 18 Juni 2013, 13:37:08 schrieb Dietmar Hahn:
> Am Montag 17 Juni 2013, 09:14:30 schrieb Konrad Rzeszutek Wilk:
>
> > Hey Dietmar,
> >
> > Did you ever test the extra change for the debug patch?
> >
> > http://lists.xenproject.org/archives/html/xen-devel/2013-05/msg02051.html
> > "
> > I tried both but none helped. I think it couldn't be expected as the first
> > > patch handles an error case and the line with the second patch,
> > > the call of pci_dma_sync_single_for_device(), gets not reached.
> >
> > OK, perhaps move the pci_dma_sync_single_for_device in the while loop?
> >
> > " ?
>
> I believe I did and I think it didn't work but I'am not sure and so I'll try
> again. But this will take some time as the PC is used for my daily work!
OK, tried again today and as expected it didn't work. Following code:
linux-3.7.10-1.11/drivers/char/agp/intel-gtt.c:
void intel_gtt_clear_range(unsigned int first_entry, unsigned int num_entries)
{
unsigned int i;
intel_private.driver->write_entry(intel_private.base.scratch_page_dma,
first_entry, 0);
printk(KERN_WARNING "HAHN-%s: sync the first page\n", __func__);
pci_dma_sync_single_for_device(intel_private.pcidev,
intel_private.base.scratch_page_dma,
PAGE_SIZE, PCI_DMA_BIDIRECTIONAL);
for (i = first_entry + 1; i < (first_entry + num_entries); i++) {
intel_private.driver->write_entry(intel_private.base.scratch_page_dma,
i, 0);
pci_dma_sync_single_for_device(intel_private.pcidev,
intel_private.base.scratch_page_dma,
PAGE_SIZE, PCI_DMA_BIDIRECTIONAL);
}
printk(KERN_WARNING "HAHN-%s: End of loop\n", __func__);
readl(intel_private.gtt+i-1);
}
The second printk() with "End of loop" is not reached.
Dietmar.
--
Company details: http://ts.fujitsu.com/imprint.html
next prev parent reply other threads:[~2013-06-19 11:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 19:46 Issues with Intel HD graphics 4000 Joshua Tuttle
2013-06-15 0:30 ` Andrew Bobulsky
2013-06-17 7:04 ` Dietmar Hahn
2013-06-17 13:14 ` Konrad Rzeszutek Wilk
2013-06-18 11:37 ` Dietmar Hahn
2013-06-19 11:36 ` Dietmar Hahn [this message]
2013-06-19 16:25 ` Konrad Rzeszutek Wilk
2013-06-24 8:21 ` Dietmar Hahn
2013-06-17 14:56 ` Joshua Tuttle
2013-06-15 9:28 ` Pasi Kärkkäinen
2013-06-17 13:13 ` Konrad Rzeszutek Wilk
2013-06-17 13:20 ` jacek burghardt
2013-06-17 14:47 ` Konrad Rzeszutek Wilk
2013-06-17 15:02 ` Joshua Tuttle
2013-06-17 15:24 ` Ben Guthro
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=6238960.KT93hsGIxD@amur \
--to=dietmar.hahn@ts.fujitsu.com \
--cc=konrad.wilk@oracle.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 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.