[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] What is domain creation flow-chart in XEND
Hello folks how does XEND pass the information abt the control channel in DomainU??. I see xc_linux_build() function does set the control channel info, but I do not see anybody in XEND using xc_linux_build (). Am I correct ?? >From what I am understanding x2d2 is like a miniXend for testing purposes. The actual XEND does NOT communicate with x2d2. Thanks Nauzad On Sun, 16 Jan 2005 01:06:23 +0000, Mark Williamson <maw48@xxxxxxxxxxxx> wrote: > > From what I can tell, Linux always listens on event channel 1. So, > > Xend just binds a local port to the domains port 1. After binding, it > > maps a shared memory region and works on a ring queue passing back and > > forth control_msg_t structures. This is how virtual devices are setup. > > > > I imagine each device gets it's own channel but I do not know for sure. > > Every domain has a "control interface" as you described, which is used for low > bandwidth communications (console and various configuration messages). > Amongst other things, the control channel is used to negotiate the locations > of shared memory pages that the network and block drivers can use for > high-bandwidth communications. > > > The domain's kernel I believe. > > See linux-2.6.10-sparse/arch/xen/kernel/ctrl_if.c and > linux-2.6.10-sparse/include/asm-xen/ctrl_if.h for code relating to the kernel > control interface driver. > > > >If someone can point me to some document for more details I would > > > appreciate it > > Andy wrote an explanation of how the block device drivers work. It's in > docs/misc/blkif-drivers-explained.txt. You might find some pertinent > information there, particularly when you look at how the drivers talk to each > other. > > HTH, > Mark > > > I posted some documentation to xc.h. This is where most of this work is > > done. I don't know of any documentation. The bulk of all this is done > > in libxc, xu.c (this binding implements a bunch of functionality), and > > x2d2 (this isn't used by Xend but is a bit easier to understand than Xend). > > > > Regards, > > > > >Thanks > > > > > >Nauzad > > > > > > > > >------------------------------------------------------- > > >The SF.Net email is sponsored by: Beat the post-holiday blues > > >Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > > >It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > > >_______________________________________________ > > >Xen-devel mailing list > > >Xen-devel@xxxxxxxxxxxxxxxxxxxxx > > >https://lists.sourceforge.net/lists/listinfo/xen-devel > > > > ------------------------------------------------------- > > The SF.Net email is sponsored by: Beat the post-holiday blues > > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@xxxxxxxxxxxxxxxxxxxxx > > https://lists.sourceforge.net/lists/listinfo/xen-devel > ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |