With proper exception boundary detection, it is possible to implment
arch_stack_walk_reliable without sframe.
Note that, arch_stack_walk_reliable does not guarantee getting reliable
stack in all scenarios. Instead, it can reliably detect when the stack
trace is not reliable, which is enough to pro
Introduce the helper function pci_epf_align_inbound_addr() to adjust
addresses according to PCI BAR alignment requirements, converting addresses
into base and offset values.
Signed-off-by: Frank Li
---
Change from v15 to v16
- none
Change from v14 to v15
- change out address type to dma_addr_t t
Add three registers: doorbell_bar, doorbell_addr, and doorbell_data. Use
pci_epf_alloc_doorbell() to allocate a doorbell address space.
Enable the Root Complex (RC) side driver to trigger pci-epc-test's doorbell
callback handler by writing doorbell_data to the mapped doorbell_bar's
address space.
Set the IRQ_DOMAIN_FLAG_MSI_IMMUTABLE flag for ITS, as it does not change
the address/data pair after setup.
Ensure compatibility with MSI users, such as PCIe Endpoint Doorbell, which
require the address/data pair to remain unchanged. Enable PCIe endpoints to
use ITS for triggering doorbells from
From: Kaustabh Chakraborty
Some replacement displays include third-party touch ICs which are
devoid of register descriptors. Create a fake data register descriptor
for such ICs and provide hardcoded default values.
It isn't possible to reliably determine if the touch IC is original or
not, so th
On 4/4/25 2:13 PM, Johannes Weiner wrote:
On Fri, Apr 04, 2025 at 01:25:33PM -0400, Waiman Long wrote:
On 4/4/25 1:12 PM, Tejun Heo wrote:
Hello,
On Thu, Apr 03, 2025 at 09:24:34PM -0400, Waiman Long wrote:
...
The simple and naive fix of changing the operator to ">", however,
changes the mem
Add the flag IRQ_DOMAIN_FLAG_MSI_IMMUTABLE and the API function
irq_domain_is_msi_immutable() to check if the MSI controller retains an
immutable address/data pair during irq_set_affinity().
Ensure compatibility with MSI users like PCIe Endpoint Doorbell, which
require the address/data pair to rem
┌┐ ┌───┐ ┌┐
││ │ │ ││
││ │ PCI Endpoint │ │ PCI Host │
││ │ │ │
platform_device_msi_init_and_alloc_irqs() performs two tasks: allocating
the MSI domain for a platform device, and allocate a number of MSIs in that
domain.
platform_device_msi_free_irqs_all() only frees the MSIs, and leaves the MSI
domain alive.
Given that platform_device_msi_init_and_alloc_irqs
2025/3/20 07:02, "Cong Wang" wrote:
>
> On Mon, Mar 17, 2025 at 05:22:54PM +0800, Jiayuan Chen wrote:
>
> >
> > The sk->sk_socket is not locked or referenced, and during the call to
> >
>
> Hm? We should have a reference in socket map, whether directly or
>
> indirectly, right? When we add
On Wed, Apr 02, 2025 at 12:14:24PM -0400, Stefan Hajnoczi wrote:
> On Tue, Apr 01, 2025 at 08:13:49PM +, Alexander Graf wrote:
> > Ever since the introduction of the virtio vsock driver, it included
> > pushback logic that blocks it from taking any new RX packets until the
> > TX queue backlog
On Thu, Mar 27, 2025 at 04:42:49PM +0100, Miroslav Lichvar wrote:
> Maybe I could simply patch the kernel to force a small clock
> multiplier to increase the rate at which the error accumulates.
I tried that and it indeed makes the issue clearly visible. The COARSE
fix makes the clock less stable.
On Wed, Apr 02, 2025 at 01:11:25PM +, Reshetova, Elena wrote:
> > > current SGX kernel code does not handle such errors in any other way
> > > than notifying that operation failed for other ENCLS leaves. So, I don't
> > > see why ENCLS[EUPDATESVN] should be different from existing behaviour?
>
Hi,
On 3/29/25 3:18 AM, Stafford Horne wrote:
On Sat, Mar 29, 2025 at 01:56:31AM +0530, Sahil Siddiq wrote:
[...]
diff --git a/arch/openrisc/include/asm/cpuinfo.h
b/arch/openrisc/include/asm/cpuinfo.h
index 82f5d4c06314..e46afbfe9b5a 100644
--- a/arch/openrisc/include/asm/cpuinfo.h
+++ b/arch/
Document the use of msi-map for PCI Endpoint (EP) controllers, which can
use MSI as a doorbell mechanism. Each EP controller can support up to 8
physical functions and 65,536 virtual functions.
Define how to construct device IDs using function bits [2:0] and virtual
function index bits [31:3], ena
Some platform devices create child devices dynamically and require the
parent device's msi-map to map device IDs to actual sideband information.
A typical use case is using ITS as a PCIe Endpoint Controller(EPC)'s
doorbell function, where PCI hosts send TLP memory writes to the EP
controller. The
On Fri, Mar 14, 2025 at 10:27:33AM +0100, Luigi Leonardi wrote:
Add a new test to ensure that when the transport changes a null pointer
dereference does not occur[1].
I'd add something like this:
"... does not occur. The bug was reported upstream [1] and fixed with
commit 2cb7c756f605 ("vsock/
On Wed, Mar 19, 2025 at 06:13:08PM +0100, Halil Pasic wrote:
> On Wed, 19 Mar 2025 11:00:06 -0400
> "Michael S. Tsirkin" wrote:
>
> > > > I was mistaken in my earlier reply - I had missed this
> > > > virtio_console_resize definition in the spec. So indeed there's a
> > > > discrepancy in Linux
Markus Fohrer wrote:
> Am Donnerstag, dem 03.04.2025 um 17:06 -0400 schrieb Michael S.
> Tsirkin:
> > On Thu, Apr 03, 2025 at 10:07:12PM +0200, Markus Fohrer wrote:
> > > Am Donnerstag, dem 03.04.2025 um 10:03 -0400 schrieb Michael S.
> > > Tsirkin:
> > > > On Thu, Apr 03, 2025 at 03:51:01PM +0200,
With imx8mp-evk board we are now configuring 'dsp' node for rproc usage,
so add rproc specific memory regions.
Also, enable dsp node because it is ready to be used.
Reviewed-by: Ahmad Fatoum
Reviewed-by: Iuliana Prodan
Reviewed-by: Peng Fan
Signed-off-by: Daniel Baluta
---
arch/arm64/boot/dt
On Thu, Mar 20 2025 at 19:01, John Stultz wrote:
> On Sun, Mar 16, 2025 at 9:56 PM Thomas Gleixner wrote:
>> #define TK_CLEAR_NTP(1 << 0)
>> #define TK_CLOCK_WAS_SET(1 << 1)
>>
>> So it clears NTP instead. Not really what you want either. :)
>
> Hey Thomas,
>Sorry for the s
On Fri, Apr 4, 2025 at 11:37 PM Uros Bizjak wrote:
>
> On Fri, Apr 4, 2025 at 4:06 PM Masahiro Yamada wrote:
>
> > > > > Current version of genksyms doesn't know anything about
> > > > > __typeof_unqual__()
> > > > > operator. Avoid the usage of __typeof_unqual__() with genksyms to
> > > > > p
Add support for sending a pagefault event if userfaultfd is registered.
Only page minor event is currently supported.
Signed-off-by: Nikita Kalyazin
---
virt/kvm/guest_memfd.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/virt/kvm/guest_memfd.c b/virt/kvm/guest_memfd.c
index fb
Am 19.03.25 um 19:37 schrieb Jens Axboe:
On 3/19/25 11:45 AM, Joe Damato wrote:
On Wed, Mar 19, 2025 at 11:20:50AM -0600, Jens Axboe wrote:
On 3/19/25 11:04 AM, Joe Damato wrote:
On Wed, Mar 19, 2025 at 10:07:27AM -0600, Jens Axboe wrote:
On 3/19/25 9:32 AM, Joe Damato wrote:
On Wed, Mar 19,
Set ret = 0 on successful completion of the processing loop in
cs_dsp_load() and cs_dsp_load_coeff() to ensure that the function
returns 0 on success.
All normal firmware files will have at least one data block, and
processing this block will set ret == 0, from the result of either
regmap_raw_writ
On Wed, Apr 02 2025, David Hildenbrand wrote:
> If we finds a vq without a name in our input array in
> virtio_ccw_find_vqs(), we treat it as "non-existing" and set the vq pointer
> to NULL; we will not call virtio_ccw_setup_vq() to allocate/setup a vq.
>
> Consequently, we create only a queue if
On Wed, Apr 02, 2025 at 08:44:52PM +0200, David Heidelberg wrote:
> Mostly irrelevant for authentic Synaptics touchscreens, but very important
> for applying workarounds to cheap TS knockoffs.
>
> These knockoffs work well with the downstream driver, and since the user
> has no way to distinguish
Log write descriptors for the control queue, leveraging
vhost_scsi_get_desc() and vhost_get_vq_desc() to retrieve the array of
write descriptors to obtain the log buffer.
For Task Management Requests, similar to the I/O queue, store the log
buffer during the submission path and log it in the compl
The device_del() call matches with the device_add() but we also need
to call put_device() to trigger the qcom_iris_release().
Fixes: 1fcef985c8bd ("remoteproc: qcom: wcnss: Fix race with iris probe")
Signed-off-by: Dan Carpenter
---
This patch is based on static analysis and has not been tested.
On Fri, Apr 4, 2025 at 9:22 PM Andrii Nakryiko
wrote:
>
> On Sun, Mar 23, 2025 at 11:43 PM Malaya Kumar Rout
> wrote:
> >
> > Static Analyis for bench_htab_mem.c with cppcheck:error
> > tools/testing/selftests/bpf/benchs/bench_htab_mem.c:284:3:
> > error: Resource leak: fd [resourceLeak]
> > tool
Am Samstag, dem 05.04.2025 um 00:05 +0200 schrieb Ilya Maximets:
> On 4/4/25 5:13 PM, Willem de Bruijn wrote:
>
> > Markus Fohrer wrote:
> >
> > > Am Freitag, dem 04.04.2025 um 10:52 +0200 schrieb Markus Fohrer:
> > >
> > > > Am Freitag, dem 04.04.2025 um 04:29 -0400 schrieb Michael S. Tsirkin:
On Thu, 3 Apr 2025 at 20:56, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 6.13.10 release.
> There are 23 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Resp
Am Freitag, dem 04.04.2025 um 04:29 -0400 schrieb Michael S. Tsirkin:
> On Fri, Apr 04, 2025 at 10:16:55AM +0200, Markus Fohrer wrote:
> > Am Donnerstag, dem 03.04.2025 um 09:04 -0400 schrieb Michael S.
> > Tsirkin:
> > > On Wed, Apr 02, 2025 at 11:12:07PM +0200, Markus Fohrer wrote:
> > > > Hi,
>
There's no need to call WARN_ON() in cfg802154_pernet_exit(), since
every point of failure in cfg802154_switch_netns() is covered with
WARN_ON(), so remove it.
Found by Linux Verification Center (linuxtesting.org) with Syzkaller.
Fixes: 66e5c2672cd1 ("ieee802154: add netns support")
Reviewed-by:
On Fri, Mar 21, 2025 at 03:48:31PM +0900, Akihiko Odaki wrote:
> Jason Wang recently proposed an improvement to struct
> virtio_net_rss_config:
> https://lore.kernel.org/r/CACGkMEud0Ki8p=z299q7b4qedonpydzbvqhhxcnvk_vo-kd...@mail.gmail.com
>
> This patch series implements it and also fixes a few mi
This is strictly a code-movement commit, pulling that part of
the rcu_torture_updown() function's loop body that processes
one rcu_torture_one_read_state_updown structure into a new
rcu_torture_updown_one() function. The checks for the end of the
torture test and the current structure being in use
On Sun, Mar 30, 2025 at 05:52:43PM -0400, Waiman Long
wrote:
> Currently, we don't allow the creation of a remote partition underneath
> another local or remote partition. However, it is currently possible to
> create a new local partition with an existing remote partition underneath
> it if top_
sgx_nr_free_pages is an atomic that is used to keep track of
free EPC pages and detect whenever page reclaiming should start.
Since successful execution of ENCLS[EUPDATESVN] requires empty
EPC and a fast way of checking for this, change this variable
around to indicate number of used pages instead.
Hi Ackerley,
Not sure if below nits have been resolved in your latest code.
I came across them and felt it's better to report them anyway.
Apologies for any redundancy if you've already addressed them.
On Tue, Sep 10, 2024 at 11:43:44PM +, Ackerley Tng wrote:
> +static void kvm_gmem_init_mou
An ovpn_peer object holds the whole status of a remote peer
(regardless whether it is a server or a client).
This includes status for crypto, tx/rx buffers, napi, etc.
Only support for one peer is introduced (P2P mode).
Multi peer support is introduced with a later patch.
Along with the ovpn_pee
On Wed, Apr 2, 2025 at 9:08 AM Nikita Kalyazin wrote:
>
> The test demonstrates that a minor userfaultfd event in guest_memfd can
> be resolved via a memcpy followed by a UFFDIO_CONTINUE ioctl.
>
> Signed-off-by: Nikita Kalyazin
> ---
> .../testing/selftests/kvm/guest_memfd_test.c | 94
With the growing popularity of running upstream Linux on mobile devices,
we're beginning to run into more and more edgecases. The OnePlus 6 is a
fairly well supported 2018 era smartphone, selling over a million units
in it's first 22 days. With this level of popularity, it's almost
inevitable that
On 03.04.25 14:21, Michael S. Tsirkin wrote:
On Wed, Apr 02, 2025 at 12:14:24PM -0400, Stefan Hajnoczi wrote:
On Tue, Apr 01, 2025 at 08:13:49PM +, Alexander Graf wrote:
Ever since the introduction of the virtio vsock driver, it included
pushback logic that blocks it from taking any new R
On Fri, Apr 04, 2025 at 08:29:21AM +0200, Ricardo Ribalda wrote:
> On Fri, 4 Apr 2025 at 08:22, Greg Kroah-Hartman
> wrote:
> >
> > On Thu, Apr 03, 2025 at 11:34:14PM +0200, Ricardo Ribalda wrote:
> > > Friendly ping
> >
> > Empty pings provide no context at all :(
>
> Do you mean that I'd rather
On Fri, Apr 04, 2025 at 10:04:38AM +0200, Alexander Graf wrote:
>
> On 03.04.25 14:21, Michael S. Tsirkin wrote:
> > On Wed, Apr 02, 2025 at 12:14:24PM -0400, Stefan Hajnoczi wrote:
> > > On Tue, Apr 01, 2025 at 08:13:49PM +, Alexander Graf wrote:
> > > > Ever since the introduction of the vir
Am Donnerstag, dem 03.04.2025 um 09:04 -0400 schrieb Michael S.
Tsirkin:
> On Wed, Apr 02, 2025 at 11:12:07PM +0200, Markus Fohrer wrote:
> > Hi,
> >
> > I'm observing a significant performance regression in KVM guest VMs
> > using virtio-net with recent Linux kernels (6.8.1+ and 6.14).
> >
> > W
When pausing rx (e.g. set up xdp, xsk pool, rx resize), we call
napi_disable() on the receive queue's napi. In delayed refill_work, it
also calls napi_disable() on the receive queue's napi. This can leads to
deadlock when napi_disable() is called on an already disabled napi. This
scenario can be re
On Fri, Apr 04, 2025 at 10:16:55AM +0200, Markus Fohrer wrote:
> Am Donnerstag, dem 03.04.2025 um 09:04 -0400 schrieb Michael S.
> Tsirkin:
> > On Wed, Apr 02, 2025 at 11:12:07PM +0200, Markus Fohrer wrote:
> > > Hi,
> > >
> > > I'm observing a significant performance regression in KVM guest VMs
>
On Fri, Apr 04, 2025 at 04:14:51AM -0400, Michael S. Tsirkin wrote:
On Fri, Apr 04, 2025 at 10:04:38AM +0200, Alexander Graf wrote:
On 03.04.25 14:21, Michael S. Tsirkin wrote:
> On Wed, Apr 02, 2025 at 12:14:24PM -0400, Stefan Hajnoczi wrote:
> > On Tue, Apr 01, 2025 at 08:13:49PM +, Alexa
Am Donnerstag, dem 03.04.2025 um 18:05 -0400 schrieb Michael S.
Tsirkin:
> On Thu, Apr 03, 2025 at 11:24:43PM +0200, Markus Fohrer wrote:
> > Am Donnerstag, dem 03.04.2025 um 17:06 -0400 schrieb Michael S.
> > Tsirkin:
> > > On Thu, Apr 03, 2025 at 10:07:12PM +0200, Markus Fohrer wrote:
> > > > Am
Am Freitag, dem 04.04.2025 um 10:52 +0200 schrieb Markus Fohrer:
> Am Freitag, dem 04.04.2025 um 04:29 -0400 schrieb Michael S. Tsirkin:
> > On Fri, Apr 04, 2025 at 10:16:55AM +0200, Markus Fohrer wrote:
> > > Am Donnerstag, dem 03.04.2025 um 09:04 -0400 schrieb Michael S.
> > > Tsirkin:
> > > > On
Am Mittwoch, dem 02.04.2025 um 23:12 +0200 schrieb Markus Fohrer:
> When running on a host system equipped with a Broadcom NetXtreme-E
> (bnxt_en) NIC and AMD EPYC CPUs, the network throughput in the guest
> drops to 100–200 KB/s. The same guest configuration performs normally
> (~100 MB/s) when us
Current version of genksyms doesn't know anything about __typeof_unqual__()
operator. Avoid the usage of __typeof_unqual__() with genksyms to prevent
errors when symbols are versioned.
There were no problems with gendwarfksyms.
Signed-off-by: Uros Bizjak
Fixes: ac053946f5c40 ("compiler.h: intro
= "qcom,sc7280-lpass-va-macro";
reg = <0 0x0337 0 0x1000>;
- pinctrl-names = "default";
- pinctrl-0 = <&lpass_dmic01_clk>, <&lpass_dmic01_data>;
-
clocks = <&lpass_aon LPASS_AON_CC_TX_MCLK_CLK>;
clock-names = "mclk";
---
base-commit: a4cda136f021ad44b8b52286aafd613030a6db5f
change-id: 20250404-sc7280-va-dmic01-6b96e810834c
Best regards,
--
Luca Weiss
On 4/3/25 17:43, Bui Quang Minh wrote:
On 4/2/25 12:42, Bui Quang Minh wrote:
When setting up XDP for a running interface, we call napi_disable() on
the receive queue's napi. In delayed refill_work, it also calls
napi_disable() on the receive queue's napi. This can leads to deadlock
when napi_di
Hi Terry,
kernel test robot noticed the following build warnings:
[auto build test WARNING on aae0594a7053c60b82621136257c8b648c67b512]
url:
https://github.com/intel-lab-lkp/linux/commits/Terry-Bowman/kernel-resource-Provide-mem-region-release-for-SOFT-RESERVES/20250404-023601
base
On Fri, Apr 4, 2025 at 7:25 PM Uros Bizjak wrote:
>
> Current version of genksyms doesn't know anything about __typeof_unqual__()
> operator. Avoid the usage of __typeof_unqual__() with genksyms to prevent
> errors when symbols are versioned.
>
> There were no problems with gendwarfksyms.
>
> Sig
On Fri, Apr 04, 2025 at 01:25:33PM -0400, Waiman Long wrote:
>
> On 4/4/25 1:12 PM, Tejun Heo wrote:
> > Hello,
> >
> > On Thu, Apr 03, 2025 at 09:24:34PM -0400, Waiman Long wrote:
> > ...
> >> The simple and naive fix of changing the operator to ">", however,
> >> changes the memory reclaim behav
Thanks for the respin.
I will take this version and put it in linux next to see if any issues come up.
-Stafford
On Sat, Mar 29, 2025 at 03:16:19PM +0530, Sahil Siddiq wrote:
> Hi,
>
> The main purpose of this series is to expose CPU cache attributes for
> OpenRISC in sysfs using the cacheinfo
On Thu, 3 Apr 2025 16:28:31 +0200
David Hildenbrand wrote:
> > Sorry I have to have a look at that discussion. Maybe it will answer
> > some my questions.
>
> Yes, I think so.
>
> >
> >> Let's fix it without affecting existing setups for now by properly
> >> ignoring the non-existing queue
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski :
On Wed, 02 Apr 2025 01:59:31 +0100 you wrote:
> From: Dmitry Safonov <0x7f454...@gmail.com>
>
> self-connect-ipv6 got slightly flaky on netdev:
> > # timeout set to 120
> > # selftests: net/tcp_ao: self-connect_ipv6
> > #
Hello Waiman.
On Thu, Apr 03, 2025 at 09:24:34PM -0400, Waiman Long
wrote:
> 1) memory.low is set to 0, but low events can still be triggered and
>so the cgroup may have a non-zero low event count. I doubt users are
>looking for that as they didn't set memory.low at all.
I agree with th
On Thu, Feb 27, 2025 at 3:39 PM Andreas Hindborg wrote:
>
> +// SAFETY: We checked that `val` will fit in `Self`
> above.
> +let val: Self = unsafe {
> val.try_into().unwrap_unchecked() };
This is wrong -- `val` can be the maximum, and thus it does not fi
Le Sat, Mar 22, 2025 at 06:00:13PM +0100, Joel Fernandes a écrit :
>
>
> On 3/18/2025 2:56 PM, Frederic Weisbecker wrote:
> > RCU relies on the context tracking nesting counter in order to determine
> > if it is running in extended quiescent state.
> >
> > However the context tracking nesting co
Currently, ',' is used as the cgroup separator of the expected effective
CPUs and partition root states in the test matrix. However, ',' can be
part of the output of the cpuset.cpus*.effective and cpuset.cpus.isolated
files. Change the separator to '|' so that ',' can appear as part of
the expected
On Tue, 1 Apr 2025 21:59:20 -0400
Gregory Price wrote:
> Device capacity intended for use as system ram should be aligned to the
> archite-defined memory block size or that capacity will be silently
archite?
> truncated and capacity stranded.
>
> As hotplug dax memory becomes more prevelant,
On Sun, Mar 23, 2025 at 11:43 PM Malaya Kumar Rout
wrote:
>
> Static Analyis for bench_htab_mem.c with cppcheck:error
> tools/testing/selftests/bpf/benchs/bench_htab_mem.c:284:3:
> error: Resource leak: fd [resourceLeak]
> tools/testing/selftests/bpf/prog_tests/sk_assign.c:41:3:
> error: Resource
On Fri, 4 Apr 2025 12:55:09 +0200
David Hildenbrand wrote:
> For virito-balloon, we should probably do the following:
>
> From 38e340c2bb53c2a7cc7c675f5dfdd44ecf7701d9 Mon Sep 17 00:00:00 2001
> From: David Hildenbrand
> Date: Fri, 4 Apr 2025 12:53:16 +0200
> Subject: [PATCH] virtio-balloon: F
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko :
On Tue, 1 Apr 2025 14:15:46 +0800 you wrote:
> Replace comma between expressions with semicolons.
>
> Using a ',' in place of a ';' can have unintended side effects.
> Although that is not the case here, it is seems
On 04.04.25 12:00, David Hildenbrand wrote:
On 04.04.25 06:36, Halil Pasic wrote:
On Thu, 3 Apr 2025 16:28:31 +0200
David Hildenbrand wrote:
Sorry I have to have a look at that discussion. Maybe it will answer
some my questions.
Yes, I think so.
Let's fix it without affecting existin
On Wed, Mar 19, 2025 at 10:59:57AM +0800, Shuai Xue wrote:
> + ARM maintainers for review.
>
> 在 2025/3/12 14:15, Shuai Xue 写道:
> > The pidfd_test fails on the ARM64 platform with the following error:
> >
> > Bail out! pidfd_poll check for premature notification on child thread
> > exec tes
On Mon, Mar 31, 2025 at 12:56:26PM +0100, Mark Brown wrote:
> On Fri, Mar 28, 2025 at 05:08:26PM -0600, Shuah Khan wrote:
> > If this is going through tip
> > Acked-by: Shuah Khan
> > Otherwise, I can send this up
> Given that this hasn't had a response from tip for several weeks it's
> probab
Gentle ping :)
On 6/3/25 20:49, Ignacio Encinas wrote:
> Vector registers are zero initialized by the kernel. Stop accepting
> "all ones" as a clean value.
>
> Note that this was not working as expected given that
> value == 0xff
> can be assumed to be always false by the compiler as value'
In handle_tx_copy, TX batching processes packets below ~PAGE_SIZE and
batches up to 64 messages before calling sock->sendmsg.
Currently, when there are no more messages on the ring to dequeue,
handle_tx_copy re-enables kicks on the ring *before* firing off the
batch sendmsg. However, sock->sendmsg
Am Donnerstag, dem 03.04.2025 um 10:26 -0400 schrieb Willem de Bruijn:
> Michael S. Tsirkin wrote:
> > On Thu, Apr 03, 2025 at 03:51:01PM +0200, Markus Fohrer wrote:
> > > Am Donnerstag, dem 03.04.2025 um 09:04 -0400 schrieb Michael S.
> > > Tsirkin:
> > > > On Wed, Apr 02, 2025 at 11:12:07PM +0200
On Fri, Apr 04, 2025 at 06:53:17AM +, Reshetova, Elena wrote:
> > On Wed, Apr 02, 2025 at 01:11:25PM +, Reshetova, Elena wrote:
> > > > > current SGX kernel code does not handle such errors in any other way
> > > > > than notifying that operation failed for other ENCLS leaves. So, I
> > >
The new operation allows to decouple the userfaulfd code from
dependencies to VMA types, specifically, shmem and hugetlb. The
vm_flags bitmap argument is processed with "any" logic, meaning if the
VMA type supports any of the flags set, it returns true. This is to
avoid multiple calls when checki
On 04.04.25 15:36, Halil Pasic wrote:
On Fri, 4 Apr 2025 12:55:09 +0200
David Hildenbrand wrote:
For virito-balloon, we should probably do the following:
From 38e340c2bb53c2a7cc7c675f5dfdd44ecf7701d9 Mon Sep 17 00:00:00 2001
From: David Hildenbrand
Date: Fri, 4 Apr 2025 12:53:16 +0200
Subj
On Fri, Apr 4, 2025 at 4:06 PM Masahiro Yamada wrote:
> > > > Current version of genksyms doesn't know anything about
> > > > __typeof_unqual__()
> > > > operator. Avoid the usage of __typeof_unqual__() with genksyms to
> > > > prevent
> > > > errors when symbols are versioned.
> > > >
> > > >
This series is built on top of the Fuad's v7 "mapping guest_memfd backed
memory at the host" [1].
With James's KVM userfault [2], it is possible to handle stage-2 faults
in guest_memfd in userspace. However, KVM itself also triggers faults
in guest_memfd in some cases, for example: PV interfaces
Remove shmem-specific code from UFFDIO_CONTINUE implementation for
non-huge pages by calling vm_ops->fault(). A new VMF flag,
FAULT_FLAG_USERFAULT_CONTINUE, is introduced to avoid recursive call to
handle_userfault().
Suggested-by: James Houghton
Signed-off-by: Nikita Kalyazin
---
include/linu
Signed-off-by: Nikita Kalyazin
---
include/linux/userfaultfd_k.h | 13 ++---
mm/userfaultfd.c | 10 +++---
2 files changed, 13 insertions(+), 10 deletions(-)
diff --git a/include/linux/userfaultfd_k.h b/include/linux/userfaultfd_k.h
index 75342022d144..64551e8a55fb 10064
The test demonstrates that a minor userfaultfd event in guest_memfd can
be resolved via a memcpy followed by a UFFDIO_CONTINUE ioctl.
Signed-off-by: Nikita Kalyazin
---
.../testing/selftests/kvm/guest_memfd_test.c | 99 +++
1 file changed, 99 insertions(+)
diff --git a/tools/te
Signed-off-by: Nikita Kalyazin
---
fs/userfaultfd.c | 3 ++-
include/uapi/linux/userfaultfd.h | 8 +++-
2 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/fs/userfaultfd.c b/fs/userfaultfd.c
index 97c4d71115d8..32152bfa462a 100644
--- a/fs/userfaultfd.c
+++ b/fs/us
Markus Fohrer wrote:
> Am Freitag, dem 04.04.2025 um 10:52 +0200 schrieb Markus Fohrer:
> > Am Freitag, dem 04.04.2025 um 04:29 -0400 schrieb Michael S. Tsirkin:
> > > On Fri, Apr 04, 2025 at 10:16:55AM +0200, Markus Fohrer wrote:
> > > > Am Donnerstag, dem 03.04.2025 um 09:04 -0400 schrieb Michael
On Fri, Apr 04, 2025 at 02:16:39PM +0100, Jonathan Cameron wrote:
> On Thu, 3 Apr 2025 13:33:12 -0500 Terry Bowman wrote:
> > Add a release_Sam_region_adjustable() interface to allow for
>
> Who is Sam? (typo)
Somebody's uncle?
...
> > #ifdef CONFIG_MEMORY_HOTREMOVE
> > extern void release
On Thu, 3 Apr 2025 13:33:14 -0500
Terry Bowman wrote:
> From: Nathan Fontenot
mum?
>
> In order to handle registering hmem devices for SOFT RESERVE
> resources after the dax hmem device initialization occurs
> we need to save a reference to the dax hmem platform device
> that will be used in
On Thu, 3 Apr 2025 13:33:13 -0500
Terry Bowman wrote:
> From: Nathan Fontenot
>
> Update handling of SOFT RESERVE iomem resources that intersect with
> CXL region resources to remove intersections from the SOFT RESERVE
> resources. The current approach of leaving SOFT RESERVE resources as
> is
Commit 098eadce3c62 ("vhost_net: disable zerocopy by default") disabled
the module parameter for the handle_tx_zerocopy path back in 2019,
nothing that many downstream distributions (e.g., RHEL7 and later) had
already done the same.
Both upstream and downstream disablement suggest this path is rar
There is a possible race between removing a cgroup diectory that is
a partition root and the creation of a new partition. The partition
to be removed can be dying but still online, it doesn't not currently
participate in checking for exclusive CPUs conflict, but the exclusive
CPUs are still there
On Fri, Apr 04, 2025 at 03:43:46PM +, Nikita Kalyazin wrote:
> This series is built on top of the Fuad's v7 "mapping guest_memfd backed
> memory at the host" [1].
Hm if this is based on an unmerged series this seems quite speculative and
should maybe be an RFC? I mean that series at least stil
On Thu, 3 Apr 2025 13:33:15 -0500
Terry Bowman wrote:
> From: Nathan Fontenot
>
> The dax hmem device initialization will consume any iomem
> SOFT RESERVE resources prior to CXL region creation. To allow
> for the CXL driver to complete region creation and trim any
> SOFT RESERVE resources befo
On Fri, 4 Apr 2025 15:48:49 +0200
David Hildenbrand wrote:
> > Sounds good to me! But I'm still a little confused by the "holes".
> > What confuses me is that i can think of at least 2 distinct types of
> > "holes": 1) Holes that can be filled later. The queue conceptually
> > exists, but there i
On Fri, Apr 4, 2025 at 10:11 PM Uros Bizjak wrote:
>
> On Fri, Apr 4, 2025 at 2:56 PM Masahiro Yamada wrote:
> >
> > On Fri, Apr 4, 2025 at 7:25 PM Uros Bizjak wrote:
> > >
> > > Current version of genksyms doesn't know anything about
> > > __typeof_unqual__()
> > > operator. Avoid the usage o
On 04.04.25 16:00, Halil Pasic wrote:
On Fri, 4 Apr 2025 15:48:49 +0200
David Hildenbrand wrote:
Sounds good to me! But I'm still a little confused by the "holes".
What confuses me is that i can think of at least 2 distinct types of
"holes": 1) Holes that can be filled later. The queue concept
On Fri, 4 Apr 2025 16:17:14 +0200
David Hildenbrand wrote:
> > It is offered. And this is precisely why I'm so keen on having a
> > precise wording here.
>
> Yes, me too. The current phrasing in the spec is not clear.
>
> Linux similarly checks
> virtio_has_feature()->virtio_check_driver_off
Currently if the filesystem for the cgroups version it wants to use is
not mounted charge_reserved_hugetlb.sh and hugetlb_reparenting_test.sh
tests will attempt to mount it on the hard coded path
/dev/cgroup/memory, deleting that directory when the test finishes. This
will fail if there is not a pr
Hi Terry,
kernel test robot noticed the following build errors:
[auto build test ERROR on aae0594a7053c60b82621136257c8b648c67b512]
url:
https://github.com/intel-lab-lkp/linux/commits/Terry-Bowman/kernel-resource-Provide-mem-region-release-for-SOFT-RESERVES/20250404-023601
base
On 04/04/2025 17:33, Lorenzo Stoakes wrote:
On Fri, Apr 04, 2025 at 03:43:46PM +, Nikita Kalyazin wrote:
This series is built on top of the Fuad's v7 "mapping guest_memfd backed
memory at the host" [1].
Hm if this is based on an unmerged series this seems quite speculative and
should ma
On Fri, Apr 04, 2025 at 05:56:58PM +0100, Nikita Kalyazin wrote:
>
>
> On 04/04/2025 17:33, Lorenzo Stoakes wrote:
> > On Fri, Apr 04, 2025 at 03:43:46PM +, Nikita Kalyazin wrote:
> > > This series is built on top of the Fuad's v7 "mapping guest_memfd backed
> > > memory at the host" [1].
> >
>
1 - 100 of 175 matches
Mail list logo
