All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: David Rientjes <rientjes@google.com>
Cc: Chen Gang <gang.chen.5i5j@gmail.com>,
	Liqin Chen <liqin.linux@gmail.com>,
	Lennox Wu <lennox.wu@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] rch/score/include/uapi/asm/ptrace.h: Add prefix 'SCORE_' for related macros
Date: Tue, 24 Jun 2014 16:10:11 -0700	[thread overview]
Message-ID: <53AA0553.6020909@roeck-us.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1406241549430.29176@chino.kir.corp.google.com>

On 06/24/2014 03:51 PM, David Rientjes wrote:
> On Tue, 24 Jun 2014, Guenter Roeck wrote:
>
>>> diff --git a/arch/score/include/uapi/asm/ptrace.h
>>> b/arch/score/include/uapi/asm/ptrace.h
>>> index f59771a..56e2de0 100644
>>> --- a/arch/score/include/uapi/asm/ptrace.h
>>> +++ b/arch/score/include/uapi/asm/ptrace.h
>>> @@ -4,16 +4,29 @@
>>>    #define PTRACE_GETREGS		12
>>>    #define PTRACE_SETREGS		13
>>>
>>> -#define PC		32
>>> -#define CONDITION	33
>>> -#define ECR		34
>>> -#define EMA		35
>>> -#define CEH		36
>>> -#define CEL		37
>>> -#define COUNTER		38
>>> -#define LDCR		39
>>> -#define STCR		40
>>> -#define PSR		41
>>> +#if !defined(__KERNEL__) || !defined(__linux__)
>>> +#define PC			32
>>> +#define CONDITION		33
>>> +#define ECR			34
>>> +#define EMA			35
>>> +#define CEH			36
>>> +#define CEL			37
>>> +#define COUNTER			38
>>> +#define LDCR			39
>>> +#define STCR			40
>>> +#define PSR			41
>>> +#else
>>> +#define SCORE_PC		32
>>> +#define SCORE_CONDITION		33
>>> +#define SCORE_ECR		34
>>> +#define SCORE_EMA		35
>>> +#define SCORE_CEH		36
>>> +#define SCORE_CEL		37
>>> +#define SCORE_COUNTER		38
>>> +#define SCORE_LDCR		39
>>> +#define SCORE_STCR		40
>>> +#define SCORE_PSR		41
>>> +#endif
>>>
>>>    #define SINGLESTEP16_INSN	0x7006
>>>    #define SINGLESTEP32_INSN	0x840C8000
>>>
>> That looks weird ... not sure if that is a good solution either.
>>
>> Are those defines actually used anywhere ? They don't seem to be used in the
>> kernel.
>>
>> Side note - an 'a' got missing in your headline.
>> And I'd suggest to abbreviate it to something like
>> 	score/uapi: ptrace.h:
>>
>
> Besides checking whether they are used in the kernel or not, I presume we
> would need to be fairly confident there are actual userspace usecases for
> these that require the change.  It begs the question of why these
> constants are too generic to be in the kernel but are acceptable in the
> set of userspace applications in the world.
>

That is another question. But for the time being it might be sufficient to
surround the defines with #if !defined(__KERNEL__) without introducing new
(and unused) kernel defines.

Guenter


  reply	other threads:[~2014-06-24 23:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 13:08 [PATCH v2] rch/score/include/uapi/asm/ptrace.h: Add prefix 'SCORE_' for related macros Chen Gang
2014-06-24 14:47 ` Guenter Roeck
2014-06-24 22:51   ` David Rientjes
2014-06-24 23:10     ` Guenter Roeck [this message]
2014-06-24 23:40       ` David Rientjes
2014-06-25  1:25         ` Chen Gang
2014-06-25 15:16           ` Lennox Wu
2014-06-25 22:09             ` Chen Gang
     [not found] <BAY404-EAS3244E3E66FF1100E4753CC9B0180@phx.gbl>
2014-06-26  0:30 ` Guenter Roeck

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=53AA0553.6020909@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=gang.chen.5i5j@gmail.com \
    --cc=lennox.wu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liqin.linux@gmail.com \
    --cc=rientjes@google.com \
    /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.