linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stef Simoens <stef.simoens@pi.be>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] PPC601 MQ handling
Date: Wed, 16 Jun 2004 15:44:54 -0500	[thread overview]
Message-ID: <1087418693.8556.236.camel@gaston> (raw)
In-Reply-To: <HZF5JG$8DFE4973242834322717FEB2CD3FE797@scarlet.be>


On Wed, 2004-06-16 at 15:42, Stef Simoens wrote:
> This is a patch to handle the MQ-register found on 601 CPU's. It's a diff against linux-2.6.7. Could this patch be included in further Linux kernels?
>
> The patch can also be downloaded from http://users.tijd.com/~tdn46485/linux-2.6.7-mq.patch
> I also wrote a small testcase (http://users.tijd.com/~tdn46485/mqtest.s)
> The test makes a division, enters a for loop, and prints the contents of the MQ register.
>
> Changes:
> * Add a CONFIG_PPC601_MQ option
> * Set CPU_FTR_MQ for 601 (arch/ppc/cputable.c, include/asm-ppc/cputable.h)
> * Save and restore the MQ register (arch/ppc/entry.S, include/asm-ppc/reg.h)
> * Delete the 'not used' message, mq debug (arch/ppc/kernel/ppc-stub.c, include/asm-ppc/ptrace.h)
>
> Signed-off-by: Stef Simoens <stef.simoens@pi.be>

Did you check it was actually saved/restored by the signal code ?

Ben.


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

  reply	other threads:[~2004-06-16 20:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16 20:42 [PATCH] PPC601 MQ handling Stef Simoens
2004-06-16 20:44 ` Benjamin Herrenschmidt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-17  9:19 Stef Simoens
2004-06-17 16:27 ` Benjamin Herrenschmidt

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=1087418693.8556.236.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paulus@samba.org \
    --cc=stef.simoens@pi.be \
    /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).