From: David Hildenbrand <david@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Richard Henderson <rth@twiddle.net>,
Alexander Graf <agraf@suse.de>, Thomas Huth <thuth@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v1 for-2.12 0/5] s390x/tcg: CCW hotplug support
Date: Mon, 4 Dec 2017 18:00:31 +0100 [thread overview]
Message-ID: <748a102a-cc55-b4d7-e18d-f65a144f5d9f@redhat.com> (raw)
In-Reply-To: <20171204175651.4acffb4e.cohuck@redhat.com>
On 04.12.2017 17:56, Cornelia Huck wrote:
> On Mon, 4 Dec 2017 13:55:00 +0100
> David Hildenbrand <david@redhat.com> wrote:
>
>> Hotplugging a ccw device currently fails due to different reasons.
>>
>> 1. The stored machine check information is partially wrong.
>> 2. The TOD programmable field cannot be restored.
>> 3. STCRW cannot get executed.
>>
>> With these patches, I am able to sucessfully hotplug e.g. virtio-rng by
>> issuing "device_add virtio-rng-ccw,id=rng0" to a Linux guest.
>
> Thank you for taking care of my unpublished todo list ;)
>
> Does device_del also work?
I did a very quick test and it seemed to work. (I remember seeing
notifications in dmesg)
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2017-12-04 17:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 12:55 [Qemu-devel] [PATCH v1 for-2.12 0/5] s390x/tcg: CCW hotplug support David Hildenbrand
2017-12-04 12:55 ` [Qemu-devel] [PATCH v1 for-2.12 1/5] s390x/kvm: factor out build_channel_report_mcic() into cpu.h David Hildenbrand
2017-12-04 17:03 ` Cornelia Huck
2017-12-04 17:16 ` David Hildenbrand
2017-12-05 10:20 ` Cornelia Huck
2017-12-05 11:29 ` David Hildenbrand
2017-12-04 12:55 ` [Qemu-devel] [PATCH v1 for-2.12 2/5] s390x/tcg: fix and cleanup mcck injection David Hildenbrand
2017-12-04 17:20 ` Cornelia Huck
2017-12-04 17:27 ` David Hildenbrand
2017-12-05 10:14 ` Cornelia Huck
2017-12-05 15:53 ` Thomas Huth
2017-12-05 16:22 ` David Hildenbrand
2017-12-04 12:55 ` [Qemu-devel] [PATCH v1 for-2.12 3/5] s390x/tcg: implement SET CLOCK PROGRAMMABLE FIELD David Hildenbrand
2017-12-05 11:05 ` Cornelia Huck
2017-12-06 15:10 ` Thomas Huth
2017-12-06 15:15 ` David Hildenbrand
2017-12-04 12:55 ` [Qemu-devel] [PATCH v1 for-2.12 4/5] s390x/tcg: indicate value of TODPR in STCKE David Hildenbrand
2017-12-06 15:24 ` Thomas Huth
2017-12-04 12:55 ` [Qemu-devel] [PATCH v1 for-2.12 5/5] s390x/tcg: wire up STORE CHANNEL REPORT WORD David Hildenbrand
2017-12-04 17:22 ` Cornelia Huck
2017-12-04 17:34 ` David Hildenbrand
2017-12-04 17:53 ` Cornelia Huck
2017-12-04 17:56 ` David Hildenbrand
2017-12-04 17:58 ` Cornelia Huck
2017-12-04 18:37 ` David Hildenbrand
2017-12-05 10:04 ` Cornelia Huck
2017-12-06 15:40 ` Thomas Huth
2017-12-04 13:10 ` [Qemu-devel] [PATCH v1 for-2.12 0/5] s390x/tcg: CCW hotplug support no-reply
2017-12-04 13:21 ` David Hildenbrand
2017-12-04 13:35 ` no-reply
2017-12-04 16:56 ` Cornelia Huck
2017-12-04 17:00 ` 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=748a102a-cc55-b4d7-e18d-f65a144f5d9f@redhat.com \
--to=david@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--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).