linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Christophe Leroy <christophe.leroy@c-s.fr>
Cc: mikey@neuling.org, linuxppc-dev@lists.ozlabs.org,
	gromero@linux.vnet.ibm.com
Subject: Re: [PATCH v3 1/2] selftests/powerpc: Add MSR bits
Date: Mon, 7 Jan 2019 10:58:03 -0200	[thread overview]
Message-ID: <3b767228-badb-6e93-3da4-8d5e003da9ce@debian.org> (raw)
In-Reply-To: <13f835f8-8c6c-9b94-9e27-c23ce3df8253@c-s.fr>

hi Christophe,

On 1/7/19 10:47 AM, Christophe Leroy wrote:
> Hi Breno,
> 
> Le 07/01/2019 à 13:44, Breno Leitao a écrit :
>> hi Christophe,
>>
>> On 1/3/19 3:19 PM, LEROY Christophe wrote:
>>> Breno Leitao <leitao@debian.org> a écrit :
>>>
>>>> This patch simply adds definitions for the MSR bits and some macros to
>>>> test for MSR TM bits.
>>>>
>>>> This was copied from arch/powerpc/include/asm/reg.h generic MSR part.
>>>
>>> Can't we find a way to avoid duplicating such defines ?
>>
>> I think there are three possible ways, but none of them respect the premises
>> we are used too. These are the possible ways I can think of:
>>
>> 1) Including arch/powerpc/include/asm as part of the selftest compilation
>> process.
>>     Problem: This might break the selftest independence of the kbuild system.
>>
>> 2) Generate a temporary header file inside selftests/include which contains
>> these macros at compilation time.
>>     Problem: The problem as above.
>>
>> 3) Define MSR fields at userspace headers (/usr/include).
>>     Problem: I am not sure userspace should have MSR bits information.
>>
>> Do you suggest me to investigate any other way?
> 
> Looking it other .h in selftests, it looks like they are limited to the only
> strictly necessary values.
> 
> Are all the values you have listed used ? If not, could you only include in
> the file the necessary ones ?

Sure. That works also.  Let send a v4 patch.

  reply	other threads:[~2019-01-07 13:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03 16:11 [PATCH v3 1/2] selftests/powerpc: Add MSR bits Breno Leitao
2019-01-03 16:11 ` [PATCH v3 2/2] selftests/powerpc: New TM signal self test Breno Leitao
2019-01-03 17:19 ` [PATCH v3 1/2] selftests/powerpc: Add MSR bits LEROY Christophe
2019-01-07 12:44   ` Breno Leitao
2019-01-07 12:47     ` Christophe Leroy
2019-01-07 12:58       ` Breno Leitao [this message]
2019-01-08  9:20     ` Michael Ellerman
2019-01-08 11:11       ` Breno Leitao
2019-01-08 11:14         ` Christophe Leroy
2019-01-08 11:31           ` Breno Leitao

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=3b767228-badb-6e93-3da4-8d5e003da9ce@debian.org \
    --to=leitao@debian.org \
    --cc=christophe.leroy@c-s.fr \
    --cc=gromero@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikey@neuling.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).