qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: aik@ozlabs.ru, alex.williamson@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] Fix MSIx lost after PE reset
Date: Tue, 26 Aug 2014 10:58:53 +1000	[thread overview]
Message-ID: <20140826005852.GA4430@shangw> (raw)
In-Reply-To: <1408528328-11560-1-git-send-email-gwshan@linux.vnet.ibm.com>

On Wed, Aug 20, 2014 at 07:52:06PM +1000, Gavin Shan wrote:
>The 2 patches fix MSIx lost after PE reset. Otherwise, the MSIx
>entries can't be restored successfully after PE reset and the
>EEH recovery fails on broadcom tg3 adapter (as tested) in guest.
>
>Note: The patchset "EEH support for guest" isn't merged yet, those
>      2 patches are based on Alex Graf's "ppc-next" branch + the
>      patchset supporting EEH for guest, which can be checked out
>      from below link:
>
>      git@github.com:gwshan/qemu.git (branch: eeh)
>
>Gavin Shan (2):
>  VFIO: Drop vfio_container_do_ioctl()
>  VFIO: Clear stale MSIx table during EEH reset
>
> hw/misc/vfio.c | 57 +++++++++++++++++++++++++++++++++++++++------------------
> 1 file changed, 39 insertions(+), 18 deletions(-)
>

Alex, any comments? :-)

Thanks,
Gavin

      parent reply	other threads:[~2014-08-26  0:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20  9:52 [Qemu-devel] [RFC PATCH 0/2] Fix MSIx lost after PE reset Gavin Shan
2014-08-20  9:52 ` [Qemu-devel] [RFC PATCH 1/2] VFIO: Drop vfio_container_do_ioctl() Gavin Shan
2014-08-26 10:27   ` Alexey Kardashevskiy
2014-08-26 20:05     ` Alex Williamson
2014-08-20  9:52 ` [Qemu-devel] [RFC PATCH 2/2] VFIO: Clear stale MSIx table during EEH reset Gavin Shan
2014-08-26 10:25   ` Alexey Kardashevskiy
2014-08-26 20:25   ` Alex Williamson
2014-08-27 13:15     ` Gavin Shan
2014-08-27 13:29       ` Alex Williamson
2014-08-29  7:13         ` Gavin Shan
2014-08-26  0:58 ` Gavin Shan [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=20140826005852.GA4430@shangw \
    --to=gwshan@linux.vnet.ibm.com \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=qemu-devel@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).