public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Steven J. Magnani" <steve@digidescorp.com>
To: microblaze-uclinux@itee.uq.edu.au
Cc: linux-kernel@vger.kernel.org, monstr@monstr.eu
Subject: RE: [microblaze-uclinux] [PATCH v2] microblaze: nommu: Don't clobber R11 on syscalls
Date: Mon, 14 Dec 2009 22:41:28 -0600	[thread overview]
Message-ID: <1260852089.3541.5.camel@iscandar.digidescorp.com> (raw)
In-Reply-To: <005801ca7d0f$deaef5b0$9c0ce110$@com>

On Mon, 2009-12-14 at 14:50 -0800, Jim Van Vorst wrote:
> Isn't R11 a temporary?  If it doesn't need to be preserved across function
> calls, why can't it be clobbered during a syscall?

Because the Microblaze syscall macros don't include r11 in the clobber
list. I suppose an alternative solution would just change the userspace
macros and not the kernel, even though there is a bug in the kernel. 

Michal, is the Microblaze ABI considered "locked down" now, or is a
kernel solution still permitted?

------------------------------------------------------------------------
 Steven J. Magnani               "I claim this network for MARS!
 www.digidescorp.com              Earthling, return my space modulator!"

 #include <standard.disclaimer>




  parent reply	other threads:[~2009-12-15  4:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 22:24 [PATCH v2] microblaze: nommu: Don't clobber R11 on syscalls steve
     [not found] ` <005801ca7d0f$deaef5b0$9c0ce110$@com>
2009-12-15  4:41   ` Steven J. Magnani [this message]
2009-12-15  7:24 ` Michal Simek

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=1260852089.3541.5.camel@iscandar.digidescorp.com \
    --to=steve@digidescorp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=microblaze-uclinux@itee.uq.edu.au \
    --cc=monstr@monstr.eu \
    /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