From: Jan Beulich <firstname.lastname@example.org> To: "Roger Pau Monné" <email@example.com> Cc: "firstname.lastname@example.org" <email@example.com>, Andrew Cooper <firstname.lastname@example.org>, Wei Liu <email@example.com> Subject: Re: [PATCH v4 2/3] x86/time: yield to hyperthreads after updating TSC during rendezvous Date: Wed, 21 Apr 2021 11:57:23 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <YH76RJTqvwYmvXu+@Air-de-Roger> On 20.04.2021 17:59, Roger Pau Monné wrote: > On Thu, Apr 01, 2021 at 11:54:27AM +0200, Jan Beulich wrote: >> Since we'd like the updates to be done as synchronously as possible, >> make an attempt at yielding immediately after the TSC write. >> >> Signed-off-by: Jan Beulich <email@example.com> > > Reviewed-by: Roger Pau Monné <firstname.lastname@example.org> Thanks. > Did you observe any difference with the pause inserted? I wouldn't even know how to measure it precisely enough. So - no, I haven't. In fact ... > I wonder whether that's enough to give a chance the hyperthread to > also perform the TSC write. In any case there's no harm from it > certainly. ... I have an inquiry pending with Intel as to better (more reliable) ways to yield, for quite a bit longer than the 8259 one, yet with the same lack of any outcome so far. Until then it really is going to be no more than "make an attempt", as said in the commit message. Jan
next prev parent reply other threads:[~2021-04-21 9:57 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-01 9:53 [PATCH v4 0/3] x86/time: calibration rendezvous adjustments Jan Beulich 2021-04-01 9:54 ` [PATCH v4 1/3] x86/time: latch to-be-written TSC value early in rendezvous loop Jan Beulich 2021-04-20 15:44 ` Roger Pau Monné 2021-04-01 9:54 ` [PATCH v4 2/3] x86/time: yield to hyperthreads after updating TSC during rendezvous Jan Beulich 2021-04-20 15:59 ` Roger Pau Monné 2021-04-21 9:57 ` Jan Beulich [this message] 2021-04-01 9:55 ` [PATCH v4 3/3] x86/time: avoid reading the platform timer in rendezvous functions Jan Beulich 2021-04-20 16:12 ` Roger Pau Monné 2021-04-21 10:06 ` Jan Beulich 2021-04-29 9:32 ` Jan Beulich 2021-04-29 12:48 ` Roger Pau Monné 2021-04-29 12:53 ` Roger Pau Monné 2021-04-29 13:51 ` Jan Beulich 2021-04-15 9:54 ` Ping: [PATCH v4 0/3] x86/time: calibration rendezvous adjustments 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v4 2/3] x86/time: yield to hyperthreads after updating TSC during rendezvous' \ /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
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).