From: Kumar Gala <galak@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: markn@au1.ibm.com, PowerPC dev list <linuxppc-dev@ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/2] Replace NT_PRXFPREG with ELF_CORE_XFPREG_TYPE #define
Date: Thu, 11 Oct 2007 17:01:43 -0500 [thread overview]
Message-ID: <2C31F1C3-3337-483B-A463-767459305F1E@kernel.crashing.org> (raw)
In-Reply-To: <18190.39864.4562.852292@cargo.ozlabs.ibm.com>
On Oct 11, 2007, at 4:55 PM, Paul Mackerras wrote:
> Kumar Gala writes:
>
>>> #define ELF_CORE_XFPREG_TYPE to be NT_PRXFPREG in all current
>>> users so
>>> there's are no change in behaviour.
>>
>> Can we make this ELF_CORE_VECREG_TYPE or something that is so coupled
>> to the x86 specific name?
>
> How is "extended floating point registers" x86-specific?
we'll I don't consider the altivec register file as 'extended fp'.
I'm assuming the name XFP came from IA32 land when MMX/SSE came into
existence.
> ELF_CORE_XFPREG_TYPE is a suitable name for something that's used in
> conjunction with a function called elf_core_copy_task_xfpregs().
agreed, I think the function name should change as well.
- k
next prev parent reply other threads:[~2007-10-11 22:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071011071558.676463639@au1.ibm.com>
[not found] ` <20071011072208.075979098@au1.ibm.com>
2007-10-11 13:04 ` Kumar Gala
2007-10-11 21:55 ` Paul Mackerras
2007-10-11 22:01 ` Kumar Gala [this message]
2007-10-11 22:14 ` Paul Mackerras
2007-10-11 23:31 ` Michael Ellerman
2007-10-12 1:37 ` Mark Nelson
2007-10-12 2:15 ` [PATCH 1/2] [V2] " Mark Nelson
2007-10-12 2:35 ` Mark Nelson
2007-10-12 2:40 ` [PATCH 1/2] [V3] " Mark Nelson
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=2C31F1C3-3337-483B-A463-767459305F1E@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=markn@au1.ibm.com \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®