From: Om Narasimhan <om.turyx@gmail.com>
To: Andi Kleen <ak@muc.de>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
linux-kernel@vger.kernel.org, randy.dunlap@oracle.com,
clemens@ladisch.de, vojtech@suse.cz, bob.picco@hp.com
Subject: Re: HPET : Legacy Routing Replacement Enable - 3rd try.
Date: Thu, 26 Oct 2006 23:11:49 -0700 [thread overview]
Message-ID: <4541A325.6030102@gmail.com> (raw)
In-Reply-To: <20061027024238.GC58088@muc.de>
Andi Kleen wrote:
>> 1. HW is LRR capable, HPET ACPI it is 1, timer interrupt is on INT2.
>> Before the fix: Linux cannot get timer interrupts on INT0, goes for ACPI
>> timer.
>
> What ACPI timer? I don't think we have any fallback for int 0.
Sorry, Mea Culpa, I should have written APIC timer.
>
> Not sure what you mean with INT2. Pin2 on ioapic 0 perhaps?
Yes. PIN2 on IOAPIC #0.
>
>> After the fix : Works fine. This is according to hpet spec.
>
> On what exact motherboard was that?
SunFire X4600
>
>> To handle case 3, I removed all references to acpi_hpet_lrr, explained
>> this case in the code and decided to solely rely on the command line
>> parameter for LRR capability. Rational for this approach is ,
>
> This means the systems which you said fixes this would need the command
> line parameter to work?
I feel I do not make things clear enough.
The command line parameter can be avoided entirely if majority of the BIOSes implement LRR routing correctly. I would rewrite the patch to avoid cmdline parameter and according to Andrew Morton's suggestions.
Thanks,
Om.
next prev parent reply other threads:[~2006-10-27 6:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 20:21 HPET : Legacy Routing Replacement Enable - 3rd try Pallipadi, Venkatesh
2006-10-25 21:20 ` Om Narasimhan
2006-10-27 2:42 ` Andi Kleen
2006-10-27 5:57 ` Vojtech Pavlik
2006-10-27 6:29 ` Mika Penttilä
2006-10-27 7:03 ` Vojtech Pavlik
2006-10-27 22:31 ` Om Narasimhan
2006-10-27 6:11 ` Om Narasimhan [this message]
2006-10-27 14:59 ` Andi Kleen
2006-10-28 17:49 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2006-10-25 7:13 Om Narasimhan
2006-10-25 18:53 ` Andi Kleen
2006-10-25 20:09 ` Om Narasimhan
2006-10-25 20:13 ` Om Narasimhan
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=4541A325.6030102@gmail.com \
--to=om.turyx@gmail.com \
--cc=ak@muc.de \
--cc=bob.picco@hp.com \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=venkatesh.pallipadi@intel.com \
--cc=vojtech@suse.cz \
/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