linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Chris Friesen <cfriesen@nortel.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: question on inline assembly and long long values
Date: Thu, 07 Apr 2005 09:57:03 +1000	[thread overview]
Message-ID: <1112831823.9568.219.camel@gaston> (raw)
In-Reply-To: <4254771B.2070802@nortel.com>

On Wed, 2005-04-06 at 17:56 -0600, Chris Friesen wrote:
> Benjamin Herrenschmidt wrote:
> 
> > But the kernel code always runs in 64 bits mode...
> 
> The ppc kernel (not ppc64) runs in 64-bit mode?  An unsigned long long 
> fits in a single register in C code?

Ah no, it doesn't, but then, be careful to have interrupts off when you
do that are the interrupt handler won't save the high half of the
registers between the mtmsrd and your "splitting" of it.

> Yeah, the optimisations really don't matter much...the ugly resulting 
> code just bothered me.
> 
> Chris
-- 
Benjamin Herrenschmidt <benh@kernel.crashing.org>

  reply	other threads:[~2005-04-06 23:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06 18:26 question on inline assembly and long long values Chris Friesen
2005-04-06 19:16 ` Kumar Gala
2005-04-06 20:01   ` Chris Friesen
2005-04-06 21:18     ` Gabriel Paubert
2005-04-06 21:37       ` Chris Friesen
2005-04-06 23:19 ` Benjamin Herrenschmidt
2005-04-06 23:30   ` Chris Friesen
2005-04-06 23:49     ` Benjamin Herrenschmidt
2005-04-06 23:56       ` Chris Friesen
2005-04-06 23:57         ` Benjamin Herrenschmidt [this message]
2005-04-07  0:09           ` Chris Friesen

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=1112831823.9568.219.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=cfriesen@nortel.com \
    --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).