qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"BALATON Zoltan" <balaton@eik.bme.hu>,
	qemu-devel <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 18:32:09 +0100	[thread overview]
Message-ID: <a5220b2e-0833-4461-828f-4fe6109c15e6@redhat.com> (raw)
In-Reply-To: <CABgObfZ4-qKX5SCp+3fD2a54SVUZ3+fA--gq6=tf1idjQYVTrw@mail.gmail.com>

On 3/3/25 17:50, Paolo Bonzini wrote:
> 
> 
> Il lun 3 mar 2025, 16:05 Cédric Le Goater <clg@redhat.com <mailto:clg@redhat.com>> ha scritto:
> 
>     On 3/3/25 15:46, Paolo Bonzini wrote:
>      > On 3/3/25 15:30, Philippe Mathieu-Daudé wrote:
>      >>>>> 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
>      >>>
>      >>> I've seen people do this on x86_64 host
>      >>
>      >> Since this patch does:
>      >>
>      >>    LINUX && PCI && (...  X86_64 ...)
>      >>
>      >> these users won't see any change.
>      >
>      > This is wrong---clearly this patch was never tested on the 32-bit platforms where it was supposed to have an effect.
> 
>     euh it was.
> 
> 
> Uff—I should have said was *only* tested on the 32-bit platforms where it was supposed to have an effect! The problem is with the 64-bit hosts...
> 
>     With this patch, on 32-bit and 64-bit host systems :
> 
>         # build/qemu-system-i386 -device vfio-pci,?
>         # qemu-system-i386: -device vfio-pci,?: Device 'vfio-pci' not found
> 
>     Same for qemu-system-ppc and qemu-system-arm
> 
>     What I am doing wrong ?
> 
> 
> ... Where you were testing the wrong target. :) qemu-system-i386 should still support VFIO if compiled on a 64-bit host, according to the subject.

yep. I have a test case for it now ! on q35 and pc-i440fx machines.

Thanks,

C.



  reply	other threads:[~2025-03-03 17:33 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 [this message]
2025-03-03 18:11         ` Cédric Le Goater
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=a5220b2e-0833-4461-828f-4fe6109c15e6@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=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --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).