All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Thibaut VARENE <T-Bone@parisc-linux.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [RFC] using 64bit wide registers with 32bit kernel
Date: Sat, 13 May 2006 12:03:07 -0500	[thread overview]
Message-ID: <1147539787.6632.7.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <7d01f9f00605130841v6185b06dybae82c9f9c77e2b4@mail.gmail.com>

On Sat, 2006-05-13 at 17:41 +0200, Thibaut VARENE wrote:
> 1) we claim what I'm trying to do should not be done on parisc-linux
> => using ldd/std, MAX2 and other insns that rely on 64bit regs should
> be prohibited by binutils for non-wide code (currently gcc/binutils
> happily build my code with -mpa-risc-2-0, which generates level 2.0
> non wide code)

I really don't think doubling the size of our register file on all tasks
and doubling the size of the saved registers on stack for interruptions
is really a sensible thing to do just so some multi-media extension can
be made to work.

> 2) we claim what I'm trying to do should be possible on parisc-linux
> => we need to fix context switching in 32bit kernels.
> 
> Comments?

There is a third possibility, and that's to execute the instruction in
the kernel where there wouldn't be a danger of context switches, where
the return values could be packaged properly and where it could be
emulated if necessary.  It would be nice to use a vDSO for this, but I
suspect Carlos' lightweight semaphore infrastructure can be pressed into
service for this.

James


_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  parent reply	other threads:[~2006-05-13 17:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-13 15:41 [parisc-linux] [RFC] using 64bit wide registers with 32bit kernel Thibaut VARENE
2006-05-13 16:33 ` [parisc-linux] " Thibaut VARENE
2006-05-13 17:03 ` James Bottomley [this message]
2006-05-13 22:32   ` [parisc-linux] " Thibaut VARENE
     [not found]   ` <yq0ves7psaw.fsf@jaguar.mkp.net>
     [not found]     ` <7d01f9f00605150255u5846f144u9c95cab3ffd35133@mail.gmail.com>
2006-05-15 10:56       ` Jes Sorensen
2006-05-15 11:53     ` Kyle McMartin
2006-05-13 17:07 ` John David Anglin
2006-05-13 22:43   ` Thibaut VARENE
2006-05-13 23:35     ` John David Anglin
2006-05-14  5:06       ` John Marvin
2006-05-14  6:27       ` Grant Grundler
     [not found]         ` <200605141510.k4EFAUv7006350@hiauly1.hia.nrc.ca>
2006-05-15  1:06           ` Grant Grundler

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=1147539787.6632.7.camel@mulgrave.il.steeleye.com \
    --to=james.bottomley@steeleye.com \
    --cc=T-Bone@parisc-linux.org \
    --cc=parisc-linux@lists.parisc-linux.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 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.