All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, mst@redhat.com, jasowang@redhat.com,
	alex.williamson@redhat.com, hare@suse.de, dmitry@daynix.com,
	pbonzini@redhat.com, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-2.6 0/2] Preparation for PCI devices convert to realize()
Date: Mon, 7 Dec 2015 10:42:21 +0800	[thread overview]
Message-ID: <5664F20D.80301@cn.fujitsu.com> (raw)
In-Reply-To: <5661D39F.6040607@redhat.com>

Hi John

On 12/05/2015 01:55 AM, John Snow wrote:
>
>
> On 12/04/2015 02:47 AM, Cao jin wrote:
>> Hi,
>>      As you know, there are many PCI devices still using .init() as its
>>      initialization function, I am planning to do the "convert to realize()"
>>      work, and PCI bridge devices are chosen first.
>>      The supporting functions should be modified first. msi_init() a supporting
>>      function for PCI devices.
>>
>>      Maybe it should be put in 2.6, as title indicated
>>
>> Cao jin (2):
>>    Add param Error** to msi_init()
>>    Modify callers of msi_init()
>>
>>   hw/audio/intel-hda.c               |  7 ++++++-
>>   hw/ide/ich.c                       |  2 +-
>>   hw/net/vmxnet3.c                   |  3 ++-
>>   hw/pci-bridge/ioh3420.c            |  6 +++++-
>>   hw/pci-bridge/pci_bridge_dev.c     |  6 +++++-
>>   hw/pci-bridge/xio3130_downstream.c |  7 ++++++-
>>   hw/pci-bridge/xio3130_upstream.c   |  7 ++++++-
>>   hw/pci/msi.c                       | 17 +++++++++++++----
>>   hw/scsi/megasas.c                  |  2 +-
>>   hw/scsi/vmw_pvscsi.c               |  3 ++-
>>   hw/usb/hcd-xhci.c                  |  5 ++++-
>>   hw/vfio/pci.c                      |  3 ++-
>>   include/hw/pci/msi.h               |  4 ++--
>>   13 files changed, 55 insertions(+), 17 deletions(-)
>>
>
> You'll need to squash these patches as the first patch will break git
> bisect.
>

Ok, will squash it. And I have another question: what`s the benefit of 
converting to realize? Because AFAICT, doing this make the error 
reporting machanism seems clean & clear, all device-init errors are 
passed above along the call chain. I mean, besides, are there any other 
benefits?

> --js
>
>
> .
>

-- 
Yours Sincerely,

Cao Jin

  reply	other threads:[~2015-12-07  2:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04  7:47 [Qemu-devel] [PATCH for-2.6 0/2] Preparation for PCI devices convert to realize() Cao jin
2015-12-04  7:47 ` [Qemu-devel] [PATCH for-2.6 1/2] Add param Error** to msi_init() Cao jin
2015-12-04  7:47 ` [Qemu-devel] [PATCH for-2.6 2/2] Modify callers of msi_init() Cao jin
2015-12-04 17:55 ` [Qemu-devel] [PATCH for-2.6 0/2] Preparation for PCI devices convert to realize() John Snow
2015-12-07  2:42   ` Cao jin [this message]
2015-12-07  8:35     ` Markus Armbruster
2015-12-07  9:50       ` Markus Armbruster

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=5664F20D.80301@cn.fujitsu.com \
    --to=caoj.fnst@cn.fujitsu.com \
    --cc=alex.williamson@redhat.com \
    --cc=dmitry@daynix.com \
    --cc=hare@suse.de \
    --cc=jasowang@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.