On 02/20/2013 07:31 PM, Simon Jeons wrote: > On 02/20/2013 06:23 PM, Lin Feng wrote: >> Hi Simon, >> >> On 02/20/2013 05:58 PM, Simon Jeons wrote: >>>> The other is that this almost certainly broken for transhuge page >>>> handling. gup returns the head and tail pages and ordinarily this is ok >>> When need gup thp? in kvm case? >> gup just pins the wanted pages(for x86 is 4k size) of user address space in >> memory. >> We can't expect the pages have been allocated for user address space are thp >> or >> normal page. So we need to deal with them and I think it have nothing to do >> with kvm. > > Ok, I'm curious about userspace process call which funtion(will call gup) to > pin pages except make_pages_present? No, userspace process doesn't pin any pages directly but through some syscalls like io_setup() indirectly for other purpose because kernel can't pagefault and it have to keep the page alive. Kernel wants to communicate with the userspace such as to notify some events so it need some sort of buffer that both Kernel and User space can both access, which leads to so called pin pages by gup.
thanks, linfeng -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
