Re: [PATCH v3] x86/xen: Add some null pointer checking to smp.c

2024-01-21 Thread Kunwu Chan
On 2024/1/19 18:40, Markus Elfring wrote: kasprintf() returns a pointer to dynamically allocated memory which can be NULL upon failure. Ensure the allocation was successful by checking the pointer validity. … --- Changes in v3: - Remove rc initialization - Simply error paths by

Re: [PATCH v3] x86/xen: Add some null pointer checking to smp.c

2024-01-21 Thread Kunwu Chan
On 2024/1/20 22:45, Markus Elfring wrote: kasprintf() returns a pointer to dynamically allocated memory which can be NULL upon failure. Ensure the allocation was successful by checking the pointer validity. How do you think about to refer to the function name instead of the file name in the

[ovmf test] 184421: all pass - PUSHED

2024-01-21 Thread osstest service owner
flight 184421 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/184421/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 0c6d29be8b1731ff6880d59e0189184395e45968 baseline version: ovmf

Re: [RFC KERNEL PATCH v4 3/3] PCI/sysfs: Add gsi sysfs for pci_dev

2024-01-21 Thread Chen, Jiqian
Hi Bjorn Helgaas, Do you have any comments on this patch? On 2024/1/5 14:22, Chen, Jiqian wrote: > There is a need for some scenarios to use gsi sysfs. > For example, when xen passthrough a device to dumU, it will > use gsi to map pirq, but currently userspace can't get gsi > number. > So, add

[linux-linus test] 184418: tolerable FAIL - PUSHED

2024-01-21 Thread osstest service owner
flight 184418 linux-linus real [real] flight 184420 linux-linus real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/184418/ http://logs.test-lab.xenproject.org/osstest/logs/184420/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking):

Re: Sketch of an idea for handling the "mixed workload" problem

2024-01-21 Thread Demi Marie Obenour
On Fri, Sep 29, 2023 at 05:42:16PM +0100, George Dunlap wrote: > The basic credit2 algorithm goes something like this: > > 1. All vcpus start with the same number of credits; about 10ms worth > if everyone has the same weight > > 2. vcpus burn credits as they consume cpu, based on the relative >

Re: Sketch of an idea for handling the "mixed workload" problem

2024-01-21 Thread Demi Marie Obenour
On Mon, Oct 02, 2023 at 12:20:31PM +0100, George Dunlap wrote: > On Sun, Oct 1, 2023 at 12:28 AM Demi Marie Obenour > wrote: > > > > On Fri, Sep 29, 2023 at 05:42:16PM +0100, George Dunlap wrote: > > > The basic credit2 algorithm goes something like this: > > > > > > 1. All vcpus start with the

[linux-linus test] 184416: tolerable FAIL - PUSHED

2024-01-21 Thread osstest service owner
flight 184416 linux-linus real [real] flight 184417 linux-linus real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/184416/ http://logs.test-lab.xenproject.org/osstest/logs/184417/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking):

[xen-unstable test] 184415: tolerable FAIL

2024-01-21 Thread osstest service owner
flight 184415 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/184415/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 184407