All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Dmitry Rockosov <rockosov@gmail.com>,
	kevin.tian@intel.com, jun.nakajima@intel.com
Cc: Xen-devel <xen-devel@lists.xen.org>
Subject: Re: Virtual Interrupt Delivery
Date: Wed, 1 Mar 2017 15:35:36 -0500	[thread overview]
Message-ID: <20170301203536.GF8577@char.us.ORACLE.com> (raw)
In-Reply-To: <CAKkXUyoR7+oVugNrHjP_qCkGTGxE+7yXppBdX3hxJR_L8ioWww@mail.gmail.com>

On Mon, Feb 27, 2017 at 09:13:29PM +0300, Dmitry Rockosov wrote:
> Hi guys,
> 
> Do you know when *recognized* Virtual Interrupt on VM-Entry will be
> delivered if Virtual-Interrupt Delivery is enabled and interrupt delivery
> is blocking by STI?

This sounds like a good question to the Intel maintainers, CC-ing them.

> 
> Previously, VMM used Interrupt-Window, but as I see in XEN code,
> Interrupt-Window
> is not used when Virtual Interrupt Delivery is enabled.

Right, the Intel SDM has a whole section about that.
> 
> Does it mean, we will get Virtual Interrupt on the next VM-entry?

By my understanding of the Intel SDM it depends on whether the
vector is one of those that the CPU can inject without involving
the VMM.

I would recommend you read the Intel SDM - the answer may be right
there.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-03-01 20:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27 18:13 Virtual Interrupt Delivery Dmitry Rockosov
2017-03-01 20:35 ` Konrad Rzeszutek Wilk [this message]
2017-03-02  6:27   ` Tian, Kevin

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=20170301203536.GF8577@char.us.ORACLE.com \
    --to=konrad.wilk@oracle.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=rockosov@gmail.com \
    --cc=xen-devel@lists.xen.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 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.