From: "Cédric Le Goater" <clg@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-devel@nongnu.org,
Alex Williamson <alex.williamson@redhat.com>,
Harsh Prateek Bora <harshpb@linux.ibm.com>,
Tony Krowiak <akrowiak@linux.ibm.com>,
Eric Farman <farman@linux.ibm.com>,
Eric Auger <eric.auger@redhat.com>
Subject: Re: [PATCH 1/2] vfio: Make vfio-pci available on 64-bit host platforms only
Date: Mon, 3 Mar 2025 19:11:19 +0100 [thread overview]
Message-ID: <9c9232f1-73f8-40ec-9064-a0df3f2e15cf@redhat.com> (raw)
In-Reply-To: <bb7c2adf-f146-50c7-7716-c1ee7b606b01@eik.bme.hu>
>>> I see PPC is defined in target/ppc/Kconfig so I think these mark the target not the host. Vfio-pci works with qemu-system-ppc
>>
>> Ah ! I am surprised. Which host and QEMU machine please ?
>
> I've seen people do this on x86_64 host with pegasos2, amigaone and mac99 running 32 bit guests (AmigaOS and MacOS). Some people running older 32 bit Windows versions on pc machine might also use this.
I tried with :
qemu-system-ppc -m 1G -smp 1 -M mac99,via=pmu -cpu g4 ....
There are some errors/warnings:
qemu-system-ppc: -device vfio-pci,host=0000:0c:00.0: warning: MSI-X is not supported by interrupt controller
Cannot manage 'ethernet controller' PCI device type 'network':
>>
>> 8086 10c9 (2 0 0)
>> set_property: NULL phandle
>> =============================================================
>> OpenBIOS 1.1 [Sep 24 2024 19:56]
...
but it does work :
root@debian-powerpc:~# uname -a
Linux debian-powerpc 6.1.0-7-powerpc #1 Debian 6.1.20-1 (2023-03-19) ppc GNU/Linux
root@debian-powerpc:~# lspci -s 00:10.0 -vv
00:10.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
Subsystem: Beijing Sinead Technology Co., Ltd. 82576 Gigabit Network Connection
Device tree node: /sys/firmware/devicetree/base/pci@f2000000/pci8086,10c9@10
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 27
Region 0: Memory at 82080000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at 82400000 (32-bit, non-prefetchable) [size=4M]
Region 2: I/O ports at 1080 [size=32]
Region 3: Memory at 82800000 (32-bit, non-prefetchable) [size=16K]
Expansion ROM at 82c00000 [disabled] [size=4M]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [a0] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0W
DevCtl: CorrErr- NonFatalErr- FatalErr+ UnsupReq-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset-
MaxPayload 256 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x4, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us
ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1 (downgraded)
TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- LTR-
10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
FRS- TPHComp- ExtTPHComp-
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 16ms to 55ms, TimeoutDis- LTR- 10BitTagReq- OBFF Disabled,
AtomicOpsCtl: ReqEn-
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1-
EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
Retimer- 2Retimers- CrosslinkRes: unsupported
Kernel driver in use: igb
Kernel modules: igb
root@debian-powerpc:~# ip link show dev enp0s16
2: enp0s16: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 80:61:5f:0a:2f:c4 brd ff:ff:ff:ff:ff:ff
The number of VFIO combinations drives me nuts. It's worse than PPC.
Thanks,
C.
next prev parent reply other threads:[~2025-03-03 18:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 8:47 [PATCH 0/2] vfio: Restrict to 64-bit host platforms Cédric Le Goater
2025-02-26 8:47 ` [PATCH 1/2] vfio: Make vfio-pci available on 64-bit host platforms only Cédric Le Goater
2025-02-26 14:12 ` BALATON Zoltan
2025-02-26 16:26 ` Cédric Le Goater
2025-02-26 17:57 ` BALATON Zoltan
2025-03-03 14:30 ` Philippe Mathieu-Daudé
2025-03-03 14:45 ` BALATON Zoltan
2025-03-03 14:46 ` Paolo Bonzini
2025-03-03 15:05 ` Cédric Le Goater
2025-03-03 15:26 ` BALATON Zoltan
2025-03-03 15:48 ` Cédric Le Goater
2025-03-03 16:04 ` Cédric Le Goater
2025-03-03 16:57 ` Peter Maydell
2025-03-03 17:32 ` Philippe Mathieu-Daudé
2025-03-05 6:38 ` Thomas Huth
2025-03-05 13:21 ` BALATON Zoltan
2025-03-03 17:34 ` Cédric Le Goater
2025-03-03 16:50 ` Paolo Bonzini
2025-03-03 17:32 ` Cédric Le Goater
2025-03-03 18:11 ` Cédric Le Goater [this message]
2025-03-03 14:43 ` Paolo Bonzini
2025-03-03 14:53 ` Philippe Mathieu-Daudé
2025-03-03 16:51 ` Daniel P. Berrangé
2025-03-03 15:07 ` Cédric Le Goater
2025-02-26 8:47 ` [PATCH 2/2] vfio: Make vfio-platform available on Aarch64 " Cédric Le Goater
2025-02-27 8:32 ` Eric Auger
2025-02-27 17:27 ` Alex Williamson
2025-03-03 14:32 ` Philippe Mathieu-Daudé
2025-03-03 18:07 ` Eric Auger
2025-02-26 14:01 ` [PATCH 0/2] vfio: Restrict to 64-bit host platforms Daniel P. Berrangé
2025-02-26 15:49 ` Cédric Le Goater
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9c9232f1-73f8-40ec-9064-a0df3f2e15cf@redhat.com \
--to=clg@redhat.com \
--cc=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=eric.auger@redhat.com \
--cc=farman@linux.ibm.com \
--cc=harshpb@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).