From: Niklas Schnelle <schnelle@linux.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
qemu-devel@nongnu.org
Cc: thuth@redhat.com, pmorel@linux.ibm.com, david@redhat.com,
cohuck@redhat.com, farman@linux.ibm.com, pasic@linux.ibm.com,
qemu-s390x@nongnu.org, rth@twiddle.net
Subject: Re: [PATCH] s390x/s390-virtio-ccw: Reset PCI devices during subsystem reset
Date: Thu, 15 Oct 2020 15:37:57 +0200 [thread overview]
Message-ID: <2dea575e-45cf-adc2-a0eb-61aaffbbaaec@linux.ibm.com> (raw)
In-Reply-To: <d705b269-b001-f810-8629-7d64fb560ac5@de.ibm.com>
On 10/15/20 3:34 PM, Christian Borntraeger wrote:
>
>
> On 15.10.20 15:32, Christian Borntraeger wrote:
>>
>>
>> On 15.10.20 15:16, Matthew Rosato wrote:
>>> Currently, a subsystem reset event leaves PCI devices enabled, causing
>>> issues post-reset in the guest (an example would be after a kexec). These
>>> devices need to be reset during a subsystem reset, allowing them to be
>>> properly re-enabled afterwards. Add the S390 PCI host bridge to the list
>>> of qdevs to be reset during subsystem reset.
>>>
>>> Signed-off-by: Matthew Rosato <mjrosato@linux.ibm.com>
>>> Reviewed-by: Eric Farman <farman@linux.ibm.com>
>>
>> Makese sense.
>> Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
>
> A question. Is this a stable candidate?
As this can prevent a SUSE guest (which does kexec during boot because of grub)
from seeing any PCI devices I'd say yes.
>
>>
>>
>>> ---
>>> hw/s390x/s390-virtio-ccw.c | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/hw/s390x/s390-virtio-ccw.c b/hw/s390x/s390-virtio-ccw.c
>>> index e52182f..2e90033 100644
>>> --- a/hw/s390x/s390-virtio-ccw.c
>>> +++ b/hw/s390x/s390-virtio-ccw.c
>>> @@ -101,6 +101,7 @@ static const char *const reset_dev_types[] = {
>>> "s390-sclp-event-facility",
>>> "s390-flic",
>>> "diag288",
>>> + TYPE_S390_PCI_HOST_BRIDGE,
>>> };
>>>
>>> static void subsystem_reset(void)
>>>
next prev parent reply other threads:[~2020-10-15 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 13:16 [PATCH] s390x/s390-virtio-ccw: Reset PCI devices during subsystem reset Matthew Rosato
2020-10-15 13:32 ` Christian Borntraeger
2020-10-15 13:34 ` Christian Borntraeger
2020-10-15 13:37 ` Niklas Schnelle [this message]
2020-10-15 13:45 ` Matthew Rosato
2020-10-16 15:36 ` Halil Pasic
2020-10-20 9:57 ` Cornelia Huck
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=2dea575e-45cf-adc2-a0eb-61aaffbbaaec@linux.ibm.com \
--to=schnelle@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=farman@linux.ibm.com \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=pmorel@linux.ibm.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).