public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Panetta <m.panetta@wegener.com>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APIC priorities, can they be changed?
Date: Thu, 15 Feb 2007 14:57:06 -0500	[thread overview]
Message-ID: <45D4BB12.1050205@wegener.com> (raw)
In-Reply-To: <fc.3b9aca006fe2a09c3b9aca00cb2296f3.fc598b@wegener.com>

linux-os (Dick Johnson) wrote:
>
> On Thu, 15 Feb 2007, Mike Panetta wrote:
>
> > I am not on the list (corperate email sucks) so please CC any replies to
> > me.  Thanks.
[snip]
> > I have seen the preempt patches, but they touch a lot of files, and we
> > have gone through testing with the 2.6.16.19 kernel and do not wish to
> > change, and we cannot find a version of the patch for this kernel. Is
> > there something smaller/simpler I can do?  My understanding is the
> > priority in the APIC is set in software via the interrupt vector number
> > (higher numbers have lower priority) is this true?  If so, how hard
> > would it be for me to just change the vector numbers around?
> >
[snip]
> > Thanks,
> > Mike
>
> Can't you muck with the BIOS settings? That's where the primary
> hardware gets 'connected'.
>

I did try that.  The BIOS only allows me to either allocate an IRQ to be 
a PCI interrupt, or reserve it (for what I have no idea).  The IRQ's 
listed in the BIOS are also different from the ones Linux sees.  I think 
the BIOS is seeing the XT-PIC IRQ numbers and Linux is seeing the APIC 
numbers.  For example the little bios blurb that prints before the 
system boots says the USB controller I am interested in is 
assigned/using IRQ 10, Linux sees it using IRQ 18.

I have found that I can keep Linux from using the APIC by disabling it 
with a kernel command line switch, but that does not help, it just makes 
Linux use the XT-PIC instead of the IO-APIC to do IRQ routing.

So I guess I'm back to my original question of  'Would changing the 
vector numbers do what I want?' and if the answer is 'yes', how would I 
do it?

Thanks,
Mike

>
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.6.16.24 on an i686 machine (5592.61 BogoMips).
> New book: http://www.AbominableFirebug.com/
> _
> \x1a\x04
>
> ****************************************************************
> The information transmitted in this message is confidential and may be 
> privileged.  Any review, retransmission, dissemination, or other use 
> of this information by persons or entities other than the intended 
> recipient is prohibited.  If you are not the intended recipient, 
> please notify Analogic Corporation immediately - by replying to this 
> message or by sending an email to DeliveryErrors@analogic.com 
> <mailto:DeliveryErrors@analogic.com> - and destroy all copies of this 
> information, including any attachments, without reading or disclosing 
> them.
>
> Thank you.
>


  parent reply	other threads:[~2007-02-15 19:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 18:29 APIC priorities, can they be changed? Mike Panetta
2007-02-15 18:55 ` linux-os (Dick Johnson)
     [not found] ` <fc.3b9aca006fe2a09c3b9aca00cb2296f3.fc598b@wegener.com>
2007-02-15 19:57   ` Mike Panetta [this message]
2007-02-16 16:18     ` Florian Schmidt

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=45D4BB12.1050205@wegener.com \
    --to=m.panetta@wegener.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    /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