Re: [PATCH] lspci: Indicate if the OS / kernel go out-of-sync on BAR

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello!

> I don't disagree; that does sound like it could be useful.  I just
> don't know the best way to accomplish it.  Seems like you'd have to do
> something in resource_show() to re-read the BAR and validate the
> cache.  I don't know what you do if you find that it's invalid.

I also do not see how to do it in a reasonably simple way.

I checked lspci and it turned out that it already add a "[virtual]"
marker in cases when the BAR is zero (which was this case -- am I right?)
and the kernel reports a non-zero address.

However, it turned out that the check is never triggered on I/O regions,
because the BAR contains a non-zero type bit.

I have modified the check to take into account just the address part
of the BAR. You can check it in the master branch.

				Martin



[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux