qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: aik@ozlabs.ru, alex.williamson@redhat.com,
	Gavin Shan <gwshan@linux.vnet.ibm.com>
Subject: [Qemu-devel] [RFC PATCH v3 0/2] Fix MSIx lost after PE reset
Date: Mon,  8 Sep 2014 14:52:38 +1000	[thread overview]
Message-ID: <1410151960-18199-1-git-send-email-gwshan@linux.vnet.ibm.com> (raw)

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.

The reset path (restarting machine) has the same problem. Also,
the MSI has the same problem as well.

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)

*** SUBJECT HERE ***

*** BLURB HERE ***

Gavin Shan (2):
  VFIO: Drop vfio_container_do_ioctl()
  VFIO: Clear stale interrupt vectors during reset

 hw/misc/vfio.c | 99 +++++++++++++++++++++++++++++++++++++++++-----------------
 1 file changed, 70 insertions(+), 29 deletions(-)

-- 
1.8.3.2

             reply	other threads:[~2014-09-08  4:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08  4:52 Gavin Shan [this message]
2014-09-08  4:52 ` [Qemu-devel] [RFC PATCH v3 1/2] VFIO: Drop vfio_container_do_ioctl() Gavin Shan
2014-09-08  4:52 ` [Qemu-devel] [RFC PATCH v3 2/2] VFIO: Clear stale interrupt vectors during reset Gavin Shan
2014-09-08  4:59 ` [Qemu-devel] [RFC PATCH v3 0/2] Fix MSIx lost after PE reset Gavin Shan

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=1410151960-18199-1-git-send-email-gwshan@linux.vnet.ibm.com \
    --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).