From: Dario Faggioli <dario.faggioli@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Dongli Zhang <dongli.zhang@oracle.com>
Cc: tim@xen.org, sstabellini@kernel.org, wei.liu2@citrix.com,
george.dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
ian.jackson@eu.citrix.com, xen-devel@lists.xen.org,
david.vrabel@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 17:53:46 +0200 [thread overview]
Message-ID: <1473350026.19612.170.camel@citrix.com> (raw)
In-Reply-To: <57D1A188020000780010D3E8@prv-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 1400 bytes --]
On Thu, 2016-09-08 at 09:36 -0600, Jan Beulich wrote:
> >
> > >
> > > >
> > > > On 08.09.16 at 07:30, <dongli.zhang@oracle.com> wrote:
> > --- a/xen/include/xen/sched.h
> > +++ b/xen/include/xen/sched.h
> > @@ -474,6 +474,9 @@ struct domain
> > unsigned int guest_request_enabled : 1;
> > unsigned int guest_request_sync : 1;
> > } monitor;
> > +
> > + /* set to 1 the first time this domain gets scheduled. */
> > + bool_t already_scheduled;
> Did you go through and check that there is nothing this information
> can already get derived from? I can't immediately point you at
> anything, but it feels like there should.
>
Indeed. And if there isn't and we need to do add our own flagging,
isn't there a better way and place where to put it (e.g., what Juergen
and Andrew are hinting at)?
> And if indeed there isn't,
> then - to extend on someone else's comments (I think it was Dario)
> - please use plain bool in new additions.
>
It's Wei that commented about bool-s use in the patch. :-)
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
next prev parent reply other threads:[~2016-09-08 15:53 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
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 [this message]
-- 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=1473350026.19612.170.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=JBeulich@suse.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=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).