[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] making changes to agp code?


  • To: "Jan Beulich" <jbeulich@xxxxxxxxxx>
  • From: "Langsdorf, Mark" <mark.langsdorf@xxxxxxx>
  • Date: Wed, 28 Mar 2007 17:37:49 -0500
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 28 Mar 2007 15:36:54 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdxUYN0J411nXaaScy+OBv05hhbTwAN/o5Q
  • Thread-topic: [Xen-devel] making changes to agp code?

> >> On a second look I believe the implementation is broken even 
> >> on native, as long as !CONFIG_FLATMEM, since there's an
> >> assumption that an invalid PFN cannot be followed by a valid
> >> one. For that reason, I think the code needs to be changed to
> >> call e820_any_mapped() (just like aperture.c does). I have a
> >> tentative patch to do that, but don't have a working box with
> >> an 8151.
> >
> >I do.  You can send it to me for testing.
> 
> Attached - depending on what tree you want to apply it on you
> may have to tweak it a little.

I applied it to xen-unstable with some tweaking (my version
doesn't seem to have an i386 e820-xen.c ??) and to 2.6.20.

System booted correctly and ran fine.

Acked-by: Mark Langsdorf <mark.langsdorf@xxxxxxx>

-Mark Langsdorf
Operating Systems Research Center
AMD, Inc.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.