qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Herongguang (Stephen)" <herongguang.he@huawei.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: marcel@redhat.com,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"wangxinxin.wang@huawei.com >> wangxin (U)"
	<wangxinxin.wang@huawei.com>
Subject: Re: [Qemu-devel] [RFC PATCH] pci: deassert intx when pci device unrealize
Date: Tue, 25 Apr 2017 10:16:36 +0800	[thread overview]
Message-ID: <58FEB184.4060102@huawei.com> (raw)
In-Reply-To: <20170425024324-mutt-send-email-mst@kernel.org>



On 2017/4/25 7:45, Michael S. Tsirkin wrote:
> On Mon, Apr 24, 2017 at 09:12:29PM +0800, Herongguang (Stephen) wrote:
>> If a pci device is not reset by VM (by writing into config space)
>> and unplugged by VM, after that when VM reboots, qemu may assert:
>> pcibus_reset: Assertion `bus->irq_count[i] == 0' failed
>>
>> Signed-off-by: herongguang <herongguang.he@huawei.com>
>
> Good grief, I can't believe we have had this bug for so long.
> Thanks a lot for finding this.
>
> Pls Cc stable on this patch.
>
>> ---
>>
>> Is there need to call pci_do_device_reset()?
>
> I don't think so, why?
>
>> ---
>>   hw/pci/pci.c | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/hw/pci/pci.c b/hw/pci/pci.c
>> index 259483b..afe6397 100644
>> --- a/hw/pci/pci.c
>> +++ b/hw/pci/pci.c
>> @@ -1078,6 +1078,7 @@ static void pci_qdev_unrealize(DeviceState *dev, Error **errp)
>>
>>       pci_unregister_io_regions(pci_dev);
>>       pci_del_option_rom(pci_dev);
>> +    pci_device_deassert_intx(pci_dev);
>
> I think the right place to call this is after class exit
> when we know no one will try to assert the interrupt.

OK, it's safer, will resend a new patch.

>
>>
>>       if (pc->exit) {
>>           pc->exit(pci_dev);
>> --
>> 1.7.12.4
> .
>

      reply	other threads:[~2017-04-25  2:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-24 13:12 [Qemu-devel] [RFC PATCH] pci: deassert intx when pci device unrealize Herongguang (Stephen)
2017-04-24 23:45 ` Michael S. Tsirkin
2017-04-25  2:16   ` Herongguang (Stephen) [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=58FEB184.4060102@huawei.com \
    --to=herongguang.he@huawei.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wangxinxin.wang@huawei.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).