From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: cornelia.huck@de.ibm.com, Keith Busch <keith.busch@intel.com>,
Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V4 18/19] pci: remove hard-coded bar size in msix_init_exclusive_bar()
Date: Fri, 20 Mar 2015 13:43:09 +0800 [thread overview]
Message-ID: <1426830189.5879.3@smtp.corp.redhat.com> (raw)
In-Reply-To: <20150319110319-mutt-send-email-mst@redhat.com>
On Thu, Mar 19, 2015 at 6:09 PM, Michael S. Tsirkin <mst@redhat.com>
wrote:
> On Thu, Mar 19, 2015 at 01:19:23PM +0800, Jason Wang wrote:
>>
>>
>> On Wed, Mar 18, 2015 at 8:52 PM, Michael S. Tsirkin
>> <mst@redhat.com> wrote:
>> >On Wed, Mar 18, 2015 at 05:35:08PM +0800, Jason Wang wrote:
>> >> This patch let msix_init_exclusive_bar() can accept bar_size
>> parameter
>> >> other than a hard-coded limit 4096. Then caller can specify a
>> bar_size
>> >> depends on msix entries and can use up to 2048 msix entries as
>> PCI
>> >> spec allows. To keep migration compatibility, 4096 is used for
>> all
>> >> callers and pba were start from half of bar size.
>> >> Cc: Keith Busch <keith.busch@intel.com>
>> >> Cc: Kevin Wolf <kwolf@redhat.com>
>> >> Cc: Stefan Hajnoczi <stefanha@redhat.com>
>> >> Cc: Michael S. Tsirkin <mst@redhat.com>
>> >> Signed-off-by: Jason Wang <jasowang@redhat.com>
>> >
>> >Hmm this API looks strange. Caller will then have to have
>> >msi specific knowledge.
>> >Can't we keep the size iternal to msix.c?
>>
>> Looks like we can, but still need an extra parameter e.g a boolean
>> compat_size to let msix_init_exclusive_bar() to use 4096 as bar
>> size.
>
> Why not just figure the size out from # of vectors?
Yes, for 2.4 we can figure the size out from the number of vectors.
next prev parent reply other threads:[~2015-03-20 5:44 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 9:34 [Qemu-devel] [PATCH V4 00/19] Support more virtio queues Jason Wang
2015-03-18 9:34 ` [Qemu-devel] [PATCH V4 01/19] pc: add 2.4 machine types Jason Wang
2015-03-18 9:34 ` [Qemu-devel] [PATCH V4 02/19] spapr: add machine type specific instance init function Jason Wang
2015-03-18 9:34 ` [Qemu-devel] [PATCH V4 03/19] ppc: spapr: add 2.4 machine type Jason Wang
2015-03-18 9:34 ` [Qemu-devel] [PATCH V4 04/19] monitor: replace the magic number 255 with MAX_QUEUE_NUM Jason Wang
2015-03-18 9:34 ` [Qemu-devel] [PATCH V4 05/19] monitor: check return value of qemu_find_net_clients_except() Jason Wang
2015-03-18 9:34 ` [Qemu-devel] [PATCH V4 06/19] virtio-ccw: using VIRTIO_NO_VECTOR instead of 0 for invalid virtqueue Jason Wang
2015-03-18 13:08 ` Michael S. Tsirkin
2015-03-20 7:39 ` Cornelia Huck
2015-03-21 18:27 ` Michael S. Tsirkin
2015-03-23 9:02 ` Cornelia Huck
2015-03-18 9:34 ` [Qemu-devel] [PATCH V4 07/19] virtio-net: validate backend queue numbers against bus limitation Jason Wang
2015-03-18 13:05 ` Michael S. Tsirkin
2015-03-19 5:26 ` Jason Wang
2015-03-18 9:34 ` [Qemu-devel] [PATCH V4 08/19] virtio-net: fix the upper bound when trying to delete queues Jason Wang
2015-03-18 13:06 ` Michael S. Tsirkin
2015-03-19 5:28 ` Jason Wang
2015-03-18 9:34 ` [Qemu-devel] [PATCH V4 09/19] virito: introduce bus specific queue limit Jason Wang
2015-03-20 10:20 ` Cornelia Huck
2015-03-31 2:34 ` Jason Wang
2015-03-18 9:35 ` [Qemu-devel] [PATCH V4 10/19] virtio-ccw: introduce ccw " Jason Wang
2015-03-20 11:33 ` Cornelia Huck
2015-03-31 2:36 ` Jason Wang
2015-03-18 9:35 ` [Qemu-devel] [PATCH V4 11/19] virtio-s390: switch to bus " Jason Wang
2015-03-20 11:34 ` Cornelia Huck
2015-03-18 9:35 ` [Qemu-devel] [PATCH V4 12/19] virtio-mmio: " Jason Wang
2015-03-18 9:35 ` [Qemu-devel] [PATCH V4 13/19] virtio-pci: switch to use " Jason Wang
2015-03-18 9:35 ` [Qemu-devel] [PATCH V4 14/19] virtio: introduce vector to virtqueues mapping Jason Wang
2015-03-20 11:39 ` Cornelia Huck
2015-03-31 2:37 ` Jason Wang
2015-03-18 9:35 ` [Qemu-devel] [PATCH V4 15/19] virtio: introduce virtio_queue_get_index() Jason Wang
2015-03-18 9:35 ` [Qemu-devel] [PATCH V4 16/19] virtio-pci: speedup MSI-X masking and unmasking Jason Wang
2015-03-18 9:35 ` [Qemu-devel] [PATCH V4 17/19] virtio-pci: increase the maximum number of virtqueues to 513 Jason Wang
2015-03-18 9:35 ` [Qemu-devel] [PATCH V4 18/19] pci: remove hard-coded bar size in msix_init_exclusive_bar() Jason Wang
2015-03-18 12:52 ` Michael S. Tsirkin
2015-03-19 5:19 ` Jason Wang
2015-03-19 10:09 ` Michael S. Tsirkin
2015-03-20 5:43 ` Jason Wang [this message]
2015-03-18 9:35 ` [Qemu-devel] [PATCH V4 19/19] virtio-pci: introduce auto_msix_bar_size property Jason Wang
2015-03-18 12:57 ` Michael S. Tsirkin
2015-03-19 5:23 ` Jason Wang
2015-03-19 10:01 ` Michael S. Tsirkin
2015-03-20 5:35 ` Jason Wang
2015-03-19 5:23 ` Jason Wang
2015-03-19 10:02 ` Michael S. Tsirkin
2015-03-20 5:38 ` Jason Wang
2015-03-18 12:58 ` [Qemu-devel] [PATCH V4 00/19] Support more virtio queues Michael S. Tsirkin
2015-03-19 5:24 ` Jason Wang
2015-03-19 7:32 ` Michael S. Tsirkin
2015-03-19 7:42 ` Jason Wang
2015-03-19 9:23 ` Michael S. Tsirkin
2015-03-20 5:11 ` Jason Wang
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=1426830189.5879.3@smtp.corp.redhat.com \
--to=jasowang@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=keith.busch@intel.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).