qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Gavin Shan <gwshan@linux.vnet.ibm.com>,
	qemu-ppc@nongnu.org, agraf@suse.de, aik@ozlabs.ru,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] vfio: Fix broken EEH
Date: Thu, 16 Jun 2016 11:00:02 +1000	[thread overview]
Message-ID: <20160616010002.GG28087@voom.fritz.box> (raw)
In-Reply-To: <20160615105255.0b2ddca4@t450s.home>

[-- Attachment #1: Type: text/plain, Size: 2103 bytes --]

On Wed, Jun 15, 2016 at 10:52:55AM -0600, Alex Williamson wrote:
> On Wed, 15 Jun 2016 15:03:15 +1000
> David Gibson <david@gibson.dropbear.id.au> wrote:
> 
> > On Wed, Jun 15, 2016 at 02:46:23PM +1000, David Gibson wrote:
> > > On Wed, Jun 15, 2016 at 02:28:27PM +1000, Gavin Shan wrote:  
> > > > vfio_eeh_container_op() is the backend that communicates with
> > > > host kernel to support EEH functionality in QEMU. However, the
> > > > functon should return the value from host kernel instead of 0
> > > > unconditionally.
> > > > 
> > > > Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>  
> > > 
> > > Applied to ppc-for-2.7, thanks.  
> > 
> > Hang on, wait.. forgot I should get an ack for this from you, Alex.
> > I'll keep it in my tree for now, unless you tell me you'd prefer to
> > take it through yours.
> 
> Hmm, clearly this patch should have cc'd qemu-devel from the start.

Yeah. Gavin's not usually a qemu developer and I forgot a bunch of
things in my 15s version of how-to-submit-qemu-patches.

> Go
> ahead and take it through your tree David.

Will do, thanks.

> 
> Acked-by: Alex Williamson <alex.williamson@redhat.com>
> 
> > 
> > > 
> > > We should probably look at applying this to the 2.6 stable branch as well.
> > >   
> > > > ---
> > > >  hw/vfio/common.c | 2 +-
> > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > 
> > > > diff --git a/hw/vfio/common.c b/hw/vfio/common.c
> > > > index e51ed3a..e51db46 100644
> > > > --- a/hw/vfio/common.c
> > > > +++ b/hw/vfio/common.c
> > > > @@ -1258,7 +1258,7 @@ static int vfio_eeh_container_op(VFIOContainer *container, uint32_t op)
> > > >          return -errno;
> > > >      }
> > > >  
> > > > -    return 0;
> > > > +    return ret;
> > > >  }
> > > >  
> > > >  static VFIOContainer *vfio_eeh_as_container(AddressSpace *as)  
> > >   
> > 
> > 
> > 
> 

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2016-06-16  1:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1465964907-17637-1-git-send-email-gwshan@linux.vnet.ibm.com>
     [not found] ` <20160615044623.GB21472@voom.fritz.box>
     [not found]   ` <20160615050315.GC21472@voom.fritz.box>
2016-06-15 16:52     ` [Qemu-devel] [PATCH] vfio: Fix broken EEH Alex Williamson
2016-06-16  1:00       ` David Gibson [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=20160616010002.GG28087@voom.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=gwshan@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).