linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH][WIP][RFC] powerpc: fixup lwsync at runtime
Date: Sat, 21 Jun 2008 20:27:23 +1000	[thread overview]
Message-ID: <1214044043.13524.6.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0806201131040.17834@blarg.am.freescale.net>

[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]

On Fri, 2008-06-20 at 11:36 -0500, Kumar Gala wrote:
> This is a work in progress towards make lwsync fixed up at runtime.  The
> patch is based (requires) the module refactoring patch.  Some of this code
> should be reworked based on the code patching work from Michael.  Also,
> ppc64 and vdso support needs a bit of cleaning up.

Hi Kumar,

This will clash in practice, though not in spirit, with the stuff I've
been working on to allow alternative feature sections. The code is in my
tree on kernel.org if you want to check it out, I was about to send
yesterday it but realised it breaks if you have exception table entries
in your alternative case code >:/

http://git.kernel.org/?p=linux/kernel/git/mpe/linux-2.6.git;a=summary

> Some questions:
> * How do we determine at runtime if we need to convert sync to lwsync.
> This is simliar to cpu_feature but has the issue that cpu_feature is about
> either having code in or not.

Isn't it just if cpus_possible = 1 ?

> * Do we simplify the section of fixup information and remove the mask and
> value since we don't use them and they double the size of the section

I guess it depends how many you end up with. My patches add another two
longs to the fixup entry also. It is all freed after boot.

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2008-06-21 10:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-20 16:36 [PATCH][WIP][RFC] powerpc: fixup lwsync at runtime Kumar Gala
2008-06-20 23:23 ` Benjamin Herrenschmidt
2008-06-21 16:07   ` Kumar Gala
2008-06-22  0:20     ` Benjamin Herrenschmidt
2008-06-23 15:02       ` Kumar Gala
2008-06-21 10:27 ` Michael Ellerman [this message]

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=1214044043.13524.6.camel@localhost \
    --to=michael@ellerman.id.au \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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).