Re: [PATCH for review] [69/145] x86_64: Disable DAC on VIA PCI bridges

[Andi Kleen]

On Thursday 10 August 2006 22:55, Muli Ben-Yehuda wrote:

> 
> > Because of several reports that it doesn't work
> > 
> > TBD needs a real confirmation this fixes the problem
> > TBD needs more testing
> 
> Should this go to mainline then?

I've haven't decided yet. I put it out for review for now at least.

I got various reports of the VIA bridges having trouble with DAC over the
years, but usually when I asked for confirmation the reporters disappeared.
I finally did the patch now because with cheap 2GB DIMMs VIA systems
with 4GB (which gives some memory over 4GB) are becomming more common.

But again the last reporters disappeared this time.

I will probably not sent it off before final confirmation again.

> > +static int allow_dac;
> 
> __read_mostly, like the rest?

Ok. Changed

> 
> > +static int bridge_from_vendor(struct device *dev, u16 vendor)
> > +{
> > +#ifdef CONFIG_PCI
> 
> My preference would be to provide two versions of this function, one
> empty (!CONFIG_PCI) and one with the code you have here.


I prefer it this way.

 
> >  int dma_supported(struct device *dev, u64 mask)
> >  {
> >  	if (dma_ops->dma_supported)
> >  		return dma_ops->dma_supported(dev, mask);
> 
> I just checked, no ops has a dma_supported method... should we remove
> it?

The if()? Possible.
 
> >  __init int iommu_setup(char *p)
> >  {
> > @@ -264,6 +302,10 @@ __init int iommu_setup(char *p)
> >  		    iommu_merge = 0;
> >  	    if (!strncmp(p, "forcesac",8))
> >  		    iommu_sac_force = 1;
> > +	    if (!strncmp(p, "allowdac", 8))
> > +		    allow_dac = 1;
> > +	    if (!strncmp(p, "nodac", 5))
> > +		    allow_dac = -1;
> 
> Why <0? we usually set 1 for enabled and 0 for disabled.

For hardware workarounds it is usually best to have three values:

- Force disabled
- Default based on black/white list 
  The black/white list is not active when != 0
- Force enabled

I tend to use -1/0/1 for this. 


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