|
|
|
|
|
|
|
|
|
|
xen-ia64-devel
RE: [Xen-ia64-devel] [PATCH] Another important Xen/ia64 domU/vbd fix
> > > >If Xen requires virtual_mem_map, then dom0 will require it too.
> > > >Since dom0 can't work yet with virtual_mem_map, enabling it
> > >
> > > in Xen is moot,
> > >
> > > >isn't it ?
> > > >
> > > >Tristan.
> >
> > Yes, I agree. For virtual_mem_map to work, I think domain0
> > needs to be given a granule of physical memory for each "island"
> > in the EFI memmap.
> I think this is a little bit too kludgy...
Definitely. I'm just looking for temporary workarounds to
allow forward progress. Even if a p2m table is the right
answer, it will be weeks (maybe months) before the implementation
is done and Xen/i164 is as stable/functional as it is today.
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-ia64-devel] [PATCH] Another important Xen/ia64 domU/vbd fix, Tian, Kevin
- RE: [Xen-ia64-devel] [PATCH] Another important Xen/ia64 domU/vbd fix, Tian, Kevin
- RE: [Xen-ia64-devel] [PATCH] Another important Xen/ia64 domU/vbd fix, Magenheimer, Dan (HP Labs Fort Collins)
- RE: [Xen-ia64-devel] [PATCH] Another important Xen/ia64 domU/vbd fix, Tian, Kevin
- RE: [Xen-ia64-devel] [PATCH] Another important Xen/ia64 domU/vbd fix, Magenheimer, Dan (HP Labs Fort Collins)
- RE: [Xen-ia64-devel] [PATCH] Another important Xen/ia64 domU/vbd fix,
Magenheimer, Dan (HP Labs Fort Collins) <=
|
|
|
|
|