qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Halil Pasic <pasic@linux.ibm.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
	"Boris Fiuczynski" <fiuczy@linux.ibm.com>,
	"Eduardo Habkost" <ehabkost@redhat.com>,
	"David Hildenbrand" <david@redhat.com>,
	"Cornelia Huck" <cohuck@redhat.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	qemu-devel@nongnu.org, "Bruce Rogers" <brogers@suse.com>,
	"Christian Borntraeger" <borntraeger@de.ibm.com>,
	qemu-s390x@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH v3 1/1] hw/s390x: modularize virtio-gpu-ccw
Date: Sat, 13 Mar 2021 03:09:33 +0100	[thread overview]
Message-ID: <20210313030933.7f89b7e5.pasic@linux.ibm.com> (raw)
In-Reply-To: <YEd2SnQkdtfhI4dL@redhat.com>

On Tue, 9 Mar 2021 13:21:14 +0000
Daniel P. Berrangé <berrange@redhat.com> wrote:

> > Well, yes, in a non-modular world this will work perfectly fine.  We
> > only compile objects actually supported into the system emulator.
> > 
> > With modular builds we have the situation that we have shared modules
> > which may or may not work in specific system emulators, for example
> > hw-display-virtio-gpu-pci.so or the ccw module added by this patch,
> > because the given system emulator doesn't provide the needed support.
> > We have some which don't support pci (avr for example).  Likewise ccw
> > is supported by s390x only.  
> 
> We could solve this by having a different location for loading modules
> for each target.
> 
>   *  /usr/$LIB/qemu/
> 
>     All the real .so's go in here as today
> 
>   *  /usr/$LIB/qemu/$TARGET
> 
>     Populated with symlinks to the .so's in the parent dir,
>     but /only/ those which are valid for this $TARGET
> 
> Then change QEMU  to load from the second dir.

I like the idea. I also prefer not trying to load a module X
that we know is not supported with, and ain't going to work with
target Y, over doing the load and making something fail afterwards.

I've not only started working on this, but I already have something
kind of works. But I'm not quite satisfied with it. I will spend some
more cycles before sending it out, but I doubt I will be able to get it
in a 'looks nice' shape. Thanks you!

Regards,
Halil


      reply	other threads:[~2021-03-13  2:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 17:35 [PATCH v3 1/1] hw/s390x: modularize virtio-gpu-ccw Halil Pasic
2021-03-05 11:25 ` Halil Pasic
2021-03-05 11:54 ` Cornelia Huck
2021-03-05 12:05   ` Halil Pasic
2021-03-05 21:46 ` Eduardo Habkost
2021-03-08 21:19   ` Halil Pasic
2021-03-09 12:45   ` Gerd Hoffmann
2021-03-09 13:21     ` Daniel P. Berrangé
2021-03-13  2:09       ` Halil Pasic [this message]

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=20210313030933.7f89b7e5.pasic@linux.ibm.com \
    --to=pasic@linux.ibm.com \
    --cc=berrange@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=brogers@suse.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=fiuczy@linux.ibm.com \
    --cc=kraxel@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=thuth@redhat.com \
    /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).