From: Ivano Cerrato <ivano.cerrato@polito.it>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: "Mauricio Vásquez" <mauricio.vasquezbernal@studenti.polito.it>,
"Fulvio Risso" <fulvio.risso@polito.it>,
QEMU <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Does PCI hotplug work with IVSHMEM?
Date: Wed, 22 Jul 2015 07:48:54 +0200 [thread overview]
Message-ID: <55AF2EC6.1060500@polito.it> (raw)
In-Reply-To: <CAJ+F1CKKzk7yrKDgMsTFam=Yg8kWg98rvy-+pDOEXqXGkVDS-A@mail.gmail.com>
Thank you for the answer!
Why do you say that it is not safe to do hotplug with ivshmem?
Ivano
Il 21/07/2015 18:37, Marc-André Lureau ha scritto:
> Hi
>
> On Tue, Jul 21, 2015 at 12:13 PM, Ivano Cerrato <ivano.cerrato@polito.it> wrote:
>> Is there any way to force the Guest OS to recognize the new device without
>> rebooting? Such as rmmod/insmod or equivalent?
> This can be observed in qemu monitor too, info qtree:
>
> dev: ivshmem, id ""
> chardev = ""
> size = "2048M"
> vectors = 1 (0x1)
> ioeventfd = false
> msi = true
> shm = "foo"
> role = ""
> use64 = 1 (0x1)
> addr = 05.0
> romfile = ""
> rombar = 1 (0x1)
> multifunction = false
> command_serr_enable = true
> class RAM controller, addr 00:05.0, pci id 1af4:1110 (sub 1af4:1100)
> bar 0: mem at 0x40000000 [0x400000ff]
> bar 2: mem at 0xffffffffffffffff [0x7ffffffe]
>
> Check dmesg, it fails to allocate for me, but with 1G it works (f22
> x86_64). I don't know what's the reason behind it.
>
> Note that it's not safe to do hotplug with ivshmem (it may assert in
> various ways), I proposed a patch series a few weeks ago, I am going
> to send an updated version soon.
>
next prev parent reply other threads:[~2015-07-22 5:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 10:13 [Qemu-devel] Does PCI hotplug work with IVSHMEM? Ivano Cerrato
2015-07-21 16:37 ` Marc-André Lureau
2015-07-21 16:42 ` Marc-André Lureau
2015-07-22 5:48 ` Ivano Cerrato [this message]
2015-08-04 14:14 ` Ivano Cerrato
2015-08-04 14:21 ` Marc-André Lureau
2015-08-05 14:44 ` Ivano Cerrato
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=55AF2EC6.1060500@polito.it \
--to=ivano.cerrato@polito.it \
--cc=fulvio.risso@polito.it \
--cc=marcandre.lureau@gmail.com \
--cc=mauricio.vasquezbernal@studenti.polito.it \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.