public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Roger Luethi <rl@hellgate.ch>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] use mmiowb in via-rhine
Date: Wed, 19 Jan 2005 12:29:05 -0800	[thread overview]
Message-ID: <20050119202905.GU12076@waste.org> (raw)
In-Reply-To: <20050119202220.GT12076@waste.org>

On Wed, Jan 19, 2005 at 12:22:20PM -0800, Matt Mackall wrote:
> Use the generic PCI memory barrier. Test-compiled.

Ignore that, doesn't work as I thought. mmiowb prevents write
reordering on multiple CPUs like Altix but doesn't prevent posting.
Perhaps another barrier is needed.
 
> Signed-off-by: Matt Mackall <mpm@selenic.com>
> 
> Index: bk/drivers/net/via-rhine.c
> ===================================================================
> --- bk.orig/drivers/net/via-rhine.c	2005-01-19 12:06:52.283455936 -0800
> +++ bk/drivers/net/via-rhine.c	2005-01-19 12:18:02.536561976 -0800
> @@ -351,9 +351,6 @@
>   * indicator. In addition, Tx and Rx buffers need to 4 byte aligned.
>   */
>  
> -/* Beware of PCI posted writes */
> -#define IOSYNC	do { ioread8(ioaddr + StationAddr); } while (0)
> -
>  static struct pci_device_id rhine_pci_tbl[] =
>  {
>  	{0x1106, 0x3043, PCI_ANY_ID, PCI_ANY_ID, 0, 0, }, /* VT86C100A */
> @@ -596,7 +593,7 @@
>  	void __iomem *ioaddr = rp->base;
>  
>  	iowrite8(Cmd1Reset, ioaddr + ChipCmd1);
> -	IOSYNC;
> +	mmiowb();
>  
>  	if (ioread8(ioaddr + ChipCmd1) & Cmd1Reset) {
>  		printk(KERN_INFO "%s: Reset not complete yet. "
> @@ -1305,7 +1302,7 @@
>  	/* Wake the potentially-idle transmit channel */
>  	iowrite8(ioread8(ioaddr + ChipCmd1) | Cmd1TxDemand,
>  	       ioaddr + ChipCmd1);
> -	IOSYNC;
> +	mmiowb();
>  
>  	if (rp->cur_tx == rp->dirty_tx + TX_QUEUE_LEN)
>  		netif_stop_queue(dev);
> @@ -1339,7 +1336,7 @@
>  		if (intr_status & IntrTxDescRace)
>  			iowrite8(0x08, ioaddr + IntrStatus2);
>  		iowrite16(intr_status & 0xffff, ioaddr + IntrStatus);
> -		IOSYNC;
> +		mmiowb();
>  
>  		if (debug > 4)
>  			printk(KERN_DEBUG "%s: Interrupt, status %8.8x.\n",
> @@ -1602,7 +1599,7 @@
>  		       ioaddr + ChipCmd);
>  		iowrite8(ioread8(ioaddr + ChipCmd1) | Cmd1TxDemand,
>  		       ioaddr + ChipCmd1);
> -		IOSYNC;
> +		mmiowb();
>  	}
>  	else {
>  		/* This should never happen */
> 
> -- 
> Mathematics is the supreme nostalgia of our time.

-- 
Mathematics is the supreme nostalgia of our time.

  reply	other threads:[~2005-01-19 20:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19 20:22 [PATCH] use mmiowb in via-rhine Matt Mackall
2005-01-19 20:29 ` Matt Mackall [this message]
2005-01-19 20:29 ` Dave Jones

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=20050119202905.GU12076@waste.org \
    --to=mpm@selenic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rl@hellgate.ch \
    /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