From: Keir Fraser <keir@xensource.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: Jun Kamada <kama@jp.fujitsu.com>,
xen-devel@lists.xensource.com,
xen-ppc-devel <xen-ppc-devel@lists.xensource.com>
Subject: Re: Re: [Xen-changelog] [linux-2.6.18-xen] Add "#ifdef ARCH_HAS_DEV_MEM" to archtecture specific file_operations.
Date: Mon, 09 Jul 2007 20:26:36 +0100 [thread overview]
Message-ID: <C2B84A7C.A8F1%keir@xensource.com> (raw)
In-Reply-To: <1184008821.26508.56.camel@basalt>
On 9/7/07 20:20, "Hollis Blanchard" <hollisb@us.ibm.com> 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... :)
If you don't need to build both then there is potentially no problem with
the Xen file hijacking the xlate_dev_mem() functions.
-- Keir
next prev parent reply other threads:[~2007-07-09 19:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200707061715.l66HF2Ns030133@xenbits.xensource.com>
2007-07-06 20:25 ` [Xen-changelog] [linux-2.6.18-xen] Add "#ifdef ARCH_HAS_DEV_MEM" to archtecture specific file_operations Hollis Blanchard
2007-07-07 9:01 ` Keir Fraser
2007-07-09 19:20 ` Hollis Blanchard
2007-07-09 19:26 ` Keir Fraser [this message]
2007-07-09 19:41 ` Hollis Blanchard
2007-07-09 20:23 ` [XenPPC] " Jimi Xenidis
2007-07-09 21:20 ` Jimi Xenidis
2007-07-11 5:44 ` Jun Kamada
2007-07-11 10:00 ` Keir Fraser
2007-07-12 11:05 ` Jun Kamada
2007-07-13 2:42 ` [Xen-devel] Re: [Xen-changelog] [linux-2.6.18-xen] Add "#ifdefARCH_HAS_DEV_MEM" " Akio Takebe
2007-07-13 12:54 ` Keir Fraser
2007-07-13 14:54 ` Isaku Yamahata
2007-07-13 15:09 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C2B84A7C.A8F1%keir@xensource.com \
--to=keir@xensource.com \
--cc=hollisb@us.ibm.com \
--cc=kama@jp.fujitsu.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ppc-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.