STE.Config = BYPASS then the PCI ATS is disabled
- If a PASID domain is attached then S1DSS = BYPASS and ATS will be
enabled. This meets the requirements of 13.6.4 to automatically
generate 1:1 ATS replies on the RID.
Update the comments to reflect this.
Signed-off-by: Jason Gunthorpe
Si
With the introduction of the new object and its infrastructure, update the
doc and the vIOMMU graph to reflect that.
Signed-off-by: Nicolin Chen
---
Documentation/userspace-api/iommufd.rst | 58 ++---
1 file changed, 42 insertions(+), 16 deletions(-)
diff --git a
With the introduction of the new object and its infrastructure, update the
doc to reflect that and add a new graph.
Signed-off-by: Nicolin Chen
---
Documentation/userspace-api/iommufd.rst | 66 -
1 file changed, 65 insertions(+), 1 deletion(-)
diff --git a/Documentation
The pull request you sent on Fri, 4 Oct 2024 10:44:57 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux_kselftest-fixes-6.12-rc2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/27cc6fdf720183dce1dbd293483ec5a9cb6b595e
Thank you!
Hi Linus,
Please pull this kselftest fixes update for Linux 6.12-rc2.
This kselftest fixes update for Linux 6.12-rc2 consists of fixes
to build warnings, install scripts, run-time error path, and
git status cleanups to tests:
-- devices/probe: fix for Python3 regex string syntax warnings
On 9/29/24 16:40, Okan Tümüklü wrote:
1:The control flow was simplified by using else if statements instead of goto
structure.
2:Error conditions are handled more clearly.
3:The device_unlock call at the end of the function is guaranteed in all cases.
Github request : https://github.com/torva
On 9/25/24 15:55, Javier Carrasco wrote:
The name of the "load_address" objects has been modified, but the
corresponding entry in the gitignore file must be updated.
Update the load_address entry in the gitignore file to account for
the new names, adding an exception to keep o
1:The control flow was simplified by using else if statements instead of
goto structure.
2:Error conditions are handled more clearly.
3:The device_unlock call at the end of the function is guaranteed in all
cases.
Github request : https://github.com/torvalds/linux/pull/967
// SPDX-License-Identi
The pull request you sent on Sat, 28 Sep 2024 11:52:08 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux_kselftest-next-6.12-rc1-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e7ebdb5161bcb98cb27b7490459419e38dee5b9a
Than
Hi Linus,
Please pull this fixes update for Linux 6.12-rc1.
This kselftest fixes update for Linux 6.12-rc1 consists of an urgent
fix to vDSO as automated testing is failing due to this bug.
diff is attached.
thanks,
-- Shuah
Fix a typo in an email address.
Reported-by: Konstantin Ryabitsev
Closes:
https://lore.kernel.org/all/20240925-rational-succinct-vulture-cca9fb@lemur/T/
Signed-off-by: Alexey Makhalov
---
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS b/MAINTA
The name of the "load_address" objects has been modified, but the
corresponding entry in the gitignore file must be updated.
Update the load_address entry in the gitignore file to account for
the new names, adding an exception to keep on tracking load_address.c.
Signed-off-by: Javie
On 9/25/24 10:25, Javier Carrasco wrote:
On 25/09/2024 17:46, Shuah Khan wrote:
On 9/24/24 06:49, Javier Carrasco wrote:
The name of the "load_address" objects has been modified, but the
corresponding entry in the gitignore file must be updated.
Update the load_address entry in the
On 25/09/2024 17:46, Shuah Khan wrote:
> On 9/24/24 06:49, Javier Carrasco wrote:
>> The name of the "load_address" objects has been modified, but the
>> corresponding entry in the gitignore file must be updated.
>>
>> Update the load_address entry in the git
On 9/24/24 06:49, Javier Carrasco wrote:
The name of the "load_address" objects has been modified, but the
corresponding entry in the gitignore file must be updated.
Update the load_address entry in the gitignore file to account for
the new names.
Signed-off-by: Javier Carrasco
-
The name of the "load_address" objects has been modified, but the
corresponding entry in the gitignore file must be updated.
Update the load_address entry in the gitignore file to account for
the new names, adding an exception to keep on tracking load_address.c.
Signed-off-by: Javie
: 4d0326b60bb753627437fff0f76bf1525bcda422
patch link:
https://lore.kernel.org/r/20240924-selftests-gitignore-v1-4-9755ac883388%40gmail.com
patch subject: [PATCH 4/4] selftests: exec: update gitignore for load_address
config: x86_64-allnoconfig
(https://download.01.org/0day-ci/archive/20240925/202409251828
The pull request you sent on Mon, 23 Sep 2024 21:54:19 -0700:
> https://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git
> tags/hwlock-v6.12
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6db6a19f1ae31e29857b0f6f3e3896c22543be21
Thank you!
--
Deet-doot-
The name of the "load_address" objects has been modified, but the
corresponding entry in the gitignore file must be updated.
Update the load_address entry in the gitignore file to account for
the new names.
Signed-off-by: Javier Carrasco
---
tools/testing/selftests/exec/.gitignore
8dc1bffd6e15da727f7cd07e2d2e7aea728f42ff:
dt-bindings: hwlock: sprd-hwspinlock: convert to YAML (2024-08-12 15:27:14
-0700)
hwspinlock update for v6.12
This converts the Spreadtrum hardware spinlock DeviceTree binding to
YAML, to allow
The pull request you sent on Mon, 16 Sep 2024 19:43:05 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux_kselftest-kunit-6.12-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/194fcd20ebccbc34bba80d7d9b203920087bb01d
Thank you
The pull request you sent on Mon, 16 Sep 2024 18:13:16 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux_kselftest-next-6.12-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/32b72debef5ab9b8bec32fcf3c5d4a62da8a4db2
Thank you!
Hi Linus,
Please pull the following kunit update for Linux 6.12-rc1.
This kunit update for Linux 6.12-rc1 consists of:
-- a new int_pow test suite
-- documentation update to clarify filename best practices
-- kernel-doc fix for EXPORT_SYMBOL_IF_KUNIT
-- change to build compile_commands.json
Hi Linus,
Please pull the following kselftest next update for Linux 6.12-rc1.
This kselftest update for Linux 6.12-rc1 consists of:
-- test coverage for dup_fd() failure handling in unshare_fd()
-- new selftest for the acct() syscall
-- basic uprobe testcase
-- several small fixes and cleanups
Signed-off-by: Ackerley Tng
---
.../kvm/x86_64/private_mem_conversions_test.c | 146 +++---
.../x86_64/private_mem_conversions_test.sh| 3 +
2 files changed, 124 insertions(+), 25 deletions(-)
diff --git a/tools/testing/selftests/kvm/x86_64/private_mem_conversions_test.c
b/too
Update private_mem_conversions_test for various private memory backing
source types.
Signed-off-by: Ackerley Tng
---
.../kvm/x86_64/private_mem_conversions_test.c | 28 ++-
1 file changed, 21 insertions(+), 7 deletions(-)
diff --git a/tools/testing/selftests/kvm/x86_64
The pull request you sent on Fri, 6 Sep 2024 14:46:31 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux_kselftest-kunit-fixes-6.11-rc7-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/b31c4492884252a8360f312a0ac2049349ddf603
Th
Hi Linus,
Please pull the following KUnit fixes second update for Linux 6.11-rc7.
This KUnit fixes update for Linux 6.11-rc7 consists of a fix to
missing function parameter warning found during documentation
build in linux-next.
diff is attached.
thanks,
-- Shuah
The pull request you sent on Wed, 4 Sep 2024 15:39:40 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux_kselftest-kunit-fixes-6.11-rc7
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/120434e5b305defa1fb1e7a38421ed08f93243d5
Than
replied only to Carlos)
>>>>
>>>> On 29.08.24 18:16, Carlos Bilbao wrote:
>>>>> From: Carlos Bilbao
>>>>>
>>>>> Include support to update the vDPA configuration fields of speed and
>>>>> duplex (as needed by VHOST_VD
Hello,
On 8/29/24 9:31 PM, Jason Wang wrote:
> On Fri, Aug 30, 2024 at 5:08 AM Dragos Tatulea wrote:
>> (resending as I accidentally replied only to Carlos)
>>
>> On 29.08.24 18:16, Carlos Bilbao wrote:
>>> From: Carlos Bilbao
>>>
>>> Include su
On Fri, Aug 30, 2024 at 5:08 AM Dragos Tatulea wrote:
>
> (resending as I accidentally replied only to Carlos)
>
> On 29.08.24 18:16, Carlos Bilbao wrote:
> > From: Carlos Bilbao
> >
> > Include support to update the vDPA configuration fields of spee
Hello,
On 8/29/24 4:07 PM, Dragos Tatulea wrote:
> (resending as I accidentally replied only to Carlos)
>
> On 29.08.24 18:16, Carlos Bilbao wrote:
>> From: Carlos Bilbao
>>
>> Include support to update the vDPA configuration fields of speed and
>> duplex (a
(resending as I accidentally replied only to Carlos)
On 29.08.24 18:16, Carlos Bilbao wrote:
> From: Carlos Bilbao
>
> Include support to update the vDPA configuration fields of speed and
> duplex (as needed by VHOST_VDPA_SET_CONFIG). This includes function
> mlx5_vdpa_set_conf
From: Carlos Bilbao
Include support to update the vDPA configuration fields of speed and
duplex (as needed by VHOST_VDPA_SET_CONFIG). This includes function
mlx5_vdpa_set_config() as well as changes in vdpa.c to fill the initial
values to UNKNOWN. Also add a warning message for when
Add a section to Documentation/livepatch/module-elf-format.rst
describing how klp-convert works for fixing relocations.
Signed-off-by: Lukas Hruska
Reviewed-by: Petr Mladek
Reviewed-by: Marcos Paulo de Souza
---
Documentation/livepatch/module-elf-format.rst | 67 +++
1 file cha
From: Masami Hiramatsu (Google)
Update fprobe documentation for the new fprobe on function-graph
tracer. This includes some bahvior changes and pt_regs to
ftrace_regs interface change.
Signed-off-by: Masami Hiramatsu (Google)
---
Changes in v2:
- Update @fregs parameter explanation
On 22/07/2024 09:10, Dang Huynh wrote:
> It's 2024, let's update the copyright year.
>
> Signed-off-by: Dang Huynh
> ---
> arch/arm64/boot/dts/qcom/sm6115-fxtec-pro1x.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/bo
It's 2024, let's update the copyright year.
Signed-off-by: Dang Huynh
---
arch/arm64/boot/dts/qcom/sm6115-fxtec-pro1x.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/qcom/sm6115-fxtec-pro1x.dts
b/arch/arm64/boot/dts/qcom/sm6115-fxtec-pro1x
:
Live update is a technique wherein an application saves its state, exec's
to an updated version of itself, and restores its state. Clients of the
application experience a brief suspension of service, on the order of
100's of milliseconds, but are otherwise unaffected.
Define and implement
On Tue, 16 Jul 2024 14:13:38 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> This is required to make numa emulation code architecture independent so
> that it can be moved to generic code in following commits.
>
> Signed-off-by: Mike Rapoport (Microsoft)
Not the most intu
12, 2024 at 9:19 PM Steve Sistare
> >>> wrote:
> >>>>
> >>>> Live update is a technique wherein an application saves its state, exec's
> >>>> to an updated version of itself, and restores its state. Clients of the
> >>>> app
On 7/16/2024 1:30 AM, Jason Wang wrote:
On Mon, Jul 15, 2024 at 10:29 PM Steven Sistare
wrote:
On 7/14/2024 10:14 PM, Jason Wang wrote:
On Fri, Jul 12, 2024 at 9:19 PM Steve Sistare wrote:
Live update is a technique wherein an application saves its state, exec's
to an updated versi
From: "Mike Rapoport (Microsoft)"
This is required to make numa emulation code architecture independent so
that it can be moved to generic code in following commits.
Signed-off-by: Mike Rapoport (Microsoft)
---
arch/x86/include/asm/numa.h | 2 ++
arch/x86/mm/numa.c | 22 +++
On Mon, 15 Jul 2024 14:47:45 -0400
Steven Rostedt wrote:
> From: "Steven Rostedt (Google)"
>
> Gone but never forgotten.
>
> [ Also moved Daniel's name to be consistent with the alphabetical order ]
>
Reviewed-by: Masami Hiramatsu (Google)
Thank you,
> Signed-off-by: Steven Rostedt (Googl
On Mon, Jul 15, 2024 at 10:29 PM Steven Sistare
wrote:
>
> On 7/14/2024 10:14 PM, Jason Wang wrote:
> > On Fri, Jul 12, 2024 at 9:19 PM Steve Sistare
> > wrote:
> >>
> >> Live update is a technique wherein an application saves its state, exec's
> >
On 2024-07-15 15:13, Steven Rostedt wrote:
On Mon, 15 Jul 2024 15:10:17 -0400
Mathieu Desnoyers wrote:
On 2024-07-15 14:47, Steven Rostedt wrote:
From: "Steven Rostedt (Google)"
Gone but never forgotten.
[ Also moved Daniel's name to be consistent with the alphabetical order ]
Hi Steven,
On Mon, 15 Jul 2024 15:10:17 -0400
Mathieu Desnoyers wrote:
> On 2024-07-15 14:47, Steven Rostedt wrote:
> > From: "Steven Rostedt (Google)"
> >
> > Gone but never forgotten.
> >
> > [ Also moved Daniel's name to be consistent with the alphabetical order ]
>
> Hi Steven,
>
> You appear to
On 2024-07-15 14:47, Steven Rostedt wrote:
From: "Steven Rostedt (Google)"
Gone but never forgotten.
[ Also moved Daniel's name to be consistent with the alphabetical order ]
Hi Steven,
You appear to have missed this entry from SCHEDULER:
R: Daniel Bristot de Oliveira (SCHED_DEADLINE
From: "Steven Rostedt (Google)"
Gone but never forgotten.
[ Also moved Daniel's name to be consistent with the alphabetical order ]
Signed-off-by: Steven Rostedt (Google)
---
CREDITS | 10 +++---
MAINTAINERS | 3 ---
2 files changed, 7 insertions(+), 6 deletions(-)
diff --git a/CRED
On 7/14/2024 10:14 PM, Jason Wang wrote:
On Fri, Jul 12, 2024 at 9:19 PM Steve Sistare wrote:
Live update is a technique wherein an application saves its state, exec's
to an updated version of itself, and restores its state. Clients of the
application experience a brief suspension of se
On Fri, Jul 12, 2024 at 9:19 PM Steve Sistare wrote:
>
> Live update is a technique wherein an application saves its state, exec's
> to an updated version of itself, and restores its state. Clients of the
> application experience a brief suspension of service, on the or
On 7/12/2024 9:18 AM, Steve Sistare wrote:
Live update is a technique wherein an application saves its state, exec's
to an updated version of itself, and restores its state. Clients of the
application experience a brief suspension of service, on the order of
100's of millisecond
Live update is a technique wherein an application saves its state, exec's
to an updated version of itself, and restores its state. Clients of the
application experience a brief suspension of service, on the order of
100's of milliseconds, but are otherwise unaffected.
Define and
On 9.07.2024 8:49 AM, Naina Mehta wrote:
> Rename qdss@8880 memory region as qlink_logging memory region
> and add qdss_mem memory region at address of 0x8850,
> qlink_logging is being added at the memory region at the address
> of 0x8880 as the region is being used by modem firmware.
>
Rename qdss@8880 memory region as qlink_logging memory region
and add qdss_mem memory region at address of 0x8850,
qlink_logging is being added at the memory region at the address
of 0x8880 as the region is being used by modem firmware.
Since different DSM region size is required for di
On Fri, 28 Jun 2024 19:40:55 +0200, Luca Weiss wrote:
> I'm slowly migrating my mail to a new domain, add an entry to map the
> mail address. Just for clarity, my work-related @fairphone.com email
> stays unchanged.
>
>
Applied, thanks!
[1/1] mailmap: Update Luca W
From: Masami Hiramatsu (Google)
Update fprobe documentation for the new fprobe on function-graph
tracer. This includes some bahvior changes and pt_regs to
ftrace_regs interface change.
Signed-off-by: Masami Hiramatsu (Google)
---
Changes in v2:
- Update @fregs parameter explanation
Hi Arseniy,
On Fri, Jun 21, 2024 at 10:25:40PM GMT, Arseniy Krasnov wrote:
Previous calculation of 'free_space' was wrong (but worked as expected
in most cases, see below), because it didn't account number of bytes in
rx queue. Let's rework 'free_space' calculation in the following way:
as this
On 6/26/2024 9:12 PM, Konrad Dybcio wrote:
On 24.06.2024 1:21 PM, Naina Mehta wrote:
On 6/18/2024 7:08 PM, Konrad Dybcio wrote:
On 6/18/24 15:13, Naina Mehta wrote:
Rename qdss@8880 memory region as qlink_logging memory region
and add qdss_mem memory region at address of 0x8850.
I'm slowly migrating my mail to a new domain, add an entry to map the
mail address. Just for clarity, my work-related @fairphone.com email
stays unchanged.
Signed-off-by: Luca Weiss
---
Since my email address also appears in a bunch of drivers and arm(64)
files, and two devicetree binding files,
Now it is safe to remove dependency from stop_machine() for us to patch
code in ftrace.
Signed-off-by: Andy Chiu
---
arch/riscv/kernel/ftrace.c | 53 --
1 file changed, 4 insertions(+), 49 deletions(-)
diff --git a/arch/riscv/kernel/ftrace.c b/arch/ri
On 24.06.2024 1:21 PM, Naina Mehta wrote:
>
>
> On 6/18/2024 7:08 PM, Konrad Dybcio wrote:
>>
>>
>> On 6/18/24 15:13, Naina Mehta wrote:
>>> Rename qdss@8880 memory region as qlink_logging memory region
>>> and add qdss_mem memory region at address of 0x8850.
>>> Split mpss_dsmharq_mem re
On Mon, 17 Jun 2024 23:22:26 +0200, André Apitzsch wrote:
> Add accelerometer, magnetometer, regulator and temperature sensor alert
> interrupt and update framebuffer supplies.
>
>
Applied, thanks!
[1/3] ARM: dts: qcom: msm8926-motorola-peregrine: Add accelerometer,
magnetomete
7; now is not needed.
>
> Yeah, so this patch should also mitigate issue reported by Alex (added in
> CC), right?
>
> If yes, please mention that problem and add a Reported-by giving credit to
> Alex.
Yes, of course!
>
>>
>> Also here is some performance
On Fri, Jun 21, 2024 at 10:25:40PM GMT, Arseniy Krasnov wrote:
Previous calculation of 'free_space' was wrong (but worked as expected
in most cases, see below), because it didn't account number of bytes in
rx queue. Let's rework 'free_space' calculation in the following way:
as this value is cons
On 6/18/2024 7:08 PM, Konrad Dybcio wrote:
On 6/18/24 15:13, Naina Mehta wrote:
Rename qdss@8880 memory region as qlink_logging memory region
and add qdss_mem memory region at address of 0x8850.
Split mpss_dsmharq_mem region into 2 separate regions and
reduce the size of mpssadsp_me
Previous calculation of 'free_space' was wrong (but worked as expected
in most cases, see below), because it didn't account number of bytes in
rx queue. Let's rework 'free_space' calculation in the following way:
as this value is considered free space at rx side from tx point of view,
it must be eq
This test checks, that we send exactly expected number of credit
update packets during deferred credit update optimization. Test
work in client/server modes:
1) Client just connects to server and send 256Kb of data. 256Kb
is chosen because it is default space for vsock peer. After
This patchset contains:
0001 - patch which reworks deferred credit update. Pls see commit message,
it contains full description of this problem.
0002 - test which uses vsockmon interface, and checks that deferred
credit update works as expected by parsing raw packets.
Arseniy
On 21/06/2024 13:46, Gokul Sriram Palanisamy wrote:
> Fixed issue in reading halt-regs parameter from device-tree.
What issue?
That's a terrible commit msg. Explain what is the problem, how can it be
reproduced.
>
> Signed-off-by: Sricharan R
> Signed-off-by: Gokul Sriram Palanisamy
> ---
>
Fixed issue in reading halt-regs parameter from device-tree.
Signed-off-by: Sricharan R
Signed-off-by: Gokul Sriram Palanisamy
---
drivers/remoteproc/qcom_q6v5_wcss.c | 22 ++
1 file changed, 14 insertions(+), 8 deletions(-)
diff --git a/drivers/remoteproc/qcom_q6v5_wcss.c
On 6/18/24 15:13, Naina Mehta wrote:
Rename qdss@8880 memory region as qlink_logging memory region
and add qdss_mem memory region at address of 0x8850.
Split mpss_dsmharq_mem region into 2 separate regions and
reduce the size of mpssadsp_mem region.
Signed-off-by: Naina Mehta
---
A
Rename qdss@8880 memory region as qlink_logging memory region
and add qdss_mem memory region at address of 0x8850.
Split mpss_dsmharq_mem region into 2 separate regions and
reduce the size of mpssadsp_mem region.
Signed-off-by: Naina Mehta
---
arch/arm64/boot/dts/qcom/sdx75.dtsi | 18 +++
On 6/17/24 23:22, André Apitzsch via B4 Relay wrote:
From: André Apitzsch
Add alert interrupt for the temperature sensor of Motorola Moto G 4G
(2013), although not used by the driver yet.
Signed-off-by: André Apitzsch
---
Reviewed-by: Konrad Dybcio
Konrad
Add accelerometer, magnetometer, regulator and temperature sensor alert
interrupt and update framebuffer supplies.
Signed-off-by: André Apitzsch
---
Changes in v2:
- Split commit into three commits
- Link to v1:
https://lore.kernel.org/r/20240616-peregrine-v1-1-85d14ae1a...@apitzsch.eu
From: André Apitzsch
Add alert interrupt for the temperature sensor of Motorola Moto G 4G
(2013), although not used by the driver yet.
Signed-off-by: André Apitzsch
---
arch/arm/boot/dts/qcom/qcom-msm8926-motorola-peregrine.dts | 12
1 file changed, 12 insertions(+)
diff --git a/
From: Masami Hiramatsu (Google)
Update fprobe documentation for the new fprobe on function-graph
tracer. This includes some bahvior changes and pt_regs to
ftrace_regs interface change.
Signed-off-by: Masami Hiramatsu (Google)
---
Changes in v2:
- Update @fregs parameter explanation
Now it is safe to remove dependency from stop_machine() for us to patch
code in ftrace.
Signed-off-by: Andy Chiu
---
arch/riscv/kernel/ftrace.c | 53 --
1 file changed, 4 insertions(+), 49 deletions(-)
diff --git a/arch/riscv/kernel/ftrace.c b/arch/ri
From: "Steven Rostedt (Google)"
For a persistent ring buffer that is saved across boots, if function
tracing was performed in the previous boot, it only saves the address of
the functions and uses "%pS" to print their names. But the current boot,
those functions may be in different locations. The
From: "Steven Rostedt (Google)"
For a persistent ring buffer that is saved across boots, if function
tracing was performed in the previous boot, it only saves the address of
the functions and uses "%pS" to print their names. But the current boot,
those functions may be in different locations. The
From: "Steven Rostedt (Google)"
For a persistent ring buffer that is saved across boots, if function
tracing was performed in the previous boot, it only saves the address of
the functions and uses "%pS" to print their names. But the current boot,
those functions may be in different locations. The
From: "Steven Rostedt (Google)"
For a persistent ring buffer that is saved across boots, if function
tracing was performed in the previous boot, it only saves the address of
the functions and uses "%pS" to print their names. But the current boot,
those functions may be in different locations. The
From: "Steven Rostedt (Google)"
The ftrace subops is only defined if CONFIG_DYNAMIC_FTRACE is enabled. If
it is not, function tracing is extremely limited, and the subops in the
ftrace_ops structure is not defined (and will fail to compile). If
DYNAMIC_FTRACE is not enabled, then function graph f
On 5/20/24 07:42, Yang Li wrote:
> The patch updates the function documentation comment for
> rv_en(dis)able_monitor to adhere to the kernel-doc specification.
>
> Signed-off-by: Yang Li
Acked-by: Daniel Bristot de Oliveira
Thanks
-- Daniel
From: "Steven Rostedt (Google)"
The change to update the permissions of the eventfs_inode had the
misconception that using the tracefs_inode would find all the
eventfs_inodes that have been updated and reset them on remount.
The problem with this approach is that the eventfs_inodes
From: "Steven Rostedt (Google)"
When a remount happens, if a gid or uid is specified update the inodes to
have the same gid and uid. This will allow the simplification of the
permissions logic for the dynamically created files and directories.
Cc: sta...@vger.kernel.org
Fixes: baa
The patch updates the function documentation comment for
rv_en(dis)able_monitor to adhere to the kernel-doc specification.
Signed-off-by: Yang Li
---
kernel/trace/rv/rv.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kernel/trace/rv/rv.c b/kernel/trace/rv/rv.c
index 2f68e93fff0b..df0745a
Hi Yang
On 5/17/24 11:14, Yang Li wrote:
> The patch updates the function documentation comment for
> rv_en(dis)able_monitor to adhere to the kernel-doc specification.
>
> Signed-off-by: Yang Li
> ---
> kernel/trace/rv/rv.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/kernel/trac
The patch updates the function documentation comment for
rv_en(dis)able_monitor to adhere to the kernel-doc specification.
Signed-off-by: Yang Li
---
kernel/trace/rv/rv.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kernel/trace/rv/rv.c b/kernel/trace/rv/rv.c
index 2f68e93fff0b..df0745a
Add a section to Documentation/livepatch/module-elf-format.rst
describing how klp-convert works for fixing relocations.
Signed-off-by: Lukas Hruska
Reviewed-by: Petr Mladek
Reviewed-by: Marcos Paulo de Souza
---
Documentation/livepatch/module-elf-format.rst | 67 +++
1 file cha
From: Masami Hiramatsu (Google)
Update fprobe documentation for the new fprobe on function-graph
tracer. This includes some bahvior changes and pt_regs to
ftrace_regs interface change.
Signed-off-by: Masami Hiramatsu (Google)
---
Changes in v2:
- Update @fregs parameter explanation
From: Masami Hiramatsu (Google)
Update fprobe documentation for the new fprobe on function-graph
tracer. This includes some bahvior changes and pt_regs to
ftrace_regs interface change.
Signed-off-by: Masami Hiramatsu (Google)
---
Changes in v2:
- Update @fregs parameter explanation
From: "Steven Rostedt (Google)"
For a persistent ring buffer that is saved across boots, if function
tracing was performed in the previous boot, it only saves the address of
the functions and uses "%pS" to print their names. But the current boot,
those functions may be in different locations. The
On 09/04/2024 20:36, Luca Weiss wrote:
> Follow the gpio-hog bindings and use otg-hog as node name.
>
> Signed-off-by: Luca Weiss
> ---
> arch/arm/boot/dts/qcom/qcom-msm8974-lge-nexus5-hammerhead.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Krzysztof Kozlowski
Best
On Wed, 10 Apr 2024 08:44:00 +0900
Masami Hiramatsu (Google) wrote:
> Looks good to me.
>
> Acked-by: Masami Hiramatsu (Google)
Thanks.
>
> BTW, isn't this a real bugfix, because the page_touched can be
> bigger than nr_pages without this fix?
Yes, I simply forgot to add the Cc stable.
--
_INTCNT, &next_page->entries);
>
> - local_inc(&cpu_buffer->pages_touched);
> /*
>* Just make sure we have seen our old_write and synchronize
> * with any interrupts that come in.
> @@ -1430,8 +1429,9 @@ static void rb_tail_page_update(stru
t come in.
@@ -1430,8 +1429,9 @@ static void rb_tail_page_update(struct
ring_buffer_per_cpu *cpu_buffer,
*/
local_set(&next_page->page->commit, 0);
- /* Again, either we update tail_page or an interrupt does */
- (void)cmpxchg(&
On Tue, 9 Apr 2024 at 21:37, Luca Weiss wrote:
>
> Follow the gpio-hog bindings and use otg-hog as node name.
>
> Signed-off-by: Luca Weiss
> ---
> arch/arm/boot/dts/qcom/qcom-msm8974-lge-nexus5-hammerhead.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Reviewed-by: Dmitry Baryshk
Follow the gpio-hog bindings and use otg-hog as node name.
Signed-off-by: Luca Weiss
---
arch/arm/boot/dts/qcom/qcom-msm8974-lge-nexus5-hammerhead.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/qcom/qcom-msm8974-lge-nexus5-hammerhead.dts
b/arch/arm/boo
1 - 100 of 9995 matches
Mail list logo
