From: Dario Faggioli <dario.faggioli@citrix.com>
To: Stefano Stabellini <sstabellini@kernel.org>, julien.grall@arm.com
Cc: xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3] xen/arm: introduce vwfi parameter
Date: Wed, 1 Mar 2017 12:50:42 +0100 [thread overview]
Message-ID: <1488369042.5548.131.camel@citrix.com> (raw)
In-Reply-To: <1488316334-20434-1-git-send-email-sstabellini@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 1834 bytes --]
On Tue, 2017-02-28 at 13:12 -0800, Stefano Stabellini wrote:
> --- a/docs/misc/xen-command-line.markdown
> +++ b/docs/misc/xen-command-line.markdown
> @@ -1638,6 +1638,20 @@ Note that if **watchdog** option is also
> specified vpmu will be turned off.
> As the virtualisation is not 100% safe, don't use the vpmu flag on
> production systems (see http://xenbits.xen.org/xsa/advisory-163.html
> )!
>
> +### vwfi
> +> `= trap | native
> +
> +> Default: `trap`
> +
> +WFI is the ARM instruction to "wait for interrupt". WFE is similar
> and
> +means "wait for event". This option, which is ARM specific, changes
> the
> +way guest WFI and WFE are implemented in Xen. By default, Xen traps
> both
> +instructions. In the case of WFI, Xen blocks the guest vcpu; in the
> case
> +of WFE, Xen yield the guest vcpu. When setting vwfi to `native`, Xen
> +doesn't trap either instruction, running them in guest context.
> Setting
> +vwfi to `native` reduces irq latency, but leads to suboptimal
> scheduling
> +decisions.
> +
These last few words sounds a bit generic to me. They may alarm people
and discourage using 'native', even when it is actually ok.
Being a bit more specific, although without going into too much
technical detail, seems worth to me.
So, how about something like:
"Using `native` reduces irq latency significantly. It can also lead to
suboptimal scheduling decisions and affect performance, but only when
the system is oversubscribed (i.e., there are, in total, more vCPUs
than pCPUs)."
?
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:[~2017-03-01 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 21:12 [PATCH v3] xen/arm: introduce vwfi parameter Stefano Stabellini
2017-03-01 11:50 ` Dario Faggioli [this message]
2017-03-01 19:39 ` Stefano Stabellini
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=1488369042.5548.131.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).