All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eugene Fedotov <e.fedotov@samsung.com>
To: xen-devel@lists.xen.org
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	[thread overview]
Message-ID: <51DE867E.6070103@samsung.com> (raw)
In-Reply-To: <1373470754.5453.123.camel@hastur.hellion.org.uk>

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.

  reply	other threads:[~2013-07-11 10:18 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03  9:15 [PATCH RFC v2 0/9] Preliminary working version of live migration Jaeyong Yoo
2013-07-03  9:15 ` [PATCH RFC v2 1/9] xen-arm: Implement basic save/load for hvm context Jaeyong Yoo
2013-07-03 11:29   ` Stefano Stabellini
2013-07-03 23:51     ` Jaeyong Yoo
2013-07-03  9:15 ` [PATCH RFC v2 2/9] xen/arm: Implement save and restore for gic, vtimer, and ptimer Jaeyong Yoo
2013-07-03 11:29   ` Stefano Stabellini
2013-07-03 23:53     ` Jaeyong Yoo
2013-07-03  9:15 ` [PATCH RFC v2 3/9] xen/arm: Add more registers for saving and restoring vcpu registers Jaeyong Yoo
2013-07-03 11:29   ` Stefano Stabellini
2013-07-03  9:15 ` [PATCH RFC v2 4/9] xen/arm: Implement get_maximum_gpfn hypercall for arm Jaeyong Yoo
2013-07-03 11:29   ` Stefano Stabellini
2013-07-03 11:35     ` Ian Campbell
2013-07-04  0:09       ` Jaeyong Yoo
2013-07-04  8:47         ` Ian Campbell
2013-07-03  9:15 ` [PATCH RFC v2 5/9] xen/arm: Implement modify_returncode Jaeyong Yoo
2013-07-03  9:15 ` [PATCH RFC v2 6/9] xen/arm: Add handling write fault for dirty-page tracing Jaeyong Yoo
2013-07-03 12:10   ` Stefano Stabellini
2013-07-04  0:44     ` Jaeyong Yoo
2013-07-03 12:26   ` Ian Campbell
2013-07-04  1:02     ` Jaeyong Yoo
2013-07-04  7:21       ` Jaeyong Yoo
2013-07-04  8:46       ` Ian Campbell
2013-07-04 11:47         ` Jaeyong Yoo
2013-07-05  4:42         ` Jaeyong Yoo
2013-07-07 16:53           ` Ian Campbell
2013-07-12  0:54             ` Jaeyong Yoo
2013-07-03  9:15 ` [PATCH RFC v2 7/9] xen/arm: Missing impl of clear_guest_offset macro Jaeyong Yoo
2013-07-03 11:37   ` Stefano Stabellini
2013-07-03 11:57     ` Ian Campbell
2013-07-04  0:09     ` Jaeyong Yoo
2013-07-03  9:15 ` [PATCH RFC v2 8/9] xen/arm: Implement hypercall for dirty page tracing (shadow op) Jaeyong Yoo
2013-07-03 12:38   ` Stefano Stabellini
2013-07-04  1:25     ` Jaeyong Yoo
2013-07-04  8:42       ` Ian Campbell
2013-07-04 10:18         ` Jaeyong Yoo
2013-07-04 10:29           ` Stefano Stabellini
2013-07-04 10:36             ` Ian Campbell
2013-07-10 15:34               ` Eugene Fedotov
2013-07-10 15:39                 ` Ian Campbell
2013-07-11 10:18                   ` Eugene Fedotov [this message]
2013-07-11 11:24                     ` Ian Campbell
2013-07-03  9:15 ` [PATCH RFC v2 9/9] xen/arm: Implement toolstack for xl restore/save and migrate Jaeyong Yoo
2013-07-03  9:21 ` [PATCH RFC v2 0/9] Preliminary working version of live migration Ian Campbell
2013-07-03 12:54 ` Stefano Stabellini

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=51DE867E.6070103@samsung.com \
    --to=e.fedotov@samsung.com \
    --cc=xen-devel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.