archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <>
To: Linus Torvalds <>
Cc: lkml <>
Subject: [BK PATCHES] misc merges
Date: Sat, 22 Mar 2003 17:27:00 -0500	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 412 bytes --]

The main thing here is the PCI cacheline size for, for the PCI MWI 
mini-API (that I added).  We need runtime, not compile-time, CPU 
cacheline size detection due to generic vendor kernels.

As IvanK notes, this is a conservative "just-the-fix" change.  A more 
aggressive change is pending later on, that will move cacheline size 
fixups elsewhere (most likely pci_enable_device, but possibly 

[-- Attachment #2: misc-2.5.txt --]
[-- Type: text/plain, Size: 1395 bytes --]

Linus, please do a

	bk pull bk://

This will update the following files:

 arch/i386/pci/common.c   |   10 +++++++++
 drivers/char/hw_random.c |    3 +-
 drivers/pci/pci.c        |   48 +++++++++++++++++++++++------------------------
 3 files changed, 36 insertions(+), 25 deletions(-)

through these ChangeSets:

<> (03/03/22 1.1202)
   [hw_random] fix amd x86-64 RNG pci id
   Contributed by Andi Kleen

<> (03/03/22 1.1201)
   [PATCH] PCI MWI cacheline size fix
   This is rather conservative variant of previous patch:
   - no changes required for drivers or architectures with HAVE_ARCH_PCI_MWI;
   - do respect BIOS settings: if the cacheline size is multiple
     of that we have expected, assume that this is on purpose;
   - assume cacheline size of 32 bytes for all x86s except K7/K8 and P4.
     Actually it's good for 386/486s as quite a few PCI devices do not support
     smaller values.
   If you all are fine with it, I can make a 2.4 counterpart.
   As for more aggressive changes: I'd prefer to wait until pending
   stuff from rmk and myself gets in and the whole thing stabilizes.
   Then we can start fine tuning of MWI, FBB, latency timers and so on.

<> (03/03/20 1.1101.23.1)
   [hw_random] add AMD x86-64 pci id
   Contributed by Andi Kleen

             reply	other threads:[~2003-03-22 22:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-22 22:27 Jeff Garzik [this message]
2003-04-26  4:17 [BK PATCHES] misc merges Jeff Garzik

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).