From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@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 5/5] s390x/tcg: wire up STORE CHANNEL REPORT WORD
Date: Mon, 4 Dec 2017 18:53:52 +0100 [thread overview]
Message-ID: <20171204185352.39f2b131.cohuck@redhat.com> (raw)
In-Reply-To: <8904d9e3-990f-46e1-49d1-9d37533d025e@redhat.com>
On Mon, 4 Dec 2017 18:34:36 +0100
David Hildenbrand <david@redhat.com> wrote:
> On 04.12.2017 18:22, Cornelia Huck wrote:
> > On Mon, 4 Dec 2017 13:55:05 +0100
> > David Hildenbrand <david@redhat.com> wrote:
> >
> >> We somehow missed that, new kernels require it.
> >
> > Why _new_ kernels? I think we have unconditionally issued stcrw since
> > back in 2.2?
>
> Okay, the problem is then rather related to my setup. No ccw devices ->
> no stcrw.
>
> How could we ever add ccw devices to a TCG guest then?
Hotplug never worked before your patches. Coldplug does not create
machine checks and thus does not trigger the guest to do STCRW. (Only
STSCH, in keeping with "all channel I/O acronyms look the same".)
next prev parent reply other threads:[~2017-12-04 17:54 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 [this message]
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
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=20171204185352.39f2b131.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=david@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).