kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Avi Kivity <avi@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 0/2] KVM: PPC: Support ioeventfd
Date: Wed, 17 Oct 2012 19:23:55 +0200	[thread overview]
Message-ID: <507EE9AB.8070904@suse.de> (raw)
In-Reply-To: <507EC5AF.2080907@redhat.com>

On 10/17/2012 04:50 PM, Avi Kivity wrote:
> On 10/16/2012 04:49 PM, Alexander Graf wrote:
>
>>> If there is a lot of prioritization and/or queuing logic, then yes.  But
>>> what about MSI?  Doesn't that have a direct path?
>> Nope. Well, yes, in a certain special case where the MPIC pushes the
>> interrupt vector on interrupt delivery into a special register. But not
>> for the "normal" case.
> Ok.  The patches are fine then, but would be good to add the PIO check.

Yup, will do as a separate patch.


Alex

      reply	other threads:[~2012-10-17 17:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15 12:02 [PATCH 0/2] KVM: PPC: Support ioeventfd Alexander Graf
2012-10-15 12:02 ` [PATCH 1/2] KVM: Distangle eventfd code from irqchip Alexander Graf
2012-10-16 10:57   ` Avi Kivity
2012-10-16 11:01     ` Alexander Graf
2012-10-15 12:02 ` [PATCH 2/2] KVM: PPC: Support eventfd Alexander Graf
2012-10-16 10:56 ` [PATCH 0/2] KVM: PPC: Support ioeventfd Avi Kivity
2012-10-16 10:59   ` Alexander Graf
2012-10-16 11:01     ` Avi Kivity
2012-10-16 11:06       ` Alexander Graf
2012-10-16 13:47         ` Avi Kivity
2012-10-16 14:49           ` Alexander Graf
2012-10-17 14:50             ` Avi Kivity
2012-10-17 17:23               ` Alexander Graf [this message]

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=507EE9AB.8070904@suse.de \
    --to=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.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).