On 30/07/2025 05:31, Junhui Liu wrote:
> On 29/07/2025 08:27, Krzysztof Kozlowski wrote:
>> On 28/07/2025 19:13, Junhui Liu wrote:
> +description:
> + This property is required only if the rpmsg/virtio functionality
> is used.
> + (see mailbox/sophgo,cv1800b-mail
On 28/07/2025 13:03, Junhui Liu wrote:
> +
> +static int cv1800b_c906l_mem_alloc(struct rproc *rproc,
> +struct rproc_mem_entry *mem)
> +{
> + void __iomem *va;
> +
> + va = ioremap_wc(mem->dma, mem->len);
> + if (!va)
> + return -ENOMEM;
> +
On Wed, Jul 30, 2025 at 03:57:09AM +, Junhui Liu wrote:
> On 29/07/2025 16:31, Inochi Amaoto wrote:
> > On Mon, Jul 28, 2025 at 07:03:23PM +0800, Junhui Liu wrote:
> >> Add C906L remote processor for CV1800B SoC, which is an asymmetric
> >> processor typically running RTOS.
> >>
> >> Signed-of
On 29/07/2025 16:31, Inochi Amaoto wrote:
> On Mon, Jul 28, 2025 at 07:03:23PM +0800, Junhui Liu wrote:
>> Add C906L remote processor for CV1800B SoC, which is an asymmetric
>> processor typically running RTOS.
>>
>> Signed-off-by: Junhui Liu
>> ---
>> .../bindings/remoteproc/sophgo,cv1800b-c906
On 29/07/2025 08:27, Krzysztof Kozlowski wrote:
> On 28/07/2025 19:13, Junhui Liu wrote:
>>>
+description:
+ This property is required only if the rpmsg/virtio functionality is
used.
+ (see mailbox/sophgo,cv1800b-mailbox.yaml)
+items:
+ - descri
I can never remember whether --raw_output takes 'all' or 'full'. No
reason we can't support both.
For the record, 'all' is the recommended, documented option.
Signed-off-by: David Gow
---
tools/testing/kunit/kunit.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/
On 7/30/2025 8:38 AM, Sean Christopherson wrote:
> On Tue, Jul 29, 2025, Dapeng Mi wrote:
>> BTW, Sean, may I know your plan about the mediated vPMU v5 patch set? Thanks.
> I'll get it out this week (hopefully tomorrow).
Thumbs up! Thanks.
>
On Tue, 2025-07-29 at 10:42 -0700, Sean Christopherson wrote:
> Extend KVM's export macro framework to provide EXPORT_SYMBOL_GPL_FOR_KVM(),
> and use the helper macro to export symbols for KVM throughout x86 if and
> only if KVM will build one or more modules, and only for those modules.
>
> To av
From: Lorenzo Stoakes
[ Upstream commit ea0916e01d0b0f2cce1369ac1494239a79827270 ]
Now we have reinstated the ability to map F_SEAL_WRITE mappings read-only,
assert that we are able to do this in a test to ensure that we do not
regress this again.
Link:
https://lkml.kernel.org/r/a6377ec470b14c
From: Lorenzo Stoakes
[ Upstream commit ea0916e01d0b0f2cce1369ac1494239a79827270 ]
Now we have reinstated the ability to map F_SEAL_WRITE mappings read-only,
assert that we are able to do this in a test to ensure that we do not
regress this again.
Link:
https://lkml.kernel.org/r/a6377ec470b14c
From: Lorenzo Stoakes
[ Upstream commit ea0916e01d0b0f2cce1369ac1494239a79827270 ]
Now we have reinstated the ability to map F_SEAL_WRITE mappings read-only,
assert that we are able to do this in a test to ensure that we do not
regress this again.
Link:
https://lkml.kernel.org/r/a6377ec470b14c
From: Lorenzo Stoakes
[ Upstream commit ea0916e01d0b0f2cce1369ac1494239a79827270 ]
Now we have reinstated the ability to map F_SEAL_WRITE mappings read-only,
assert that we are able to do this in a test to ensure that we do not
regress this again.
Link:
https://lkml.kernel.org/r/a6377ec470b14c
On Tue, Jul 29, 2025, Dapeng Mi wrote:
> BTW, Sean, may I know your plan about the mediated vPMU v5 patch set? Thanks.
I'll get it out this week (hopefully tomorrow).
On Fri, Apr 25, 2025, Kan Liang wrote:
> On 2025-04-25 9:43 a.m., Peter Zijlstra wrote:
> > On Fri, Apr 25, 2025 at 09:06:26AM -0400, Liang, Kan wrote:
> >>
> >>
> >> On 2025-04-25 7:15 a.m., Peter Zijlstra wrote:
> >>> On Mon, Mar 24, 2025 at 05:30:50PM +, Mingwei Zhang wrote:
> From: Kan
On Fri, 25 Jul 2025 18:31:17 +0200, Johannes Nixdorf wrote:
> If WAIT_KILLABLE_RECV was specified, and an event is received, the
> tracee's syscall is not supposed to be interruptible. This was not properly
> ensured if the reply was sent too fast, and an interrupting signal was
> received before t
The pull request you sent on Mon, 28 Jul 2025 17:13:48 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux_kselftest-next-6.17-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0db240bc077fd16cc16bcecfd7f4645bc474aa7e
Thank you!
The pull request you sent on Mon, 28 Jul 2025 14:40:00 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux_kselftest-kunit-6.17-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6f46e6fb4e267acf8741cb2c29d368b4de7b6c15
Thank you
The pull request you sent on Mon, 28 Jul 2025 17:47:53 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/spdx.git
> tags/spdx-6.17-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/137177af71cf24a71a9854a5a5efbad6e0c5c5ac
Thank you!
--
Deet-doot-dot, I
On Sat, Jul 26, 2025 at 12:48:14PM -0500, Andrew Davis wrote:
> On 7/26/25 9:39 AM, Hiago De Franco wrote:
> > Hi Andrew, Beleswar,
> >
> > On Fri, Jul 25, 2025 at 02:29:22PM -0500, Andrew Davis wrote:
> > >
> > > So the issue then looks to be this message we send here when we setup
> > > the mai
On Tue, Jul 29, 2025 at 10:31:11AM +0800, Huayu Zong wrote:
> Add the compatible for mt8189 SCP to the binding.
>
> Signed-off-by: Huayu Zong
Acked-by: Conor Dooley
signature.asc
Description: PGP signature
Extend KVM's export macro framework to provide EXPORT_SYMBOL_GPL_FOR_KVM(),
and use the helper macro to export symbols for KVM throughout x86 if and
only if KVM will build one or more modules, and only for those modules.
To avoid unnecessary exports when CONFIG_KVM=m but kvm.ko will not be
built (
Rework almost all of KVM x86's exports to expose symbols only to KVM's
vendor modules, i.e. to kvm-{amd,intel}.ko. Keep the generic exports that
are guarded by CONFIG_KVM_EXTERNAL_WRITE_TRACKING=y, as they're explicitly
designed/intended for external usage.
Signed-off-by: Sean Christopherson
---
Drop the exporting of several kvm_arch_xxx() hooks that are only called
from arch-neutral code, i.e. that are only called from kvm.ko.
Signed-off-by: Sean Christopherson
---
arch/x86/kvm/x86.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index a1c
Move kvm_intr_is_single_vcpu() to lapic.c, drop its export, and make its
"fast" helper local to lapic.c. kvm_intr_is_single_vcpu() is only usable
if the local APIC is in-kernel, i.e. it most definitely belongs in the
local APIC code.
No functional change intended.
Fixes: 2f5fb6b965b3 ("KVM: x86:
Rework the vast majority of KVM's exports to expose symbols only to KVM
submodules, i.e. to x86's kvm-{amd,intel}.ko and PPC's kvm-{pr,hv}.ko.
With few exceptions, KVM's exported APIs are intended (and safe) for KVM-
internal usage only.
Keep kvm_get_kvm(), kvm_get_kvm_safe(), and kvm_put_kvm() as
Use kvm_is_gpa_in_memslot() to check the validity of the notification
indicator byte address instead of open coding equivalent logic in the VFIO
AP driver.
Opportunistically use a dedicated wrapper that exists and is exported
expressly for the VFIO AP module. kvm_is_gpa_in_memslot() is generally
Use the newfangled EXPORT_SYMBOL_GPL_FOR_MODULES() along with some macro
shenanigans to export KVM-internal symbols if and only if KVM has one or
more sub-modules, and only for those sub-modules, e.g. x86's kvm-amd.ko
and/or kvm-intel.ko.
Patch 5 gives KVM x86 the full treatment. If anyone wants
On Tue Jul 29, 2025 at 3:07 AM CEST, Kees Cook wrote:
> On Fri, Jul 25, 2025 at 06:31:19PM +0200, Johannes Nixdorf wrote:
>> +struct itimerval timer = {
>> +.it_value = { .tv_usec = 1000 },
>> +.it_interval = { .tv_usec = 1000 },
>> +}
Hi Dan,
On 7/23/2025 12:31 AM, dan.j.willi...@intel.com wrote:
Smita Koralahalli wrote:
Introduce a background worker in cxl_acpi to delay SOFT RESERVE handling
until the cxl_mem driver has probed at least one device. This coordination
ensures that DAX registration or fallback handling for soft
Hi Beleswar,
On Thu, Jul 24, 2025 at 07:01:44PM +0530, Beleswar Padhi wrote:
> When attaching to a remote processor, it is implied that the rproc was
> booted by an external entity. Thus, it's carveout and devmem resources
> would already have been processed by the external entity during boot.
>
On Mon, Jul 28, 2025 at 3:35 PM Alexei Starovoitov
wrote:
>
> Please make a full description of what the test does,
> since it's not trivial to decipher from the code.
> If I'm reading it correctly, first, the user space
> makes the LPM completely full and then lookup/update
> use random key-s wit
On Mon, Jul 28, 2025 at 10:58 PM Alexander Gordeev
wrote:
>
> On Thu, Jul 24, 2025 at 03:49:40PM +0200, Alexey Gladkov wrote:
>
> Hi Alexey, Masahiro,
>
> > From: Masahiro Yamada
> >
> > Keep the .modinfo section during linking, but strip it from the final
> > vmlinux.
> >
> > Adjust scripts/mksy
On 7/29/2025 2:39 AM, Jason Wang wrote:
Commit 7918bb2d19c9 ("vhost: basic in order support") introduces
vq->nheads to store the number of batched used buffers per used elem
but it forgets to initialize the vq->nheads to NULL in
vhost_dev_init() this will cause kfree() that would try to free it
w
On Tue, Jul 29, 2025 at 12:18 AM Alexey Gladkov wrote:
>
> On Mon, Jul 28, 2025 at 04:01:09PM +0200, Heiko Carstens wrote:
> > On Sat, Jul 26, 2025 at 07:59:16PM +0900, Masahiro Yamada wrote:
> > > On Thu, Jul 24, 2025 at 10:50 PM Alexey Gladkov wrote:
> > > >
> > > > Reorder the sections to be p
On 7/29/2025 4:33 AM, Shengjiu Wang wrote:
On Mon, Jul 28, 2025 at 11:09 PM Iuliana Prodan wrote:
On 7/28/2025 5:14 PM, Mathieu Poirier wrote:
On Mon, Jul 28, 2025 at 01:39:38PM +0300, Daniel Baluta wrote:
On Tue, Jul 22, 2025 at 11:16 AM Shengjiu Wang wrote:
When enabled FW recovery, but
The estimator kthreads' affinity are defined by sysctl overwritten
preferences and applied through a plain call to the scheduler's affinity
API.
However since the introduction of managed kthreads preferred affinity,
such a practice shortcuts the kthreads core code which eventually
overwrites the t
在 2025/7/25 16:55, Xuan Zhuo 写道:
On Thu, 24 Jul 2025 16:30:05 +0800, Wang Liang wrote:
When sending a packet with virtio_net_hdr to tun device, if the gso_type
in virtio_net_hdr is SKB_GSO_UDP and the gso_size is less than udphdr
size, below crash may happen.
[ cut here ]-
The estimator kthreads' affinity are defined by sysctl overwritten
preferences and applied through a plain call to the scheduler's affinity
API.
However since the introduction of managed kthreads preferred affinity,
such a practice shortcuts the kthreads core code which eventually
overwrites the t
Add tests for process_madvise(), focusing on verifying behavior under
various conditions including valid usage and error cases.
Signed-off-by: wang lian
Suggested-by: Lorenzo Stoakes
Suggested-by: David Hildenbrand
Suggested-by: Mark Brown
Acked-by: SeongJae Park
Reviewed-by: Zi Yan
Tested-b
On Tue, Apr 22, 2025 at 10:21:18AM +0200, Stephan Gerhold wrote:
> On Mon, Apr 21, 2025 at 04:04:15AM +0200, Barnabás Czémán wrote:
> > mbox_request_channel() returning value was changed in case of error.
> > It uses returning value of of_parse_phandle_with_args().
> > It is returning with -ENOENT
: 038d61fd642278bab63ee8ef722c50d10ab01e8f
patch link:
https://lore.kernel.org/r/20250728-cv1800-rproc-v2-2-5bbee4abe9dc%40pigmoral.tech
patch subject: [PATCH v2 2/2] drivers: remoteproc: Add C906L controller for
Sophgo CV1800B SoC
config: parisc-randconfig-r123-20250729
(https://download.01.org/0day
After investigation, it was confirmed that the issue was indeed caused by
the code added to the kpatch software by the community I joined, as stated
in the patch:
1. Add a new code branch to solve the following problem. Due to the parsing
of a certain symbol name, for example, if the symbol name
After investigation, it was confirmed that the issue was indeed caused by
the code added to the kpatch software by the community I joined, as stated
in the patch:
1. Add a new code branch to solve the following problem. Due to the parsing
of a certain symbol name, for example, if the symbol name
On Tue, Jul 29, 2025 at 03:39:16PM +0800, Jason Wang wrote:
Commit 7918bb2d19c9 ("vhost: basic in order support") introduces
vq->nheads to store the number of batched used buffers per used elem
but it forgets to initialize the vq->nheads to NULL in
vhost_dev_init() this will cause kfree() that wo
On Tue, Jul 29, 2025 at 03:39:16PM +0800, Jason Wang wrote:
> Commit 7918bb2d19c9 ("vhost: basic in order support") introduces
> vq->nheads to store the number of batched used buffers per used elem
> but it forgets to initialize the vq->nheads to NULL in
> vhost_dev_init() this will cause kfree() t
On Mon, Jul 28, 2025 at 07:03:23PM +0800, Junhui Liu wrote:
> Add C906L remote processor for CV1800B SoC, which is an asymmetric
> processor typically running RTOS.
>
> Signed-off-by: Junhui Liu
> ---
> .../bindings/remoteproc/sophgo,cv1800b-c906l.yaml | 79
> ++
> 1 file c
On Sat Jul 26, 2025 at 8:07 PM CEST, Miguel Ojeda wrote:
> Since commit 028df914e546 ("rust: str: convert `rusttest` tests into
> KUnit"), we do not have anymore host `#[test]`s that run in the host.
>
> Moreover, we do not plan to add any new ones -- tests should generally
> run within KUnit, sinc
On 2025-07-29 9:39 AM, Jason Wang wrote:
Commit 7918bb2d19c9 ("vhost: basic in order support") introduces
vq->nheads to store the number of batched used buffers per used elem
but it forgets to initialize the vq->nheads to NULL in
vhost_dev_init() this will cause kfree() that would try to free it
On Thu, Jul 17, 2025 at 01:52:12PM +0200, David Hildenbrand wrote:
>... and hide it behind a kconfig option. There is really no need for
>any !xen code to perform this check.
>
>The naming is a bit off: we want to find the "normal" page when a PTE
>was marked "special". So it's really not "finding
On Thu, Jul 17, 2025 at 01:52:11PM +0200, David Hildenbrand wrote:
>Let's introduce vm_normal_page_pud(), which ends up being fairly simple
>because of our new common helpers and there not being a PUD-sized zero
>folio.
>
>Use vm_normal_page_pud() in folio_walk_start() to resolve a TODO,
>structuri
On Tue, Jul 29, 2025 at 5:25 AM JAEHOON KIM wrote:
>
>
> Dear Jason Wang,
>
> I would like to kindly report a kernel crash issue on our s390x server
> which seems to be related to the following patch.
> ---
Commit 7918bb2d19c9 ("vhost: basic in order support") introduces
vq->nheads to store the number of batched used buffers per used elem
but it forgets to initialize the vq->nheads to NULL in
vhost_dev_init() this will cause kfree() that would try to free it
without be allocated if SET_OWNER is not ca
On Mon, Jul 28, 2025 at 10:11:51AM +0800, Yu Jugen wrote:
> From: Jugen Yu
>
> The member "hwlock" in struct regmap is defined with struct hwspinlock.
> Both regmap_write and regmap_read use struct regmap as a argument, so
> their KABI are affected by the hwspinlock structures.
There is no such
53 matches
Mail list logo
