[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Remaining ia64 differences in xen driver code -- privcmd


  • To: "Hollis Blanchard" <hollisb@xxxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Fri, 4 Nov 2005 12:34:06 -0800
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 04 Nov 2005 20:34:19 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcXhfgs/rXN2D1CERCCKRfxpjSmRtQAAMB1Q
  • Thread-topic: [Xen-devel] Remaining ia64 differences in xen driver code -- privcmd

> > That makes sense, but currently there is no directory structure
> > to support the archdep/arch-neutral boundaries for xen drivers
> > (so no place to put arch_privcmd_ioctl) other than in header files.
> 
> What do you mean "directory structure"? Just add a prototype to 
> include/asm-xen/linux-public/privcmd.h and implement it somewhere in 
> architecture code. You can add your own files or directories 
> if you like: 
> it's your architecture...

Yes, that will work for this case.  There is another case
that wasn't as easy but, honestly, I can't find it right now :-}
TGIF.

Dan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.