From: Anh Nguyen <nguyenminhanh@gmail.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: xen-devel@lists.xensource.com,
Stefano Stabellini <stefano@stabellini.net>
Subject: Re: a xen question
Date: Thu, 6 May 2010 13:45:14 -0700 [thread overview]
Message-ID: <j2xf90f1ab01005061345x65848895v3d22f4e2a014eeec@mail.gmail.com> (raw)
In-Reply-To: <j2pde76405a1005061336sc7d1965dye456febef5d0b707@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1942 bytes --]
Hi George,
I am interested in the xen-linux kernel for PV guests.
For HVM guests, I find it a bit difficult to pinpoint exactly what devices
are enabled because the ioemu-qemu-xen directory inside xen source seems to
contain a lot of code not used by xen.
Thanks,
On Thu, May 6, 2010 at 1:36 PM, George Dunlap
<George.Dunlap@eu.citrix.com>wrote:
> Ahn, the backends and frontends depends on which version of the kernel
> you're using. Do you want to look at the pv-ops kernel (the long-term
> future), or the xen-linux kernel (a fork which will never make it
> as-is into Linux, but is ATM more widely used)?
>
> Stefano, which devices are enabled in qemu in our Xen tree? Can you
> give Anh some pointers on how to find out which files correspond to
> those devices? Thanks!
>
> -George
>
> On Sun, May 2, 2010 at 12:47 AM, Anh Nguyen <nguyenminhanh@gmail.com>
> wrote:
> > Hi George,
> > I want to measure the size of Xen virtual devices (in term of lines of
> > code), for both HVM and PV guests. From what I learnt, Xen uses
> > Qemu daemon running in Dom 0 to emulate virtual devices for HVM guests.
> For
> > PV guests, backend devices in Dom 0 talks to frontend devices in Dom U.
> > I tried to post this question to xen-devel list but they did not go
> through.
> > I would really appreciate if you could help me to answer them, or point
> me
> > to the right direction:
> > 1. What devices are offered to Xen HVM guests, what about Xen PV guests?
> > 2. Where can I find the source code for those devices?
> > Thanks a lot,
> > Anh
> >
> > On Sat, May 1, 2010 at 5:18 PM, Sam King <kingst@uiuc.edu> wrote:
> >>
> >> Hi George,
> >>
> >> One of my students, Anh (included in this email), has some questions
> about
> >> Xen. He has tried posting to the newsgroup without much luck, I was
> hoping
> >> that you could either answer his questions or point him in the right
> >> direction.
> >>
> >> Cheers,
> >> Sam
> >
> >
>
[-- Attachment #1.2: Type: text/html, Size: 2631 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-05-06 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BDCC4EC.5070704@uiuc.edu>
[not found] ` <i2mf90f1ab01005012247kef06f908jbda998be2eb071c8@mail.gmail.com>
2010-05-06 20:36 ` a xen question George Dunlap
2010-05-06 20:45 ` Anh Nguyen [this message]
2010-05-07 10:56 ` Stefano Stabellini
2010-05-07 21:13 ` Anh Nguyen
2010-05-07 21:14 ` Anh Nguyen
2010-05-10 9:20 ` 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=j2xf90f1ab01005061345x65848895v3d22f4e2a014eeec@mail.gmail.com \
--to=nguyenminhanh@gmail.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=stefano@stabellini.net \
--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).