On Fri, 17 Sep 2010, Blue Swirl wrote:
> On Fri, Sep 17, 2010 at 11:15 AM, <anthony.perard@xxxxxxxxxx> wrote:
> > From: Anthony PERARD <anthony.perard@xxxxxxxxxx>
> >
> > Open and bind event channels; map ioreq and buffered ioreq rings.
>
> In general, because of CPUState accesses and cpu_in/out use, this
> looks like CPU code, specifically x86. Could this belong to
> target-i386/xen.c instead, much like target-i386/kvm.c vs ./kvm-all.c?
> Do other CPU types use this stuff?
>
Even though it might look like CPU code, this code only deals with IO
events from xen on behalf of the guest.
In fact it runs as it is on ia64 AFAIK.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home