From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
dri-devel@lists.sourceforge.net, xen-devel@lists.xensource.com,
Jan Beulich <JBeulich@novell.com>
Subject: Re: Re: ATI radeon fails with "iommu=soft swiotlb=force" (seen on RV730/RV740 and RS780/RS800)
Date: Mon, 5 Oct 2009 10:49:03 -0400 [thread overview]
Message-ID: <20091005144903.GA3991@phenom.dumpdata.com> (raw)
In-Reply-To: <a728f9f90910050741h5ec2ed99q45c26954db33eef1@mail.gmail.com>
On Mon, Oct 05, 2009 at 10:41:04AM -0400, Alex Deucher wrote:
> On Mon, Oct 5, 2009 at 10:01 AM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> > On Mon, Oct 05, 2009 at 11:32:31AM +0100, Jan Beulich wrote:
> >> >>> Jeremy Fitzhardinge <jeremy@goop.org> 02.10.09 20:42 >>>
> >> >On 10/02/09 10:23, Boris Derzhavets wrote:
> >> >> Jeremy,
> >> >> Please, be aware of bugzilla.xensource.com [1519] the most recent
> >> >> entries :-
> >> >>
> >> >> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1519
> >> >>
> >> >
> >> >Ah, OK. I pushed a variant of Konrad's patches. Could you try them out?
> >>
> >> Are you really convinced fixing this in DRM is the right thing to do? To
> >> me, the use of vmalloc_32() in drivers/ieee1394/ seems to make similar
> >> assumptions (pci_map_sg() not modifying the buffer addresses), and
> >> who knows where else such assumptions exist. After all, vmalloc_32()
> >> is *defined* to have the property assumed by both of the users, and
> >> other than for most kmalloc() cases using GFP_DMA{,32} we're talking
> >> about double buffering generally large amounts of data here even in
> >> the cases where the DMA API is being used properly.
> >
> > I was chatting with Jeremy about this, and I realized that in some
> > sense the radeon driver assumes that physical != bus addresses. Which is
> > OK on x86, but if this card was ever moved to a Sun box it would fail.
> >
>
> FWIW, the radeon drm has been working fine on both sparc and ppc for years.
Thank you for keeping me honest!
I thought that the IOMMU on those boxes would return physical != bus addresses?
Maybe those days are long gone?
next prev parent reply other threads:[~2009-10-05 14:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 6:58 Re: ATI radeon fails with "iommu=soft swiotlb=force" (seen on RV730/RV740 and RS780/RS800) Boris Derzhavets
2009-10-02 17:18 ` Jeremy Fitzhardinge
2009-10-02 17:23 ` Boris Derzhavets
2009-10-02 18:42 ` Jeremy Fitzhardinge
2009-10-02 19:25 ` Boris Derzhavets
2009-10-05 10:32 ` Jan Beulich
2009-10-05 14:01 ` Konrad Rzeszutek Wilk
2009-10-05 14:37 ` Konrad Rzeszutek Wilk
2009-10-05 19:12 ` Jeremy Fitzhardinge
2009-10-05 14:41 ` [Xen-devel] " Alex Deucher
2009-10-05 14:49 ` Konrad Rzeszutek Wilk [this message]
2009-10-05 14:54 ` Alex Deucher
2009-10-05 19:09 ` Jeremy Fitzhardinge
2009-10-06 8:10 ` Jan Beulich
2009-10-06 19:01 ` Jeremy Fitzhardinge
[not found] <20090930152149.GA29603@phenom.dumpdata.com>
2009-10-01 17:35 ` Konrad Rzeszutek Wilk
2009-10-01 19:07 ` Jeremy Fitzhardinge
2009-10-01 19:21 ` Konrad Rzeszutek Wilk
2009-10-02 12:52 ` Jan Beulich
2009-10-02 14:44 ` Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2009-10-02 5:02 Boris Derzhavets
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=20091005144903.GA3991@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@novell.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=jeremy@goop.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 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.