From: Jason Wang <jasowang@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org
Cc: dgilbert@redhat.com, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] e1000e: correctly tear down MSI-X memory regions
Date: Fri, 10 Mar 2017 18:59:18 +0800 [thread overview]
Message-ID: <5295b123-f4ce-fb95-1469-221be84bbf8e@redhat.com> (raw)
In-Reply-To: <a74b9e2a-dd72-8179-c2e2-c215093e8fef@redhat.com>
On 2017年03月09日 20:05, Laurent Vivier wrote:
> On 09/03/2017 12:58, Paolo Bonzini wrote:
>> MSI-X has been disabled by the time the e1000e device is unrealized, hence
>> msix_uninit is never called. This causes the object to be leaked, which
>> shows up as a RAMBlock with empty name when attempting migration.
>>
>> Reported-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>> Cc: Jason Wang <jasowang@redhat.com>
>> Cc: qemu-stable@nongnu.org
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>> hw/net/e1000e.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/hw/net/e1000e.c b/hw/net/e1000e.c
>> index b0f429b..6e23493 100644
>> --- a/hw/net/e1000e.c
>> +++ b/hw/net/e1000e.c
>> @@ -306,7 +306,7 @@ e1000e_init_msix(E1000EState *s)
>> static void
>> e1000e_cleanup_msix(E1000EState *s)
>> {
>> - if (msix_enabled(PCI_DEVICE(s))) {
>> + if (msix_present(PCI_DEVICE(s))) {
>> e1000e_unuse_msix_vectors(s, E1000E_MSIX_VEC_NUM);
>> msix_uninit(PCI_DEVICE(s), &s->msix, &s->msix);
>> }
>>
> Tested-by: Laurent Vivier <lvivier@redhat.com>
>
Applied, thanks.
prev parent reply other threads:[~2017-03-10 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 11:58 [Qemu-devel] [PATCH] e1000e: correctly tear down MSI-X memory regions Paolo Bonzini
2017-03-09 12:05 ` Laurent Vivier
2017-03-10 10:59 ` Jason Wang [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=5295b123-f4ce-fb95-1469-221be84bbf8e@redhat.com \
--to=jasowang@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/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).