From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86/HPET: don't needlessly set up channels for broadcast
Date: Thu, 27 Sep 2012 16:31:06 +0100 [thread overview]
Message-ID: <CC8A2FCA.400C3%keir.xen@gmail.com> (raw)
In-Reply-To: <506484FA020000780009E43D@nat28.tlf.novell.com>
On 27/09/2012 15:55, "Jan Beulich" <JBeulich@suse.com> wrote:
> When there are more FSB delivery capable HPET channels than CPU cores
> (or threads), we can simply use a dedicated channel per CPU. This
> avoids wasting the resources to handle the excess channels (including
> the pointless triggering of the respective interrupt on each
> wraparound) as well as the ping-pong of the interrupts' affinities
> (when getting assigned to different CPUs).
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Keir Fraser <keir@xen.org>
> --- a/xen/arch/x86/hpet.c
> +++ b/xen/arch/x86/hpet.c
> @@ -369,7 +369,7 @@ static void __init hpet_fsb_cap_lookup(v
> if ( !hpet_events )
> return;
>
> - for ( i = 0; i < num_chs; i++ )
> + for ( i = 0; i < num_chs && num_hpets_used < nr_cpu_ids; i++ )
> {
> struct hpet_event_channel *ch = &hpet_events[num_hpets_used];
> u32 cfg = hpet_read32(HPET_Tn_CFG(i));
> @@ -408,6 +408,9 @@ static struct hpet_event_channel *hpet_g
> if ( num_hpets_used == 0 )
> return hpet_events;
>
> + if ( num_hpets_used >= nr_cpu_ids )
> + return &hpet_events[cpu];
> +
> do {
> next = next_channel;
> if ( (i = next + 1) == num_hpets_used )
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2012-09-27 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 14:55 [PATCH] x86/HPET: don't needlessly set up channels for broadcast Jan Beulich
2012-09-27 15:31 ` Keir Fraser [this message]
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=CC8A2FCA.400C3%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.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).