Pavel Machek writes:
>> Hello Sasha,
>>
>> Thank you for considering this patch for the stable tree 6.9, 6.8, 6.6, and
>> 6.1.
>>
>> This patch does two things:
>> 1. Fixes a potential memory corruption issue mentioned as the third point in
>> the commit message
>> 2. Enables the kernel to avoid
On Wed, Jun 19, 2024 at 4:48 AM Bjorn Helgaas wrote:
>
> On Thu, Apr 25, 2024 at 03:33:01PM +0800, Kai-Heng Feng wrote:
> > On Fri, Apr 19, 2024 at 4:35 AM Bjorn Helgaas wrote:
> > >
> > > On Tue, Apr 16, 2024 at 12:32:24PM +0800, Kai-Heng Feng wrote:
> > > > When the power rail gets cut off, the
Hello Chenyu,
On 6/18/2024 1:19 PM, Chen Yu wrote:
[..snip..]
Vincent [5] pointed out a case where the idle load kick will fail to
run on an idle CPU since the IPI handler launching the ILB will check
for need_resched(). In such cases, the idle CPU relies on
newidle_balance() to pull tasks to
On Fri, 03 May 2024 11:17:31 -0700, David Matlack wrote:
> This series changes KVM to mark a vCPU as preempted/ready if-and-only-if
> it's scheduled out while running. i.e. Do not mark a vCPU
> preempted/ready if it's scheduled out during a non-KVM_RUN ioctl() or
> when userspace is doing KVM_RUN w
On Tue, Apr 09, 2024 at 09:17:57AM +0300, Baruch Siach wrote:
> Current code using zone_dma_bits assume that all addresses range in the
> bits mask are suitable for DMA. For some existing platforms this
> assumption is not correct. DMA range might have non zero lower limit.
[...]
> @@ -59,7 +60,7 @
On Tue, Apr 09, 2024 at 09:17:55AM +0300, Baruch Siach wrote:
> of_dma_get_max_cpu_address() returns the highest CPU address that
> devices can use for DMA. The implicit assumption is that all CPU
> addresses below that limit are suitable for DMA. However the
> 'dma-ranges' property this code uses
From: Kai-Heng Feng
If the link is powered off during suspend, electrical noise may cause
errors that trigger DPC. If the DPC interrupt is enabled and shares an IRQ
with PME, that causes a spurious wakeup during suspend.
Disable DPC triggering and the DPC interrupt during suspend to prevent
thi
From: Kai-Heng Feng
If the link is powered off during suspend, electrical noise may cause
errors that are logged via AER. If the AER interrupt is enabled and shares
an IRQ with PME, that causes a spurious wakeup during suspend.
Disable the AER interrupt during suspend to prevent this. Clear er
From: Bjorn Helgaas
This is an old series from Kai-Heng that I didn't handle soon enough. The
intent is to fix several suspend/resume issues:
- Spurious wakeup from s2idle
(https://bugzilla.kernel.org/show_bug.cgi?id=216295)
- Steam Deck doesn't resume after suspend
(https://bugzil
On Thu, Apr 25, 2024 at 03:33:01PM +0800, Kai-Heng Feng wrote:
> On Fri, Apr 19, 2024 at 4:35 AM Bjorn Helgaas wrote:
> >
> > On Tue, Apr 16, 2024 at 12:32:24PM +0800, Kai-Heng Feng wrote:
> > > When the power rail gets cut off, the hardware can create some electric
> > > noise on the link that tr
On 12/06/2024 07.23, Nicholas Piggin wrote:
Add some initial PMU testing.
- PMC5/6 tests
- PMAE / PMI test
- BHRB basic tests
Signed-off-by: Nicholas Piggin
---
...
diff --git a/powerpc/pmu.c b/powerpc/pmu.c
new file mode 100644
index 0..bdc45e167
--- /dev/null
+++ b/powerpc/pmu.c
@@
(finally getting around to looking at this series, sorry for the delay)
On Tue, Apr 09, 2024 at 09:17:54AM +0300, Baruch Siach wrote:
> From: Catalin Marinas
>
> Hardware DMA limit might not be power of 2. When RAM range starts above
> 0, say 4GB, DMA limit of 30 bits should end at 5GB. A single
On Tue, Jun 18, 2024 at 07:21:42PM +0200, Vlastimil Babka wrote:
> On 6/18/24 6:48 PM, Paul E. McKenney wrote:
> > On Tue, Jun 18, 2024 at 11:31:00AM +0200, Uladzislau Rezki wrote:
> >> > On 6/17/24 8:42 PM, Uladzislau Rezki wrote:
> >> > >> +
> >> > >> + s = container_of(work, struct kmem_cach
On 6/18/24 6:48 PM, Paul E. McKenney wrote:
> On Tue, Jun 18, 2024 at 11:31:00AM +0200, Uladzislau Rezki wrote:
>> > On 6/17/24 8:42 PM, Uladzislau Rezki wrote:
>> > >> +
>> > >> + s = container_of(work, struct kmem_cache, async_destroy_work);
>> > >> +
>> > >> + // XXX use the real kme
On Tue, Jun 18, 2024 at 11:31:00AM +0200, Uladzislau Rezki wrote:
> > On 6/17/24 8:42 PM, Uladzislau Rezki wrote:
> > >> +
> > >> +s = container_of(work, struct kmem_cache, async_destroy_work);
> > >> +
> > >> +// XXX use the real kmem_cache_free_barrier() or similar thing
> > >> h
On 12/06/2024 07.23, Nicholas Piggin wrote:
Add some initial PMU testing.
- PMC5/6 tests
- PMAE / PMI test
- BHRB basic tests
Signed-off-by: Nicholas Piggin
---
lib/powerpc/asm/processor.h | 2 +
lib/powerpc/asm/reg.h | 9 +
lib/powerpc/asm/setup.h | 1 +
lib/powerpc/setup
commit 80d496be89ed ("perf report: Add support for profiling JIT
generated code") added support for profiling JIT generated code.
This patch handles dso's of form "/tmp/perf-$PID.map".
Some of the references doesn't check exactly for same pattern.
some uses "if (!strncmp(dso_name, "/tmp/perf-", 10
perf test "perf script tests" fails as below in systems
with python 3.6
File
"/home/athira/linux/tools/perf/tests/shell/../../scripts/python/parallel-perf.py",
line 442
if line := p.stdout.readline():
^
SyntaxError: invalid syntax
--- Cleaning up ---
Perf test for perf probe of function from different CU fails
as below:
./perf test -vv "test perf probe of function from different CU"
116: test perf probe of function from different CU:
--- start ---
test child forked, pid 2679
Failed to find symbol foo in
On Tue, Jun 18, 2024 at 10:12:54PM +1000, Michael Ellerman wrote:
> Segher Boessenkool writes:
> > On Mon, Jun 17, 2024 at 10:35:09AM +0800, Jinglin Wen wrote:
> >> + cmplwi cr0,r4,0/* runtime base addr is zero */
> >
> > Just write
> >cmpwi r4,0
> >
> > cr0 is the default, also impl
Le 02/04/2024 à 07:11, Rohan McLure a écrit :
> Support page table check on all PowerPC platforms. This works by
> serialising assignments, reassignments and clears of page table
> entries at each level in order to ensure that anonymous mappings
> have at most one writable consumer, and likewise
Segher Boessenkool writes:
> Hi!
>
> On Mon, Jun 17, 2024 at 10:35:09AM +0800, Jinglin Wen wrote:
>> +cmplwi cr0,r4,0/* runtime base addr is zero */
>
> Just write
>cmpwi r4,0
>
> cr0 is the default, also implicit in many other instructions, please
> don't clutter the source code.
On 17/06/2024 17:47, Athira Rajeev wrote:
>
>
>> On 17 Jun 2024, at 8:30 PM, James Clark wrote:
>>
>>
>>
>> On 17/06/2024 13:21, Athira Rajeev wrote:
>>> Running "perftool-testsuite_probe" fails as below:
>>>
>>> ./perf test -v "perftool-testsuite_probe"
>>> 83: perftool-testsuite_probe : FA
Hi Segher Boessenkool,
Segher Boessenkool writes:
> Hi!
>
> On Mon, Jun 17, 2024 at 10:35:09AM +0800, Jinglin Wen wrote:
> > + cmplwi cr0,r4,0/* runtime base addr is zero */
>
> Just write
>cmpwi r4,0
>
> cr0 is the default, also implicit in many other instructions, please
> don
Hi Michael Ellerman,
Michael Ellerman writes:
> Jinglin Wen writes:
> > According to the code logic, when the kernel is loaded to address 0,
> > no copying operation should be performed, but it is currently being
> > done.
> >
> > This patch fixes the issue where the kernel code was incorrectly
> On 6/17/24 8:42 PM, Uladzislau Rezki wrote:
> >> +
> >> + s = container_of(work, struct kmem_cache, async_destroy_work);
> >> +
> >> + // XXX use the real kmem_cache_free_barrier() or similar thing here
> > It implies that we need to introduce kfree_rcu_barrier(), a new API, which i
> > wanted
> On 18 Jun 2024, at 12:41 PM, Adrian Hunter wrote:
>
> On 17/06/24 16:03, Athira Rajeev wrote:
>> commit 80d496be89ed ("perf report: Add support for profiling JIT
>> generated code") added support for profiling JIT generated code.
>> This patch handles dso's of form "/tmp/perf-$PID.map".
>>
Hi!
> Hello Sasha,
>
> Thank you for considering this patch for the stable tree 6.9, 6.8, 6.6, and
> 6.1.
>
> This patch does two things:
> 1. Fixes a potential memory corruption issue mentioned as the third point in
> the commit message
> 2. Enables the kernel to avoid unnecessary fadump re-reg
On Tue, Jun 18, 2024 at 06:43:06AM GMT, Masami Hiramatsu wrote:
> On Mon, 17 Jun 2024 18:28:07 +0530
> Naveen N Rao wrote:
>
> > Hi Abhishek,
> >
> > On Mon, Jun 10, 2024 at 11:45:09AM GMT, Abhishek Dubey wrote:
> > > This is an adaptation of commit f3a112c0c40d ("x86,rethook,kprobes:
> > > Repl
On 2024-06-17 at 14:03:41 +0530, K Prateek Nayak wrote:
> Hello Chenyu,
>
> On 6/14/2024 10:01 PM, Chen Yu wrote:
> > On 2024-06-14 at 12:48:37 +0200, Vincent Guittot wrote:
> > > On Fri, 14 Jun 2024 at 11:28, Peter Zijlstra wrote:
> > > >
> > > > On Thu, Jun 13, 2024 at 06:15:59PM +, K Prat
On Mon, Jun 17, 2024 at 9:30 PM Markus Elfring wrote:
> Would you become interested to apply a statement like
> “guard(mutex)(&i2s_info_p->lock);”?
> https://elixir.bootlin.com/linux/v6.10-rc4/source/include/linux/mutex.h#L196
I take it. Thanks.
--
Piotr Wojtaszczyk
Timesys
On 17/06/24 16:03, Athira Rajeev wrote:
> commit 80d496be89ed ("perf report: Add support for profiling JIT
> generated code") added support for profiling JIT generated code.
> This patch handles dso's of form "/tmp/perf-$PID.map".
>
> Some of the references doesn't check exactly for same pattern.
Kees Cook writes:
> On Fri, Jun 14, 2024 at 11:08:44PM +0530, Anjali K wrote:
>> Reading the dispatch trace log from /sys/kernel/debug/powerpc/dtl/cpu-*
>> results in a BUG() when the config CONFIG_HARDENED_USERCOPY is enabled as
>> shown below.
>>
>> kernel BUG at mm/usercopy.c:102!
>> O
33 matches
Mail list logo
