All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Liu John <bradevuu@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Implementation choices, XEN or KVM?
Date: Mon, 27 Jun 2011 08:50:13 +0100	[thread overview]
Message-ID: <4E083635.5020104@citrix.com> (raw)
In-Reply-To: <BANLkTi=j7dWC3vxPtymMHPpoYRyCORxcqQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 697 bytes --]



On 24/06/11 21:56, Liu John wrote:
> Hello all,
>
> I will do research experiment using hypervisor. But I have not decided
> the platform; both XEN and KVM work for me(my work is about MMU,
> specifically shadow page tables). Though I prefer XEN, it seems XEN
> development and debugging are not easy. For example, every time you
> add some code in hypervisor, you have to restart computer.
>
> I appreciate your suggestion.
>
>
> Thanks
> Liu, John 

I am curious to know under what circumstances you think it is, or should
be possible to make hypervisor code changes without rebooting?

-- 
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com


[-- Attachment #1.2: Type: text/html, Size: 1435 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2011-06-27  7:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24 20:56 Implementation choices, XEN or KVM? Liu John
2011-06-27  7:50 ` Andrew Cooper [this message]
2011-06-27  9:45   ` George Dunlap
2011-06-27  8:46 ` Tim Deegan
2011-06-27 10:25   ` James Harper
2011-06-27 10:30     ` Tim Deegan
2011-06-27 10:30   ` Wei Liu
2011-06-27 10:40     ` Tim Deegan
2011-06-28 12:53       ` Andre Przywara

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=4E083635.5020104@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=bradevuu@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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.