From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, MaoXiaoyun <tinnycloud@hotmail.com>
Cc: xen devel <xen-devel@lists.xensource.com>
Subject: RE: A simple question of CPU emulation in Xen
Date: Fri, 13 May 2011 10:39:09 -0700 (PDT) [thread overview]
Message-ID: <a8a2a8db-bd03-4a5b-8ea2-204631dc3c0f@default> (raw)
In-Reply-To: <20110513155110.56ca976c@lxorguk.ukuu.org.uk>
> From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk]
> Subject: Re: [Xen-devel] A simple question of CPU emulation in Xen
>
> On Fri, 13 May 2011 22:41:44 +0800
> MaoXiaoyun <tinnycloud@hotmail.com> wrote:
>
> >
> > Hi :
> >
> > I have a simple question on CPU emulation in Xen.
> >
> > Currently, inside guest, we can see that the CPU information
> incluing types and frequency is exactly
> > same as physical CPU. Is it possible for Xen(or qemu) to emulate a
> different type of CPU. That is inside
> > guest, we see a different CPU types?
>
> Qemu supports a huge range of CPU and platform emulations,
> www.qemu.org.
> Most of this falls outside of Xen as Qemu doesn't need or benefit from
> Xen or KVM when doing cross cpu emulation.
Also see "MagiXen: Combining Binary Translation and Virtualization"
here: http://www.hpl.hp.com/techreports/2007/HPL-2007-77.html
next prev parent reply other threads:[~2011-05-13 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <COL0-MC1-F16ijYRq7A00088f57@col0-mc1-f16.Col0.hotmail.com>
2011-05-13 14:41 ` A simple question of CPU emulation in Xen MaoXiaoyun
2011-05-13 14:51 ` Alan Cox
2011-05-13 17:39 ` Dan Magenheimer [this message]
2011-05-13 23:41 ` James Harper
2011-05-15 16:48 ` hotmaim
2011-05-16 1:46 ` James Harper
2011-05-16 2:11 ` MaoXiaoyun
2011-05-16 8:04 ` Ian Campbell
2011-05-19 2:15 ` MaoXiaoyun
2011-05-19 6:21 ` Ian Campbell
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=a8a2a8db-bd03-4a5b-8ea2-204631dc3c0f@default \
--to=dan.magenheimer@oracle.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=tinnycloud@hotmail.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 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).