From: David Howells <dhowells@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: dhowells@redhat.com, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Thomas Gleixner <tglx@linutronix.de>,
Yoshinori Sato <ysato@users.sourceforge.jp>
Subject: Re: [PATCH] Allow preemption during lazy mmu updates
Date: Wed, 08 Apr 2009 19:10:21 +0100 [thread overview]
Message-ID: <21081.1239214221@redhat.com> (raw)
In-Reply-To: <49DCDFC9.9000505@goop.org>
Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> David, do you have a specific reason for defining
> arch_enter/leave_lazy_cpu_mode() in asm-frv/pgtable.h? It seems to have come
> in with 28936117af849b8c2fca664a41ea7651a0d99591 "FRV: Add some missng lazy
> MMU hooks for NOMMU mode". The intention was that asm-generic/pgtable.h
> should supply the default definitions; is that incompatible with nommu or
> something?
I don't remember. It was over two years ago. My guess is that it was to get
things to compile. Note that in NOMMU mode, <asm-generic/pgtable.h> is _not_
#included by <asm-frv/pgtable.h>.
David
next prev parent reply other threads:[~2009-04-08 18:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 18:02 [PATCH] Allow preemption during lazy mmu updates Jeremy Fitzhardinge
2009-03-27 18:02 ` [PATCH 1/8] mm: disable preemption in apply_to_pte_range Jeremy Fitzhardinge
2009-03-27 18:02 ` [PATCH 2/8] x86/paravirt: remove lazy mode in interrupts Jeremy Fitzhardinge
2009-03-27 18:02 ` [PATCH 3/8] x86/pvops: replace arch_enter_lazy_cpu_mode with arch_start_context_switch Jeremy Fitzhardinge
2009-03-27 18:02 ` [PATCH 4/8] x86/paravirt: flush pending mmu updates on context switch Jeremy Fitzhardinge
2009-03-27 18:02 ` [PATCH 5/8] x86/paravirt: finish change from lazy cpu to context switch start/end Jeremy Fitzhardinge
2009-03-27 18:02 ` [PATCH 6/8] x86/paravirt: allow preemption with lazy mmu mode Jeremy Fitzhardinge
2009-03-27 18:02 ` [PATCH 7/8] mm: allow preemption in apply_to_pte_range Jeremy Fitzhardinge
2009-04-07 21:38 ` Andrew Morton
2009-04-07 21:54 ` Jeremy Fitzhardinge
2009-03-27 18:02 ` [PATCH 8/8] x86/paravirt: use percpu_ rather than __get_cpu_var Jeremy Fitzhardinge
2009-03-27 23:48 ` [PATCH] Allow preemption during lazy mmu updates Peter Zijlstra
2009-04-08 14:54 ` Ingo Molnar
2009-04-08 15:11 ` Peter Zijlstra
2009-04-19 10:15 ` Avi Kivity
2009-04-19 10:47 ` Peter Zijlstra
2009-04-19 23:53 ` Jeremy Fitzhardinge
2009-04-20 6:02 ` Avi Kivity
2009-04-08 17:32 ` Jeremy Fitzhardinge
2009-04-08 18:10 ` David Howells [this message]
2009-04-08 18:30 ` [PATCH] FRV: Use <asm-generic/pgtable.h> in NOMMU mode David Howells
2009-04-08 18:35 ` Jeremy Fitzhardinge
2009-04-08 18:47 ` David Howells
2009-04-08 18:44 ` Sam Ravnborg
2009-04-08 18:47 ` David Howells
2009-04-08 20:56 ` Sam Ravnborg
2009-04-08 21:25 ` David Howells
2009-04-08 21:40 ` Sam Ravnborg
2009-04-08 21:48 ` David Howells
2009-04-08 22:04 ` Sam Ravnborg
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=21081.1239214221@redhat.com \
--to=dhowells@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=ysato@users.sourceforge.jp \
/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.