Hi Krishna,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 3006adf3be79cde4d14b1800b963b82b6e5572e0]
url:
https://github.com/intel-lab-lkp/linux/commits/Krishna-chaitanya-chundru/bus-mhi-host-Add-tracing-support/2023-135816
base:
This change adds ftrace support for following functions which
helps in debugging the issues when there is Channel state & MHI
state change and also when we receive data and control events:
1. mhi_intvec_mhi_states
2. mhi_process_data_event_ring
3. mhi_process_ctrl_ev_ring
4. mhi_gen_tre
5.
Hi Krishna,
kernel test robot noticed the following build errors:
[auto build test ERROR on 3006adf3be79cde4d14b1800b963b82b6e5572e0]
url:
https://github.com/intel-lab-lkp/linux/commits/Krishna-chaitanya-chundru/bus-mhi-host-Add-tracing-support/2023-101955
base:
Hi Petr,
kernel test robot noticed the following build warnings:
[auto build test WARNING on shuah-kselftest/next]
[also build test WARNING on shuah-kselftest/fixes linus/master v6.6
next-20231110]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch
On Fri, 10 Nov 2023 20:44:22 -0500
Steven Rostedt wrote:
> On Fri, 10 Nov 2023 16:17:39 +0900
> Masami Hiramatsu (Google) wrote:
>
> > > + used = 0;
> > > + hlist_for_each_entry_from_rcu(node, hlist) {
> > > + if (node->addr != func)
> > > + break;
> > > + fp =
On Fri, 10 Nov 2023 11:11:31 +
Mark Rutland wrote:
> On Thu, Nov 09, 2023 at 08:14:52AM +0900, Masami Hiramatsu wrote:
> > On Wed, 8 Nov 2023 23:24:32 +0900
> > "Masami Hiramatsu (Google)" wrote:
> >
> > > From: Masami Hiramatsu (Google)
> > >
> > > To clarify what will be expected on
This change adds ftrace support for following functions which
helps in debugging the issues when there is Channel state & MHI
state change and also when we receive data and control events:
1. mhi_intvec_mhi_states
2. mhi_process_data_event_ring
3. mhi_process_ctrl_ev_ring
4. mhi_gen_tre
5.
On Fri, 10 Nov 2023 16:17:39 +0900
Masami Hiramatsu (Google) wrote:
> > + used = 0;
> > + hlist_for_each_entry_from_rcu(node, hlist) {
> > + if (node->addr != func)
> > + break;
> > + fp = READ_ONCE(node->fp);
> > + if (!fp ||
Hello RT-list!
I'm pleased to announce the 4.14.328-rt156 stable release.
This release is just an update to the new stable 4.14.328
version and no RT specific changes have been made.
You can get this release via the git tree at:
Hi Petr,
kernel test robot noticed the following build errors:
[auto build test ERROR on shuah-kselftest/next]
[also build test ERROR on shuah-kselftest/fixes linus/master v6.6 next-20231110]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we
Hello RT-list!
I'm pleased to announce the 5.10.199-rt97 stable release.
This release is an update to the new stable 5.10.199 version and no
RT-specific changes were made, with the exception of a fix to a build
failure due to upstream changes affecting only the PREEMPT_RT code.
You can get this
Hi Petr,
kernel test robot noticed the following build warnings:
[auto build test WARNING on shuah-kselftest/next]
[also build test WARNING on shuah-kselftest/fixes linus/master v6.6
next-20231110]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch
On Tue, 31 Oct 2023 15:18:14 +0530
Mukesh Ojha wrote:
>
>
> On 10/31/2023 9:43 AM, Yujie Liu wrote:
> > The order of descriptions should be consistent with the argument list of
> > the function, so "kretprobe" should be the second one.
> >
> > int __kprobe_event_gen_cmd_start(struct
On Fri, Nov 10, 2023 at 06:04:21PM +0100, Petr Mladek wrote:
> This POC is a material for the discussion "Simplify Livepatch Callbacks,
> Shadow Variables, and States handling" at LPC 2013, see
> https://lpc.events/event/17/contributions/1541/
>
> It obsoletes the patchset adding the garbage
Enable nodes required for multipd remoteproc bring up.
Signed-off-by: Manikanta Mylavarapu
---
Changes in v6:
- Added user pd remoteproc nodes in RDP442 dts
Changes in v5:
- Rebased on linux-next
Changes in v4:
- Rebased on linux-next
Add new binding document for multipd model remoteproc.
IPQ5332, IPQ9574 follows multipd model.
Signed-off-by: Manikanta Mylavarapu
Reviewed-by: Krzysztof Kozlowski
---
Changes in v6:
- No changes.
Changes in v5:
- No changes.
Changes in v4:
- No changes.
Changes in
In multipd model Q6 firmware takes care of bringup clocks,
so remove them.
Signed-off-by: Manikanta Mylavarapu
Reviewed-by: Krzysztof Kozlowski
---
Changes in v6:
- No changes.
Changes in v5:
- No changes.
Changes in v4:
- Pick up R-b tag
Changes in v3:
-
Enable nodes required for multipd remoteproc bring up.
Signed-off-by: Manikanta Mylavarapu
---
Changes in v6:
- Rebased on linux-next
Changes in v5:
- Rebased on linux-next
Changes in v4:
- Rebased on linux-next
Changes in v3:
- Fixed all comments and rebased
In multipd model Q6 firmware takes care of bringup clocks,
so remove them.
Signed-off-by: Manikanta Mylavarapu
Reviewed-by: Krzysztof Kozlowski
---
Changes in v6:
- No changes
Changes in v5:
- No changes
Changes in v4:
- Pick up R-b tag
Changes in v3:
-
APSS brings Q6 out of reset and then Q6 brings
WCSS block (wifi radio's) out of reset.
---
--> |WiFi 2G radio|
|--
|
---
In multipd model, root & user pd remoteproc's interrupts are
different. User pd needs additional interrupts like spawn.
Instead of going with qcom_q6v5_init(), we defined a new
function to register userpd rproc interrupts in mpd driver.
Since userpd rproc uses some of common interrupts like fatal,
In multipd model Q6 firmware takes care of bringup clocks,
so remove them from gcc driver.
Signed-off-by: Manikanta Mylavarapu
---
Changes in v6:
- Rebased on linux-next.
Changes in v5:
- Rebased on linux-next.
Changes in v4:
- In V3 series this patch is [04/11]. Here
IPQ5332 user pd remoteproc firmwares need to be locked
with MSA(modem secure access) features. This patch add
support to lock/unlock MSA features.
Signed-off-by: Manikanta Mylavarapu
---
Changes in v6:
- Removed extern keyword from msa lock/unlock
function prototype.
Changes
On Friday 2023-11-10 18:44, Michal Suchánek wrote:
>> It's a complicated mumble-jumble. Prior art exists as in:
>>
>> /opt/vendorThing/bin/...
>> /usr/X11R6/lib/libXi.so.6 [host binary]
>> /usr/x86_64-w64-mingw32/bin/as [host binary]
>> /usr/x86_64-w64-mingw32/sys-root/mingw/bin/as.exe
It adds support to bring up remoteproc's on multipd model.
Pd means protection domain. It's similar to process in Linux.
Here QDSP6 processor runs each wifi radio functionality on a
separate process. One process can't access other process
resources, so this is termed as PD i.e protection domain.
In multipd model Q6 firmware takes care of bringup clocks,
so remove them from gcc driver.
Signed-off-by: Manikanta Mylavarapu
---
Changes in v6:
- Rebased on linux-next.
Changes in v5:
- Rebased on linux-next.
Changes in v4:
- In V3 series this patch is [05/11]. Here
IPQ5332 security software running under trustzone
requires metadata size. With V2 cmd, pass metadata
size as well.
Signed-off-by: Manikanta Mylavarapu
---
Changes in v6:
- Rebased on linux-next
Changes in v5:
- Rebased on linux-next
Changes in v4:
- Rebased on
On Wed, Oct 18, 2023 at 03:12:41AM +0200, Jan Engelhardt wrote:
> On Tuesday 2023-10-17 17:10, Michal Suchánek wrote:
> >
> >> In my system (Ubuntu), I see the directory paths
> >>
> >> /usr/aarch64-linux-gnu/lib/
> >> /usr/i686-linux-gnu/lib/
> >> /usr/x86_64-linux-gnu/lib/
> >>
> >> If there
The livepatch state API was added to help with maintaining:
+ changes done by livepatch callbasks
+ lifetime of shadow variables
The original API was hard to use. Both objectives are better handled
by the new per-state callbacks. They are called when the state is
introduced or removed.
All selftests have been migrated to the new per-state callbacks.
And the obsoleted per-object callbacks can be safely removed.
FIXME:
This patch is removing the sample module and documentation
without any replacement. They obviously have to be converted
for the state-callbacks.
It has been
The original livepatch callbacks has been obsoleted by the livepatch
state callbacks.
The important difference is that the original callbacks were associated
with the livepatched object. The state callbacks are associated with
the livepatch states which are associated with the livepatch.
As a
The per-object callbacks have been obsoleted by per-state callbacks.
As a result, the callbacks test modules have been obsoleted
by updated klp state tests.
The callbacks test modules are re-used in the sysfs selftests.
It would be possible to replace them by klp state test modules
but the newly
Recent changes in the livepatch core have allowed to connect states,
shadow variables, and callbacks. Use these new features in
the state tests.
Use the shadow variable API to store the original loglevel. It is
better suited for this purpose than directly accessing the .data
pointer in state
The handling of the lifetime of the shadow variables is not easy
when the atomic replace is used. The new patch does not know
if a shadow variable has already been used by the previous livepatch.
Or if there is a shadow variable which will not longer be used.
Shadow variables are almost always
The basic livepatch functionality is to redirect problematic functions
to a fixed or improved variants. In addition, there are two features
helping with more problematic situations:
+ pre_patch(), post_patch(), pre_unpatch(), post_unpatch() callbacks
might be called before and after the
This POC is a material for the discussion "Simplify Livepatch Callbacks,
Shadow Variables, and States handling" at LPC 2013, see
https://lpc.events/event/17/contributions/1541/
It obsoletes the patchset adding the garbage collection of shadow
variables. This new solution is based on ideas from
On Thu, Nov 09, 2023 at 06:48:46PM -0500, Michael S. Tsirkin wrote:
> On Tue, Nov 07, 2023 at 11:52:17AM -0400, Jason Gunthorpe wrote:
> > On Tue, Nov 07, 2023 at 09:30:21AM -0500, Michael S. Tsirkin wrote:
> > > On Tue, Nov 07, 2023 at 10:12:37AM -0400, Jason Gunthorpe wrote:
> > > > Big
Hi!
Le dimanche 29 octobre 2023, 05:10:46 EET Masami Hiramatsu (Google) a écrit :
> From: Masami Hiramatsu (Google)
>
> Check the number of probe target symbols in the target module when
> the module is loaded. If the probe is not on the unique name symbols
> in the module, it will be rejected
Hello,
This is resend of the last patch in the series that adds prefix support
to kernel module location together with additional patch for validating
the user supplied input to options that are interpreted as directories.
Thanks
Michal
Michal Suchanek (2):
libkmod, depmod, modprobe: Make
Now that modprobe.d is searched under ${prefix}/lib, allow a complete
transition to files only under ${prefix} by adding a ${module_directory}
configuration. This specifies the directory where to search for kernel
modules and should match the location where the kernel/distro installs
them.
With
configure checks that its built-in directory options get an absolute
path. Copy the check for custom options.
Signed-off-by: Michal Suchanek
---
v6: new patch
---
configure.ac | 17 +
1 file changed, 17 insertions(+)
diff --git a/configure.ac b/configure.ac
index
On Thu, Nov 09, 2023 at 08:14:52AM +0900, Masami Hiramatsu wrote:
> On Wed, 8 Nov 2023 23:24:32 +0900
> "Masami Hiramatsu (Google)" wrote:
>
> > From: Masami Hiramatsu (Google)
> >
> > To clarify what will be expected on ftrace_regs, add a comment to the
> > architecture independent
42 matches
Mail list logo
