All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 5/16] hypervisor functions for Celleb
Date: Wed, 15 Nov 2006 23:04:45 +0100	[thread overview]
Message-ID: <200611152304.45243.arnd@arndb.de> (raw)
In-Reply-To: <20061115183746.GC21633@lst.de>

On Wednesday 15 November 2006 19:37, Christoph Hellwig wrote:
> > +static inline int64_t beat_allocate_memory(uint64_t __in0, uint64_t
> > __in1, uint64_t __in2, uint64_t __in3,void** __out0,uint64_t* __out1) {
> > +=A0=A0=A0=A0=A0register uint64_t __reg0 __asm__("r3");
> > +=A0=A0=A0=A0=A0register uint64_t __reg1 __asm__("r4");
> > +=A0=A0=A0=A0=A0register uint64_t __reg2 __asm__("r5");
> > +=A0=A0=A0=A0=A0register uint64_t __reg3 __asm__("r6");
> > +=A0=A0=A0=A0=A0register uint64_t __sn __asm__("r11") =3D (0UL);
>
> No point in declaring this a register variable, gcc ignores the
> specifier. =A0

Actually, this is the one place where gcc forces you to use the
'register' keyword, the '__asm__("r3")' specifier does not work
for variables declared without it.

> Is there any chance to not duplicate the inline assembly=20
> for every single hypercall but have generic call with n arguments
> helper, as for the phyp hvcalls?

It's not easy to do it the way phyp does, because the assembly
needs to pass the call number in %r11, which is not one of the
argument registers.

I'd like to unify the hcall mechanism at least between celleb
and ps3, since they are very similar. I need to forward-port
the patch I had for this.

	Arnd <><

  reply	other threads:[~2006-11-15 22:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15  9:37 [PATCH 5/16] hypervisor functions for Celleb Ishizaki Kou
2006-11-15 18:37 ` Christoph Hellwig
2006-11-15 22:04   ` Arnd Bergmann [this message]
2006-11-16 18:40     ` Jimi Xenidis
2006-11-17  5:21       ` Anton Blanchard
2006-11-18  9:08         ` Arnd Bergmann

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=200611152304.45243.arnd@arndb.de \
    --to=arnd@arndb.de \
    --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 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.