From: David Hildenbrand <david@redhat.com>
To: Pankaj Gupta <pankaj.gupta.linux@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Michael Tokarev <mjt@tls.msk.ru>
Subject: Re: [PATCH v2] virtio: kconfig: memory devices are PCI only
Date: Thu, 26 Sep 2024 10:51:10 +0200 [thread overview]
Message-ID: <b43b821e-3fe9-47fe-af68-79e75f872b20@redhat.com> (raw)
In-Reply-To: <CAM9Jb+gZ4+M1GOvRy6x8eg8OgOCyoEkBwKS6ZYQhGOOYndh6_g@mail.gmail.com>
On 25.09.24 09:39, Pankaj Gupta wrote:
>> Virtio memory devices rely on PCI BARs to expose the contents of memory.
>> Because of this they cannot be used (yet) with virtio-mmio or virtio-ccw.
>> In fact the code that is common to virtio-mem and virtio-pmem, which
>> is in hw/virtio/virtio-md-pci.c, is only included if CONFIG_VIRTIO_PCI
>> is set. Reproduce the same condition in the Kconfig file, only allowing
>> VIRTIO_MEM and VIRTIO_PMEM to be defined if the transport supports it.
>>
>> Without this patch it is possible to create a configuration with
>> CONFIG_VIRTIO_PCI=n and CONFIG_VIRTIO_MEM=y, but that causes a
>> linking failure.
>
> Just curious what is required to make virtio-mem & virtio-pmem compatible with
> virtio-mmio?
I assume not that much: primarily implementing the virtio-md-mmio
abstraction, and the virtio-mem-mmio/virtio-pmem-mmio proxy devices.
Then, it needs to be wired up in the machine hotplug code.
I posted the virtio-ccw variant a couple of days ago [1].
>
> Maybe late but still:
> Reviewed-by: Pankaj Gupta <pankaj.gupta@amd.com>
I already sent a merge request that includes this change. If I have to
resend it, I'll include that. Thanks!
[1] https://lkml.kernel.org/r/20240910175809.2135596-1-david@redhat.com
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2024-09-26 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 10:16 [PATCH v2] virtio: kconfig: memory devices are PCI only Paolo Bonzini
2024-09-06 10:25 ` David Hildenbrand
2024-09-09 12:01 ` David Hildenbrand
2024-09-25 7:39 ` Pankaj Gupta
2024-09-26 8:51 ` David Hildenbrand [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=b43b821e-3fe9-47fe-af68-79e75f872b20@redhat.com \
--to=david@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=pankaj.gupta.linux@gmail.com \
--cc=pbonzini@redhat.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).