On Fri, 26 Apr 2019, Enrico Weigelt, metux IT consult wrote:
> On 25.04.19 12:50, Thomas Gleixner wrote:
> > On Thu, 25 Apr 2019, Enrico Weigelt, metux IT consult wrote:
> >
> >> On 25.04.19 12:42, Li, Aubrey wrote:
> >>>
> >>> Yep, I'll make it disabled by default and not switchable and let arch
On 25.04.19 12:50, Thomas Gleixner wrote:
> On Thu, 25 Apr 2019, Enrico Weigelt, metux IT consult wrote:
>
>> On 25.04.19 12:42, Li, Aubrey wrote:
>>>
>>> Yep, I'll make it disabled by default and not switchable and let arch
>>> select it.
>>>
>>
>> That's not quite what I've suggested. Instead:
On Thu, 25 Apr 2019, Enrico Weigelt, metux IT consult wrote:
> On 25.04.19 12:42, Li, Aubrey wrote:
> >
> > Yep, I'll make it disabled by default and not switchable and let arch
> > select it.
> >
>
> That's not quite what I've suggested. Instead:
>
> #1: make the switch depend on the arch's
On 25.04.19 12:42, Li, Aubrey wrote:
>
> Yep, I'll make it disabled by default and not switchable and let arch select
> it.
>
That's not quite what I've suggested. Instead:
#1: make the switch depend on the arch's that support it
#2: still leave it selectable to the user, so somebody who
On 2019/4/25 18:11, Enrico Weigelt, metux IT consult wrote:
> On 25.04.19 03:50, Li, Aubrey wrote:
>
+>>> +config PROC_PID_ARCH_STATUS>>> + bool "Enable
> /proc//arch_status file" Why is this switchable? x86 selects it
> if PROC_FS is enabled and all other>> architectures are
On 24.04.19 23:18, Thomas Gleixner wrote:
Hi,
>> +config PROC_PID_ARCH_STATUS
>> +bool "Enable /proc//arch_status file"
>
> Why is this switchable? x86 selects it if PROC_FS is enabled and all other
> architectures are absolutely not interested in this.
IMHO, it's good to have a switch,
On 25.04.19 03:50, Li, Aubrey wrote:
>>> +>>> +config PROC_PID_ARCH_STATUS>>> + bool "Enable
/proc//arch_status file" Why is this switchable? x86 selects it
if PROC_FS is enabled and all other>> architectures are absolutely not
interested in this.> > Above and this, I was trying to avoid
On 2019/4/25 16:20, Thomas Gleixner wrote:
> On Thu, 25 Apr 2019, Li, Aubrey wrote:
>> On 2019/4/25 15:20, Thomas Gleixner wrote:
>>> Let the arch select CONFIG_PROC_PID_ARCH_STATUS
>>
>> Sorry, I didn't get the point here, above you mentioned not mixing arch and
>> proc code
>> and not enabling
On Thu, 25 Apr 2019, Li, Aubrey wrote:
> On 2019/4/25 15:20, Thomas Gleixner wrote:
> > Let the arch select CONFIG_PROC_PID_ARCH_STATUS
>
> Sorry, I didn't get the point here, above you mentioned not mixing arch and
> proc code
> and not enabling this on x86 right away, then how to let x86
On 2019/4/25 15:20, Thomas Gleixner wrote:
> On Thu, 25 Apr 2019, Li, Aubrey wrote:
>
>> On 2019/4/25 5:18, Thomas Gleixner wrote:
>>> On Mon, 22 Apr 2019, Aubrey Li wrote:
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 5ad92419be19..d5a9c5ddd453 100644
---
On Thu, 25 Apr 2019, Li, Aubrey wrote:
> On 2019/4/25 5:18, Thomas Gleixner wrote:
> > On Mon, 22 Apr 2019, Aubrey Li wrote:
> >> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> >> index 5ad92419be19..d5a9c5ddd453 100644
> >> --- a/arch/x86/Kconfig
> >> +++ b/arch/x86/Kconfig
> >> @@ -208,6
On 2019/4/25 5:18, Thomas Gleixner wrote:
> On Mon, 22 Apr 2019, Aubrey Li wrote:
>> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
>> index 5ad92419be19..d5a9c5ddd453 100644
>> --- a/arch/x86/Kconfig
>> +++ b/arch/x86/Kconfig
>> @@ -208,6 +208,7 @@ config X86
>> select
On Mon, 22 Apr 2019, Aubrey Li wrote:
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 5ad92419be19..d5a9c5ddd453 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -208,6 +208,7 @@ config X86
> select USER_STACKTRACE_SUPPORT
> select VIRT_TO_BUS
> select
The architecture specific information of the running processes
could be useful to the userland. Add /proc//arch_status
interface support to examine process architecture specific
information externally.
Signed-off-by: Aubrey Li
Cc: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Andi Kleen
Cc: Tim Chen
14 matches
Mail list logo
