public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: "Pan\, Jacob jun" <jacob.jun.pan@intel.com>
Cc: "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"H. Peter Anvin" <hpa@linux.intel.com>
Subject: Re: [PATCH 9/9] x86/apic: support moorestown interrupt subsystem
Date: Fri, 26 Jun 2009 16:46:24 -0700	[thread overview]
Message-ID: <m163eieey7.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <43F901BD926A4E43B106BF17856F0755641A47CD@orsmsx508.amr.corp.intel.com> (Jacob jun Pan's message of "Fri\, 26 Jun 2009 16\:24\:22 -0700")

"Pan, Jacob jun" <jacob.jun.pan@intel.com> writes:

>>-----Original Message-----
>>From: Eric W. Biederman [mailto:ebiederm@xmission.com]
>>Sent: Friday, June 26, 2009 12:42 PM
>>To: Pan, Jacob jun
>>Cc: linux-kernel@vger.kernel.org; H. Peter Anvin
>>Subject: Re: [PATCH 9/9] x86/apic: support moorestown interrupt subsystem
>>
>>"Pan, Jacob jun" <jacob.jun.pan@intel.com> writes:
>>
>>>>From 82d64ca4f963d2e205326534aff0c77d9bfa5858 Mon Sep 17 00:00:00 2001
>>> From: Jacob Pan <jacob.jun.pan@intel.com>
>>> Date: Fri, 12 Jun 2009 02:16:05 -0700
>>> Subject: [PATCH] x86/apic: support moorestown interrupt subsystem
>>>
>>> This patch uses platform flags to selectively enable apic related setup
>>> code.
>>>
>>> Since moorestown does not have legacy timer or PIC, the only system
>>> timer irqs are routed via ioapic. Early timer ioapic enabling is also
>>> added to allow boot time timing services.
>>
>>This patch is horribly wrong.   We should not have a moorestown specific
>>hack  we should not do early timer ioapic on everything that supports
>>it which is most x86 machines since apics became common.
>>
> [[JPAN]] maybe I misunderstood. But I am doing the special early timer ioapic
> setup in x86_quirks, so it is not for every platform.
>
>>At which point moorestown support should just be a little work somewhere
>>in the table parsers.
>>
> [[JPAN]] can you elaborate a little? I was hoping to move APIC initialization earlier so that I don't have to have the special treatment for system timer.
> But it seems require early memory allocator.

We have early memory allocators.  And we are not talking super
early.  Just at the point init_IRQ is called.

> [[JPAN]] Moorestown does not have 8259, even IOAPIC is emulated by FW. Are you
> saying we should try to completely separate 8259 instead of use if(8259) here
> and there in the IOAPIC code? T

Yes, completely separate out the 8259.  I believe that complete
separation will come for free if you move the ioapic earlier.

What kind of PIC is native?

Eric

  reply	other threads:[~2009-06-26 23:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26  0:15 [PATCH 9/9] x86/apic: support moorestown interrupt subsystem Pan, Jacob jun
2009-06-26  7:07 ` Ingo Molnar
2009-06-26 13:48   ` Pan, Jacob jun
2009-06-26 17:18   ` Pan, Jacob jun
2009-06-29  2:59     ` Feng Tang
2009-06-29 16:10       ` Len Brown
2009-06-29 16:35         ` Len Brown
2009-06-26 19:41 ` Eric W. Biederman
2009-06-26 23:24   ` Pan, Jacob jun
2009-06-26 23:46     ` Eric W. Biederman [this message]
2009-06-29 18:57       ` Pan, Jacob jun

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=m163eieey7.fsf@fess.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=hpa@linux.intel.com \
    --cc=jacob.jun.pan@intel.com \
    --cc=linux-kernel@vger.kernel.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