| |
|
 |
|
 |
|
|
|
| |
|
|
xen-ia64-devel
Re: [Xen-ia64-devel] [PATCH] discontig memory support
Hi Alex,
I confirmed the same Oops as you.
I'll try to investigate this.
BTW, I think that it is unnecessary to support large holes on
dom0 in p2m/vp model. Or dom0 still requires to be configured with
virtual memory map because of MMIO. Is it true?
Thanks,
Kouya
Alex Williamson writes:
> On Fri, 2006-04-14 at 21:08 +0900, Kouya SHIMURA wrote:
> > Hi all,
> >
> > Sorry for the delay.
> > I'll post the revised patches to support discontiguous physical memory.
>
> Hi Kouya,
>
> This seems to be working pretty well. I'm able to boot a zx1 system
> and see all of the memory! A quick test showed no performance change in
> dom0 kernel build times, I still need to check domU. One, perhaps
> expected, side-effect of this patch is that dom0 is now given a memory
> map that requires it to be configured with virtual memory map (or one of
> the other flavors of memory supporting large holes). Unfortunately we
> seem to have an outstanding issue that a dom0 kernel configured with
> these options Oops when booting domU. The Oops is a page fault in the
> loop driver and seems to hit when the vbd frontend in domU tries to
> attach. Has anyone else seen this? AFAICT, it happens with or without
> this patch applied to Xen. Thanks,
>
> Alex
>
> --
> Alex Williamson HP Linux & Open Source Lab
>
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
|
|
| |
|
Home