xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>, Keir Fraser <keir@xen.org>,
	"Nakajima, Jun" <jun.nakajima@intel.com>,
	"Dong, Eddie" <eddie.dong@intel.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"Xu, Dongxiao" <dongxiao.xu@intel.com>,
	Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH] x86/hvm: implement save/restore for posted interrupts
Date: Fri, 18 Jul 2014 15:58:31 +0200	[thread overview]
Message-ID: <20140718135831.GA10870@aepfle.de> (raw)
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E0AB31DF7@SHSMSX104.ccr.corp.intel.com>

On Thu, Jul 17, Zhang, Yang Z wrote:

> Olaf Hering wrote on 2014-07-17:
> > I can probably do that. And I think initially I just changed
> > lapic_save_regs, which was not enough. I think in the end the reason
> > is that with posted irqs the code paths are different and just
> > having IRR set is not enough.
> It doesn't make sense. PIR is more like a tmp_IRR. All interrupts
> pending in PIR will finally sync to IRR by hardware. In your case, you
> already record it in IRR, it should be enough.  The problem I am
> seeing is that the eoi_exit_bitmap need to be setup correct after
> migration, please try attached patch to see whether it solves your
> problem:

No, this patch does not work for me. Does it work for you?

Olaf

  reply	other threads:[~2014-07-18 13:58 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 15:09 [PATCH] x86/hvm: implement save/restore for posted interrupts Olaf Hering
2014-07-03 15:27 ` Jan Beulich
2014-07-09 11:24 ` Zhang, Yang Z
2014-07-09 21:14   ` Tian, Kevin
2014-07-16 14:28     ` Olaf Hering
2014-07-16 16:11       ` Tian, Kevin
2014-07-17  7:11         ` Olaf Hering
2014-07-17  9:29           ` Zhang, Yang Z
2014-07-18 13:58             ` Olaf Hering [this message]
2014-07-22 23:06               ` Zhang, Yang Z
2014-07-23  8:03                 ` Olaf Hering
2014-07-25 21:38             ` Tian, Kevin
2014-07-28  6:52               ` Olaf Hering
2014-07-29  7:48                 ` Zhang, Yang Z
2014-07-29  8:27                   ` Jan Beulich
2014-08-02 10:59                   ` Olaf Hering
2014-08-04  1:08                     ` Zhang, Yang Z
2014-08-04  7:50                       ` Olaf Hering
2014-08-04  7:57                         ` Zhang, Yang Z
2014-08-05 10:32                           ` Olaf Hering
2014-08-08  0:18                             ` Zhang, Yang Z
2014-09-01  6:44                             ` Zhang, Yang Z
2014-09-18  3:29                             ` Zhang, Yang Z
2014-09-19 13:32                               ` Olaf Hering
2014-09-19 13:39                                 ` Jan Beulich
2014-09-19 17:51                                   ` Andrew Cooper
2014-09-22 22:43                                     ` Tian, Kevin
2014-09-24 16:26                                       ` Malcolm Crossley
2014-09-30 16:19                                 ` Jan Beulich
2014-10-01  8:07                                   ` Olaf Hering
2014-10-01  8:29                                     ` Jan Beulich
2014-10-01 20:13                                       ` Olaf Hering
2014-10-02  6:51                                         ` Jan Beulich
2014-10-02  8:10                                           ` Andrew Cooper
2014-10-02  8:20                                             ` Olaf Hering
2014-10-08  7:37                                         ` Zhang, Yang Z
2014-10-08  7:40                                           ` Olaf Hering
2014-10-08  7:55                                             ` Zhang, Yang Z
2014-10-08  8:28                                           ` Olaf Hering
2014-10-08  8:35                                             ` Zhang, Yang Z
2014-10-08  8:54                                               ` Olaf Hering
2014-10-09  7:24                                                 ` Zhang, Yang Z
2014-10-09  8:41                                                   ` Fabio Fantoni
2014-10-09  8:43                                                     ` Zhang, Yang Z
2014-10-09 12:49                                                       ` Fabio Fantoni
2014-10-09 11:35                                                   ` Malcolm Crossley
2014-10-09 13:19                                                   ` Andrew Cooper
2014-10-10  0:48                                                     ` Zhang, Yang Z
2014-10-09 13:31                                                   ` Olaf Hering
2014-10-09 14:11                                                     ` Olaf Hering
2014-10-10  0:52                                                       ` Zhang, Yang Z
2014-07-25  9:40 ` Jan Beulich
2014-07-25 12:49   ` Tian, Kevin
2014-07-25 13:59     ` Jan Beulich
2014-07-25 21:31       ` Tian, Kevin
2014-07-28  6:46         ` Jan Beulich
2014-07-28  7:52           ` Wu, Feng
2014-07-28  8:17           ` Zhang, Yang Z
2014-07-28  9:02             ` Jan Beulich
2014-07-28  9:50               ` Liuqiming (John)

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=20140718135831.GA10870@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=dongxiao.xu@intel.com \
    --cc=eddie.dong@intel.com \
    --cc=jbeulich@suse.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir@xen.org \
    --cc=kevin.tian@intel.com \
    --cc=xen-devel@lists.xen.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).