From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/8] msix: Support specifying offsets, BARs, and capability location
Date: Mon, 18 Jun 2012 11:23:41 +0200 [thread overview]
Message-ID: <4FDEF39D.3050503@siemens.com> (raw)
In-Reply-To: <20120618071913.GA19877@redhat.com>
On 2012-06-18 09:19, Michael S. Tsirkin wrote:
> On Mon, Jun 18, 2012 at 09:06:01AM +0200, Jan Kiszka wrote:
>> On 2012-06-14 23:31, Michael S. Tsirkin wrote:
>>> On Thu, Jun 14, 2012 at 12:15:42PM -0600, Alex Williamson wrote:
>>>> v3:
>>>> - more patches, smaller diff, must be headed in the right direction
>>>> - macros for all hardcoded values in msix_init_exclusive_bar
>>>> - fold msix_add_config into msix_init allowing less churn to moving
>>>> around msix_uninit
>>>> - note native endian bug
>>>> - split msix_mmio_read move to separate patch
>>>> - split changing return value of msix_uninit to separate patch
>>>>
>>>> Thanks,
>>>>
>>>> Alex
>>>
>>> Thanks, applied all.
>>> Will test/push next week.
>>
>> Could you publish your queue? I'd like to rebase my missing bits.
>>
>> Thanks,
>> Ja
>>
>
> Will do. FYI Anthony said on irc he objects to the caching approach,
> asked for more time to review it all. Maybe we'll have to
> go back to your original idea of a special API just for
> assigned devices.
Yes, we can still add caching on top.
I really like to have some hook upstream soon as time is running out
quickly for the 1.2 merge window and there is still some work to do on
the qemu-kvm side.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-06-18 9:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 18:15 [Qemu-devel] [PATCH v3 0/8] msix: Support specifying offsets, BARs, and capability location Alex Williamson
2012-06-14 18:15 ` [Qemu-devel] [PATCH v3 1/8] msix: Add simple BAR allocation MSIX setup functions Alex Williamson
2012-06-14 18:16 ` [Qemu-devel] [PATCH v3 2/8] ivshmem: Convert to msix_init_exclusive_bar() interface Alex Williamson
2012-06-14 18:16 ` [Qemu-devel] [PATCH v3 3/8] virtio: " Alex Williamson
2012-06-14 18:16 ` [Qemu-devel] [PATCH v3 4/8] msix: Move msix_mmio_read Alex Williamson
2012-06-14 18:16 ` [Qemu-devel] [PATCH v3 5/8] msix: Note endian TODO item Alex Williamson
2012-06-14 18:16 ` [Qemu-devel] [PATCH v3 6/8] msix: Split PBA into it's own MemoryRegion Alex Williamson
2012-06-14 18:16 ` [Qemu-devel] [PATCH v3 7/8] msix: Allow full specification of MSIX layout Alex Williamson
2012-06-14 18:16 ` [Qemu-devel] [PATCH v3 8/8] msix: Switch msix_uninit to return void Alex Williamson
2012-06-14 21:31 ` [Qemu-devel] [PATCH v3 0/8] msix: Support specifying offsets, BARs, and capability location Michael S. Tsirkin
2012-06-18 7:06 ` Jan Kiszka
2012-06-18 7:19 ` Michael S. Tsirkin
2012-06-18 9:23 ` Jan Kiszka [this message]
2012-06-18 9:57 ` Michael S. Tsirkin
2012-06-18 10:36 ` Jan Kiszka
2012-06-18 22:37 ` Jan Kiszka
2012-06-18 22:40 ` 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=4FDEF39D.3050503@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=alex.williamson@redhat.com \
--cc=mst@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).