From: Dario Faggioli <dario.faggioli@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Juergen Gross <JGross@suse.com>,
george.dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
ian.jackson@eu.citrix.com, xen-devel@lists.xen.org,
dgdegra@tycho.nsa.gov
Subject: Re: [PATCH] xen: add hypercall option to temporarily pin a vcpu
Date: Fri, 26 Feb 2016 14:39:02 +0100 [thread overview]
Message-ID: <1456493942.2959.187.camel@citrix.com> (raw)
In-Reply-To: <56D0620A02000078000D6BB6@prv-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 1254 bytes --]
On Fri, 2016-02-26 at 06:32 -0700, Jan Beulich wrote:
> > > > On 26.02.16 at 14:07, <dario.faggioli@citrix.com> wrote:
> > We can argue about that being useful or not, and about it being
> > (potentially) too noisy or not. I personally think it could be
> > useful
> > (it's XENLOG_DEBUG, after all), but I won't oppose getting rid of
> > it...
> > I am just not getting why you're saying "not currently running on
> > pCPU0".
> Oh, you're right, that was too strict - "not being allowed to run
> on CPU0" would be the right description. And indeed that makes
> it look not as noisy (but too much, since during suspend this is
> what one has to expect would happen).
>
Yes, mostly on the ground that it's the intended behavior and (in that
case really) temporary, I'm indeed ok silencing this on suspend.
Since it's pretty independent, I'd prefer this to be done in a separate
patch, together with the resume side, as (AFAIUI) Juergen is planning
to do already.
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: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-26 13:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 16:50 [PATCH] xen: add hypercall option to temporarily pin a vcpu Juergen Gross
2016-02-26 10:39 ` Jan Beulich
[not found] ` <56D0395702000078000D69A6@suse.com>
2016-02-26 11:14 ` Juergen Gross
2016-02-26 11:20 ` Dario Faggioli
2016-02-26 11:43 ` Juergen Gross
2016-02-26 12:39 ` Jan Beulich
2016-02-26 13:07 ` Dario Faggioli
2016-02-26 13:32 ` Jan Beulich
2016-02-26 13:39 ` Dario Faggioli [this message]
[not found] ` <56D0559C02000078000D6AFE@suse.com>
2016-02-26 12:49 ` Juergen Gross
2016-02-26 13:34 ` Jan Beulich
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=1456493942.2959.187.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=JBeulich@suse.com \
--cc=JGross@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.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).