From: Marcelo Tosatti <mtosatti@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 2/2] kvm: set affinity hint for assigned device msi
Date: Wed, 11 Jan 2012 14:10:00 -0200 [thread overview]
Message-ID: <20120111161000.GA12868@amt.cnet> (raw)
In-Reply-To: <20111017170440.GA8894@redhat.com>
On Mon, Oct 17, 2011 at 07:04:40PM +0200, Michael S. Tsirkin wrote:
> On Mon, Oct 17, 2011 at 02:07:41PM -0200, Marcelo Tosatti wrote:
> > > > Configurations to consider, all common ones used for assigned devices?
> > >
> > > I mean, besides round robin, any other modes that
> > > have an issue? Interrupts can also be multicast,
> > > I think, but we probably don't care what happens
> > > to affinity then, as msi interrupts are probably never
> > > broadcast ...
> >
> > There is also lowest priority, which can be used with MSI.
>
>
> So the following will probably address that comment?
Yes, it does. Patch looks fine.
next prev parent reply other threads:[~2012-01-11 16:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1318358229.git.mst@redhat.com>
2011-10-11 18:38 ` [PATCH RFC 1/2] kvm: pass host irq number to set irq calls Michael S. Tsirkin
2011-10-11 18:38 ` [PATCH RFC 2/2] kvm: set affinity hint for assigned device msi Michael S. Tsirkin
[not found] ` <7458f62a58ad7d4022eefba4333336ba268e4ef9.1318358229.git.mst@redhat.com>
2011-10-13 14:54 ` Marcelo Tosatti
2011-10-16 13:12 ` Michael S. Tsirkin
2011-10-17 10:58 ` Marcelo Tosatti
2011-10-17 13:32 ` Michael S. Tsirkin
2011-10-17 16:07 ` Marcelo Tosatti
2011-10-17 16:14 ` Michael S. Tsirkin
2011-10-17 17:04 ` Michael S. Tsirkin
2012-01-11 16:10 ` Marcelo Tosatti [this message]
2011-10-17 11:09 ` Marcelo Tosatti
2011-10-17 13:35 ` Michael S. Tsirkin
2012-01-12 14:09 ` Avi Kivity
2012-01-15 13:24 ` 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=20120111161000.GA12868@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mst@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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).