All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, david.jander@protonic.nl, wd@denx.de,
	gunnar@genesi-usa.com
Subject: Re: [RFC][PATCH v3] powerpc: e300c2/c3/c4 TLB errata workaround
Date: Sat, 14 Mar 2009 08:26:42 +1100	[thread overview]
Message-ID: <1236979602.25062.55.camel@pasglop> (raw)
In-Reply-To: <1236957383-20240-1-git-send-email-galak@kernel.crashing.org>

> +BEGIN_FTR_SECTION
> +	b      TlbWo    /* Code for TLB-errata workaround doesn't fit here */
> +END_FTR_SECTION_IFSET(CPU_FTR_NEED_DTLB_SW_LRU)
> +RFTlbWo:

Can you use nicer label names ? :-)

Also, that's a lot of code for such a hot path...

Cheers,
Ben.

  parent reply	other threads:[~2009-03-13 21:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-13 15:16 [RFC][PATCH v3] powerpc: e300c2/c3/c4 TLB errata workaround Kumar Gala
2009-03-13 21:25 ` Benjamin Herrenschmidt
2009-03-13 21:26 ` Benjamin Herrenschmidt [this message]
2009-03-13 22:06   ` Kumar Gala
2009-03-16 12:42     ` Kumar Gala

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=1236979602.25062.55.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=david.jander@protonic.nl \
    --cc=galak@kernel.crashing.org \
    --cc=gunnar@genesi-usa.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=wd@denx.de \
    /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.