* Zachary Amsden ([EMAIL PROTECTED]) wrote: > William Lee Irwin III wrote: > >>clone_pgd_range() for consistency? and it seems we lost a > >>paravirt_alloc_pd_clone() in there somewhere. > >> > > > >Yes, another reason why it shouldn't have been posted as-is. It was not > >intended to for anything more than comparative benchmarking on systems > >without graphics running on the bare metal as opposed to Xen/etc. guests. > > > > So clone_pgd_range is mostly useless now. Originally, I intended it to > take the part of paravirt_alloc_pd_clone. We should probably merge the > two into just one function, unless someone thinks clone_pgd_range is > actually useful for something.
No, I was going to suggest just that. It was orginially introduced as the place holder for that IIRC. thanks, -chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/