From: "Jan Beulich" <JBeulich@suse.com>
To: "Xuquan (Euler)" <xuquan8@huawei.com>
Cc: "yang.zhang.wz@gmail.com" <yang.zhang.wz@gmail.com>,
Kevin Tian <kevin.tian@intel.com>,
"Hanweidong (Randy)" <hanweidong@huawei.com>,
"George.Dunlap@eu.citrix.com" <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: [RFC PATCH] x86/apicv: fix RTC periodic timer and apicv issue
Date: Tue, 06 Sep 2016 07:20:35 -0600 [thread overview]
Message-ID: <57CEDEC3020000780010C252@prv-mh.provo.novell.com> (raw)
In-Reply-To: <E0A769A898ADB6449596C41F51EF62C6AA3DAB@SZXEMI506-MBX.china.huawei.com>
>>> On 06.09.16 at 13:22, <xuquan8@huawei.com> wrote:
> On September 06, 2016 5:05 PM, Jan Beulich <JBeulich@suse.com>
>>>>> On 06.09.16 at 10:53, <xuquan8@huawei.com> wrote:
>>> to be honest, my fix is also a tradeoff.. w/ my patch, multiple
>>> pending pt interrupt instances may be combined as one injection of
>>> guest timer interrupt..
>>> but as Yang said, It should be ok since it happens rarely and even
>>> native OS will encounter the same problem if it disable the interrupt for too
>>long.
>>
>>And one OS may properly deal with that situation while another might not. For
>>example, let me remind you of issues the hypervisor had in earlier days when no
>>event/softirq processing happened for long enough, resulting in time
>>management issues due to missed platform timer overflow handling. IOW an OS
>>may avoid that situation by simply not disabling IRQs for too long a time.
>>
> Thanks for your reminding,
> Jan, do you have any suggestion to fix this PT and apicv issue?
> What do you think about Kevin's?
Kevin's suggestion sounded reasonable, iirc, and I'd rely on his
and your better VMX knowledge for the low level details.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-06 13:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 12:58 [RFC PATCH] x86/apicv: fix RTC periodic timer and apicv issue Xuquan (Euler)
2016-08-22 9:38 ` Yang Zhang
2016-08-22 10:52 ` Xuquan (Euler)
2016-08-22 10:35 ` Jan Beulich
2016-08-22 11:40 ` Yang Zhang
2016-08-22 11:52 ` Xuquan (Euler)
2016-08-22 12:01 ` Jan Beulich
2016-08-22 11:41 ` Xuquan (Euler)
2016-08-22 12:04 ` Jan Beulich
2016-08-22 13:09 ` Yang Zhang
2016-08-22 13:18 ` Xuquan (Euler)
2016-08-22 14:57 ` Jan Beulich
2016-08-23 2:11 ` Yang Zhang
2016-08-22 14:02 ` Xuquan (Euler)
2016-08-22 14:07 ` Yang Zhang
2016-08-22 14:15 ` Yang Zhang
2016-08-22 15:11 ` Jan Beulich
2016-08-23 0:40 ` Xuquan (Euler)
2016-08-30 5:58 ` Tian, Kevin
2016-09-06 8:53 ` Xuquan (Euler)
2016-09-06 9:04 ` Jan Beulich
2016-09-06 11:22 ` Xuquan (Euler)
2016-09-06 13:20 ` Jan Beulich [this message]
2016-09-07 0:47 ` Xuquan (Euler)
2016-09-09 3:02 ` Xuquan (Euler)
2016-09-12 7:57 ` Tian, Kevin
2016-09-12 9:07 ` Xuquan (Euler)
2016-09-19 9:25 ` Tian, Kevin
2016-09-20 0:25 ` Xuquan (Euler)
2016-09-20 0:46 ` 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=57CEDEC3020000780010C252@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=hanweidong@huawei.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xen.org \
--cc=xuquan8@huawei.com \
--cc=yang.zhang.wz@gmail.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.