public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] 2.4.14 Missing asm clobbers
Date: Mon, 26 Nov 2001 23:12:57 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805544@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805537@msgid-missing>

>>>>> On Wed, 21 Nov 2001 11:40:56 +1100, Keith Owens <kaos@ocs.com.au> said:

  Keith> include/asm-ia64/spinlock.h.

  Keith>   spin_lock() changes ar.ccv, p7 without a clobber (!NEW_LOCK
  Keith> version).  read_lock() changes p6 without a clobber.
  Keith> write_lock() changes ar.ccv, p7 without a clobber.

Ok, those should be fixed now.  They clearly are needed, though I
don't think the missing ar.ccv really had any effect because gcc uses
that register only for the builtin synchronization ops use them (which
we don't use in the kernel).

  Keith> arch/ia64/kernel/traps.c

  Keith>   fp_emulate() does ldf f10, f11 without a clobber.

That's fine because f10 and f11 are marked "fixed" on the command
line.

  Keith> arch/ia64/kernel/unaligned.c

  Keith>   invala_gr() and invala_fr() do invala without a "memory"
  Keith> clobber.  Not sure if it is necessary or not.

This is fine because the instructions affect the code that caused the
unaliged access, not the unaligned handler itself.  However, we
shouldn't need that code anymore because we now do an "invala" on
entry to the kernel.  I'll remove it in 2.5.xx.

Thanks,

	--david


      parent reply	other threads:[~2001-11-26 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21  0:40 [Linux-ia64] 2.4.14 Missing asm clobbers Keith Owens
2001-11-21  1:37 ` David Mosberger
2001-11-26 23:12 ` David Mosberger [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=marc-linux-ia64-105590698805544@msgid-missing \
    --to=davidm@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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