[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2025-04-18 Thread Jürg Häfliger
** Tags added: kernel-daily-bug

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-11-29 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-gcp-tcpx/6.8.0-1002.3
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gcp-tcpx' to 'verification-done-
jammy-linux-gcp-tcpx'. If the problem still exists, change the tag
'verification-needed-jammy-linux-gcp-tcpx' to 'verification-failed-
jammy-linux-gcp-tcpx'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-gcp-tcpx-v2 
verification-needed-jammy-linux-gcp-tcpx

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-11-25 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-gkeop/6.8.0-1002.4
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-gkeop' to 'verification-done-noble-
linux-gkeop'. If the problem still exists, change the tag 'verification-
needed-noble-linux-gkeop' to 'verification-failed-noble-linux-gkeop'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-noble-linux-gkeop-v2 
verification-needed-noble-linux-gkeop

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-10-30 Thread Frank Heimes
** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-10-30 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.8.0-48.48

---
linux (6.8.0-48.48) noble; urgency=medium

  * noble/linux: 6.8.0-48.48 -proposed tracker (LP: #2082437)

  * [SRU][Noble] Bad EPP defaults cause performance regressions on select Intel
CPUs (LP: #2077470)
- x86/cpu/vfm: Update arch/x86/include/asm/intel-family.h
- cpufreq: intel_pstate: Allow model specific EPPs
- cpufreq: intel_pstate: Update default EPPs for Meteor Lake
- cpufreq: intel_pstate: Switch to new Intel CPU model defines
- cpufreq: intel_pstate: Update Meteor Lake EPPs
- cpufreq: intel_pstate: Use Meteor Lake EPPs for Arrow Lake
- cpufreq: intel_pstate: Update Balance performance EPP for Emerald Rapids

  * power: Enable intel_rapl driver (LP: #2078834)
- powercap: intel_rapl: Add support for ArrowLake-H platform

  * x86/vmware: Add TDX hypercall support (LP: #2077729)
- x86/vmware: Introduce VMware hypercall API
- x86/vmware: Add TDX hypercall support

  * Guest crashes post migration with migrate_misplaced_folio+0x4cc/0x5d0
(LP: #2076866)
- mm/mempolicy: use numa_node_id() instead of cpu_to_node()
- mm/numa_balancing: allow migrate on protnone reference with
  MPOL_PREFERRED_MANY policy
- mm: convert folio_estimated_sharers() to folio_likely_mapped_shared()
- mm: factor out the numa mapping rebuilding into a new helper
- mm: support multi-size THP numa balancing
- mm/migrate: make migrate_misplaced_folio() return 0 on success
- mm/migrate: move NUMA hinting fault folio isolation + checks under PTL
- mm: fix possible OOB in numa_rebuild_large_mapping()

  * Add 'mm: hold PTL from the first PTE while reclaiming a large folio' to fix
L2 Guest hang during LTP Test (LP: #2076147)
- mm: hold PTL from the first PTE while reclaiming a large folio

  * KOP L2 guest fails to boot with 1 core - SMT8 topology (LP: #2070329)
- KVM: PPC: Book3S HV nestedv2: Add DPDES support in helper library for 
Guest
  state buffer
- KVM: PPC: Book3S HV nestedv2: Fix doorbell emulation

  * L2 Guest migration: continuously dumping while running NFS guest migration
(LP: #2076406)
- KVM: PPC: Book3S HV: Fix the set_one_reg for MMCR3
- KVM: PPC: Book3S HV: Fix the get_one_reg of SDAR
- KVM: PPC: Book3S HV: Add one-reg interface for DEXCR register
- KVM: PPC: Book3S HV nestedv2: Keep nested guest DEXCR in sync
- KVM: PPC: Book3S HV: Add one-reg interface for HASHKEYR register
- KVM: PPC: Book3S HV nestedv2: Keep nested guest HASHKEYR in sync
- KVM: PPC: Book3S HV: Add one-reg interface for HASHPKEYR register
- KVM: PPC: Book3S HV nestedv2: Keep nested guest HASHPKEYR in sync

  * perf build disables tracepoint support (LP: #2076190)
- [Packaging] perf: reenable libtraceevent

  * Please backport the more restrictive XSAVES deactivation for  Zen1/2 arch
(LP: #2077321)
- x86/CPU/AMD: Improve the erratum 1386 workaround

  * Fix alsa scarlett2 driver in 6.8  (LP: #2076402)
- ALSA: scarlett2: Move initialisation code lower in the source
- ALSA: scarlett2: Implement handling of the ACK notification

  * rtw89: reset IDMEM mode to prevent download firmware failure (LP: #2077396)
- wifi: rtw89: 885xb: reset IDMEM mode to prevent download firmware failure

  * CVE-2024-43858
- jfs: Fix array-index-out-of-bounds in diFree

  * CVE-2024-42280
- mISDN: Fix a use after free in hfcmulti_tx()

  * CVE-2024-42271
- net/iucv: fix use after free in iucv_sock_close()

  * [Ubuntu-24.04] FADump with recommended crash size is making the L1 hang
(LP: #2060039)
- powerpc/64s/radix/kfence: map __kfence_pool at page granularity

  * Noble update: upstream stable patchset 2024-09-09 (LP: #2079945)
- ocfs2: add bounds checking to ocfs2_check_dir_entry()
- jfs: don't walk off the end of ealist
- fs/ntfs3: Add a check for attr_names and oatbl
- fs/ntfs3: Validate ff offset
- usb: gadget: midi2: Fix incorrect default MIDI2 protocol setup
- ALSA: hda/realtek: Enable headset mic on Positivo SU C1400
- ALSA: hda/realtek: Fix the speaker output on Samsung Galaxy Book Pro 360
- arm64: dts: qcom: qrb4210-rb2: switch I2C2 to i2c-gpio
- arm64: dts: qcom: msm8996: Disable SS instance in Parkmode for USB
- arm64: dts: qcom: sm6350: Disable SS instance in Parkmode for USB
- arm64: dts: qcom: ipq6018: Disable SS instance in Parkmode for USB
- arm64: dts: qcom: sdm630: Disable SS instance in Parkmode for USB
- ALSA: pcm_dmaengine: Don't synchronize DMA channel when DMA is paused
- ALSA: seq: ump: Skip useless ports for static blocks
- filelock: Fix fcntl/close race recovery compat path
- tun: add missing verification for short frame
- tap: add missing verification for short frame
- s390/mm: Fix VM_FAULT_HWPOISON handling in do_exception()
- ALSA: hda/tas2781: Add new quirk for Lenovo Hera2 Laptop
- arm64: dts: qcom: sc7180: Disable S

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-10-17 Thread Frank Heimes
No, no need for further verification, that was already done, see:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2070329/comments/10
and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2070329/comments/11

(just this tag 'verification-needed-noble-linux' is the relevant one for
us here - the others are 'spam' from the tooling)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-10-17 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If the problem still exists, change the tag
'verification-needed-noble-linux-xilinx' to 'verification-failed-noble-
linux-xilinx'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-noble-linux-xilinx-v2 
verification-needed-noble-linux-xilinx

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-10-15 Thread Frank Heimes
Man thanks Gautam for the successful verification!
(I'm updating the tags accordingly ...)

** Tags removed: verification-needed-noble-linux
** Tags added: verification-done-noble-linux

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-10-12 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
oracle-6.8' to 'verification-done-jammy-linux-oracle-6.8'. If the
problem still exists, change the tag 'verification-needed-jammy-linux-
oracle-6.8' to 'verification-failed-jammy-linux-oracle-6.8'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-oracle-6.8-v2 
verification-needed-jammy-linux-oracle-6.8

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-10-12 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
aws-6.8' to 'verification-done-jammy-linux-aws-6.8'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-aws-6.8'
to 'verification-failed-jammy-linux-aws-6.8'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-aws-6.8-v2 
verification-needed-jammy-linux-aws-6.8

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-10-01 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux/6.8.0-48.48 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-noble-linux' to 'verification-done-noble-linux'. If
the problem still exists, change the tag 'verification-needed-noble-
linux' to 'verification-failed-noble-linux'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-noble-linux-v2 verification-needed-noble-linux

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-09-26 Thread Stefan Bader
** Changed in: linux (Ubuntu Noble)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Noble)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-09-26 Thread Frank Heimes
** Changed in: ubuntu-power-systems
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-09-26 Thread Frank Heimes


-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-09-24 Thread Timo Aaltonen
** Changed in: linux (Ubuntu Oracular)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-09-02 Thread Frank Heimes
Pull request submitted to kernel team's mailing list:
https://lists.ubuntu.com/archives/kernel-team/2024-September/thread.html#153260
changing status to 'In Progress', assigning kernel team.

** Changed in: linux (Ubuntu Noble)
   Status: Confirmed => In Progress

** Changed in: ubuntu-power-systems
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Noble)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-09-02 Thread Frank Heimes
A test kernel is currently being build in this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp2070329

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-08-30 Thread Frank Heimes
** Description changed:

+ SRU Justification:
+ 
+ [ Impact ]
+ 
+  * On a P10 system with SMT-8 configured
+a level 2 guest (VM) fails to boot in case
+it only has one core assigned.
+ 
+ [ Test Plan ]
+ 
+  * Setup an IBM Power 10 system - that support up to SMT-8
+and with firmware 1060, that offers support for KVM -
+using Ubuntu Server 24.04 for ppc64el.
+ 
+  * Setup qemu/KVM on this system.
+ 
+  * Configure a KVM guest (e.g. using virtinst or
+qemu-system-ppc64 directly) now with smt-8,
+but only one virtual CPU.
+ 
+  * Try to boot this specific guest:
+qemu-system-ppc64 \
+   -drive file=rhel.qcow2,format=qcow2 \
+   -m 20G \
+   -smp 8,cores=1,threads=8 \
+   -cpu  host \
+   -nographic \
+   -machine pseries,ic-mode=xics -accel kvm
+ 
+  * It will fail to boot with a kernel that does not
+have the two patches in place.
+ 
+  * Since this setup requires a special firmware level,
+the verification will be done by the IBM Power team.
+ 
+ [ Where problems could occur ]
+ 
+  * Primarily support for using DPDES (register) is required,
+since its needed for enabling usage of doorbells in L2 gusts.
+This is mainly done by adding DEFINEs, stubs and case.
+If the definitions are not correct or if the code executed by
+the new case (KVMPPC_GSID_DPDES) is done wrong,
+the guest state could be incorrect, harming the L2 guest doorbell.
+(DPDES is to provide the means for the hypervisor to save a
+ [sub-]processor's Directed Privileged Doorbell exception state
+ when the set of programs running on the [sub-]processor is
+ swapped out or moved from one [sub-]processor to another.)
+ 
+  * The missing Doorbell emulation got added by a 4 line if statement
+in powerpc/kvm/book3s_hv.c, which is relatively traceable.
+ 
+  * The main issue I can think of is that kvmppc_set_dpdes is called
+with wrong arguments.
+ 
+  * And kvmppc_set_dpdes will not work (at all) if the above DPDES
+support (and commit/patch) is missing.
+ 
+ [ Other Info ]
+ 
+  * Since (nested) KVM support is new on P10,
+this does not affect older Power generation
+(P9 is the only other hw generation that is supported by 24.04,
+but it only supports native virtualization).
+ 
+  * Both patches are upstream accepted since v6.11(-rc1),
+hence will be in oracular
+and are also upstream tagged as stable updates.
+ 
+  * Since the required firmware FW1060 is relatively new,
+we can assume that not many user ran into this issue yet.
+ __
+ 
  == Comment: #0 - SEETEENA THOUFEEK  - 2024-06-25 
01:24:11 ==
  +++ This bug was initially created as a clone of Bug #205277 +++
  
  ---Problem Description---
  KOP L2 guest fails to boot with 1 core - SMT8 topology
-  
+ 
  ---Additional Hardware Info---
- na 
+ na
  
-  
  ---Debugger Data---
- na 
-  
+ na
+ 
  ---Steps to Reproduce---
-  KOP L2 guest fails to boot when we set the CPU topology as 1 core - SMT 8
+  KOP L2 guest fails to boot when we set the CPU topology as 1 core - SMT 8
  
  command line used to verify the issue:
  #!/bin/sh
  
  QEMU="/home/mgautam/qemu"
  qemu-system-ppc64 -s \
  -drive file=/root/debian-12-nocloud-ppc64el.qcow2,format=qcow2 \
  -m 20G \
  -smp 8,cores=1,sockets=1,threads=8 \
  -cpu host \
  -nographic \
  -machine pseries,ic-mode=xics -accel kvm  \
  -net nic,model=virtio \
  -net user,host=10.0.2.10,hostfwd=tcp:127.0.0.1:10022-:22
  
- 
  NOTE: L2 boots fine when doorbells are turned off in L1 kernel
  
- 
- As per the investigation so far, the doorbell exception is not getting fired 
inside L2 guest. At L1 level, if we set DPDES=1 in the GSB for L2, the guest 
never receives the doorbell and also it is never cleared from the GSB. We are 
discussing this behaviour with phyp team.
+ As per the investigation so far, the doorbell exception is not getting
+ fired inside L2 guest. At L1 level, if we set DPDES=1 in the GSB for L2,
+ the guest never receives the doorbell and also it is never cleared from
+ the GSB. We are discussing this behaviour with phyp team.
  
  The root cause of this issue is lack of DPDES support at L1. I've posted
  the fix upstream - https://lore.kernel.org/linuxppc-
  dev/20240522084949.123148-1-gau...@linux.ibm.com/T/#u
  
+ The fix has been accepted upstream and will be backported for kernels >=
+ 6.7
  
- The fix has been accepted upstream and will be backported for kernels >= 6.7
+ https://lore.kernel.org/linuxppc-
+ dev/20240605113913.83715-1-gau...@linux.ibm.com/
  
- 
https://lore.kernel.org/linuxppc-dev/20240605113913.83715-1-gau...@linux.ibm.com/
-  
  ---Patches Installed---
  na
-  
+ 
  ---System Hang---
-  na
-  
+  na
+ 
  ---uname output---
  na
-  
- Contact Information = na 
-  
- Machine Type = na 
  
- Userspace rpm: na 
-  
- Userspace tool common name: na 
-  
- The userspace tool has the following bit modes: na 
+ Contact Information = na
  
- Userspace tool obtained from project website:  n

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-08-27 Thread Frank Heimes
** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Oracular)
   Importance: High
   Status: Confirmed

** Changed in: linux (Ubuntu Noble)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Oracular)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology

2024-06-25 Thread Frank Heimes
Looks like the names changed slightly, thanks for pointing the the right
upstream commits!

And I see that they are marked as stable updates ("Cc: sta...@vger.kernel.org # 
v6.7+"), which is great!
With that they will be soon automatically be picked up by the Canonical kernel 
team.

** Changed in: ubuntu-power-systems
   Status: New => Confirmed

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology (Fedora)

2024-06-25 Thread Frank Heimes
Hello and thanks for having reported this issue.

Once the patch set 'Fix doorbell emulation for v2 API on PPC' with patches:
- arch/powerpc/kvm: Add DPDES support in helper library for Guest state buffer
- arch/powerpc/kvm: Fix doorbell emulation for v2 API
are upstream accepted (having them in 'linux-next' is sufficient), we can think 
about picking them.
I cannot find them in 'linux-next' yet 
(https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/?qt=grep&q=Fix+doorbell+emulation+for+v2+API),
 but assume they are still part of a staging tree and will hit linux-next soon.

Based on your statement "The fix has been accepted upstream and will be 
backported for kernels >= 6.7" I assume the patch(es) are (or will be soon) 
also upstream marked as "stable updates", and will then land in kernel 6.8 
(that we have in 24.04).
As soon as this happens, the "stable updates" for 6.8 will be picked by the 
Canonical kernel team automatically.

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
(unassigned)

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

** Summary changed:

- KOP L2 guest fails to boot with 1 core - SMT8 topology (Fedora)
+ KOP L2 guest fails to boot with 1 core - SMT8 topology

** Changed in: ubuntu-power-systems
   Importance: Undecided => High

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070329

Title:
  KOP L2 guest fails to boot with 1 core - SMT8 topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs