contigmalloc won't allocate more than one page

[Super Bisquit]

Why not post this to hackers or the normal questions list to see if anyone
has an x86i machine for testing the code?


On Mon, Jul 22, 2013 at 4:35 PM, Justin Hibbits <jrh29 at alumni.cwru.edu>wrote:

> On Sun, Jul 21, 2013 at 9:54 PM, Konstantin Belousov <kostikbel at gmail.com
> >wrote:
>
> > On Sun, Jul 21, 2013 at 06:51:22PM -0700, Justin Hibbits wrote:
> > > I've been spending the day trying to get ofwdump to work correctly on
> > > ppc64, and found that for at least one property it needs a full page
> for
> > > the property value.  So, to fix this I checked the maximum ioctl sizes,
> > and
> > > with a buffer it totals 5 pages, so I tried to get
> > ofw_real_bounce_alloc()
> > > to allocate 5 pages instead of one.  WIth this, it hangs when
> allocating
> > > the memory for the buffer.  So, I tried just two pages, and got the
> same
> > > result.
> > Could you test on other architectures, esp. on x86i, please ?
> >
>
> Unfortunately for this test, all I have physical access to are PowerPC.
>  It's possible that contigmalloc() can allocate more memory, but possibly
> later in the boot cycle, as this code runs very early on.
>
>
> > What version do you use, head ?
> >
>
> Yes, running head as of a few days ago.
>
> - Justin
> _______________________________________________
> freebsd-ppc at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc
> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe at freebsd.org"
>