From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eugene Fedotov Subject: Re: [PATCH RFC v2 8/9] xen/arm: Implement hypercall for dirty page tracing (shadow op) Date: Thu, 11 Jul 2013 14:18:38 +0400 Message-ID: <51DE867E.6070103@samsung.com> References: <1372842943-27482-1-git-send-email-jaeyong.yoo@samsung.com> <1372842943-27482-9-git-send-email-jaeyong.yoo@samsung.com> <003a01ce7855$6a6dd820$3f498860$%yoo@samsung.com> <1372927377.7184.7.camel@kazak.uk.xensource.com> <000f01ce789f$c9566a60$5c033f20$%yoo@samsung.com> <1372934187.7184.43.camel@kazak.uk.xensource.com> <51DD7F00.2070407@samsung.com> <1373470754.5453.123.camel@hastur.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-reply-to: <1373470754.5453.123.camel@hastur.hellion.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org Hi. > Either that or perhaps reuse the existing set memory map hypercall? The HVM parameter is easy to implement since we have many of them unused on ARM. I'll think of reusing set_memory_map (this looks like a PV-specific on x86 and compat code for x86-64) > Actually, we should be generating the DTB based on the guest > configuration, rather than parsing the DTB to determine the > configuration IYSWIM. Could guest's device tree generation be done automatically with some tool? Best regards, Evgeny.