Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1946245AbXBPVNp (ORCPT ); Fri, 16 Feb 2007 16:13:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1946247AbXBPVNp (ORCPT ); Fri, 16 Feb 2007 16:13:45 -0500 Received: from netops-testserver-3-out.sgi.com ([192.48.171.28]:37582 "EHLO netops-testserver-3.corp.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1946245AbXBPVNo (ORCPT ); Fri, 16 Feb 2007 16:13:44 -0500 Date: Fri, 16 Feb 2007 13:13:43 -0800 (PST) From: Christoph Lameter To: Zachary Amsden cc: Jeremy Fitzhardinge , Andi Kleen , Andrew Morton , linux-kernel@vger.kernel.org, virtualization@lists.osdl.org, xen-devel@lists.xensource.com, Chris Wright Subject: Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface In-Reply-To: <45D61C74.2000601@vmware.com> Message-ID: References: <20070216022449.739760547@goop.org> <45D61C74.2000601@vmware.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 700 Lines: 15 On Fri, 16 Feb 2007, Zachary Amsden wrote: > For the most part, it doesn't disturb VMware or KVM. Xen does need some > additional functionality in paravirt-ops because they took a different design > choice - direct page tables instead of shadow page tables. This is where all > the requirements for the new Xen paravirt-ops hooks come from. It still seems to be implemented for Xen and not to support a variety of page table methods in paravirt ops. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/