linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <porter@cox.net>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Todd Poynor <tpoynor@mvista.com>,
	linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: consistent_free re-revisited
Date: Thu, 12 Sep 2002 10:05:31 -0700	[thread overview]
Message-ID: <20020912100531.A8552@home.com> (raw)
In-Reply-To: <20020912142945.GC13840@opus.bloom.county>; from trini@kernel.crashing.org on Thu, Sep 12, 2002 at 07:29:45AM -0700


On Thu, Sep 12, 2002 at 07:29:45AM -0700, Tom Rini wrote:
> IIRC, to fix the interrupt context bit, we need something like the
> following, which was Paul's idea, and he said he would talk to Dave M.
> about it.  Did anything ever happen there?

<snip>

In addition to that, you need to scrub the entire consistent_alloc
path...that includes map_page()->pte_alloc_kernel() which may
do a GFP_KERNEL allocation.

Then it's more complex yet with Book E's need to have those possible
page table allocations from the pinned TLB region.

Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2002-09-12 17:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-11 21:45 consistent_free re-revisited Todd Poynor
2002-09-12  3:26 ` David Gibson
2002-09-12 14:29   ` Tom Rini
2002-09-12  7:23     ` Benjamin Herrenschmidt
2002-09-12 14:51       ` Tom Rini
2002-09-12  7:49         ` Benjamin Herrenschmidt
2002-09-12 15:23           ` Tom Rini
2002-09-12  8:08             ` Benjamin Herrenschmidt
2002-09-12 17:05     ` Matt Porter [this message]
2002-09-12 21:33   ` Todd Poynor

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=20020912100531.A8552@home.com \
    --to=porter@cox.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=tpoynor@mvista.com \
    --cc=trini@kernel.crashing.org \
    /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).