qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/8] msix: Support specifying offsets, BARs, and capability location
Date: Tue, 19 Jun 2012 00:37:13 +0200	[thread overview]
Message-ID: <4FDFAD99.9040800@web.de> (raw)
In-Reply-To: <4FDF04C1.6020804@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 909 bytes --]

On 2012-06-18 12:36, Jan Kiszka wrote:
>>>>> 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
>>
>> Anthony are your ideas for 1.2 timeframe?
> 
> http://wiki.qemu.org/Planning/1.2

How to proceed? Your queue currently contains the caching, my add-on
patches make use of it. I can change them to not do this, but I'd like
to learn the preferred direction first.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2012-06-18 22:37 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
2012-06-18  9:57         ` Michael S. Tsirkin
2012-06-18 10:36           ` Jan Kiszka
2012-06-18 22:37             ` Jan Kiszka [this message]
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=4FDFAD99.9040800@web.de \
    --to=jan.kiszka@web.de \
    --cc=alex.williamson@redhat.com \
    --cc=aliguori@us.ibm.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).