From: Keir Fraser <keir@xen.org>
To: "Li, Jiongxi" <jiongxi.li@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [ PATCH 2/2] xen: enable Virtual-interrupt delivery
Date: Thu, 06 Sep 2012 11:47:09 +0100 [thread overview]
Message-ID: <CC6E3DBD.4ADE4%keir@xen.org> (raw)
In-Reply-To: <D9137FCD9CFF644B965863BCFBEDABB877CBB8@SHSMSX101.ccr.corp.intel.com>
On 06/09/2012 11:00, "Li, Jiongxi" <jiongxi.li@intel.com> wrote:
>>> int hvm_local_events_need_delivery(struct vcpu *v) {
>>> - struct hvm_intack intack = hvm_vcpu_has_pending_irq(v);
>>> + struct hvm_intack intack;
>>> +
>>> + pt_update_irq(v);
>>
>> Why would this change be needed for vAPIC?
> When vcpu is scheduled out, there will be periodic timer interrupt pending for
> injection. Every VMExit is a chance to inject the pending periodic timer
> interrupt on vmx_intr_assist. In no virtual interrupt delivery case, although
> injected timer interrupt is edge trigger, EOI always induces VMExit, pending
> periodic timer can be kept injected till there is no pending left. But in
> virtual interrupt delivery case, only level trigger interrupt can induce
> VMExit, there is much less chance for injecting pending timer interrupt
> through VMExit.
> Adding pt_update_irq here is another code path to inject pending periodic
> timer, but it can't guarantee every pending timer interrupt can be injected.
> Another way is to make every EOI of pending timer interrupt induce VMExit, but
> it may obey the spirit of virtual interrupt delivery - reducing VMExit.
> We have been evaluating that.
Should cause EOI to induce VMExit only when there is more periodic timer
work to be done? That would be better than this hack.
-- Keir
next prev parent reply other threads:[~2012-09-06 10:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 9:30 [ PATCH 2/2] xen: enable Virtual-interrupt delivery Li, Jiongxi
2012-08-31 9:57 ` Keir Fraser
2012-09-06 10:00 ` Li, Jiongxi
2012-09-06 10:40 ` Jan Beulich
2012-09-07 2:08 ` Zhang, Yang Z
2012-09-13 10:13 ` Li, Jiongxi
2012-09-06 10:47 ` Keir Fraser [this message]
2012-09-13 10:12 ` Li, Jiongxi
2012-08-31 12:31 ` Jan Beulich
2012-09-06 10:00 ` Li, Jiongxi
2012-09-06 10:35 ` Jan Beulich
2012-09-06 11:03 ` Christoph Egger
2012-09-06 11:13 ` Jan Beulich
2012-09-13 10:13 ` Li, Jiongxi
2012-09-13 12:01 ` Jan Beulich
2012-09-14 2:31 ` Li, Jiongxi
2012-09-07 0:25 ` Zhang, Yang Z
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=CC6E3DBD.4ADE4%keir@xen.org \
--to=keir@xen.org \
--cc=jiongxi.li@intel.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.