On 18/1/21 9:57 pm, Mel Gorman wrote:
On Mon, Jan 18, 2021 at 09:32:18PM +1100, Imran Khan wrote:
task_numa_fault is invoked from do_numa_page/do_huge_pmd_numa_page,
for task_numa_work induced memory faults. task_numa_work is scheduled
from task_tick_numa which is invoked only if
we can avoid checking it again in task_numa_fault.
Signed-off-by: Imran Khan
---
kernel/sched/fair.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 04a3ce20da67..282ebd6c4197 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
On 6/1/21 3:22 pm, Roman Gushchin wrote:
Imran Khan reported a regression in hackbench results caused by the
commit f2fe7b09a52b ("mm: memcg/slab: charge individual slab objects
instead of pages"). The regression is noticeable in the case of
a consequent allocation of several relati
e with those obtained
from v5.8 kernel.
Signed-off-by: Imran Khan
---
mm/memcontrol.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 0d74b80..c04633c 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -3256,7 +3256,7 @@ static void ref
On 8/23/2017 2:06 AM, Peter Zijlstra wrote:
> On Mon, Aug 21, 2017 at 03:55:53PM +0530, Imran Khan wrote:
>> khungtask by default monitors either all tasks or no tasks at all
>> for long unterruptible sleeps.
>> For Android like environments this arrangement is not optimal b
s,
Imran
> Thanks!
>
> BR, Shile
>
> -Original Message-
> From: Imran Khan [mailto:kim...@codeaurora.org]
> Sent: Monday, August 21, 2017 6:26 PM
> To: mi...@kernel.org
> Cc: imrank140...@gmail.com; Imran Khan ; Luis R.
> Rodriguez ; Kees Cook ; Peter
> Zij
, /proc/sys/kernel/
hung_task_check_selected, to enable monitoring of selected tasks using
khungtask daemon. If this sysctl option is enabled then only the tasks
specified in /proc/hung_task_monitor_list are monitored otherwise all
tasks are monitored, just like the default case.
Signed-off-by: Imran
On 5/2/2017 4:17 AM, Bjorn Andersson wrote:
> On Mon 01 May 06:07 PDT 2017, Imran Khan wrote:
>
>> On 4/26/2017 4:38 AM, Bjorn Andersson wrote:
>>> On Tue 25 Apr 10:13 PDT 2017, Rob Herring wrote:
>>>
>>>> On Mon, Apr 24, 2017 at 6:05 PM, Bjorn Andersson
On 4/26/2017 4:38 AM, Bjorn Andersson wrote:
> On Tue 25 Apr 10:13 PDT 2017, Rob Herring wrote:
>
>> On Mon, Apr 24, 2017 at 6:05 PM, Bjorn Andersson
>> wrote:
>>> On Mon 24 Apr 09:27 PDT 2017, Rob Herring wrote:
> [..]
Splitting things between common and private seems like a good direction.
On 4/25/2017 4:35 AM, Bjorn Andersson wrote:
> On Mon 24 Apr 09:27 PDT 2017, Rob Herring wrote:
>
>> On Mon, Apr 24, 2017 at 11:00 AM, Imran Khan wrote:
>>> On 4/18/2017 7:53 PM, Imran Khan wrote:
>>> Hi Rob,
>>> Could you please provide some fe
On 4/18/2017 7:53 PM, Imran Khan wrote:
Hi Rob,
Could you please provide some feedback so that this discussion can move forward
and ABI document can be finalized?
Without the ABI document we are not able to get the corresponding driver
finalized and get merged.
Thanks again for your time,
Imran
Hi Rob,
On 3/6/2017 12:19 PM, Imran Khan wrote:
> On 2/22/2017 7:34 PM, Rob Herring wrote:
>> On Mon, Feb 20, 2017 at 10:17:15PM +0530, Khan, Imran wrote:
>>> The socinfo ABI document describes the information provided
>>> by socinfo driver and the corresponding at
On 4/12/2017 7:30 PM, Chalamarla, Tirumalesh wrote:
>
>
> On 4/11/17, 10:13 PM, "linux-arm-kernel on behalf of Imran Khan"
> kim...@codeaurora.org> wrote:
>
> On 4/7/2017 7:36 AM, Ganesh Mahendran wrote:
> > 2017-04-06 23:58 GMT+08:00 Catalin Marin
On 4/7/2017 7:36 AM, Ganesh Mahendran wrote:
> 2017-04-06 23:58 GMT+08:00 Catalin Marinas :
>> On Thu, Apr 06, 2017 at 12:52:13PM +0530, Imran Khan wrote:
>>> On 4/5/2017 10:13 AM, Imran Khan wrote:
>>>>> We may have to revisit this logic and consider L1_CACHE_B
On 4/5/2017 10:13 AM, Imran Khan wrote:
Hi Catalin,
> Hi Catalin,
>
>> From: Catalin Marinas
>> Date: Mon, Mar 21, 2016 at 10:44 PM
>> Subject: Re: [PATCH] Revert "arm64: Increase the max granular size"
>> To: "Chalamarla, Tirumalesh&quo
On 2/22/2017 7:34 PM, Rob Herring wrote:
> On Mon, Feb 20, 2017 at 10:17:15PM +0530, Khan, Imran wrote:
>> The socinfo ABI document describes the information provided
>> by socinfo driver and the corresponding attributes to access
>> that information.
>>
&
Hi,
I am observing some degradation in context switch performance (reported by
sched benchmark of perf), after including the change
to keep thread_info in sp_el0:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6cdf9c7ca687e01840d0215437620a20263012fc
However, if I use
The socinfo ABI document describes the information provided
by socinfo driver and the corresponding attributes to access
that information.
Signed-off-by: Imran Khan
---
.../ABI/testing/sysfs-driver-qcom_socinfo | 171 +
1 file changed, 171 insertions(+)
create mode
The SoC info driver provides information such as Chip ID,
Chip family, serial number and other such details about
Qualcomm SoCs to user space, so that if needed some user
space utility(like antutu) can query such information
using sysfs interface.
Signed-off-by: Imran Khan
---
drivers/soc/qcom
socinfo can not be read use a single dummy socinfo
with error values.
- Removed usage of early_machine_is_xxx.
Imran Khan (2):
soc: qcom: Add SoC info driver
Documentation/ABI: Add ABI infomation for QCOM socinfo driver
.../ABI/testing/sysfs-driver-qcom_socinfo
On 2/18/2017 4:06 AM, Stephen Boyd wrote:
> On 01/10, Imran Khan wrote:
>> The socinfo ABI document describes the information provided
>> by socinfo driver and the corresponding attributes to access
>> that information.
>>
>> Signed-off-by: Imran Khan
>>
Hi Stephen,
Thanks for your review comments.
On 2/18/2017 4:21 AM, Stephen Boyd wrote:
> On 02/16, Imran Khan wrote:
>> diff --git a/drivers/soc/qcom/smem.c b/drivers/soc/qcom/smem.c
>> index 18ec52f..4f0ccf8 100644
>> --- a/drivers/soc/qcom/smem.c
>> +++ b/drivers/
The SoC info driver provides information such as Chip ID,
Chip family, serial number and other such details about
Qualcomm SoCs to user space, so that if needed some user
space utility(like antutu) can query such information
using sysfs interface.
Signed-off-by: Imran Khan
---
v8 -->
On 2/15/2017 5:54 AM, Bjorn Andersson wrote:
> On Tue 10 Jan 07:48 PST 2017, Imran Khan wrote:
>
>> diff --git a/drivers/soc/qcom/socinfo.c b/drivers/soc/qcom/socinfo.c
>> new file mode 100644
>> index 000..40c180d
>> --- /dev/null
>> +++ b/drivers/
-by: Imran Khan
---
drivers/base/firmware_class.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/base/firmware_class.c b/drivers/base/firmware_class.c
index 4497d26..d09c1aa 100644
--- a/drivers/base/firmware_class.c
+++ b/drivers/base/firmware_class.c
@@ -339,6 +339,9 @@ static void
The SoC info driver provides information such as Chip ID,
Chip family, serial number and other such details about
Qualcomm SoCs to user space, so that if needed some user
space utility(like antutu) can query such information
using sysfs interface.
Signed-off-by: Imran Khan
---
v7 -->
The socinfo ABI document describes the information provided
by socinfo driver and the corresponding attributes to access
that information.
Signed-off-by: Imran Khan
---
Documentation/ABI/stable/sysfs-driver-qcom_socinfo | 147 +
1 file changed, 147 insertions(+)
create mode
This is patchset v8, it takes care of compilation warnings
reported in v7.
Imran Khan (2):
soc: qcom: Add SoC info driver
Documentation/ABI: Add ABI information for QCOM socinfo driver
Documentation/ABI/stable/sysfs-driver-qcom_socinfo | 147 ++
drivers/soc/qcom/Kconfig
Add initial pinctrl driver to support pin configuration with
pinctrl framework for msm8998.
Signed-off-by: Imran Khan
---
.../bindings/pinctrl/qcom,msm8998-pinctrl.txt | 200 ++
drivers/pinctrl/qcom/Kconfig |8 +
drivers/pinctrl/qcom/Makefile
The socinfo ABI document describes the information provided
by socinfo driver and the corresponding attributes to access
that information.
Signed-off-by: Imran Khan
---
Documentation/ABI/stable/sysfs-driver-qcom_socinfo | 147 +
1 file changed, 147 insertions(+)
create mode
M specific interpretation of SMEM socinfo
content
- Read machine value from DT, rather than using soc-id as index
in an ever increasing array of machine names
Imran Khan (2):
soc: qcom: Add SoC info driver
Documentation/ABI: Add ABI information for QCOM socinfo driver
Documentation/ABI/st
The SoC info driver provides information such as Chip ID,
Chip family, serial number and other such details about
Qualcomm SoCs to user space, so that if needed some user
space utility(like antutu) can query such information
using sysfs interface.
Signed-off-by: Imran Khan
---
v6 --> v7:
- S
ue from DT, rather than using soc-id as index
in an ever increasing array of machine names
Imran Khan (2):
soc: qcom: Add SoC info driver
Documentation/ABI: Add ABI information for QCOM socinfo driver
Documentation/ABI/stable/sysfs-driver-qcom_socinfo | 147 ++
drivers/soc/qc
The socinfo ABI document describes the information provided
by socinfo driver and the corresponding attributes to access
that information.
Signed-off-by: Imran Khan
---
Documentation/ABI/stable/sysfs-driver-qcom_socinfo | 147 +
1 file changed, 147 insertions(+)
create mode
The SoC info driver provides information such as Chip ID,
Chip family, serial number and other such details about
Qualcomm SoCs to user space, so that if needed some user
space utility(like antutu) can query such information
using sysfs interface.
Signed-off-by: Imran Khan
---
v6 --> v7:
- S
On 12/29/2016 4:05 AM, Stephen Boyd wrote:
> On 12/23, Imran Khan wrote:
>> On 12/22/2016 6:01 AM, Stephen Boyd wrote:
>>>
>>> Raw numbers sounds fine, but how do we know what ODM it is to
>>> understand how to parse the numbers appropriately? Perhaps the
>&g
On 12/22/2016 6:01 AM, Stephen Boyd wrote:
> On 12/21, Imran Khan wrote:
>> On 12/21/2016 4:20 AM, Stephen Boyd wrote:
>>>
>>> I'll wait to see what the next patch version has. We will
>>> probably need to have some way to know which ODM the kernel i
On 12/21/2016 4:20 AM, Stephen Boyd wrote:
> On 12/18, Imran Khan wrote:
>>
>> I had discussed this with Bjorn and it was recommended to keep it out of
>> smem.h. If needed I can move it back there.
>
> Ok no worries from me then if this has already been discussed.
>
On 12/17/2016 6:56 AM, Stephen Boyd wrote:
> On 12/15, Imran Khan wrote:
>> On 12/14/2016 5:56 AM, Stephen Boyd wrote:
>>> On 12/12, Imran Khan wrote:
>>>> The SoC info driver provides information such as Chip ID,
>>>> Chip family, serial number and o
On 12/14/2016 5:56 AM, Stephen Boyd wrote:
> On 12/12, Imran Khan wrote:
>> The SoC info driver provides information such as Chip ID,
>> Chip family, serial number and other such details about
>> Qualcomm SoCs.
>
> Yes but why do we care?
>
We intend to expose some
On 12/5/2016 11:35 PM, Bjorn Andersson wrote:
> On Wed 16 Nov 05:22 PST 2016, Imran Khan wrote:
>
>>
>> diff --git a/drivers/soc/qcom/socinfo.c b/drivers/soc/qcom/socinfo.c
>> new file mode 100644
>> index 000..eca46df
>> --- /dev/null
>> +++ b/dr
The SoC info driver provides information such as Chip ID,
Chip family, serial number and other such details about
Qualcomm SoCs.
Signed-off-by: Imran Khan
---
v5 --> v6:
- use dev_ext_attribute to represent SMEM image items
- Avoid redundant function calls
- Avoid use of unnecessary glo
On 11/15/2016 10:57 AM, Bjorn Andersson wrote:
> On Mon 14 Nov 06:30 PST 2016, Imran Khan wrote:
>
>> On 11/8/2016 1:05 AM, Bjorn Andersson wrote:
>>> On Mon 07 Nov 06:35 PST 2016, Imran Khan wrote:
>>>
>>>
>>>
>>> [..]
>>>
The SoC info driver provides information such as Chip ID,
Chip family, serial number and other such details about
Qualcomm SoCs.
Signed-off-by: Imran Khan
---
v4 --> v5:
- Removed redundant function socinfo_print
v3 --> v4:
- Corrected makefile so that smem and socinfo are treated
On 11/8/2016 1:05 AM, Bjorn Andersson wrote:
> On Mon 07 Nov 06:35 PST 2016, Imran Khan wrote:
>
>
>
> [..]
>
>>>> +static void socinfo_populate(struct soc_device_attribute *soc_dev_attr)
>>>> +{
>>>> + u32 soc_version = socinfo_get_versio
information
can be useful.
Signed-off-by: Imran Khan
---
include/linux/sys_soc.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/linux/sys_soc.h b/include/linux/sys_soc.h
index 2739ccb..e2eadd8 100644
--- a/include/linux/sys_soc.h
+++ b/include/linux/sys_soc.h
@@ -13,6 +13,9
The SoC info driver provides information such as Chip ID,
Chip family, serial number and other such details about
Qualcomm SoCs.
Signed-off-by: Imran Khan
---
v3 --> v4:
- Corrected makefile so that smem and socinfo are treated as one module
- Moved the code snippet to get socinfo smem i
02 Nov 03:06 PDT 2016, Imran Khan wrote:
>
>> The SoC info driver provides information such as Chip ID,
>> Chip family, serial number and other such details about
>> Qualcomm SoCs.
>>
>> Signed-off-by: Imran Khan
> [..]
>> diff --git a/drivers/soc/qcom/
The SoC info driver provides information such as Chip ID,
Chip family, serial number and other such details about
Qualcomm SoCs.
Signed-off-by: Imran Khan
---
v2 --> v3:
- Add support to toss soc information data into entropy pool
- Since socinfo is rolled into smem driver, compile
On 10/28/2016 1:35 AM, Linus Walleij wrote:
> On Thu, Oct 27, 2016 at 11:22 AM, Imran Khan wrote:
>
>> The SoC info driver provides information such as Chip ID,
>> Chip family, serial number and other such details about
>> Qualcomm SoCs.
>>
>> Signed-off-by
On 10/27/2016 7:11 PM, Arnd Bergmann wrote:
> On Thursday, October 27, 2016 6:40:27 PM CEST Imran Khan wrote:
>> On 10/26/2016 8:16 PM, Arnd Bergmann wrote:
>>> On Wednesday, October 26, 2016 7:42:08 PM CEST Imran Khan wrote:
>>>> On 10/26/2016 7:35 PM, Arnd Ber
The SoC info driver provides information such as Chip ID,
Chip family, serial number and other such details about
Qualcomm SoCs.
Signed-off-by: Imran Khan
---
Changes since v1:
- Removed inclusion of system_misc.h
- merged socinfo.h into socinfo.c
- made platform type and subtype arrays
On 10/26/2016 8:16 PM, Arnd Bergmann wrote:
> On Wednesday, October 26, 2016 7:42:08 PM CEST Imran Khan wrote:
>> On 10/26/2016 7:35 PM, Arnd Bergmann wrote:
>>>>> As we are talking about generic soc_device_attribute fields, I was hoping
>>>>> that
>>
On 10/26/2016 7:35 PM, Arnd Bergmann wrote:
>> > As we are talking about generic soc_device_attribute fields, I was hoping
>> > that
>> > having a vendor field would be helpful as along with family it would
>> > provide
>> > a more thorough information. Also as more than one foundries may be used
On 10/26/2016 2:19 AM, Arnd Bergmann wrote:
> On Tuesday, October 25, 2016 3:23:34 PM CEST Imran Khan wrote:
>> On 10/21/2016 4:03 PM, Arnd Bergmann wrote:
>>>> +/* socinfo: sysfs functions */
>>>
>>> This seems overly verbose, having both raw and human-read
On 10/21/2016 4:03 PM, Arnd Bergmann wrote:
> On Thursday, October 20, 2016 7:36:22 PM CEST Imran Khan wrote:
>> +#include
>> +#include
>> +
>> +#include
>
> I don't see anything here that needs asm/system_misc.h
>
Okay. I will not use this heade
On 10/20/2016 8:50 PM, Andy Gross wrote:
> On Thu, Oct 20, 2016 at 07:36:22PM +0530, Imran Khan wrote:
>> The SoC info driver provides information such as Chip ID,
>> Chip family, serial number and other such details about
>> Qualcomm SoCs.
>>
&
The SoC info driver provides information such as Chip ID,
Chip family, serial number and other such details about
Qualcomm SoCs.
Signed-off-by: Imran Khan
---
.../devicetree/bindings/soc/qcom/qcom,socinfo.txt | 18 +
drivers/soc/qcom/socinfo.c | 1173
58 matches
Mail list logo
