Re: [PATCH v14] i2c: virtio: add a virtio i2c frontend driver

On 22-07-21, 08:06, Greg KH wrote: > No new features are allowed for 5.14, you know this. It's but fixes > only now. I was trying to be (overly) optimistic here since this was a fairly independent driver which won't break anything else, and had been pending on the list since many months now. But

Re: [PATCH v14] i2c: virtio: add a virtio i2c frontend driver

On Thu, Jul 22, 2021 at 10:44:33AM +0530, Viresh Kumar wrote: > On 09-07-21, 10:25, Jie Deng wrote: > > Add an I2C bus driver for virtio para-virtualization. > > > > The controller can be emulated by the backend driver in > > any device model software by following the virtio protocol. > > > > The

Re: [PATCH v14] i2c: virtio: add a virtio i2c frontend driver

On 09-07-21, 10:25, Jie Deng wrote: > Add an I2C bus driver for virtio para-virtualization. > > The controller can be emulated by the backend driver in > any device model software by following the virtio protocol. > > The device specification can be found on > https://lists.oasis-open.org/archive

Re: [PATCH 04/12] x86/sev: Do not hardcode GHCB protocol version

On 7/21/21 9:20 AM, Joerg Roedel wrote: > From: Joerg Roedel > > Introduce the sev_get_ghcb_proto_ver() which will return the negotiated > GHCB protocol version and use it to set the version field in the GHCB. > > Signed-off-by: Joerg Roedel > --- > arch/x86/boot/compressed/sev.c | 5 + >

RE: [PATCH v2 3/4] tools headers UAPI: add cpu_relax() implementation for x86 and arm64

From: Yunsheng Lin > Sent: 20 July 2021 03:22 > > As x86 and arm64 is the two available systems that I can build > and test the cpu_relax() implementation, so only add cpu_relax() > implementation for x86 and arm64, other arches can be added easily > when needed. > ... > +#if defined(__i386__) ||

Re: [PATCH v2 0/4] virtiofs,fuse: support per-file DAX

On Wed, Jul 21, 2021 at 08:48:57AM -0400, Vivek Goyal wrote: [..] > > > So is "dax=inode" enough for your needs? What's your requirement, > > > can you give little bit of more details. > > > > In our use case, the backend fs is something like SquashFS on host. The > > content of the file on host i

Re: [PATCH v2 3/4] fuse: add per-file DAX flag

On Wed, Jul 21, 2021 at 10:14:44PM +0800, JeffleXu wrote: [..] > > Also, please copy virtiofs list (virtio...@redhat.com) when you post > > patches next time. > > > > Got it. By the way, what's the git repository of virtiofsd? AFAIK, > virtiofsd included in qemu (g...@github.com:qemu/qemu.git) do

[PATCH 1/1] virtio/vsock: Make vsock virtio packet buff size configurable

From: Ram Muthiah After a virtual device has been running for some time, the SLAB sustains ever increasing fragmentation. Contributing to this fragmentation are the virtio packet buffer allocations which are a drain on 64Kb compound pages. Eventually these can't be allocated due to fragmentation.

[PATCH v3 3/4] virtio: Protect vqs list access

VQs may be accessed to mark the device broken while they are created/destroyed. Hence protect the access to the vqs list. Fixes: e2dcdfe95c0b ("virtio: virtio_break_device() to mark all virtqueues broken.") Signed-off-by: Parav Pandit --- changelog: v1->v2: - use the hole in current struct to p

[PATCH v3 4/4] virtio_pci: Support surprise removal of virtio pci device

When a virtio pci device undergo surprise removal (aka async removal in PCIe spec), mark the device as broken so that any upper layer drivers can abort any outstanding operation. When a virtio net pci device undergo surprise removal which is used by a NetworkManager, a below call trace was observe

[PATCH v3 1/4] virtio: Improve vq->broken access to avoid any compiler optimization

Currently vq->broken field is read by virtqueue_is_broken() in busy loop in one context by virtnet_send_command(). vq->broken is set to true in other process context by virtio_break_device(). Reader and writer are accessing it without any synchronization. This may lead to a compiler optimization w

[PATCH v3 2/4] virtio: Keep vring_del_virtqueue() mirror of VQ create

Keep the vring_del_virtqueue() mirror of the create routines. i.e. to delete list entry first as it is added last during the create routine. Signed-off-by: Parav Pandit --- drivers/virtio/virtio_ring.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/virtio/virtio_ri

[PATCH v3 0/4] virtio short improvements

Hi, This series contains small improvements for virtio pci driver. The main idea is to support surprise removal of virtio pci device when the driver is already loaded. Future patches will further improve other areas of hotplug. Patches 1 to 3 prepare the code to handle surprise removal by marking

[PATCH 12/12] x86/sev: Support kexec under SEV-ES with AP Jump Table blob

From: Joerg Roedel When the AP Jump Table blob is installed the kernel can hand over the APs from the old to the new kernel. Enable kexec when the AP Jump Table blob has been installed. Signed-off-by: Joerg Roedel --- arch/x86/include/asm/sev.h | 2 ++ arch/x86/kernel/machine_kexec_64

