From: Chao Gao <chao.gao@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Kevin Tian <kevin.tian@intel.com>, Wei Liu <wei.liu2@citrix.com>,
George Dunlap <george.dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org, Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: [PATCH v4 4/4] Xentrace: add support for HVM's PI blocking list operation
Date: Mon, 10 Jul 2017 08:45:26 +0800 [thread overview]
Message-ID: <20170710004522.GA85738@skl-2s3.sh.intel.com> (raw)
In-Reply-To: <595FC6C00200007800169C26@prv-mh.provo.novell.com>
On Fri, Jul 07, 2017 at 09:37:04AM -0600, Jan Beulich wrote:
>>>> On 07.07.17 at 08:49, <chao.gao@intel.com> wrote:
>> --- a/xen/arch/x86/hvm/vmx/vmx.c
>> +++ b/xen/arch/x86/hvm/vmx/vmx.c
>> @@ -190,7 +190,9 @@ static void vmx_vcpu_block(struct vcpu *v)
>> */
>> ASSERT(old_lock == NULL);
>>
>> - per_cpu(vmx_pi_blocking, v->processor).counter++;
>> + per_cpu(vmx_pi_blocking, pi_cpu).counter++;
>
>Isn't this an unrelated change, which likely would belong into an
>earlier patch (f it's really intended in the first place)?
You are right. this change should be in patch 3/4.
Thanks
Chao
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-07-10 0:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 6:48 [PATCH v4 0/4] mitigate the per-pCPU blocking list may be too long Chao Gao
2017-07-07 6:48 ` [PATCH v4 1/4] VT-d PI: track the vcpu number on pi blocking list Chao Gao
2017-07-07 15:41 ` Jan Beulich
2017-07-10 0:50 ` Chao Gao
2017-07-21 15:04 ` George Dunlap
2017-07-07 6:48 ` [PATCH v4 2/4] x86/vcpu: track hvm vcpu number on the system Chao Gao
2017-07-07 15:42 ` Jan Beulich
2017-07-07 6:48 ` [PATCH v4 3/4] VT-d PI: restrict the vcpu number on a given pcpu Chao Gao
2017-07-07 15:57 ` Jan Beulich
2017-07-10 1:17 ` Chao Gao
2017-07-10 9:36 ` Jan Beulich
2017-07-10 11:42 ` Chao Gao
2017-07-21 15:43 ` George Dunlap
2017-07-07 6:49 ` [PATCH v4 4/4] Xentrace: add support for HVM's PI blocking list operation Chao Gao
2017-07-07 15:37 ` Jan Beulich
2017-07-10 0:45 ` Chao Gao [this message]
2017-07-21 16:26 ` George Dunlap
2017-07-28 8:23 ` Chao Gao
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=20170710004522.GA85738@skl-2s3.sh.intel.com \
--to=chao.gao@intel.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=wei.liu2@citrix.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 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).