similar to: [PATCH v2 01/11] genirq/affinity:: Export irq_create_affinity_masks()

On Tue, Mar 28, 2023 at 11:03?AM Yongji Xie <xieyongji at bytedance.com> wrote: > > On Fri, Mar 24, 2023 at 2:28?PM Jason Wang <jasowang at redhat.com> wrote: > > > > On Thu, Mar 23, 2023 at 1:31?PM Xie Yongji <xieyongji at bytedance.com> wrote: > > > > > > To support interrupt affinity spreading mechanism, > > > this makes use of

On Tue, Mar 28, 2023 at 12:05?PM Yongji Xie <xieyongji at bytedance.com> wrote: > > On Tue, Mar 28, 2023 at 11:44?AM Jason Wang <jasowang at redhat.com> wrote: > > > > On Tue, Mar 28, 2023 at 11:33?AM Yongji Xie <xieyongji at bytedance.com> wrote: > > > > > > On Tue, Mar 28, 2023 at 11:14?AM Jason Wang <jasowang at redhat.com> wrote: >

On Tue, Feb 28, 2023 at 5:42?PM Xie Yongji <xieyongji at bytedance.com> wrote: > > This introduces set_irq_affinity callback in > vdpa_config_ops so that vdpa device driver can > get the interrupt affinity hint from the virtio > device driver. The interrupt affinity hint would > be needed by the interrupt affinity spreading > mechanism. > > Signed-off-by: Xie

? 2023/2/28 17:41, Xie Yongji ??: > Add eventfd for the vdpa callback so that user > can signal it directly instead of running the > callback. It will be used for vhost-vdpa case. > > Signed-off-by: Xie Yongji <xieyongji at bytedance.com> > --- > drivers/vhost/vdpa.c | 2 ++ > drivers/virtio/virtio_vdpa.c | 1 + > include/linux/vdpa.h | 3 +++

? 2023/3/23 13:30, Xie Yongji ??: > Since virtio-vdpa bus driver already support interrupt > affinity spreading mechanism, let's implement the > set_vq_affinity callback to bring it to vduse device. > After we get the virtqueue's affinity, we can spread > IRQs between CPUs in the affinity mask, in a round-robin > manner, to run the irq callback. > > Signed-off-by:

This is a note to let you know that I''ve just added the patch titled genirq: Add IRQF_RESUME_EARLY and resume such IRQs earlier to the 3.1-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: genirq-add-irqf_resume_early-and-resume-such-irqs-earlier.patch and it can be found in the

This small series enables virtio-net device type in VDUSE. With it, basic operation have been tested, both with virtio-vdpa and vhost-vdpa using DPDK Vhost library series adding VDUSE support using split rings layout (merged in DPDK v23.07-rc1). Control queue support (and so multiqueue) has also been tested, but requires a Kernel series from Jason Wang relaxing control queue polling [1] to

Hi All, Here is the latest version of vhost-blk implementation. Major difference from my previous implementation is that, I now merge all contiguous requests (both read and write), before submitting them. This significantly improved IO performance. I am still collecting performance numbers, I will be posting in next few days. Comments ? Todo: - Address hch's comments on annontations -

Hi All, Here is the latest version of vhost-blk implementation. Major difference from my previous implementation is that, I now merge all contiguous requests (both read and write), before submitting them. This significantly improved IO performance. I am still collecting performance numbers, I will be posting in next few days. Comments ? Todo: - Address hch's comments on annontations -

This lpc_restore_order was partially inspired by Miroslav's affd, though my (not very great) ARM asm version resembled this, as well. The other two reduce CPU array indexing overhead in loops a little. Additionally, a request for help: My not very optimized lpc_restore_signal is at the below URL, I couldn't get the ldm* instructions to work as advertised, even though I've talked

Hi, Inspired by vhost-net implementation, I did initial prototype of vhost-blk to see if it provides any benefits over QEMU virtio-blk. I haven't handled all the error cases, fixed naming conventions etc., but the implementation is stable to play with. I tried not to deviate from vhost-net implementation where possible. NOTE: Only change I had to make to vhost core code is to increase

Hi, Inspired by vhost-net implementation, I did initial prototype of vhost-blk to see if it provides any benefits over QEMU virtio-blk. I haven't handled all the error cases, fixed naming conventions etc., but the implementation is stable to play with. I tried not to deviate from vhost-net implementation where possible. NOTE: Only change I had to make to vhost core code is to increase

Hi All, The ipxe git commit version changed, but its release version should still stay at v1.0.0 Signed-off-by: Yongjie Ren <yongjie.ren@intel.com<mailto:yongjie.ren@intel.com>> ------ diff -r 4086e4811547 tools/firmware/etherboot/Makefile --- a/tools/firmware/etherboot/Makefile Thu Jan 05 17:25:23 2012 +0000 +++ b/tools/firmware/etherboot/Makefile Fri Jan 06 14:30:54 2012 +0800 @@

document update in xl.cfg.pod.5 for ''stdvga=1'' by default Signed-off-by: Yongjie Ren <yongjie.ren@intel.com> diff -r b98feb4d6359 docs/man/xl.cfg.pod.5 --- a/docs/man/xl.cfg.pod.5 Tue Jun 26 12:56:31 2012 +0800 +++ b/docs/man/xl.cfg.pod.5 Tue Jun 26 13:27:19 2012 +0800 @@ -718,9 +718,10 @@ =item B<stdvga=BOOLEAN> Select a standard VGA card with VBE (VESA BIOS

flight 10626 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/10626/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-multivcpu 16 guest-start.2 fail in 10623 REGR. vs. 10621 Tests which are failing intermittently (not blocking): test-amd64-i386-rhel6hvm-intel 4 xen-install fail

Hi All, We did a round testing for Xen 4.2 RC1 (CS#25692) with Linux 3.4.7 dom0. We covered VT-d, SR-IOV, Power Management, TXT, IVB new features, HSW new features. We covered many cases for HVM guests (both Redhat Linux and MS Windows guest). We tested on Westmere-EP, SandyBridge-EP, IvyBridge desktop, and Haswell hardware platforms. We found no new issues, and verified 1 fixed bug. Fixed bug

Hi folks, From the roadmap for Xen 4.3 development, Xen 4.3 will use upstream QEMU (partially done). So I''d like to confirm the following questions. 1. Will Xen 4.3 really use upstream QEMU by default ? I have the question because so far the xen.git tree still uses qemu-xen-unstable by default. 2. If ''yes'' for 1st question, which QEMU upstream will be used in Xen

flight 11929 xen-unstable running [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/11929/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-i386-i386-xl-qemuu-winxpsp3 <none executed> queued test-amd64-amd64-xl-qemuu-winxpsp3 <none executed> queued test-amd64-amd64-xl-qemuu-win7-amd64

Hi Yongjie, I have just compiled and installed Xen 4.3-unstable changeset 26666 and Linux kernel 3.8.1, according to your specifications. However, I still cannot get success with Intel HD Graphics 4600 IGD VGA passthrough. Although in Device Manager in Windows 7 HVM domU, it says "This device is working properly" for Intel HD Graphics 4600, I can only get 16 colors. Please refer to

Hi Yongjie, I have just compiled and installed Xen 4.3-unstable changeset 26666 and Linux kernel 3.8.1, according to your specifications. However, I still cannot get success with Intel HD Graphics 4600 IGD VGA passthrough. Although in Device Manager in Windows 7 HVM domU, it says "This device is working properly" for Intel HD Graphics 4600, I can only get 16 colors. Please refer to