I missed the fact that the "video-firmware" subnode is
> > > > > > > already
> > > > > > > documented for iris as well through qcom,venus-common.yaml (which
> > > > > > > is
> > > > > > > in
removed during teardown. Additionally, SHM bridge setup is
required to enable memory protection for both remoteproc metadata and
its memory regions. When the aforementioned hypervisor is absent, the
operating system must perform these configurations instead.
When Linux runs as the hypervisor (at EL2) on
A few months ago, we discussed the challenges at Linaro Connect 2025 [1]
related to Secure PAS remoteproc enablement when Linux is running at EL2.
[1] https://resources.linaro.org/en/resource/sF8jXifdb9V1mUefdbfafa
Below, is the summary of the discussion.
Qualcomm is working to enable remote
The same inclusion is already satisfied by vdso/clocksource.h.
Signed-off-by: Thomas Weißschuh
---
include/linux/clocksource.h | 4
1 file changed, 4 deletions(-)
diff --git a/include/linux/clocksource.h b/include/linux/clocksource.h
index
12d853b1883265cb47d93e33d8370e3957e7e695
On Mon, Sep 08, 2025 at 05:23:45PM +0800, Haixu Cui wrote:
> This is the 10th version of the virtio SPI Linux driver patch series which is
> intended to be compliant with the upcoming virtio specification
> version 1.4. The specification can be found in repository:
> https://github.c
This header is unnecessary and together with some upcoming changes would
introduce compiler warnings.
Link:
https://lore.kernel.org/lkml/20250916-mm-rcuwait-v1-1-39a3beea6...@linutronix.de/
Signed-off-by: Thomas Weißschuh
---
lib/vdso/datastore.c | 1 -
1 file changed, 1 deletion(-)
diff --git
On Fri, 12 Sep 2025 22:53:23 +0300 Yana Bashlykova wrote:
> This series adds comprehensive testing infrastructure for Netlink
> and Generic Netlink
>
> The implementation includes both kernel module and userspace tests to
> verify correct Generic Netlink and Netlink behaviors under
> various condi
t; > Sorry, I missed the fact that the "video-firmware" subnode is
> > > > > > already
> > > > > > documented for iris as well through qcom,venus-common.yaml (which is
> > > > > > included for qcom,sm8550-iris
MADV_COLLAPSE is part of linux/mman.h and needs to be included
for this selftest for glibc compatibility. It is also included
in other tests that use MADV_COLLAPSE.
Fixes: d9c7ff4dae62 ("selftests: prctl: introduce tests for disabling THPs
completely")
Reported-by: Mark Brown
Clos
On 09/09/2025 13:19, Mukesh Ojha wrote:
Have you continued working on this to unblock adding the IOMMU needed
for the IRIS firmware?
We are discussing on this internally and if this can be taken along with
non-pixel case or not, will come back on this.
If it takes too much, will drop video supp
This is the 10th version of the virtio SPI Linux driver patch series which is
intended to be compliant with the upcoming virtio specification
version 1.4. The specification can be found in repository:
https://github.com/oasis-tcs/virtio-spec.git branch virtio-1.4.
The original contributor Harald
y with this next-20250814 tag ?
> > > > You sent it on the 19th, so it's in your best interest to run a quick
> > > >
> > > > git rebase --onto linux-next/master $(git describe --abbrev=0)
> > > >
> > > > and giving the series a prom
;s in your best interest to run a quick
git rebase --onto linux-next/master $(git describe --abbrev=0)
and giving the series a prompt re-test before sending, because there
might have
been incompatible changes, whether ones that would prevent applying,
or break
things functionally
I can't eve
On 03/09/2025 15:02, Dmitry Baryshkov wrote:
On Wed, Sep 03, 2025 at 02:31:55PM +0100, Bryan O'Donoghue wrote:
On 03/09/2025 12:56, Konrad Dybcio wrote:
Can you try with this next-20250814 tag ?
You sent it on the 19th, so it's in your best interest to run a quick
git rebase --
On 03/09/2025 15:02, Dmitry Baryshkov wrote:
On Wed, Sep 03, 2025 at 02:31:55PM +0100, Bryan O'Donoghue wrote:
On 03/09/2025 12:56, Konrad Dybcio wrote:
Can you try with this next-20250814 tag ?
You sent it on the 19th, so it's in your best interest to run a quick
git rebase --
On Wed, Sep 03, 2025 at 02:31:55PM +0100, Bryan O'Donoghue wrote:
> On 03/09/2025 12:56, Konrad Dybcio wrote:
> > > Can you try with this next-20250814 tag ?
> > You sent it on the 19th, so it's in your best interest to run a quick
> >
> > git rebase
On 03/09/2025 12:56, Konrad Dybcio wrote:
Can you try with this next-20250814 tag ?
You sent it on the 19th, so it's in your best interest to run a quick
git rebase --onto linux-next/master $(git describe --abbrev=0)
and giving the series a prompt re-test before sending, because there
ement of Secure Peripheral Image
>>> Loader support on Qualcomm SoCs when Linux runs at EL2.
>>>
>>> A few months ago, we also discussed the challenges at Linaro Connect
>>> 2025 [2] related to enabling remoteproc when Linux is running at EL2.
>>>
>>>
This is the 9th version of the virtio SPI Linux driver patch series which is
intended to be compliant with the upcoming virtio specification
version 1.4. The specification can be found in repository:
https://github.com/oasis-tcs/virtio-spec.git branch virtio-1.4.
The original contributor Harald
erf build warnings:
>
> Warning: Kernel ABI header differences:
> diff -u tools/perf/trace/beauty/include/uapi/linux/vhost.h
> include/uapi/linux/vhost.h
>
> Please see tools/include/uapi/README for further details.
>
> Cc: "Michael S. Tsirkin"
> Cc: J
/include/uapi/linux/vhost.h
include/uapi/linux/vhost.h
Please see tools/include/uapi/README for further details.
Cc: "Michael S. Tsirkin"
Cc: Jason Wang
Cc: k...@vger.kernel.org
Cc: virtualizat...@lists.linux.dev
Signed-off-by: Namhyung Kim
---
* This is on top of the fix belo
?
> > > > > >
> > > > >
> > > > > Sorry, I missed the fact that the "video-firmware" subnode is already
> > > > > documented for iris as well through qcom,venus-common.yaml (which is
> > > > > included for qco
> > > > included for qcom,sm8550-iris). I don't think it's strictly required to
> > > > add every possibility to the examples of the schema, since we'll also
> > > > have the actual DTBs later to test this part of the schema.
> > > >
>
On 23/08/2025 17:46, Krzysztof Kozlowski wrote:
> On 23/08/2025 17:41, Krzysztof Kozlowski wrote:
>> On 22/08/2025 17:13, Mukesh Ojha wrote:
>>> On Fri, Aug 22, 2025 at 10:45:50AM +0200, Krzysztof Kozlowski wrote:
On 19/08/2025 18:54, Mukesh Ojha wrote:
> +int iris_fw_init(struct iris_core
On 23/08/2025 17:41, Krzysztof Kozlowski wrote:
> On 22/08/2025 17:13, Mukesh Ojha wrote:
>> On Fri, Aug 22, 2025 at 10:45:50AM +0200, Krzysztof Kozlowski wrote:
>>> On 19/08/2025 18:54, Mukesh Ojha wrote:
+int iris_fw_init(struct iris_core *core)
+{
+ struct platform_device_info in
On 22/08/2025 17:13, Mukesh Ojha wrote:
> On Fri, Aug 22, 2025 at 10:45:50AM +0200, Krzysztof Kozlowski wrote:
>> On 19/08/2025 18:54, Mukesh Ojha wrote:
>>> +int iris_fw_init(struct iris_core *core)
>>> +{
>>> + struct platform_device_info info;
>>> + struct iommu_domain *iommu_dom;
>>> + st
ris). I don't think it's strictly required to
> > > add every possibility to the examples of the schema, since we'll also
> > > have the actual DTBs later to test this part of the schema.
> > >
> > > I would recommend to extend the desc
or iris as well through qcom,venus-common.yaml (which is
> > included for qcom,sm8550-iris). I don't think it's strictly required to
> > add every possibility to the examples of the schema, since we'll also
> > have the actual DTBs later to test this part of the sch
On Fri, Aug 22, 2025 at 10:45:50AM +0200, Krzysztof Kozlowski wrote:
> On 19/08/2025 18:54, Mukesh Ojha wrote:
> > +int iris_fw_init(struct iris_core *core)
> > +{
> > + struct platform_device_info info;
> > + struct iommu_domain *iommu_dom;
> > + struct platform_device *pdev;
> > + struct
actual DTBs later to test this part of the schema.
>
> I would recommend to extend the description of the "video-firmware" node
> in qcom,venus-common.yaml a bit. You do use the reset functionality of
> TrustZone, so the description there doesn't fit for your use ca
strictly required to
add every possibility to the examples of the schema, since we'll also
have the actual DTBs later to test this part of the schema.
I would recommend to extend the description of the "video-firmware" node
in qcom,venus-common.yaml a bit. You do use the reset functionali
On 19/08/2025 18:54, Mukesh Ojha wrote:
> +int iris_fw_init(struct iris_core *core)
> +{
> + struct platform_device_info info;
> + struct iommu_domain *iommu_dom;
> + struct platform_device *pdev;
> + struct device_node *np;
> + int ret;
> +
> + np = of_get_child_by_name(cor
t; always need to come before the driver changes.
Do you mean to update the examples section[1] with the firmware subnode,
something similar to venus schema[2] ?
Regards,
Vikash
[1]
https://elixir.bootlin.com/linux/v6.17-rc2/source/Documentation/devicetree/bindings/media/qcom,sm8550-iris.yaml#L109
[2]
https://elixir.bootlin.com/linux/v6.17-rc2/source/Documentation/devicetree/bindings/media/qcom,sc7280-venus.yaml#L128
t; >
> > > Support for handling IOMMU and SHM setup in the absence of a hypervisor
> > > is now in place. Extend the Iris driver to enable this functionality on
> > > platforms where IOMMU is managed by Linux (i.e., non-Gunyah, non-QHEE).
> > >
> >
roc metadata and
> > its memory regions.
> >
> > When the aforementioned hypervisor is absent, the operating system must
> > perform these configurations instead.
> >
> > When Linux runs as the hypervisor (at EL2) on a SoC, it will have its
> > own device
nd its memory
> > regions.
> >
> > When the hypervisor is absent, the operating system must perform these
> > configurations instead.
> >
> > Support for handling IOMMU and SHM setup in the absence of a hypervisor
> > is now in place. Extend the Iris dri
tend the Iris driver to enable this functionality on
> > platforms where IOMMU is managed by Linux (i.e., non-Gunyah, non-QHEE).
> >
> > Additionally, the Iris driver must map the firmware and its required
> > resources to the firmware SID, which is now specified via the device tre
handling IOMMU and SHM setup in the absence of a hypervisor
is now in place. Extend the Iris driver to enable this functionality on
platforms where IOMMU is managed by Linux (i.e., non-Gunyah, non-QHEE).
Additionally, the Iris driver must map the firmware and its required
resources to the firmware SID
On Wed, Aug 20, 2025 at 12:03:16PM +0100, Bryan O'Donoghue wrote:
> On 19/08/2025 17:54, Mukesh Ojha wrote:
> > This is a further continuation with a new approach to the topic
> > discussed in [1] regarding the enablement of Secure Peripheral Image
> > Loader support o
On 19/08/2025 17:54, Mukesh Ojha wrote:
This is a further continuation with a new approach to the topic
discussed in [1] regarding the enablement of Secure Peripheral Image
Loader support on Qualcomm SoCs when Linux runs at EL2.
A few months ago, we also discussed the challenges at Linaro
g system must perform these
> configurations instead.
>
> Support for handling IOMMU and SHM setup in the absence of a hypervisor
> is now in place. Extend the Iris driver to enable this functionality on
> platforms where IOMMU is managed by Linux (i.e., non-Gunyah, non-QHEE).
>
, the operating system must
> perform these configurations instead.
>
> When Linux runs as the hypervisor (at EL2) on a SoC, it will have its
> own device tree overlay file that specifies the firmware stream ID now
> managed by Linux for a particular remote processor. If the iommus
> p
removed during teardown. Additionally, SHM bridge setup is
required to enable memory protection for both remoteproc metadata and
its memory regions.
When the aforementioned hypervisor is absent, the operating system must
perform these configurations instead.
When Linux runs as the hypervisor (at EL2
a hypervisor
is now in place. Extend the Iris driver to enable this functionality on
platforms where IOMMU is managed by Linux (i.e., non-Gunyah, non-QHEE).
Additionally, the Iris driver must map the firmware and its required
resources to the firmware SID, which is now specified via the device tree
This is a further continuation with a new approach to the topic
discussed in [1] regarding the enablement of Secure Peripheral Image
Loader support on Qualcomm SoCs when Linux runs at EL2.
A few months ago, we also discussed the challenges at Linaro Connect
2025 [2] related to enabling remoteproc
The pull request you sent on Mon, 28 Jul 2025 17:13:48 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux_kselftest-next-6.17-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0db240bc077fd16cc16bcecfd7f4645bc474aa7e
Tha
The pull request you sent on Mon, 28 Jul 2025 14:40:00 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux_kselftest-kunit-6.17-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6f46e6fb4e267acf8741cb2c29d368b4de7b6c15
he following patch.
> --
>commit 7918bb2d19c9 ("vhost: basic in order support")
> https://git.kernel.org/pub/scm/linux/kernel/git/
Hi Linus,
Please pull this kselftest next update for Linux 6.17-rc1.
Fixes
- false failure of subsystem event test
- glob filter test to use mutex_unlock() instead of mutex_trylock()
- several spelling errors in tests
- test_kexec_jump build errors
- pidfd test duplicate-symbol warnings for
vhost: basic in order support")
https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git/commit/?id=7918bb2d19c9
--
This patch landed in linux-next between July 16th and 1
Hi Linus,
Please pull the following kunit next update for Linux 6.17-rc1.
Corrects MODULE_IMPORT_NS() syntax documentation, makes kunit_test timeout
configurable via a module parameter and a Kconfig option, fixes longest
symbol length test, adds a test for static stub, and adjusts kunit_test
Replace instances of "__auto_type" with "auto" in include/linux.
Signed-off-by: H. Peter Anvin (Intel)
---
include/linux/cleanup.h | 6 +++---
include/linux/compiler.h | 2 +-
include/linux/minmax.h | 6 +++---
3 files changed, 7 insertions(+), 7 deletions(-)
diff -
Replace instances of "__auto_type" with "auto" in include/linux.
Signed-off-by: H. Peter Anvin (Intel)
---
include/linux/cleanup.h | 4 ++--
include/linux/compiler.h | 2 +-
include/linux/minmax.h | 6 +++---
3 files changed, 6 insertions(+), 6 deletions(-)
diff -
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski :
On Fri, 27 Jun 2025 20:04:51 + you wrote:
> linux/version.h was used by the out-of-tree version, but not needed in
> the upstream one anymore.
>
> While I'm at it, sort the includes.
>
&
On 27/06/2025 22.04, Mina Almasry wrote:
linux/version.h was used by the out-of-tree version, but not needed in
the upstream one anymore.
While I'm at it, sort the includes.
Reported-by: kernel test robot
Closes:
https://lore.kernel.org/oe-kbuild-all/202506271434.gk0epc9h-...@inte
On Fri, 27 Jun 2025 at 23:05, Mina Almasry wrote:
>
> linux/version.h was used by the out-of-tree version, but not needed in
> the upstream one anymore.
>
> While I'm at it, sort the includes.
>
> Reported-by: kernel test robot
> Closes:
> https://lore.kerne
Mina Almasry writes:
> linux/version.h was used by the out-of-tree version, but not needed in
> the upstream one anymore.
>
> While I'm at it, sort the includes.
>
> Reported-by: kernel test robot
> Closes:
> https://lore.kernel.org/oe-kbuild-all/202506271434.gk0
On Fri, Jun 27, 2025 at 08:04:51PM +, Mina Almasry wrote:
> linux/version.h was used by the out-of-tree version, but not needed in
> the upstream one anymore.
>
> While I'm at it, sort the includes.
>
> Reported-by: kernel test robot
> Closes:
> https://
linux/version.h was used by the out-of-tree version, but not needed in
the upstream one anymore.
While I'm at it, sort the includes.
Reported-by: kernel test robot
Closes:
https://lore.kernel.org/oe-kbuild-all/202506271434.gk0epc9h-...@intel.com/
Signed-off-by: Mina Almasry
---
.../self
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski :
On Mon, 23 Jun 2025 12:00:53 +0200 you wrote:
> From: Stefano Garzarella
>
> If a userspace application just include will fail
> to build with the following errors:
>
> /usr/include/linux/v
From: Stefano Garzarella
If a userspace application just include will fail
to build with the following errors:
/usr/include/linux/vm_sockets.h:182:39: error: invalid application of
‘sizeof’ to incomplete type ‘struct sockaddr’
182 | unsigned char svm_zero[sizeof(struct
The header is unused. Furthermore this is not a real UAPI header,
but only exists in tools/include/.
This prevents building the selftest against real UAPI headers.
Drop the include.
Signed-off-by: Thomas Weißschuh
---
tools/testing/selftests/vDSO/vdso_test_getrandom.c | 1 -
1 file changed, 1 d
Hi Linus,
Please pull the following kselftest next update for Linux 6.16-rc1.
-- Fixes
- cpufreq test to not double suspend in rtcwake case.
- compile error in pid_namespace test.
- run_kselftest.sh to use readlink if realpath is not available.
- cpufreq basic read and update
Hi Linus,
Please pull the following kunit next update for Linux 6.16-rc1.
- Enables qemu_config for riscv32, sparc 64-bit, PowerPC 32-bit BE and
64-bit LE.
- Enables CONFIG_SPARC32 to clearly differentiate between sparc 32-bit
and 64-bit configurations.
- Enables CONFIG_CPU_BIG_ENDIAN to
> From: Sean Christopherson
> Sent: Saturday, May 17, 2025 7:08 AM
>
> Pass in the Linux IRQ associated with an IRQ bypass producer instead of
> relying on the caller to set the field prior to registration, as there's
> no benefit to relying on callers to do the right t
Pass in the Linux IRQ associated with an IRQ bypass producer instead of
relying on the caller to set the field prior to registration, as there's
no benefit to relying on callers to do the right thing.
Take care to set producer->irq before __connect(), as KVM expects the IRQ
to be valid as
2025 at 11:26:34AM -0700, Paul E. McKenney wrote:
> > > > On Wed, May 14, 2025 at 10:47:30AM +0800, kernel test robot wrote:
> > > > >
> > > > > hi, Paul,
> > > > >
> > > > > for this commit we tested before, now we found it ca
:30AM +0800, kernel test robot wrote:
> > > >
> > > > hi, Paul,
> > > >
> > > > for this commit we tested before, now we found it causes issues in
> > > > linux-next
> > > > master branch.
> > >
> > > Good c
> for this commit we tested before, now we found it causes issues in
> > > linux-next
> > > master branch.
> >
> > Good catch as always!!! Yes, using HRTIMER_MODE_HARD means that this
> > ircutorture_one_extend_check() function must check for hardirq as well
hi, Paul,
On Wed, May 14, 2025 at 11:26:34AM -0700, Paul E. McKenney wrote:
> On Wed, May 14, 2025 at 10:47:30AM +0800, kernel test robot wrote:
> >
> > hi, Paul,
> >
> > for this commit we tested before, now we found it causes issues in
> > linux-next
>
On Wed, May 14, 2025 at 10:47:30AM +0800, kernel test robot wrote:
>
> hi, Paul,
>
> for this commit we tested before, now we found it causes issues in linux-next
> master branch.
Good catch as always!!! Yes, using HRTIMER_MODE_HARD means that this
ircutorture_one_extend_check(
The header is unused. Furthermore this is not a real UAPI header,
but only exists in tools/include/.
This prevents building the selftest against real UAPI headers.
Drop the include.
Signed-off-by: Thomas Weißschuh
---
tools/testing/selftests/vDSO/vdso_test_getrandom.c | 1 -
1 file changed, 1 d
The header is unused. Furthermore this is not a real UAPI header,
but only exists in tools/include/.
This prevents building the selftest against real UAPI headers.
Drop the include.
Signed-off-by: Thomas Weißschuh
---
tools/testing/selftests/vDSO/vdso_test_getrandom.c | 1 -
1 file changed, 1 d
The pull request you sent on Fri, 18 Apr 2025 11:36:35 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux_kselftest-kunit-fixes-6.15-rc3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7f424c6690df7a5e807548371b9546d515
The pull request you sent on Fri, 18 Apr 2025 11:23:27 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux_kselftest-fixes-6.15-rc3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/338d40ceef38d9a36b48164e22768b40d6f89701
Hi Linus,
Please pull the following kunit fixes update for Linux 6.15-rc3.
Fixes arch sh kunit qemu_configs script sh.py to honor kunit cmdline.
diff is attached.
thanks,
-- Shuah
The following changes since commit
Hi Linus,
Please pull the following kselftest fixes update for Linux 6.15-rc3.
Fixes dynevent_limitations.tc test failure on dash by detecting and
handling bash and dash differences in evaluating \\.
diff is attached.
thanks,
-- Shuah
The pull request you sent on Wed, 9 Apr 2025 16:13:39 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux_kselftest-fixes-6.15-rc2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/3b07108ada81a8ebcebf1fe61367b4e436c895bd
Tha
Hi Linus,
Please pull the following kselftest fixes update for Linux 6.15-rc2
Fixes tpm2, futex, and mincore tests. Creates a dedicated .gitignore
for tpm2
Details:
selftests: tpm2: test_smoke: use POSIX-conformant expression operator
selftests/futex: futex_waitv wouldblock test should fail
Hi Linus,
Please pull the following kunit fixes update for Linux 6.15-rc2
Fixes tool to report test count in case of a late test plan when tests
are specified before the test plan. Fixes spelling error in the commit
that went into 6.15-rc1.
diff is attached.
thanks,
-- Shuah
The pull request you sent on Tue, 8 Apr 2025 16:31:50 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux_kselftest-kunit-6.15-rc2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/a24588245776dafc227243a01bfbeb8a59bafba9
Tha
cant performance regression in KVM guest VMs
> > > using virtio-net with recent Linux kernels (6.8.1+ and 6.14).
> > >
> > > When running on a host system equipped with a Broadcom NetXtreme-E
> > > (bnxt_en) NIC and AMD EPYC CPUs, the network throughput
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).
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
to have a look:
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098961
>
> We're seeing lots of those in dmesg output:
>
> [ 561.505323] net_ratelimit: 1396 callbacks suppressed
> [ 561.505339] ens18: bad gso: type: 4, size: 1448
> [ 561.505343] ens18: bad
g, 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,
>>>
gt; > > > > > Tsirkin:
> > > > > >
> > > > > > > On Wed, Apr 02, 2025 at 11:12:07PM +0200, Markus Fohrer wrote:
> > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > &
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).
> > > >
> > > > When r
rer 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,
>>>>>>>
>>>>>&g
; > > > > > wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > I'm observing a significant performance regression in KVM
> > > > > > > guest
> > > > > > > VMs
> > > >
> >
> > > > > > I'm observing a significant performance regression in KVM
> > > > > > guest
> > > > > > VMs
> > > > > > using virtio-net with recent Linux kernels (6.8.1+ and
> > > > > > 6.14).
> >
gt; wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > I'm observing a significant performance regression in KVM
> > > > > > > guest
> > > > > > > VMs
> > > > > > &g
+0200, Markus Fohrer
> > > > > > wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > I'm observing a significant performance regression in KVM
> > > > > > > guest
> > > >
> 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 w
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 regress
l 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
> > > > >
um 09:04 -0400 schrieb
> > > > > > Michael S.
> > > > > > Tsirkin:
> > > > > > > On Wed, Apr 02, 2025 at 11:12:07PM +0200, Markus Fohrer
> > > > > > > wrote:
> > > > > > > > Hi,
> > > &
cant performance regression in KVM guest VMs
> > > using virtio-net with recent Linux kernels (6.8.1+ and 6.14).
> > >
> > > When running on a host system equipped with a Broadcom NetXtreme-E
> > > (bnxt_en) NIC and AMD EPYC CPUs, the network throughput
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 recen
0 MB/s) when using kernel 6.8.0 or when the VM is moved to a host
> with Intel NICs.
Hi,
as I am affected too, here is the link to the Ubuntu issue, just in
case someone wants to have a look:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098961
We're seeing lots of t
; > >
> > > > I'm observing a significant performance regression in KVM guest VMs
> > > > using virtio-net with recent Linux kernels (6.8.1+ and 6.14).
> > > >
> > > > When running on a host system equipped with a Broadcom NetXtreme-E
>
1 - 100 of 45071 matches
Mail list logo
