From: Dario Faggioli <dfaggioli@suse.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
Charles Arnold <carnold@suse.com>,
Tomas Mozes <hydrapolic@gmail.com>, Glen <glenbarney@gmail.com>,
George Dunlap <george.dunlap@citrix.com>,
Jan Beulich <jbeulich@suse.com>, Sarah Newman <srn@prgmr.com>,
xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] [PATCH 0/2] xen: credit2: fix vcpu starvation due to too few credits
Date: Fri, 13 Mar 2020 07:19:00 +0100 [thread overview]
Message-ID: <a0d3f6d05a99a18014357cec015504e014f54b5d.camel@suse.com> (raw)
In-Reply-To: <20200312175924.GM24458@Air-de-Roger.citrite.net>
[-- Attachment #1.1: Type: text/plain, Size: 1105 bytes --]
On Thu, 2020-03-12 at 18:59 +0100, Roger Pau Monné wrote:
> On Thu, Mar 12, 2020 at 06:02:03PM +0100, Dario Faggioli wrote:
> > What do you mean with "Which timer does this hardware use" ?
>
> Xen uses a hardware timer (HPET, PMTIMER or PIT IIRC) in order to get
> interrupts at specified times, on my box I see for example:
>
> (XEN) Platform timer is 23.999MHz HPET
>
> You should also see something along those lines.
>
Right. If booted Xen, I see this, which looks fine to me (this is
currently Xen 4.12.2):
# xl dmesg |grep time
(XEN) [00018d6c323bf350] Platform timer is 14.318MHz HPET <===========
(XEN) [ 22.097647] TSC deadline timer enabled
(XEN) [ 23.068865] mwait-idle: lapic_timer_reliable_states 0xffffffff
(XEN) [ 27.316536] mcheck_poll: Machine check polling timer started.
Regards
--
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<<This happens because _I_ choose it to happen!>> (Raistlin Majere)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-03-13 6:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 13:44 [Xen-devel] [PATCH 0/2] xen: credit2: fix vcpu starvation due to too few credits Dario Faggioli
2020-03-12 13:44 ` [Xen-devel] [PATCH 1/2] xen: credit2: avoid vCPUs to ever reach lower credits than idle Dario Faggioli
2020-03-12 13:55 ` Andrew Cooper
2020-03-12 14:40 ` George Dunlap
2020-03-12 15:10 ` Dario Faggioli
2020-03-12 14:58 ` Dario Faggioli
2020-03-12 14:45 ` George Dunlap
2020-03-12 17:03 ` Dario Faggioli
2020-03-12 15:26 ` Jan Beulich
2020-03-12 16:00 ` Jürgen Groß
2020-03-12 16:59 ` Dario Faggioli
2020-03-12 16:11 ` Dario Faggioli
2020-03-12 16:36 ` Jan Beulich
2020-03-12 13:44 ` [Xen-devel] [PATCH 2/2] xen: credit2: fix credit reset happening too few times Dario Faggioli
2020-03-12 15:08 ` [Xen-devel] [PATCH 0/2] xen: credit2: fix vcpu starvation due to too few credits Roger Pau Monné
2020-03-12 17:02 ` Dario Faggioli
2020-03-12 17:59 ` Roger Pau Monné
2020-03-13 6:19 ` Dario Faggioli [this message]
2020-03-12 15:51 ` Jürgen Groß
2020-03-12 16:27 ` Andrew Cooper
2020-03-13 7:26 ` Dario Faggioli
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=a0d3f6d05a99a18014357cec015504e014f54b5d.camel@suse.com \
--to=dfaggioli@suse.com \
--cc=carnold@suse.com \
--cc=george.dunlap@citrix.com \
--cc=glenbarney@gmail.com \
--cc=hydrapolic@gmail.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=roger.pau@citrix.com \
--cc=srn@prgmr.com \
--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).