qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Toolybird <1922325@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1922325] Re: s390x-virtio-gpu-ccw module unnecessary?
Date: Sun, 16 May 2021 03:47:55 -0000	[thread overview]
Message-ID: <162113687583.1840.2786925975909600515.malone@wampee.canonical.com> (raw)
In-Reply-To: 161734548902.18419.14050704437268299293.malonedeb@soybean.canonical.com

I only enable a few emulators and qemu-system-s390x isn't one of them.

I was thinking it couldn't be useful on an x86_64 host, even if using
the qemu-system-s390x emulator! I guess my understanding was wrong. Will
close as invalid.

** Changed in: qemu
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1922325

Title:
  s390x-virtio-gpu-ccw module unnecessary?

Status in QEMU:
  Invalid

Bug description:
  Hi

  Test building latest 6.0.0 release candidate on x86_64 host. A new
  module has appeared:

  /usr/lib/qemu/hw-s390x-virtio-gpu-ccw.so

  Unless I'm missing something obvious, it would appear to be only
  useful on s390x platform.

  Why would I need this? For me it doesn't seem to do much:

  $ nm -D /usr/lib/qemu/hw-s390x-virtio-gpu-ccw.so
                   w __cxa_finalize
                   w __gmon_start__
                   w _ITM_deregisterTMCloneTable
                   w _ITM_registerTMCloneTable
  00000000000010f0 T qemu_module_dummy
  0000000000001100 T qemu_stamp_0d4aa0592256528f9885a56f182883665e60f8ec

  Bug or ... ?

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1922325/+subscriptions


      parent reply	other threads:[~2021-05-16  3:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-02  6:38 [Bug 1922325] [NEW] s390x-virtio-gpu-ccw module unnecessary? Toolybird
2021-05-15 10:41 ` [Bug 1922325] " Thomas Huth
2021-05-16  3:47 ` Toolybird [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=162113687583.1840.2786925975909600515.malone@wampee.canonical.com \
    --to=1922325@bugs.launchpad.net \
    --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).