From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Brian King <brking@linux.vnet.ibm.com>
Cc: Seth Jennings <sjenning@linux.vnet.ibm.com>,
Robert Jennings <rcj@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
Dave Hansen <dave@linux.vnet.ibm.com>
Subject: Re: tlb flushing on Power
Date: Fri, 27 Jan 2012 08:39:13 +1100 [thread overview]
Message-ID: <1327613953.24487.9.camel@pasglop> (raw)
In-Reply-To: <4F216620.2010509@linux.vnet.ibm.com>
On Thu, 2012-01-26 at 08:41 -0600, Brian King wrote:
> CC'ing linuxppc-dev...
>
>
> On 01/26/2012 08:18 AM, Seth Jennings wrote:
> > Hey Dave,
> >
> > So I submitted the zsmalloc patches to lkml at the beginning
> > of the year
> >
> > https://lkml.org/lkml/2012/1/9/389
> >
> > I found there are two functions Nitin used in the mapping
> > functions that are not supported in the powerpc arch:
> > set_pte() and __flush_tlb_one().
.../...
The arch management of page tables can be tricky indeed :-) I need to
have a better understanding of what you are doing to see how I can try
to adapt it to power.
set_pte() is long gone on all archs really (or if it's still there it's
not meant to be used as is), use set_pte_at().
__flush_tlb_one() doesn't mean anything as an arch independent
functionality. We have a local_flush_tlb_page() that -might- do what you
want but why in hell is that patch not using proper existing
interfaces ?
Can you explain to me a bit more the whole business in this patch set
about doing kmap_atomic() vs. manually trying to populate the PTEs ? Why
not just use two kmap atomic entries ? If interrupts are disabled
kmap_atomic() should give you contiguous ones I suppose (unless NMIs are
allowed to use kmap_atomic, are they ?)
Cheers,
Ben.
next prev parent reply other threads:[~2012-01-26 21:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F2160B3.60708@linux.vnet.ibm.com>
2012-01-26 14:41 ` tlb flushing on Power Brian King
2012-01-26 21:39 ` Benjamin Herrenschmidt [this message]
2012-01-26 22:30 ` Dave Hansen
2012-01-27 2:40 ` Benjamin Herrenschmidt
2012-02-08 17:39 ` Seth Jennings
2012-02-08 21:04 ` Benjamin Herrenschmidt
2012-02-10 19:14 ` Seth Jennings
2012-02-16 17:11 ` Seth Jennings
2012-02-16 20:31 ` Benjamin Herrenschmidt
2012-03-05 17:56 ` Seth Jennings
2012-03-07 5:28 ` Michael Neuling
2012-03-07 21:18 ` Seth Jennings
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=1327613953.24487.9.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=brking@linux.vnet.ibm.com \
--cc=dave@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rcj@linux.vnet.ibm.com \
--cc=sjenning@linux.vnet.ibm.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).