From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <JBeulich@suse.com>
Subject: Re: [V6 PATCH 6.2/7] pvh dom0: Add and remove foreign
 pages
Date: Mon, 16 Dec 2013 07:47:18 +0000
Message-ID: <52AEBE16020000780010D6E1@nat28.tlf.novell.com>
References: <1386297524-15483-1-git-send-email-mukesh.rathor@oracle.com>
	<1386297524-15483-7-git-send-email-mukesh.rathor@oracle.com>
	<20131210162753.2e402081@mantra.us.oracle.com>
	<20131210164442.3879f6c0@mantra.us.oracle.com>
	<52A7C14C.2020504@linaro.org>
	<20131210174755.05e5550f@mantra.us.oracle.com>
	<20131211142903.GB6450@deinos.phlegethon.org>
	<20131211184606.4f0d9366@mantra.us.oracle.com>
	<20131212184449.77cc02db@mantra.us.oracle.com>
	<20131213112548.GA57692@deinos.phlegethon.org>
	<52AB000F020000780010CF63@nat28.tlf.novell.com>
	<52AB59B0.9090103@eu.citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <52AB59B0.9090103@eu.citrix.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: George Dunlap <george.dunlap@eu.citrix.com>, Mukesh Rathor <mukesh.rathor@oracle.com>, Tim Deegan <tim@xen.org>
Cc: Xen-devel@lists.xensource.com, Ian Campbell <Ian.Campbell@citrix.com>, Julien Grall <julien.grall@linaro.org>, eddie.dong@intel.com, keir.xen@gmail.com, jun.nakajima@intel.com
List-Id: xen-devel@lists.xenproject.org

>>> On 13.12.13 at 20:02, George Dunlap <george.dunlap@eu.citrix.com> wrote:
> On 12/13/2013 11:39 AM, Jan Beulich wrote:
>>>>> On 13.12.13 at 12:25, Tim Deegan <tim@xen.org> wrote:
>>> Also, Jan may have an opinion about whether a teardown operation that
>>> has to walk each p2m entry would have to be made preemptible.  I'm not
>>> sure where we draw the line on such things.
>> There's no line here - "each" is too much in any case.
> 
> By which you mean, yes a teardown operation that has to walk each p2m 
> entry does need to be made pre-emptible?
> 
> It that's not what you mean, I'm at a loss for an interpretation of the 
> above sentence. :-)

Any operation - teardown or other - that needs to walk all of a
domain's pages has to be preemptible. So yes, your interpretation
of my earlier response was right.

Jan