Since long time ago, the only user of vq->log is vhost-net. The concern is
to add support for more devices (i.e. vhost-scsi or vsock) may reveals
unknown issue in the vhost API. Add a WARNING.
Suggested-by: Joao Martins
Signed-off-by: Dongli Zhang
---
drivers/vhost/vhost.c | 18
Log write descriptors for the event queue, leveraging vhost_get_vq_desc()
to retrieve the array of write descriptors to obtain the log buffer.
There is only one path for event queue.
Suggested-by: Joao Martins
Signed-off-by: Dongli Zhang
Reviewed-by: Mike Christie
---
drivers/vhost/scsi.c | 1
Although the support of VIRTIO_F_ANY_LAYOUT + VIRTIO_F_VERSION_1 was
signaled by the commit 664ed90e621c ("vhost/scsi: Set
VIRTIO_F_ANY_LAYOUT + VIRTIO_F_VERSION_1 feature bits"),
vhost_scsi_send_bad_target() still assumes the response in a single
descriptor.
In addition, although vhost_scsi_send_
Although the support of VIRTIO_F_ANY_LAYOUT + VIRTIO_F_VERSION_1 was
signaled by the commit 664ed90e621c ("vhost/scsi: Set
VIRTIO_F_ANY_LAYOUT + VIRTIO_F_VERSION_1 feature bits"),
vhost_scsi_send_bad_target() still assumes the response in a single
descriptor.
Similar issue in vhost_scsi_send_bad_t
Currently, the only user of vhost_log_write() is vhost-net. The 'len'
argument prevents logging of pages that are not tainted by the RX path.
Adjustments are needed since more drivers (i.e. vhost-scsi) begin using
vhost_log_write(). So far vhost-net RX path may only partially use pages
shared via
The live migration with vhost-scsi has been enabled by QEMU commit
b3e89c941a85 ("vhost-scsi: Allow user to enable migration"), which
thoroughly explains the workflow that QEMU collaborates with vhost-scsi on
the live migration.
Although it logs dirty data for the used ring, it doesn't log any wri
On Tue, Apr 1, 2025 at 9:30 PM Stefano Garzarella wrote:
>
> On Fri, Mar 28, 2025 at 06:02:45PM +0800, Cindy Lu wrote:
> >The vhost now uses vhost_task and workers as a child of the owner thread.
> >While this aligns with containerization principles,it confuses some legacy
>
> nit: missing space "
On Tue, Apr 1, 2025 at 9:21 PM Stefano Garzarella wrote:
>
> On Fri, Mar 28, 2025 at 06:02:52PM +0800, Cindy Lu wrote:
> >Introduce a new config knob `CONFIG_VHOST_ENABLE_FORK_OWNER_IOCTL`,
> >to control the availability of the `VHOST_FORK_FROM_OWNER` ioctl.
> >When CONFIG_VHOST_ENABLE_FORK_OWNER_
The pull request you sent on Mon, 31 Mar 2025 16:16:40 -0500:
> g...@gitolite.kernel.org:pub/scm/linux/kernel/git/nvdimm/nvdimm.git
> tags/libnvdimm-for-6.15
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/447d2d272e4e0c7cd9dfc6aeeadad9d70b3fb1ef
Thank you!
--
Deet-
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski :
On Fri, 28 Mar 2025 15:15:28 +0100 you wrote:
> From: Stefano Garzarella
>
> When a peer attempts to establish a connection, vsock_connect() contains
> a loop that waits for the state to be TCP_ESTABLISHED. However, the
On 01/04/2025 15:05, Sabrina Dubroca wrote:
2025-03-18, 02:40:41 +0100, Antonio Quartulli wrote:
+void ovpn_socket_release(struct ovpn_peer *peer)
+{
+ struct ovpn_socket *sock;
+
+ might_sleep();
+
+ /* release may be invoked after socket was detached */
+ rcu_read_lock(
Le Wed, Apr 02, 2025 at 06:53:24AM +, Kuyo Chang (張建文) a écrit :
> Hi,
>
> By review the get_nohz_timer_target(), it's probably making an offline
> CPU visible at timer candidates, maybe this patch could fix it?
>
>
> [PATCH] sched/core: Exclude offline CPUs from the timer candidates
>
> Th
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 it actually exists (name != NULL)
and assign an incremen
The creation of the sysroot does not require a kernel configuration.
Drop the dependency.
Signed-off-by: Thomas Weißschuh
---
tools/testing/selftests/nolibc/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/nolibc/Makefile
b/tools/testing/self
If no explicit XARCH is specified, use the toolchains default.
Signed-off-by: Thomas Weißschuh
---
Thomas Weißschuh (2):
selftests/nolibc: drop dependency from sysroot to defconfig
selftests/nolibc: only consider XARCH for CFLAGS when requested
tools/testing/selftests/nolibc/Makefil
On Wed, Apr 2, 2025 at 9:08 AM Nikita Kalyazin wrote:
>
> Signed-off-by: Nikita Kalyazin
> ---
> include/linux/userfaultfd_k.h | 13 -
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/userfaultfd_k.h b/include/linux/userfaultfd_k.h
> index 75342022d144
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 +++
1 file changed, 94 insertions(+)
diff --git a/tools/te
Remove shmem-specific code from UFFDIO_CONTINUE implementation for
non-huge pages by calling vm_ops->fault(). A new VMF flag,
FAULT_FLAG_NO_USERFAULT_MINOR, is introduced to avoid recursive call to
handle_userfault().
Signed-off-by: Nikita Kalyazin
---
include/linux/mm_types.h | 3 +++
mm/huge
On Wed, Apr 02, 2025 at 12:19:13PM -0400, Joel Fernandes wrote:
> Hello,
>
> On Wed, 2 Apr 2025 16:17:06 GMT, Sebastian Andrzej Siewior wrote:
> > On 2025-03-31 14:03:06 [-0700], Paul E. McKenney wrote:
> > > The torture.sh --do-rt command-line parameter is intended to mimic -rt
> > > kernels. No
On Wed, Apr 2, 2025 at 9:07 AM Nikita Kalyazin wrote:
>
> Remove shmem-specific code from UFFDIO_CONTINUE implementation for
> non-huge pages by calling vm_ops->fault(). A new VMF flag,
> FAULT_FLAG_NO_USERFAULT_MINOR, is introduced to avoid recursive call to
> handle_userfault().
>
> Signed-off-
From: Kaustabh Chakraborty
Some replacement displays include third-party touch ICs which do not
expose the function number and the interrupt status in its PDT entries.
OnePlus 6 (original touch IC)
rmi4_i2c 12-0020: read 6 bytes at 0x00e3: 0 (2b 22 0d 06 01 01)
OnePlus 6 (aftermarket touch IC
On 10/03/2025 20:10, Dmitry Torokhov wrote:
Hi David,
On Sat, Mar 08, 2025 at 03:08:38PM +0100, David Heidelberg via B4 Relay wrote:
From: Caleb Connolly
Some third party rmi4-compatible ICs don't expose their PDT entries
very well. Add a few checks to skip duplicate entries as well as entrie
From: Kaustabh Chakraborty
Some replacement displays include third-party touch ICs which incur a
significant penalty (1-2 seconds) when doing certain unaligned reads.
This is enough to break functionality when it happens in the hot path,
so adjust the interrupt handler to not read from an unalign
From: Kaustabh Chakraborty
Some replacement displays include third-party touch ICs which do not
report the product ID correctly unless we read directly from the
product ID register. Add a check and a fallback read to handle this.
Signed-off-by: Kaustabh Chakraborty
Signed-off-by: Caleb Connolly
From: Caleb Connolly
Some third party rmi4-compatible ICs don't expose their PDT entries
very well. Add a few checks to skip duplicate entries as well as entries
for unsupported functions.
This is required to support some phones with third party displays.
Validated on a stock OnePlus 6T (origin
The pull request you sent on Tue, 1 Apr 2025 23:16:06 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/rcu/linux.git
> tags/rcu-fixes-v6.15
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/da0512b2a3b4124b1483751f090d7ac13a713f0e
Thank you!
--
Deet-doot-dot, I
Hello,
On Wed, 2 Apr 2025 16:17:06 GMT, Sebastian Andrzej Siewior wrote:
> On 2025-03-31 14:03:06 [-0700], Paul E. McKenney wrote:
> > The torture.sh --do-rt command-line parameter is intended to mimic -rt
> > kernels. Now that CONFIG_PREEMPT_RT is upstream, this commit makes this
> > mimicking m
This series is built on top of 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 like
On Sat, 22 Mar 2025 01:29:54 +0100
Halil Pasic wrote:
> As per virtio spec the fields cols and rows are specified as little
> endian.
[..]
@Amit: Any feedback?
>
> Fixes: 8345adbf96fc1 ("virtio: console: Accept console size along with resize
> control message")
> Signed-off-by: Halil Pasic
On Wed, Apr 02, 2025 at 03:06:46PM +, 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 becomes shallower than the virtqueue size.
>
> This logic works fine whe
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 becomes shallower than the virtqueue size.
This logic works fine when you connect a user space application on the
hypervisor with a virtio-vso
Le Tue, Apr 01, 2025 at 12:30:40PM -0400, Joel Fernandes a écrit :
> Hello, Frederic,
>
> On Tue, 1 Apr 2025 16:27:36 GMT, Frederic Weisbecker wrote:
> > Le Mon, Mar 31, 2025 at 02:29:52PM -0700, Paul E. McKenney a écrit :
> > > The disagreement is a feature, at least up to a point. That feature
On Wed, Apr 02, 2025 at 05:19:25PM +0800, Xiangzhi Tang wrote:
> Add host driver to control the mediatek Risc-V coprocessor
>
> 1.Support rproc mechanism to load vcm firmware from filesystem
> 2.Support SMC services to request ATF to setting vcp boot sequence
> 3.Host communicated with VCP depends
On Wed, Apr 02, 2025 at 09:43:55AM +0800, Peng Fan wrote:
> On Tue, Apr 01, 2025 at 10:05:03AM -0600, Mathieu Poirier wrote:
> >On Tue, Apr 01, 2025 at 09:41:24AM +0800, Peng Fan wrote:
...
> >
> >The core is already checking if @loaded_table is valid in rproc_start(), why
> >can't that be used ins
On Wed, Apr 02, 2025 at 10:26:05AM +0100, Simon Horman 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 becomes shallo
> On Tue, Apr 01, 2025 at 09:35:33AM +, Reshetova, Elena wrote:
> > > > None of these exceptional conditions are fatal or present an
> > > > immediate danger to the system security. So, allowing the re-tries
> > > > seems logical in this case. In case re-tries also fail, the system
> > > > admi
On 01/04/2025 11:59, Sabrina Dubroca wrote:
2025-03-18, 02:40:44 +0100, Antonio Quartulli wrote:
+/* this swap is not atomic, but there will be a very short time frame where the
+ * old_secondary key won't be available. This should not be a big deal as most
+ * likely both peers are already usin
On 01/04/2025 14:51, Sabrina Dubroca wrote:
2025-03-18, 02:40:51 +0100, Antonio Quartulli wrote:
@@ -124,6 +154,13 @@ void ovpn_decrypt_post(void *data, int ret)
goto drop;
}
+ if (ovpn_is_keepalive(skb)) {
+ net_dbg_ratelimited(
On 01/04/2025 12:02, Sabrina Dubroca wrote:
2025-03-18, 02:40:46 +0100, Antonio Quartulli wrote:
+static void ovpn_tcp_rcv(struct strparser *strp, struct sk_buff *skb)
+{
[...]
+ /* we need the first byte of data to be accessible
nit: and "first byte" here too (that comment could maybe
On 02/04/2025 11:19, Xiangzhi Tang wrote:
> Add support MediaTek's Video Companion Processor(VCP) host driver to
> control the MediaTek VCP Risc-V coprocessor.
> The VCP host driver using rproc mechanism to load vcm firmware
> from filesystem, and using SMC services to request ATF to setting
> vcp
Add the new binding document for MediaTek Video Companion
Processor(VCP) on MediaTek mt8196.
Signed-off-by: Xiangzhi Tang
---
.../remoteproc/mediatek,mt8196-vcp.yaml | 174 ++
1 file changed, 174 insertions(+)
create mode 100644
Documentation/devicetree/bindings/remotepro
41 matches
Mail list logo
