lkml.org 
[lkml]   [2000]   [Oct]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: IRQ affinity vs. MTRRs, was Re: 36 bit MTRRs, Re: test10-pre1 problems on 4-way SuperServer8050
On 12 Oct 2000, David Wragg wrote:

> Boszormenyi Zoltan <zboszor@externet.hu> writes:
> > I came up with an idea. The MTRRs are per-cpu things.
> > Ingo Molnar's IRQ affinity code helps binding certain
> > IRQ sources to certain CPUs.
>
> They are implemented as per-cpu things but the Intel manuals say that
> all cpus should have the same MTRR settings. They also give
> pseudo-code for how to update them on an SMP system, which mtrr.c
> follows.
>
> If the BIOS has set them up differently at boot time, mtrr.c will
> complain and copy the MTRR settings of CPU0 to the others.

Yes, I read the Intel manuals and I know how the mtrr driver works.

The idea is that when it is sure that _only one_ (or some) CPU will access
a PCI card's mmio area then only that CPU's (those CPUs') MTRRs needs to
contain an entry for that area.

Although there are (must be) common MTRR entries for the main memory
and the commonly accessed mmio register areas.

The idea came because fiddling with MTRRs quickly revaled that
only 8 variable ones exist.

Regards,
Zoltan Boszormenyi

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:41    [W:0.107 / U:3.260 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site