Re: USB mini-summit at LinuxCon Vancouver
From: Marko Ristola
Date: Tue Aug 09 2011 - 11:12:46 EST
I've been thinking about the Kernel driver side.
Mauro and others emailed requirements on Jun or July.
I'm sorry for this spam: maybe you have thought this already.
A linked list of read/write locks as the solution for these protections could be
a base for the general solution. Locks could be accessed either by name "string name"
or by an integer identifier.
The bridge driver would be the container of the lock list.
Lock take / release handles would be changeable by Bridge driver at driver init.
This way bridge could tune the lock taking actions. Sub devices would not have
to know the details of the bridge device.
When implemented as a library ".ko" module, this could be
used by all related kernel drivers. The locking code would be very general.
Maybe adding a lock list into each PCI bus device would solve the device export problem to KVM too.
If some module wouldn't handle the proper locking yet,
it would not deliver the protection, but it would work as before: no regressions.
The library could also be called so that a driver would ask three locks at the same time.
If the driver would get all three locks, it would return success.
If the driver would not get all three locks, it would not lock any of them (with _trylock case).
I don't have time to implement this feature.
Happy meeting for all of you,
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/