All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: 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>,
	David Howells <dhowells@redhat.com>,
	Yoshinori Sato <ysato@users.sourceforge.jp>
Subject: Re: [PATCH] Allow preemption during lazy mmu updates
Date: Wed, 08 Apr 2009 10:32:57 -0700	[thread overview]
Message-ID: <49DCDFC9.9000505@goop.org> (raw)
In-Reply-To: <20090408145440.GN12931@elte.hu>

Ingo Molnar wrote:
> * Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>
>   
>>  include/asm-frv/pgtable.h          |    4 +-
>>     
>
> Needs the ack of the FRV arch maintainer both for content and for 
> flow (i.e. via x86 tree). If any second thoughts are expressed about 
> the flow then this needs to go on separate tracks.
>   

I don't know why frv defines this; its just cut'n'paste from the default 
no-op implementation in asm-generic/pgtable.h.  (h8300 too, it seems.)

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?

Yoshinori-san, do you have a specific reason for defining 
arch_enter/leave_lazy_cpu_mode() in asm-h3800/pgtable.h?  It seems to 
have come in with c728d60455e8e8722ee08312a75f38dd7a866b5e "h8300 
generic irq", which doesn't seem like a related change.

>>  include/asm-generic/pgtable.h      |   21 +++++++------
>>     
>
> Needs the ack of arch maintainers in general and a linux-arch 
> cross-post.
>   

asm-generic/pgtable.h defines the default no-op implementation which is 
used when the architecture has no particular use for the hook.  The only 
non-x86 definitions are frv and h3800, and they're both copies of the 
no-op definition.

In any case, if this series is a sticking point, we can easily drop it 
as the subsequent patches have no dependency on it.

    J

  parent reply	other threads:[~2009-04-08 17:33 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 [this message]
2009-04-08 18:10     ` David Howells
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=49DCDFC9.9000505@goop.org \
    --to=jeremy@goop.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --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.