On Jul 9, 2007, at 4:23 PM, Jimi Xenidis wrote:
On Jul 9, 2007, at 3:41 PM, Hollis Blanchard wrote:
On Mon, 2007-07-09 at 20:26 +0100, Keir Fraser wrote:
On 9/7/07 20:20, "Hollis Blanchard" <hollisb@xxxxxxxxxx> wrote:
By the way, I wonder how PPC manages to build both drivers/char/
mem.c and
drivers/xen/char/mem.c without ARCH_HAS_DEV_MEM? The model is
supposed to be
that mem_fops defined by the Xen file is picked up by the
generic file. If
!ARCH_HAS_DEV_MEM then that doesn't happen -- so who picks up
the Xen
mem_fops?
Hmmm, yeah. Looks like we haven't tested that... :)
yeah, we have :)
xlate_dev_mem_ptr() works just fine for us, so drivers/char/mem.c
just works and the xen version of the ops is never considered.
Actually we should be forcing CONFIG_XEN_DEVMEM, but the Makefile
ignores it.
s/CONFIG_XEN_DEVMEM/CONFIG_XEN_DEVMEM=n/
-JX
_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ppc-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|