On Wed, Nov 16, 2016 at 11:51 AM, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote: > The MMC/SD block core request processing thread is taking a > semaphore in the request processing section and the same > semaphore is taken around suspend/resume operations. > > The purpose of the semaphore is to block any request from being > issued to the MMC/SD host controllers when the system is > suspended. A semaphore is used in place of a mutex since the > calls are coming from different threads. > > This construction predates the kernel thread freezer mechanism: > we can easily replace the semaphore by instead activating the > freezer with set_freezable() and call try_to_freeze() instead > of the up(); schedule(); down(); construction that is devised > to let the suspend/resume calls get in and grab the semaphore. > > Tested with a few suspend/resume to memory cycles on the Ux500 > when doing intense dd operations in the background: the > thread thaws and resumes operation after resume. Well, we had a session at the KS regarding usage of the freezer on kernel threads and the conclusion was to get rid of that (as opposed to freezing user space, which is necessary IMO). So this change would go in the opposite direction. :-) Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
