qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: qemu-devel@nongnu.org
Cc: "Mike Day" <ncmike@ncultra.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	qemu-ppc@nongnu.org, "Alexander Graf" <agraf@suse.de>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH 0/4] spapr-pci: prepare for vfio
Date: Wed, 12 Mar 2014 14:33:16 +1100	[thread overview]
Message-ID: <531FD57C.8000106@ozlabs.ru> (raw)
In-Reply-To: <52FB5EA6.3020700@ozlabs.ru>

On 02/12/2014 10:44 PM, Alexey Kardashevskiy wrote:
> On 01/15/2014 06:10 PM, Alexey Kardashevskiy wrote:
>> On 12/20/2013 01:47 PM, Alexey Kardashevskiy wrote:
>>> On 12/05/2013 08:39 PM, Alexey Kardashevskiy wrote:
>>>> On 11/21/2013 03:08 PM, Alexey Kardashevskiy wrote:
>>>>> Here are few reworks for spapr-pci PHB which I'd like to have to support VFIO.
>>>>> QOM, errors printing, traces, nothing really serious. Thanks!
>>>>>
>>>>> Alexey Kardashevskiy (4):
>>>>>   spapr-pci: convert init() callback to realize()
>>>>>   spapr-pci: introduce a finish_realize() callback
>>>>>   spapr-pci: add spapr_pci trace
>>>>>   spapr-pci: converts fprintf to error_report
>>>>>
>>>>>  hw/ppc/spapr_pci.c          | 90 ++++++++++++++++++++++++++-------------------
>>>>>  include/hw/pci-host/spapr.h | 18 ++++++++-
>>>>>  trace-events                |  1 +
>>>>>  3 files changed, 69 insertions(+), 40 deletions(-)
>>>>
>>>>
>>>> Ping?
>>>
>>> Ping?
>>
>> Ping?
> 
> Alex?

I do realize Alex is in vacation and when he is not, he is busy and
everything like that but this set is really simple and it is blocking me
from posting other VFIO bits so if anyone could find a minute and have a
look, that would be great. Thanks!



-- 
Alexey

      reply	other threads:[~2014-03-12  3:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21  4:08 [Qemu-devel] [PATCH 0/4] spapr-pci: prepare for vfio Alexey Kardashevskiy
2013-11-21  4:08 ` [Qemu-devel] [PATCH 1/4] spapr-pci: convert init() callback to realize() Alexey Kardashevskiy
2014-03-12 13:20   ` [Qemu-devel] " Mike Day
2014-03-12 13:56   ` Mike Day
2014-03-12 23:25     ` Alexey Kardashevskiy
2014-03-13  1:45   ` [Qemu-devel] [PATCH 1/4] " Andreas Färber
2013-11-21  4:08 ` [Qemu-devel] [PATCH 2/4] spapr-pci: introduce a finish_realize() callback Alexey Kardashevskiy
2014-03-12 15:30   ` [Qemu-devel] " Mike Day
2014-03-13  1:56   ` [Qemu-devel] [PATCH 2/4] " Andreas Färber
2014-03-13  7:29     ` Alexey Kardashevskiy
2013-11-21  4:08 ` [Qemu-devel] [PATCH 3/4] spapr-pci: add spapr_pci trace Alexey Kardashevskiy
2014-03-13  1:46   ` Andreas Färber
2014-03-13  7:37     ` Alexey Kardashevskiy
2013-11-21  4:08 ` [Qemu-devel] [PATCH 4/4] spapr-pci: converts fprintf to error_report Alexey Kardashevskiy
2014-03-12 15:41   ` [Qemu-devel] " Mike Day
2014-03-13  1:50   ` [Qemu-devel] [PATCH 4/4] " Andreas Färber
2013-12-05  9:39 ` [Qemu-devel] [PATCH 0/4] spapr-pci: prepare for vfio Alexey Kardashevskiy
2013-12-20  2:47   ` Alexey Kardashevskiy
2014-01-15  7:10     ` Alexey Kardashevskiy
2014-02-12 11:44       ` Alexey Kardashevskiy
2014-03-12  3:33         ` Alexey Kardashevskiy [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=531FD57C.8000106@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=ncmike@ncultra.org \
    --cc=pbonzini@redhat.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).