Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: RE: Introducing paravirt_ops for x86_64
Date: Wed, 8 Aug 2007 07:53:43 -0700
Message-ID: <97D612E30E1F88419025B06CB4CF1BE10326E129@scsmsx412.amr.corp.intel.com>
In-Reply-To: <11865467522495-git-send-email-gcosta@redhat.com>
Thread-Topic: Introducing paravirt_ops for x86_64
thread-index: AcfZiui69WjRuAQ5RC6WyxK38acLtAAPrVaQ
From: "Nakajima, Jun" <jun.nakajima@intel.com>
To: "Glauber de Oliveira Costa" <gcosta@redhat.com>,
       <linux-kernel@vger.kernel.org>
Cc: <lguest@ozlabs.org>, <virtualization@lists.linux-foundation.org>,
       <chrisw@sous-sol.org>, <anthony@codemonkey.ws>,
       <akpm@linux-foundation.org>, <mingo@elte.hu>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 758
Lines: 23

Glauber de Oliveira Costa wrote:
> Hi folks,
> 
> After some time away from it, and a big rebase as a consequence, here
is
> the updated version of paravirt_ops for x86_64, heading to inclusion.
> 
> Your criticism is of course, very welcome.
> 
> Have fun

Do you assume that the kernel ougtht to use 2MB pages for its mappings
(e.g. initilal text/data,  direct mapping of physical memory) under your
paravirt_ops?  As far as I look at the patches, I don't find one. 

Jun
---
Intel Open Source Technology Center
-
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/