contigmalloc won't allocate more than one page

Justin Hibbits jrh29 at alumni.cwru.edu
Tue Jul 23 14:25:49 UTC 2013


On Mon, Jul 22, 2013 at 8:39 PM, Super Bisquit <superbisquit at gmail.com>wrote:

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

Because my initial assumption was that it was ppc only.

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 ?
>> >
>>
>
Turns out this was noise only.  I had adjusted the size but not the
boundary.  Adjusting the boundary fixed it.

- Justin


More information about the freebsd-ppc mailing list