All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Tim Deegan <tim@xen.org>,
	Frediano Ziglio <frediano.ziglio@citrix.com>,
	Keir Fraser <keir@xen.org>, Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH v5 2/5] x86/hpet: Use singe apic vector rather than irq_descs for HPET interrupts
Date: Thu, 6 Mar 2014 14:40:51 +0000	[thread overview]
Message-ID: <531888F3.8000504@citrix.com> (raw)
In-Reply-To: <5318956402000078001218FA@nat28.tlf.novell.com>

On 06/03/14 14:33, Jan Beulich wrote:
>>>> On 05.03.14 at 16:43, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>>  ** If an HPET firing at an appropriate time can be found (up to 20us late), a
>>     CPU will simply request to be woken up with that HPET.
> With exit latencies from C1/C1E in the range of 1...10us, 20us seems
> like a lot of additional latency added here.

Well - it is down from 50us, and also not ahead of time.  Any narrowing
of this window does mean higher contention when fighting over the
remaining hpets.

>
>>  ** Failing finding an appropriate timed HPET, a CPU shall find the soonest
>>     late HPET and program it earlier.
>>  ** Failing any late HPETs, a CPU shall wake up with the latest early HPET it
>>     can find.
> And do what?

Wake up early, in the hope that the hpet arrangements are different when
it next comes to look

>
>>  ** Failing all else, a CPU shall retry to find a free HPET.  This guarantees
>>     that a CPU will never leave hpet_broadcast_enter() without arranging an
>>     interrupt.
> For how long? Indefinitely (i.e. until the wakeup time is reached)?
>
> All without having looked at the details of the patch yet.
>
> Jan
>

Forever.  There are certain sleep paths which cannot be aborted by this
point, so exiting without having set up a wakup is not an option.

A different option would be to make all sleep paths abortable, at which
point my v4 series would be appropriate (plus spinlock bugfix)

~Andrew

  reply	other threads:[~2014-03-06 14:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 15:43 [RFC v5 0/5] HPET fix interrupt logic Andrew Cooper
2014-03-05 15:43 ` [PATCH v5 1/5] x86/hpet: Pre cleanup Andrew Cooper
2014-03-05 15:43 ` [PATCH v5 2/5] x86/hpet: Use singe apic vector rather than irq_descs for HPET interrupts Andrew Cooper
2014-03-06 14:11   ` Tim Deegan
2014-03-06 14:33   ` Jan Beulich
2014-03-06 14:40     ` Andrew Cooper [this message]
2014-03-06 15:38       ` Jan Beulich
2014-03-06 16:08   ` Jan Beulich
2014-03-05 15:43 ` [PATCH v5 3/5] x86/hpet: Post cleanup Andrew Cooper
2014-03-05 15:43 ` [PATCH v5 4/5] x86/hpet: Debug and verbose hpet logging Andrew Cooper
2014-03-05 15:43 ` [PATCH v5 5/5] x86/hpet: debug keyhandlers Andrew Cooper
  -- strict thread matches above, loose matches on Subject: below --
2013-11-14 15:52 [Patch v4 2/5] x86/hpet: Use singe apic vector rather than irq_descs for HPET interrupts Tim Deegan
2013-11-14 16:01 ` [Patch v5 " Andrew Cooper
2013-11-22 15:45   ` Jan Beulich
2013-11-22 16:23     ` Andrew Cooper
2013-11-22 16:49       ` Jan Beulich
2013-11-22 17:38         ` Andrew Cooper
2013-11-25  7:52           ` Jan Beulich
2013-11-25  7:50       ` Jan Beulich
2013-11-26 18:32         ` Andrew Cooper
2013-11-27  8:35           ` Jan Beulich
2013-11-27 22:37             ` Andrew Cooper
2013-11-28 14:33               ` Jan Beulich
2013-11-28 15:06                 ` 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=531888F3.8000504@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=frediano.ziglio@citrix.com \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.