xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Chao Gao <chao.gao@intel.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Tim Deegan <tim@xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	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, Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v2 2/5] vcpu: track hvm vcpu number on the system
Date: Fri, 12 May 2017 16:23:42 +0800	[thread overview]
Message-ID: <20170512082341.GA17576@skl-2s3.sh.intel.com> (raw)
In-Reply-To: <20170511113737.jr2vft2hryz2uoz3@citrix.com>

On Thu, May 11, 2017 at 12:37:37PM +0100, Wei Liu wrote:
>On Thu, May 11, 2017 at 12:35:11PM +0100, Wei Liu wrote:
>> On Thu, May 11, 2017 at 02:04:09PM +0800, Chao Gao wrote:
>> > This number is used to calculate how many hvm vcpu on a pcpu on average.
>> > 
>> > Signed-off-by: Chao Gao <chao.gao@intel.com>
>> > ---
>> >  xen/common/domain.c     | 8 ++++++++
>> >  xen/include/xen/sched.h | 2 ++
>> >  2 files changed, 10 insertions(+)
>> > 
>> > diff --git a/xen/common/domain.c b/xen/common/domain.c
>> > index b22aacc..d433d9e 100644
>> > --- a/xen/common/domain.c
>> > +++ b/xen/common/domain.c
>> > @@ -71,6 +71,9 @@ struct vcpu *idle_vcpu[NR_CPUS] __read_mostly;
>> >  
>> >  vcpu_info_t dummy_vcpu_info;
>> >  
>> > +/* how many hvm vcpu on this system? */
>> > +atomic_t num_hvm_vcpus;
>> > +
>> 
>> This is x86 specific and should go to x86/domain.c
>
>... as with all the code that manipulates it. I'm sure you can find the
>appropriate places like arch_initialise/destroy_vcpu.

Agree. I could make things better if thinking more about it.

Thanks
Chao

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-05-12  8:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11  6:04 [PATCH v2 0/5] mitigate the per-pCPU blocking list may be too long Chao Gao
2017-05-11  6:04 ` [PATCH v2 1/5] xentrace: add TRC_HVM_PI_LIST_ADD Chao Gao
2017-05-15  1:33   ` Tian, Kevin
2017-05-15  8:57     ` Chao Gao
2017-05-15 15:14   ` George Dunlap
2017-05-11  6:04 ` [PATCH v2 2/5] vcpu: track hvm vcpu number on the system Chao Gao
2017-05-11 11:35   ` Wei Liu
2017-05-11 11:37     ` Wei Liu
2017-05-12  8:23       ` Chao Gao [this message]
2017-05-11  6:04 ` [PATCH v2 3/5] VT-d PI: restrict the vcpu number on a given pcpu Chao Gao
2017-05-15  5:24   ` Tian, Kevin
2017-05-15  9:27     ` Chao Gao
2017-05-15 15:48   ` George Dunlap
2017-05-15 16:13     ` Chao Gao
2017-05-11  6:04 ` [PATCH v2 4/5] VT-d PI: Adding reference count to pi_desc Chao Gao
2017-05-15 14:42   ` George Dunlap
2017-05-11  6:04 ` [PATCH v2 5/5] VT-d PI: Don't add vCPU to PI blocking list for a case 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=20170512082341.GA17576@skl-2s3.sh.intel.com \
    --to=chao.gao@intel.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --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).