qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Frank Blaschka <blaschka@linux.vnet.ibm.com>,
	cornelia.huck@de.ibm.com, borntraeger@de.ibm.com,
	pbonzini@redhat.com, alex.williamson@redhat.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3 RFC] add PCI support for the s390 platform
Date: Sun, 02 Nov 2014 22:10:37 +0100	[thread overview]
Message-ID: <54569DCD.6090307@suse.de> (raw)
In-Reply-To: <1413990720-39602-1-git-send-email-blaschka@linux.vnet.ibm.com>



On 22.10.14 17:11, Frank Blaschka wrote:
> This set of patches implemets PCI support for the s390 platform.
> Now it is possible to run virtio-net-pci and potentially all
> virtual pci devices conforming to s390 platform constrains.
> (In parallel I also post some changes to make vfio run on s390)
> 
> I hope to get feedback and guidance especially for
> 
> kvm: extend kvm_irqchip_add_msi_route to work on s390
> 
> which adds the s390 interpretation of MSI-X to the common kvm
> add_msi_route functionality.
> 
> Thx for any help,

The patch set certainly looks like way-above-RFC-quality to me ;).
Unfortunately timing is suboptimal with soft freeze in place already and
hard freeze coming up soon, but from a quick glimpse I like it. No
reviewed-by yet though, as I'd have to dig in further for that ;).


Alex

      parent reply	other threads:[~2014-11-02 21:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 15:11 [Qemu-devel] [PATCH 0/3 RFC] add PCI support for the s390 platform Frank Blaschka
2014-10-22 15:11 ` [Qemu-devel] [PATCH 1/3 RFC] s390: Add PCI bus support Frank Blaschka
2014-10-22 15:11 ` [Qemu-devel] [PATCH 2/3 RFC] s390: implement pci instructions Frank Blaschka
2014-10-23 13:12   ` Thomas Huth
2014-10-22 15:12 ` [Qemu-devel] [PATCH 3/3 RPC] kvm: extend kvm_irqchip_add_msi_route to work on s390 Frank Blaschka
2014-10-30 17:37   ` Cornelia Huck
2014-11-02 21:10 ` Alexander Graf [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=54569DCD.6090307@suse.de \
    --to=agraf@suse.de \
    --cc=alex.williamson@redhat.com \
    --cc=blaschka@linux.vnet.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=pbonzini@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).