mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: David Brownell <david-b@pacbell.net>
Cc: Anton Blanchard <anton@samba.org>,
	Jeff Garzik <jgarzik@pobox.com>,
	linux-kernel@vger.kernel.org
Subject: Re: pci_set_mwi() ... why isn't it used more?
Date: Thu, 30 Jan 2003 19:59:44 +0300	[thread overview]
Message-ID: <20030130195944.A4966@jurassic.park.msu.ru> (raw)
In-Reply-To: <3E3951E3.7060806@pacbell.net>; from david-b@pacbell.net on Thu, Jan 30, 2003 at 08:25:07AM -0800

On Thu, Jan 30, 2003 at 08:25:07AM -0800, David Brownell wrote:
> At least on 2.5.59, the pci_generic_prep_mwi() code doesn't check
> for that type of error:  it just writes the cacheline size, and
> doesn't verify that setting it worked as expected.  Checking for
> that kind of problem would make it safer to call pci_set_mwi() in
> such cases ... e.g. using it on a P4 with 128 byte L1 cachelines
> would fail cleanly, while on an Athlon (64 byte L1) it might work
> (depending in which top bits are unusable).

Hmm, what happens if you boot the kernel configured for 80386
on P4 and enable MWI?

Ivan.

  reply	other threads:[~2003-01-30 16:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-20 18:41 David Brownell
2003-01-20 19:00 ` Jeff Garzik
2003-01-20 19:37   ` David Brownell
2003-01-30 13:52     ` Anton Blanchard
2003-01-30 16:25       ` David Brownell
2003-01-30 16:59         ` Ivan Kokshaysky [this message]
2003-01-30 18:35           ` David Brownell
2003-01-30 23:34             ` Ivan Kokshaysky
2003-01-31  0:11               ` Jeff Garzik
2003-01-31  0:51               ` David Brownell

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=20030130195944.A4966@jurassic.park.msu.ru \
    --to=ink@jurassic.park.msu.ru \
    --cc=anton@samba.org \
    --cc=david-b@pacbell.net \
    --cc=jgarzik@pobox.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

all inboxes | Powered by JetHome®