xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Juergen Gross <jgross@suse.com>, Wei Liu <wei.liu2@citrix.com>
Cc: sstabellini@kernel.org, george.dunlap@eu.citrix.com,
	Dongli Zhang <dongli.zhang@oracle.com>,
	tim@xen.org, xen-devel@lists.xen.org, david.vrabel@citrix.com,
	jbeulich@suse.com, andrew.cooper3@citrix.com,
	ian.jackson@eu.citrix.com
Subject: Re: [PATCH v3 1/1] xen: move TLB-flush filtering out into populate_physmap during vm creation
Date: Thu, 8 Sep 2016 16:49:01 +0200	[thread overview]
Message-ID: <1473346141.19612.164.camel@citrix.com> (raw)
In-Reply-To: <07306b9e-9bd5-0276-4df7-ffb1c8c0e792@suse.com>


[-- Attachment #1.1: Type: text/plain, Size: 892 bytes --]

On Thu, 2016-09-08 at 13:19 +0200, Juergen Gross wrote:
> The first scheduling is done via unpausing the domain. Why not
> setting
> the flag to true in that path?
> 
That could be a good idea.

And in general, I'm all for finding a place and/or a state that better
represents the condition of "setting to run this vcpu for the first
time" and set the flag there, rather than re-assigning 1 to an
"already_scheduled" flag each an every time we go through schedule()
(and not for performance and optimization reason).

Which domain_unpause() (or whatever) do you have in mind precisely?

Thanks and Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

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

  reply	other threads:[~2016-09-08 14:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08  5:30 [PATCH v3 1/1] xen: move TLB-flush filtering out into populate_physmap during vm creation Dongli Zhang
2016-09-08  7:19 ` Dario Faggioli
2016-09-08 10:50 ` Wei Liu
2016-09-08 11:01   ` Dario Faggioli
2016-09-08 11:11     ` Wei Liu
2016-09-08 11:19       ` Juergen Gross
2016-09-08 14:49         ` Dario Faggioli [this message]
2016-09-08 14:52           ` Andrew Cooper
2016-09-08 14:28       ` Ian Jackson
2016-09-08 15:36 ` Jan Beulich
2016-09-08 15:53   ` Dario Faggioli
  -- strict thread matches above, loose matches on Subject: below --
2016-09-09  5:37 Dongli Zhang
2016-09-09  7:56 ` Jan Beulich
2016-09-09  9:34   ` Andrew Cooper
2016-09-09  9:46     ` Jan Beulich
2016-09-09  9:52       ` Andrew Cooper

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=1473346141.19612.164.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=dongli.zhang@oracle.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jgross@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).