| 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
| ||
|
Date: Tue, 3 Nov 2009 12:32:50 -0200 From: Marcelo Tosatti <mtosatti@...hat.com> To: Gleb Natapov <gleb@...hat.com> Cc: kvm@...r.kernel.org, linux-mm@...ck.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 03/11] Handle asynchronous page fault in a PV guest. On Tue, Nov 03, 2009 at 04:25:33PM +0200, Gleb Natapov wrote: > On Tue, Nov 03, 2009 at 12:14:23PM -0200, Marcelo Tosatti wrote: > > On Sun, Nov 01, 2009 at 01:56:22PM +0200, Gleb Natapov wrote: > > > Asynchronous page fault notifies vcpu that page it is trying to access > > > is swapped out by a host. In response guest puts a task that caused the > > > fault to sleep until page is swapped in again. When missing page is > > > brought back into the memory guest is notified and task resumes execution. > > > > Can't you apply this to non-paravirt guests, and continue to deliver > > interrupts while waiting for the swapin? > > > > It should allow the guest to schedule a different task. > But how can I make the guest to not run the task that caused the fault? Any attempt to access the swapped out data will cause a #PF vmexit, since the translation is marked as not present. If there's swapin in progress, you wait for that swapin, otherwise start swapin and wait. Its not as efficient as paravirt because you have to wait for a timer interrupt and the guest scheduler to decide to taskswitch, but OTOH its transparent. -- 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/
Powered by blists - more mailing lists