qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	Michael Tokarev <mjt@tls.msk.ru>, Avi Kivity <avi@redhat.com>,
	kvm <kvm@vger.kernel.org>,
	qemu-devel@nongnu.org
Subject: [Qemu-devel] plan for device assignment upstream
Date: Mon, 2 Jul 2012 12:18:13 +0300	[thread overview]
Message-ID: <20120702091813.GF8268@redhat.com> (raw)

I've been thinking hard about Jan's patches for device
assignment. Basically while I thought it makes sense
to make all devices: assignment and not - behave the
same and use same APIs for injecting irqs, Anthony thinks there is huge
value in making irq propagation hierarchical and device assignment
should be special cased.

We seem to be at impasse for now and I think merging
assignment ASAP has higher value than this specific
issue. So I fold - let's do it as Anthony and Jan's
original patches proposed.

Jan, can you please rebase and repost your original patchset (against
master, not against pci) that added query for host irqs callbacks for
device assignment? I'll re-review ignoring the idea of using the cache,
with intent apply after I'll drop cache code from the pci branch in a
couple of days (busy otherwise now).

I still intend to rework this later on, but that can wait.

Thanks,

-- 
MST

             reply	other threads:[~2012-07-02  9:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-02  9:18 Michael S. Tsirkin [this message]
2012-07-02  9:29 ` [Qemu-devel] plan for device assignment upstream Avi Kivity
2012-07-02  9:30 ` Jan Kiszka
2012-07-02  9:43   ` Avi Kivity
2012-07-03 19:06     ` Blue Swirl
2012-07-04  8:05       ` Avi Kivity
2012-07-05 18:23         ` Blue Swirl
2012-07-04 10:42     ` Michael S. Tsirkin
2012-07-04 11:24       ` Avi Kivity
2012-07-04 12:54         ` 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=20120702091813.GF8268@redhat.com \
    --to=mst@redhat.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --cc=mtosatti@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).