[PATCH 10/12] x86/sev: Add MMIO handling support to boot/compressed/ code

From: Joerg Roedel Move the code for MMIO handling in the #VC handler to sev-shared.c so that it can be used in the decompressor code. The decompressor needs to handle MMIO events for writing to the VGA framebuffer. When the kernel is booted via UEFI the VGA console is not enabled that early, bu

[PATCH 11/12] x86/sev: Handle CLFLUSH MMIO events

From: Joerg Roedel Handle CLFLUSH instruction to MMIO memory in the #VC handler. The instruction is ignored by the handler, as the Hypervisor is responsible for cache management of emulated MMIO memory. Signed-off-by: Joerg Roedel --- arch/x86/kernel/sev-shared.c | 9 + 1 file changed,

[PATCH 09/12] x86/sev: Use AP Jump Table blob to stop CPU

From: Joerg Roedel To support kexec under SEV-ES the APs can't be parked with HLT. Upon wakeup the AP needs to find its way to execute at the reset vector set by the new kernel and in real-mode. This is what the AP Jump Table blob provides, so stop the APs the SEV-ES way by calling the AP-reset-

[PATCH 08/12] x86/sev: Park APs on AP Jump Table with GHCB protocol version 2

From: Joerg Roedel GHCB protocol version 2 adds the MSR-based AP-reset-hold VMGEXIT which does not need a GHCB. Use that to park APs in 16-bit protected mode on the AP Jump Table. Signed-off-by: Joerg Roedel --- arch/x86/include/asm/realmode.h| 3 + arch/x86/kernel/sev.c | 48

[PATCH 07/12] x86/sev: Setup code to park APs in the AP Jump Table

From: Joerg Roedel The AP Jump Table under SEV-ES contains the reset vector where non-boot CPUs start executing when coming out of reset. This means that a CPU coming out of the AP-reset-hold VMGEXIT also needs to start executing at the reset vector stored in the AP Jump Table. The problem is to

[PATCH 06/12] x86/sev: Cache AP Jump Table Address

From: Joerg Roedel Store the physical address of the AP Jump Table in kernel memory so that it does not need to be fetched from the Hypervisor again. Signed-off-by: Joerg Roedel --- arch/x86/kernel/sev.c | 26 ++ 1 file changed, 14 insertions(+), 12 deletions(-) diff -

[PATCH 05/12] x86/sev: Use GHCB protocol version 2 if supported

From: Joerg Roedel Check whether the hypervisor supports GHCB version 2 and use it if available. Signed-off-by: Joerg Roedel --- arch/x86/boot/compressed/sev.c | 10 -- arch/x86/include/asm/sev.h | 4 ++-- arch/x86/kernel/sev-shared.c | 17 ++--- 3 files changed, 24

[PATCH 04/12] x86/sev: Do not hardcode GHCB protocol version

From: Joerg Roedel Introduce the sev_get_ghcb_proto_ver() which will return the negotiated GHCB protocol version and use it to set the version field in the GHCB. Signed-off-by: Joerg Roedel --- arch/x86/boot/compressed/sev.c | 5 + arch/x86/kernel/sev-shared.c | 5 - arch/x86/kernel/

[PATCH 03/12] x86/sev: Save and print negotiated GHCB protocol version

From: Joerg Roedel Save the results of the GHCB protocol negotiation into a data structure and print information about versions supported and used to the kernel log. Signed-off-by: Joerg Roedel --- arch/x86/boot/compressed/sev.c | 2 +- arch/x86/kernel/sev-shared.c | 22

[PATCH 02/12] x86/kexec/64: Forbid kexec when running as an SEV-ES guest

From: Joerg Roedel For now, kexec is not supported when running as an SEV-ES guest. Doing so requires additional hypervisor support and special code to hand over the CPUs to the new kernel in a safe way. Until this is implemented, do not support kexec in SEV-ES guests. Cc: sta...@vger.kernel.or

[PATCH 01/12] kexec: Allow architecture code to opt-out at runtime

From: Joerg Roedel Allow a runtime opt-out of kexec support for architecture code in case the kernel is running in an environment where kexec is not properly supported yet. This will be used on x86 when the kernel is running as an SEV-ES guest. SEV-ES guests need special handling for kexec to ha

[PATCH 00/12] x86/sev: KEXEC/KDUMP support for SEV-ES guests

From: Joerg Roedel Hi, here are changes to enable kexec/kdump in SEV-ES guests. The biggest problem for supporting kexec/kdump under SEV-ES is to find a way to hand the non-boot CPUs (APs) from one kernel to another. Without SEV-ES the first kernel parks the CPUs in a HLT loop until they get re

Re: [PATCH v2 3/4] fuse: add per-file DAX flag

On 7/21/21 3:27 AM, Vivek Goyal wrote: > On Tue, Jul 20, 2021 at 02:51:34PM +0800, JeffleXu wrote: >> >> >> On 7/20/21 3:44 AM, Vivek Goyal wrote: >>> On Fri, Jul 16, 2021 at 06:47:52PM +0800, Jeffle Xu wrote: Add one flag for fuse_attr.flags indicating if DAX shall be enabled for this

