All of lore.kernel.org
 help / color / mirror / Atom feed
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 5/5] s390x/tcg: wire up STORE CHANNEL REPORT WORD
Date: Mon, 4 Dec 2017 19:37:26 +0100	[thread overview]
Message-ID: <e33bd227-4cb2-2e9b-9ebd-e498ec4aafe7@redhat.com> (raw)
In-Reply-To: <20171204185833.64a68453.cohuck@redhat.com>

On 04.12.2017 18:58, Cornelia Huck wrote:
> On Mon, 4 Dec 2017 18:56:00 +0100
> David Hildenbrand <david@redhat.com> wrote:
> 
>> On 04.12.2017 18:53, Cornelia Huck wrote:
>>> 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".)
>>>   
>>
>> But booting Fedora 26/27 without any involved hotplugs (therefore
>> machine checks) triggers a STCRW.
>>
>> That's how I originally found it. (I started playing with machine checks
>> after I had fedora 26/27 running)
>>
> 
> Confused. Do you have a backtrace? (Guest/host)
> 

Unfortunately not. Strange, I just tried to reproduce but can't trigger
it. Maybe aside effect from the other BUGs I have been fixing :)

So I'll just rephrase this to "CRW machine check handling requires STCRW."

-- 

Thanks,

David / dhildenb

  reply	other threads:[~2017-12-04 18:37 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 [this message]
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=e33bd227-4cb2-2e9b-9ebd-e498ec4aafe7@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 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.