mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Jiang Liu <jiang.liu@linux.intel.com>
Cc: Feng Wu <feng.wu@intel.com>,
	mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [v4 1/3] genirq: Introduce irq_set_vcpu_affinity() to target an interrupt to a VCPU
Date: Wed, 13 May 2015 23:03:44 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1505132302540.4225@nanos> (raw)
In-Reply-To: <555306C9.6040405@linux.intel.com>


On Wed, 13 May 2015, Jiang Liu wrote:

> On 2015/4/30 15:06, Feng Wu wrote:
> > With Posted-Interrupts support in Intel CPU and IOMMU, an external
> > interrupt from assigned-devices could be directly delivered to a
> > virtual CPU in a virtual machine. Instead of hacking KVM and Intel
> > IOMMU drivers, we propose a platform independent interface to target
> > an interrupt to a specific virtual CPU in a virtual machine, or set
> > virtual CPU affinity for an interrupt.
> > 
> > By adopting this new interface and the hierarchy irqdomain, we could
> > easily support posted-interrupts on Intel platforms, and also provide
> > flexible enough interfaces for other platforms to support similar
> > features.
> > 
> > Here is the usage scenario for this interface:
> > Guest update MSI/MSI-X interrupt configuration
> >         -->QEMU and KVM handle this
> >         -->KVM call this interface (passing posted interrupts descriptor
> >            and guest vector)
> >         -->irq core will transfer the control to IOMMU
> >         -->IOMMU will do the real work of updating IRTE (IRTE has new
> >            format for VT-d Posted-Interrupts)
> 
> Hi Thomas,
> 	Any comments or suggestions about this abstraction interface?

It's on my review list...

  reply	other threads:[~2015-05-13 21:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30  7:06 [v4 0/3] prerequisite changes for VT-d posted-interrupts Feng Wu
2015-04-30  7:06 ` [v4 1/3] genirq: Introduce irq_set_vcpu_affinity() to target an interrupt to a VCPU Feng Wu
2015-05-13  8:09   ` Jiang Liu
2015-05-13 21:03     ` Thomas Gleixner [this message]
2015-05-14  1:04       ` Wu, Feng
2015-05-15 13:18   ` Thomas Gleixner
2015-05-18  2:42     ` Wu, Feng
2015-04-30  7:06 ` [v4 2/3] x86, irq: Implement irq_set_vcpu_affinity for pci_msi_ir_controller Feng Wu
2015-05-15 13:19   ` Thomas Gleixner
2015-04-30  7:06 ` [v4 3/3] x86, irq: Define a global vector for VT-d Posted-Interrupts Feng Wu
2015-05-15 13:27   ` Thomas Gleixner
2015-05-18  2:44     ` Wu, Feng
2015-05-07  2:05 ` [v4 0/3] prerequisite changes for VT-d posted-interrupts Wu, Feng

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=alpine.DEB.2.11.1505132302540.4225@nanos \
    --to=tglx@linutronix.de \
    --cc=feng.wu@intel.com \
    --cc=hpa@zytor.com \
    --cc=jiang.liu@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    /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

all inboxes | Powered by JetHome®