Re: [PATCH v2 0/4] virtiofs,fuse: support per-file DAX

On Wed, Jul 21, 2021 at 08:32:19PM +0800, JeffleXu wrote: > > > On 7/21/21 3:18 AM, Vivek Goyal wrote: > > On Tue, Jul 20, 2021 at 01:25:11PM +0800, JeffleXu wrote: > >> > >> > >> On 7/20/21 5:30 AM, Vivek Goyal wrote: > >>> On Fri, Jul 16, 2021 at 06:47:49PM +0800, Jeffle Xu wrote: > This p

Re: [PATCH v2 3/4] fuse: add per-file DAX flag

On 7/21/21 3:40 AM, Vivek Goyal wrote: > On Tue, Jul 20, 2021 at 03:19:50PM +0800, JeffleXu wrote: >> >> >> On 7/20/21 2:41 AM, Vivek Goyal wrote: >>> On Fri, Jul 16, 2021 at 06:47:52PM +0800, Jeffle Xu wrote: Add one flag for fuse_attr.flags indicating if DAX shall be enabled for this

Re: [PATCH v2 0/4] virtiofs,fuse: support per-file DAX

On 7/21/21 3:18 AM, Vivek Goyal wrote: > On Tue, Jul 20, 2021 at 01:25:11PM +0800, JeffleXu wrote: >> >> >> On 7/20/21 5:30 AM, Vivek Goyal wrote: >>> On Fri, Jul 16, 2021 at 06:47:49PM +0800, Jeffle Xu wrote: This patchset adds support of per-file DAX for virtiofs, which is inspired b

Re: [PATCH v4 0/5] bus: Make remove callback return void

On Tue, Jul 13, 2021 at 09:35:17PM +0200, Uwe Kleine-König wrote: > Hello, > > this is v4 of the final patch set for my effort to make struct > bus_type::remove return void. > > The first four patches contain cleanups that make some of these > callbacks (more obviously) always return 0. They are

[PATCH v2] MAINTAINERS: Update for VMCI driver

Add maintainer info for the VMware VMCI driver. v2: moved pv-drivers to L: as private list Acked-by: Vishnu Dasa Signed-off-by: Jorgen Hansen --- MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index a61f4f3..969a67a 100644 --- a/MAINTAINERS ++

[WorldCIST'22]: Call for Workshops Proposals

- Call for Workshops Proposals WorldCist'22 - 10th World Conference on Information Systems and Technologies Budva, Montenegro, 12 - 14 April 2022 http://worldcist.org/ --

Re: [RFC 0/3] cpuidle: add poll_source API and virtio vq polling

On Wed, Jul 21, 2021 at 11:29:55AM +0800, Jason Wang wrote: > > 在 2021/7/14 上午12:19, Stefan Hajnoczi 写道: > > These patches are not polished yet but I would like request feedback on this > > approach and share performance results with you. > > > > Idle CPUs tentatively enter a busy wait loop befor

Re: [PATCH] MAINTAINERS: Update for VMCI driver

On Wed, Jul 21, 2021 at 09:26:15AM +, Jorgen Hansen wrote: > > > > On 21 Jul 2021, at 11:00, Greg KH wrote: > > > > On Wed, Jul 21, 2021 at 08:46:15AM +, Jorgen Hansen wrote: > >> > >> > >>> On 20 Jul 2021, at 12:39, Greg KH wrote: > >>> > >>> On Tue, Jul 20, 2021 at 03:29:01AM -070

Re: [PATCH] MAINTAINERS: Update for VMCI driver

> On 21 Jul 2021, at 11:00, Greg KH wrote: > > On Wed, Jul 21, 2021 at 08:46:15AM +, Jorgen Hansen wrote: >> >> >>> On 20 Jul 2021, at 12:39, Greg KH wrote: >>> >>> On Tue, Jul 20, 2021 at 03:29:01AM -0700, Jorgen Hansen wrote: Add maintainer info for the VMware VMCI driver.

Re: [PATCH] MAINTAINERS: Update for VMCI driver

On Wed, Jul 21, 2021 at 08:46:15AM +, Jorgen Hansen wrote: > > > > On 20 Jul 2021, at 12:39, Greg KH wrote: > > > > On Tue, Jul 20, 2021 at 03:29:01AM -0700, Jorgen Hansen wrote: > >> Add maintainer info for the VMware VMCI driver. > >> > >> Signed-off-by: Jorgen Hansen > >> --- > >> MAIN

Re: [PATCH] MAINTAINERS: Update for VMCI driver

> On 20 Jul 2021, at 12:39, Greg KH wrote: > > On Tue, Jul 20, 2021 at 03:29:01AM -0700, Jorgen Hansen wrote: >> Add maintainer info for the VMware VMCI driver. >> >> Signed-off-by: Jorgen Hansen >> --- >> MAINTAINERS | 8 >> 1 file changed, 8 insertions(+) >> >> diff --git a/MAINTA