|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] question on the evtchan stuff
Yes, pretty much. I/O will require you to implement virtual drivers
based on interdomain communications (i.e., shared memory + inter-domin
event channels). You could perhaps get some mileage out of the Linux
drivers though (also, using those will allow you to track changes in
the API as we move towards a 2.0 release of Xen).
-- Keir
>
> I'm assuming that for an early port of an OS to Xen I need only worry
> about the VIRQs in evtchan, is this mostly right? I.e. I need not worry
> about PIRQs for the initial cut since it is a guest, not DOM0.
>
> ron
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/xen-devel
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
|
|
|
|