From: "Jan Beulich" <JBeulich@suse.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Yang Z Zhang <yang.z.zhang@intel.com>,
Kevin Tian <kevin.tian@intel.com>,
Eddie Dong <eddie.dong@intel.com>,
Jun Nakajima <jun.nakajima@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86/hvm: implement save/restore for posted interrupts
Date: Tue, 30 Sep 2014 17:19:08 +0100 [thread overview]
Message-ID: <542AF41C020000780003B2EC@mail.emea.novell.com> (raw)
In-Reply-To: <20140919133227.GA2611@aepfle.de>
>>> On 19.09.14 at 15:32, <olaf@aepfle.de> wrote:
> On Thu, Sep 18, Zhang, Yang Z wrote:
>
>> Zhang, Yang Z wrote on 2014-09-01:
>> > Zhang, Yang Z wrote on 2014-08-08:
>> >> Can you tell how you reproduce it? I am following the steps you told
>> >> me previously, but I cannot reproduce it with this fixing.
>> > Any update on this?
>> Ping again.
>
> I will have a look at this issue next week.
Any update here? It would really be nice to get this settled,
considering for how long this has been pending. Yet I think without
Intel having a way to repro we're not going to make any progress.
Jan
next prev parent reply other threads:[~2014-09-30 16:19 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
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 [this message]
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=542AF41C020000780003B2EC@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=eddie.dong@intel.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=olaf@aepfle.de \
--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).