All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: "Nakajima, Jun" <jun.nakajima@intel.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	xen-devel <xen-devel@lists.xen.org>,
	"keir.xen@gmail.com" <keir.xen@gmail.com>,
	Jan Beulich <JBeulich@suse.com>,
	"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: [Xenhackthon] Virtualized APIC registers - virtual interrupt delivery.
Date: Mon, 15 Jul 2013 10:54:33 -0400	[thread overview]
Message-ID: <20130715145433.GA5521@phenom.dumpdata.com> (raw)
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E0A887B4F@SHSMSX104.ccr.corp.intel.com>

On Thu, Jun 06, 2013 at 03:08:07AM +0000, Zhang, Yang Z wrote:
> Stefano Stabellini wrote on 2013-06-05:
> > On Wed, 5 Jun 2013, Zhang, Yang Z wrote:
> >>>> Or just split the mechanism. Meaning use the event callback for "legacy"
> >>>> type events, and for PCI passthrough devices (where the host supports
> >>>> posted interrupts) just use the baremetal implementation.
> >>>> 
> >>>> That would entail some form of hypercall to identify whether a PCIe device
> >>>> is "posted-interrupt" candidate and if so don't use the event channel
> >>>> mechanism for it.
> >> What you mean "a PCIe device is posted-interrupt candidate"? Do you mean
> > pass-through device will use event channel currently?
> > 
> > On Linux, yes: Linux is going to remap the MSI/MSI-X onto an event
> > channel. Therefore if we want to use posted-interrupts with pass-through
> > devices we would need to disable event channel remapping for them.
> Then we must disable event channel remapping if posted interrupt is used.

When can we expect some of these patches to be posted? Thanks!
> 
> Best regards,
> Yang
> 
> 

  parent reply	other threads:[~2013-07-15 14:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22 16:21 [Xenhackthon] Virtualized APIC registers - virtual interrupt delivery Konrad Rzeszutek Wilk
2013-05-23  7:49 ` Jan Beulich
2013-05-23  8:25   ` Zhang, Yang Z
2013-05-24 14:31     ` Konrad Rzeszutek Wilk
2013-05-27  4:56       ` Zhang, Yang Z
2013-05-27 10:43         ` Stefano Stabellini
2013-05-28 10:51           ` Zhang, Yang Z
2013-05-28 13:22             ` Konrad Rzeszutek Wilk
2013-05-28 16:10             ` Stefano Stabellini
2013-05-29  0:40               ` Zhang, Yang Z
2013-05-29 10:07                 ` Stefano Stabellini
2013-06-03 12:59                   ` Konrad Rzeszutek Wilk
2013-06-03 15:22                     ` Stefano Stabellini
2013-06-05  0:37                       ` Zhang, Yang Z
2013-06-05 12:51                         ` Stefano Stabellini
2013-06-06  3:08                           ` Zhang, Yang Z
2013-06-06 13:02                             ` Konrad Rzeszutek Wilk
2013-07-15 14:54                             ` Konrad Rzeszutek Wilk [this message]
2013-07-16  2:12                               ` Zhang, Yang Z
2013-05-24 14:30   ` Konrad Rzeszutek Wilk

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=20130715145433.GA5521@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir.xen@gmail.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=xiantao.zhang@intel.com \
    --cc=yang.z.zhang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.