qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Frank Blaschka <blaschka@linux.vnet.ibm.com>
Cc: MIHAJLOV@de.ibm.com, qemu-devel@nongnu.org, agraf@suse.de,
	borntraeger@de.ibm.com, fiuczy@linux.vnet.ibm.com,
	cornelia.huck@de.ibm.com
Subject: Re: [Qemu-devel] [PATCH 2/2 RFC] s390x/pci: rework pci infrastructure modeling
Date: Wed, 11 Mar 2015 15:57:05 +0100	[thread overview]
Message-ID: <20150311154551-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <20150311143844.GA9483@tuxmaker.boeblingen.de.ibm.com>

On Wed, Mar 11, 2015 at 03:38:44PM +0100, Frank Blaschka wrote:
> I like Alex's idea because:
> 1) It reflects pretty well the actual nature of the pci system in real s390 hw

why do you say this? does real hw has this
one device per bridge limit?

  reply	other threads:[~2015-03-11 14:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 13:03 [Qemu-devel] [PATCH 0/2 RFC] Extend s390 pci representation in qemu V2 Frank Blaschka
2015-03-10 13:03 ` [Qemu-devel] [PATCH 1/2 RFC] pci: detangle Sysbus PCI bridge from PCIBus Frank Blaschka
2015-03-10 13:03 ` [Qemu-devel] [PATCH 2/2 RFC] s390x/pci: rework pci infrastructure modeling Frank Blaschka
2015-03-10 14:26   ` Michael S. Tsirkin
2015-03-11 14:38     ` Frank Blaschka
2015-03-11 14:57       ` Michael S. Tsirkin [this message]
2015-03-12  8:46         ` Frank Blaschka
2015-03-12  9:26           ` Michael S. Tsirkin
2015-03-11 17:42       ` Michael S. Tsirkin
2015-03-12  9:54         ` Frank Blaschka
2015-03-12 10:03           ` Michael S. Tsirkin
2015-03-12 10:50             ` Frank Blaschka
2015-03-12 13:16               ` Frank Blaschka
2015-03-12 14:59                 ` Alexander Graf
2015-03-12 15:22                   ` Michael S. Tsirkin
2015-03-17  7:11                     ` Alexander Graf
2015-03-17 12:15                       ` Frank Blaschka
2015-03-12 15:18                 ` Michael S. Tsirkin

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=20150311154551-mutt-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=MIHAJLOV@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=blaschka@linux.vnet.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=fiuczy@linux.vnet.ibm.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).