linux-kernel - Re: [PATCH 0/4] PCI: fix cardbus and sriov regressions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 25 Jun 2011 13:35:36 +0200
From:	Oliver Hartkopp <socketcan@...tkopp.net>
To:	Ram Pai <linuxram@...ibm.com>, yinghai@...nel.org
CC:	jbarnes@...tuousgeek.org,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/4] PCI: fix cardbus and sriov regressions

On 24.06.2011 21:29, Ram Pai wrote:
> On Thu, Jun 23, 2011 at 04:55:06PM +0200, Oliver Hartkopp wrote:
>> Hello RP,
>>
>> unfortunately i noticed the discussion on linux-kernel ML a bit late, as i did
>> not subscribe it due to the traffic.
> 
> sorry, did not see this mail earlier.
> 
> 
>>>>> When comparing the logs with mgdiff, i found
>>>>>
>>>>> in revered:
>>>>>
>>>>> pci_bus 0000:04: resource 0 [io  0x2000-0x20ff]
>>>>> pci_bus 0000:04: resource 1 [io  0x2400-0x24ff]
>>>>>
>>>>> in the fixed version (4 patches)
>>>>>
>>>>> pci_bus 0000:04: resource 0 [io  0x2400-0x24ff]
>>>>> pci_bus 0000:04: resource 1 [io  0x2001-0x2100]
>>
>> Did you get further with the unusual alignment?
> 
> No. i was thinking this alignment  should be ok, since that cardbus resource
> has to be SIZE aligned and not START aligned.
> 
> However if it is not acceptable, i will figure out a way
> to get it aligned on the right boundaries.

I'm not sure how drivers expect to access the register layouts of their
specific hardware. E.g. if you have a 32-bit register at the beginning of the
io resource and the driver accesses this with a 32-bit write operation, the
misalignment would be handled (by the CPU) very expensive at runtime, which is
definitely a big drawback in performance. I know the networking people
re-arranging structs to get less cycles in accessing data structures ...

I tried to understand the reason for the original commit in 3.0.0-rc1 that
broke my system - very ambitious :-)

But IMHO you should meet analogue starting boundaries as we had before to make
sure that you don't brake things on machines that did not show up yet.

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