From: James Bottomley <James.Bottomley@steeleye.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andi Kleen <ak@muc.de>, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, virtualization@lists.osdl.org,
xen-devel@lists.xensource.com, Chris Wright <chrisw@sous-sol.org>,
Zachary Amsden <zach@vmware.com>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-arch@vger.kernel.org
Subject: Re: [patch 09/26] Xen-paravirt_ops: remove HAVE_ARCH_MM_LIFETIME, define no-op architecture implementations
Date: Tue, 27 Feb 2007 09:15:58 -0600 [thread overview]
Message-ID: <1172589358.3408.2.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <20070227081632.356636957@goop.org>
On Tue, 2007-02-27 at 00:13 -0800, Jeremy Fitzhardinge wrote:
> plain text document attachment (kill-HAVE_ARCH_MM_LIFETIME.patch)
> akpm:
> > Can we lose __HAVE_ARCH_MM_LIFETIME? Just define these (preferably in C,
> > not in cpp) in the appropriate include/asm-foo/ files?
>
> Signed-off-by: Jeremy Fitzhardinge <jeremy@xensource.com>
> Cc: linux-arch@vger.kernel.org
>
> ---
> include/asm-alpha/mmu_context.h | 9 +++++++++
> include/asm-arm/mmu_context.h | 9 +++++++++
> include/asm-arm26/mmu_context.h | 9 +++++++++
> include/asm-avr32/mmu_context.h | 9 +++++++++
> include/asm-cris/mmu_context.h | 8 ++++++++
> include/asm-frv/mmu_context.h | 8 ++++++++
> include/asm-h8300/mmu_context.h | 8 ++++++++
> include/asm-i386/mmu_context.h | 2 +-
> include/asm-i386/paravirt.h | 18 +++++++++++++++---
> include/asm-ia64/mmu_context.h | 8 ++++++++
> include/asm-m32r/mmu_context.h | 8 ++++++++
> include/asm-m68k/mmu_context.h | 8 ++++++++
> include/asm-m68knommu/mmu_context.h | 8 ++++++++
> include/asm-mips/mmu_context.h | 8 ++++++++
> include/asm-parisc/mmu_context.h | 9 +++++++++
> include/asm-powerpc/mmu_context.h | 10 ++++++++++
> include/asm-ppc/mmu_context.h | 9 +++++++++
> include/asm-s390/mmu_context.h | 8 ++++++++
> include/asm-sh/mmu_context.h | 8 ++++++++
> include/asm-sh64/mmu_context.h | 8 ++++++++
> include/asm-sparc/mmu_context.h | 8 ++++++++
> include/asm-sparc64/mmu_context.h | 8 ++++++++
> include/asm-um/mmu_context.h | 8 ++++++++
> include/asm-v850/mmu_context.h | 8 ++++++++
> include/asm-x86_64/mmu_context.h | 8 ++++++++
> include/asm-xtensa/mmu_context.h | 9 +++++++++
> include/linux/sched.h | 6 ------
> mm/mmap.c | 1 +
> 28 files changed, 218 insertions(+), 10 deletions(-)
Wouldn't it be a lot easier to do this via asm-generic?
James
next prev parent reply other threads:[~2007-02-27 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070227081337.434798469@goop.org>
2007-02-27 8:13 ` [patch 08/26] Xen-paravirt_ops: add hooks to intercept mm creation and destruction Jeremy Fitzhardinge
2007-02-27 8:13 ` [patch 09/26] Xen-paravirt_ops: remove HAVE_ARCH_MM_LIFETIME, define no-op architecture implementations Jeremy Fitzhardinge
2007-02-27 15:15 ` James Bottomley [this message]
2007-02-27 17:21 ` Jeremy Fitzhardinge
2007-02-27 17:35 ` James Bottomley
2007-02-27 17:56 ` Jeremy Fitzhardinge
2007-02-27 18:04 ` James Bottomley
2007-02-27 18:48 ` Jeremy Fitzhardinge
2007-02-27 18:53 ` James Bottomley
[not found] <20070301232443.195603797@goop.org>
2007-03-01 23:24 ` Jeremy Fitzhardinge
2007-03-16 9:27 ` Ingo Molnar
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=1172589358.3408.2.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=ak@muc.de \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.com \
--cc=zach@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).