cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Rafał Bilski" <rafalbilski@interia.pl>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] Longhaul - There are limits
Date: Mon, 3 Jul 2006 12:52:20 -0400	[thread overview]
Message-ID: <20060703165220.GM14292@redhat.com> (raw)
In-Reply-To: <44A93F07.3020905@interia.pl>

On Mon, Jul 03, 2006 at 06:00:07PM +0200, Rafał Bilski wrote:

 > > It's not unfeasible for an SMP kernel to be run on UP hardware,
 > > (and several distros are shipping SMP kernels as default)
 > > so I'm in two minds about removing the !SMP check, and making it be a
 > > 
 > > 	if (num_online_cpus() > 1)
 > > 		return -ENODEV;
 > > 
 > > in the init routine.
 > > 
 > > Thoughts?
 > > 
 > > 		Dave
 > > 
 > 
 > It is good idea, but I think there should be check for APIC too, 
 > but I don't know how to make it. !X86_UP_APIC is for non SMP 
 > kernels only. It is possible that in this case there will be 
 > SMP kernel running on single processor with APIC enabled. 
 > I don't know much about APIC, but as far I know we are poking 
 > PIC registers direcly and in such case not all interrupts will
 > be disabled.

I wonder if this could be solved with something as trivial as..

	if (cpu_has_apic)
		disable_local_APIC()

	...

	if (cpu_has_apic)
		enable_local_APIC()

We should probably also avoid touching the PIC if we're in APIC mode
with something like..

    if (pic_mode == 1) {
		...
		PIC poking goes here..
	}

(Will also need to EXPORT_SYMBOL(pic_mode) from mpparse.c)

		Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2006-07-03 16:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-03  5:18 [PATCH] Longhaul - There are limits Rafał Bilski
2006-07-03 14:11 ` Dave Jones
2006-07-03 16:00   ` Rafał Bilski
2006-07-03 16:52     ` Dave Jones [this message]
2006-07-03 17:39       ` Rafał Bilski
2006-07-03 18:37       ` Rafał Bilski
2006-07-03 19:14       ` Rafał Bilski
  -- strict thread matches above, loose matches on Subject: below --
2006-07-04 15:50 Rafał Bilski
2006-07-06 19:46 ` Dave Jones

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=20060703165220.GM14292@redhat.com \
    --to=davej@redhat.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=rafalbilski@interia.pl \
    /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