From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dave Airlie <airlied@gmail.com>
Cc: xen-devel@lists.xensource.com,
Zhenyu Wang <zhenyu.z.wang@intel.com>,
Joerg Roedel <joerg.roedel@amd.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
David Woodhouse <dwmw2@infradead.org>,
Keir Fraser <kier.fraser@eu.citrix.com>
Subject: Re: [Xen-devel] Re: [RFC] Make AGP work with IOMMU
Date: Thu, 06 Aug 2009 12:32:22 -0700 [thread overview]
Message-ID: <4A7B2FC6.9070104@goop.org> (raw)
In-Reply-To: <21d7e9970908051612v140c2ebfu591e8fe817237889@mail.gmail.com>
On 08/05/09 16:12, Dave Airlie wrote:
> My main problem with doing this is getting testing coverage on older
> systems, if we change all the AGP drivers, the time to find we busted
> something is probably not until the next major distro release with this code
> in it. So people can run stuff on 5 year old hardware in 6 months? I'm
> not sure the gains justify the costs, but if you guys really want to do it
> I'll take the patch, just be prepared to have it ripped out the minute
> we get a regression we can't figure out because we haven't got the hw anymore.
>
Can you point to some changesets/patches to act as an example/template
for the changes needed?
If we come up with someone reporting crashes when using old hardware, we
can then make change then get them to test both native and Xen.
J
next prev parent reply other threads:[~2009-08-06 19:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 15:04 [RFC] Make AGP work with IOMMU David Woodhouse
2009-07-29 6:28 ` Dave Airlie
2009-07-29 7:15 ` David Woodhouse
2009-07-29 8:43 ` Dave Airlie
2009-07-29 9:01 ` David Woodhouse
2009-07-29 9:36 ` David Woodhouse
2009-08-03 6:50 ` Zhenyu Wang
2009-08-03 8:39 ` David Woodhouse
2009-08-04 23:52 ` [Xen-devel] " Jeremy Fitzhardinge
2009-08-05 6:44 ` David Woodhouse
2009-08-05 6:57 ` Dave Airlie
2009-08-05 7:08 ` David Woodhouse
2009-08-05 18:26 ` Jeremy Fitzhardinge
2009-08-05 23:12 ` Dave Airlie
2009-08-06 19:32 ` Jeremy Fitzhardinge [this message]
2009-08-06 19:36 ` David Woodhouse
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=4A7B2FC6.9070104@goop.org \
--to=jeremy@goop.org \
--cc=airlied@gmail.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--cc=kier.fraser@eu.citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
--cc=zhenyu.z.wang@intel.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