From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.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
Subject: Re: [V6 PATCH 6.2/7] pvh dom0: Add and remove foreign pages
Date: Fri, 13 Dec 2013 19:02:08 +0000 [thread overview]
Message-ID: <52AB59B0.9090103@eu.citrix.com> (raw)
In-Reply-To: <52AB000F020000780010CF63@nat28.tlf.novell.com>
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. :-)
-George
next prev parent reply other threads:[~2013-12-13 19:02 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 2:38 [V6 PATCH 0/7]: PVH dom0 Mukesh Rathor
2013-12-06 2:38 ` [V6 PATCH 1/7] pvh dom0: move some pv specific code to static functions Mukesh Rathor
2013-12-06 2:38 ` [V6 PATCH 2/7] pvh dom0: construct_dom0 changes Mukesh Rathor
2013-12-06 2:38 ` [V6 PATCH 3/7] pvh dom0: implement XENMEM_add_to_physmap_range for x86 Mukesh Rathor
2013-12-06 2:38 ` [V6 PATCH 4/7] pvh dom0: Introduce p2m_map_foreign Mukesh Rathor
2013-12-09 12:02 ` Tim Deegan
2013-12-06 2:38 ` [V6 PATCH 5/7] pvh: change xsm_add_to_physmap Mukesh Rathor
2013-12-06 2:38 ` [V6 PATCH 6/7] pvh dom0: Add and remove foreign pages Mukesh Rathor
2013-12-06 2:54 ` Mukesh Rathor
2013-12-06 11:46 ` Jan Beulich
2013-12-07 2:09 ` Mukesh Rathor
2013-12-07 2:34 ` [V6 PATCH 6.1/7] " Mukesh Rathor
2013-12-07 16:06 ` Julien Grall
2013-12-09 9:50 ` Jan Beulich
2013-12-10 1:30 ` Mukesh Rathor
2013-12-09 10:31 ` Ian Campbell
2013-12-09 13:46 ` Julien Grall
2013-12-09 12:11 ` Tim Deegan
2013-12-10 2:16 ` Mukesh Rathor
2013-12-09 2:45 ` [V6 PATCH 6/7] " Julien Grall
2013-12-09 2:57 ` Julien Grall
2013-12-10 2:17 ` Mukesh Rathor
2013-12-11 0:27 ` [V6 PATCH 6.2/7] " Mukesh Rathor
2013-12-11 0:44 ` Mukesh Rathor
2013-12-11 1:35 ` Julien Grall
2013-12-11 1:47 ` Mukesh Rathor
2013-12-11 9:23 ` Jan Beulich
2013-12-11 14:29 ` Tim Deegan
2013-12-12 2:46 ` Mukesh Rathor
2013-12-13 2:44 ` Mukesh Rathor
2013-12-13 11:25 ` Tim Deegan
2013-12-13 11:39 ` Jan Beulich
2013-12-13 19:02 ` George Dunlap [this message]
2013-12-16 7:47 ` Jan Beulich
2013-12-14 2:48 ` Mukesh Rathor
2013-12-16 8:40 ` Jan Beulich
2013-12-16 23:27 ` Mukesh Rathor
2013-12-16 23:44 ` Julien Grall
2013-12-17 1:51 ` Mukesh Rathor
2013-12-17 2:33 ` Mukesh Rathor
2013-12-17 10:10 ` Tim Deegan
2013-12-17 23:24 ` Mukesh Rathor
2013-12-18 2:34 ` Mukesh Rathor
2013-12-18 9:51 ` Jan Beulich
2013-12-18 9:53 ` Tim Deegan
2013-12-06 2:38 ` [V6 PATCH 7/7] pvh dom0: add opt_dom0pvh to setup.c Mukesh Rathor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52AB59B0.9090103@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=Xen-devel@lists.xensource.com \
--cc=eddie.dong@intel.com \
--cc=julien.grall@linaro.org \
--cc=jun.nakajima@intel.com \
--cc=keir.xen@gmail.com \
--cc=mukesh.rathor@oracle.com \
--cc=tim@xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).